Communication from JCL to system (non-APPC)

The statements described in this topic are not supported in an APPC scheduling environment.

Use the following to communicate from your JCL to the system:

In a JES2 system,
- The JCL COMMAND statement to enter any MVS™ and JES commands that can be issued from the operator's console
- The JCL command statement to enter system operator commands
- The JES2 /*$command statement to enter JES2 commands.
In a JES3 system,
- The JCL COMMAND statement to enter any MVS and JES commands that can be issued from the operator's console
- The JCL command statement to enter system operator commands
- The JES3 //**command statement to enter JES3 commands.

The system executes any in-stream command as soon as it is read. Therefore, the command will not be synchronized with the execution of any job or step.

Examples:

   In a JES2 system:
        /*$SI3-5

        //    COMMAND  'CANCEL MYJOB,DUMP'

   In a JES3 system:
        //**START