JCL command statement

Purpose: Use the JCL command statement to enter an MVS™ operator command through the input stream on a JES2 or JES3 system.

However, the COMMAND statement is the preferred way within the job control language to specify MVS and JES commands.

Note: To enter a JES2 command, use the JES2 command statement. To enter a JES3 command, use the JES3 command statement.Note also that the JCL Converter does not identify every input command that is not valid, but relies also on MVS command processing: see the following Example 3.

If an in-stream command is to be executed (see the explanation in the following section "Defaults" ), the system usually executes it as soon as it is read. Therefore, the command will not be synchronized with the execution of any job or step in the input stream. To synchronize a command with the job processing, tell the operator the commands you want entered and when they should be issued, and let the operator enter them from the console.

The system processes each command according to installation options for both the input device from which the job was read, and the job class.

Considerations for an APPC Scheduling Environment: The command statement has no function in an APPC scheduling environment. If you code the command statement, the system will check it for syntax and ignore it.

References: For more information on MVS commands and for descriptions of their parameters, see z/OS MVS System Commands.