JES2 job output commands

JES2 commands allow you to display and control job output. For example, you can display the amount of output for a job or jobs in either the held or released output classes. For information about JES2 commands you can issue to display job output, see “Displaying Job Information” .

You can issue commands to release or cancel held output data sets. You can also cancel all or selected ready but inactive output data sets on a class and/or routing basis.

Releasing or canceling output groups

Use the $O command to release or cancel held output groups. You can control the held output of a single job, a range of jobs, specific output classes, or all output classes. Specify CANCEL to cancel held output groups; use the R= parameter to release held output groups to a specified destination.

The DAYS= and HOURS= parameters allow you to control held output according to the day and hour it was created. For example, issuing $O J1-20,DAYS>5 causes JES2 to release all held output groups that are at least 5 days old for batch jobs 1 through 20.

Canceling output data sets

To cancel a job's output, issue either the $C O Job command or the $PO Job command. You can cancel a job's output by output class (using the Q= filter), route code (using the R= filter) or output group (the OUTGRP= filter). The $HASP686 message displays information about each output group cancelled. The $HASP250 message is issued when all output for a job is deleted and the job is purged.

To speed throughput or ease the amount of work queued for a device, you can route both normal and specially routed output for a job or jobs to an alternate location. Specially routed output is independent of the normal job output, which is unaffected.

Producing a separator page

The $T PRINTDEF command allows you to specify whether JES2 produces the print separator page or the format of the print separator page through the SEPPAGE= parameter. You can suppress the separator page, print only the detail box information, print one full separator page, or print two full separator pages. For more information about this function, see “Control a Printer” .

Rerouting job output

The $R command allows you to reroute to another destination both ready and held output for batch jobs, started tasks, or TSO/E users. This command allows an operator to change the specified destination on a piece of output as often as necessary. You can issue the $R command only for output groups. You can display the destination of output groups by entering the $DO J command (destination appears on the ROUTECDE= parameter in the display).

In addition, you can use the $R command to change the command authority routing on jobs, or allow them to remain the same. Command authority allows an operator to control output disposition and display jobs.

The command authority of a job can be specified from two distinct places:

The route code of the input device that brought the job into the system.
The remote or node specified on either the JES2 /*ROUTE PRT or the /*ROUTE PUN JES2 control statement.

You can display the command authority of a job by entering the $D Jn,LONG command; the $HASP890 message displays the CMDAUTH= parameter. If you do not code ALL,Q= or OUTDISP= with the J= or the R= parameter (in conjunction with the D= parameter) on the $R command, both the routing for the output of the job and the command authority of the job are transferred.

For the sending node to retain the authority to change output characteristics while routing all output from one remote to another, specify the ALL,Q= parameters or OUTDisp= parameter to reroute the specified JOE (job output elements) to an alternate location. The command authority for those jobs remains unchanged. If you enter

$R all,r=j5,d=r7,outd=(w,h,k,l),

JES2 routes all eligible print and punch output from remote 5 to remote 7, but retains command authority at remote 5.

If you do not specify the OUTDisp parameter, all output with a disposition of WRITE, HOLD, KEEP, or LEAVE will be rerouted.

If output is not routed when you issue the $R command, wait a few minutes and retry the command. If your output is still not routed, contact your system programmer.