For information about using the OUTPUT, STATUS, and CANCEL commands, see . For information about the syntax of the OUTPUT, STATUS, and CANCEL commands, see .

You can write an exit for OUTPUT, STATUS, and CANCEL to tailor the way the commands operate. For example, you can allow users to cancel other users' jobs, process the output from other users' jobs, or restrict users from obtaining the status of other users' jobs. For more information about how you can use the OUTPUT, STATUS, and CANCEL exit, see Possible uses.

The exit is common to all three command processors. If you do not write an exit, the command processors invoke a default exit routine that TSO/E provides. For more information about the default exit, see TSO/E-supplied exit.

If you have RACF® installed, and you are using the RACF resource class JESJOBS and/or JESSPOOL, you may want to review the processing of the IBM® supplied exit, IKJEFF53, with the sample exit in member IKJEFF5X of SYS1.SAMPLIB to see if your installation requires the checking of jobname restrictions. For more information, see TSO/E sample exit.

The exit can receive control many times during the processing of the OUTPUT, STATUS, or CANCEL command. When and how many times the exit gets control depends on the number of job names that the user specifies on the command and the return code the exit sets when it returns control to the command processor.

The exit initially receives control whenever a user issues the OUTPUT or CANCEL command, or the STATUS command with operands. When the exit gets control for the first time, it processes the first job name that the user specified on the command and then returns control to the command processor. If the user specified more than one job name, the exit receives control again for each job name that the user specified.

The exit may get control again with the same job name depending on the return code it sets when it returns control to the command processor. For example, the exit can set return code 8 if it wants the command processor to display a message to the user. The exit sets the return code and returns control to the command processor. The command processor displays the message and then invokes the exit again with the same job name. For more information about the return codes, see Return specifications.

If a user issues the STATUS command with no operands, the exit does not receive control. In this case, the STATUS command processor displays only the status of jobs whose job names consist of the user's user ID and one identifying character. For more information about job names and the JOB statement, see .