Controlling jobs at another node

JES2 allows you to route jobs for execution at other nodes using the $R XEQ,D= command. You can display information about these jobs using the $G D command and control their processing using the commands described in this .

Note: You may issue the $G D command or any of the commands listed in the following description for any job at any node. Yours does not have to be the originating node.

The following considerations apply to all $G commands issued to display information about, or control, jobs at another node:

The destination node must have your node flagged as having job authority. If the job did not originate at your node or have default print/punch output for your node, the destination node must have your node flagged as having network authority. (The destination node can issue the $T NODE(nnnn),AUTH= command to assign your node command authority.)
If more than one job has the specified job name, you'll need to specify the job ID. If you do not know the job ID, issue the $G D command to display the IDs of all of the jobs with this name at a specific node.

You can control jobs at another node in the following ways:

Issue the $G H command to hold a job at another node.
Issue the $G A command to release a job at another node.
Issue the $G C command to cancel a job at another node:
- The $G C command allows you to terminate the scheduling or execution of a batch job. You can also issue this command to cancel STCs or TSUs after they have completed execution.
- To diagnose a problem, you may specify the D parameter to request a storage dump upon cancellation. Alternatively, you may cancel the job output by specifying the P parameter. You must specify the P parameter to cancel a job that is already in the output processing phase.
Issue the $G R command to request another node to route a job to yet another node for execution. By issuing the $G R command, you are, in effect, issuing a $R XEQ,D= command for another node.
- You can also issue the $G R command to route normal output for a job at another node to an alternate location. You are, in effect, issuing a $R ,D= command for another node.