msgIEE707I when issuing jes commands from Jes Automatic commands

[Itschak Mugzach]

I entered some Jes2 commands to run under the timed commands feature
mentioned in the subject. The command(s) are quit complex and include
search of appropriate jobs to act on. When a command like $T JC,/JN
=xxx*,QUEUE=XEQ,/C=K,C=P entered from Jes automatic commands, I get an
IEE707I msg, which indicates that the command didn't run. Same command,
when entered from the console (aka SDSF), works fine.

Any idea why, and how to force Jes to properly execute those commands?

TX,
ITschak

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@listserv.ua.edu with the message: INFO IBM-MAIN

[Lizette Koehler]

So I did a couple of internet searches and came up with this
http://bit.listserv.ibm-main.narkive.com/weG3Xf5c/getting-iee707i-message-with-start-command

Before processing command cm yyy, MVS presented the command to all subsystems that monitor commands. Based on the response returned, MVS did not process the command for one of the following reasons:

One or more subsystems intentionally failed the command with a return code of 8.
One or more subsystems issued a return code that was not valid.
The command installation exit issued a return code of 8.

If it was a subsystem, then you may need to open a PMR and ask Level 2 for the SSI component to assist you in setting a SLIP IF in the subsystem broadcast router to trace subsystem function calls for the command function code, or to dump when a function routine for the command function code returns a fail code.

You can try to do the D SSI and see if it is active?

Lizette