Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
$G D - Display job information for a job at another node z/OS JES2 Commands SA32-0990-00 |
|
FunctionTo display job information for a job at another node. Syntax>>-$G--D--+-N--nnnn-+--,'jobname'--+-,J--|--JOB--n-+------------> +-name----+ +-,S--|--STC--n-+ '-destid--' '-,T--|--TSU--n-' >--,O=--+-LOCAL--|--ANYLOCAL-+--------------------------------->< +-nodename-----------+ '-destid-------------' Parameters
Authority RequiredThis command requires display authority. The description of the $T RDRnn command explains how to ensure that the authority of the appropriate MVS™ system command group is assigned. This command requires read security access authority. For a description of assigning command input authority, see z/OS JES2 Initialization and Tuning Guide, SA32-0991. For the authority required at the destination node, see Displaying and controlling jobs at other nodes. Processing Considerations
ScopeNetwork-wide. This command only needs to be issued from a single member; the command has an effect across the entire MAS. MessagesThe $HASP000 command indicates that the command has been accepted. The message id of the message displaying the status of the job is dependent on the operating system on the node to which the command was issued. For example, a command issued to a JES2 system may display $HASP890, depending on the level of JES2 on the target system. Examples
JES2 sends a global display command record through the
network to node 2. Node 2 returns to the sending node a display of
job information for all jobs named MYJOB on node 2 that are owned
by the sending node (that is, jobs originating at the sending node
or jobs for which the sending node has network authority at node 2).
Because a specific destination node was not specified, JES2 sends a global display command to every reachable node in the network. Each node responds with either a JOB NOT FOUND response or a display of job information for the job named JOBA that originated at the node named DENVER and had an original job number of 17. (Note that, unless the node entering the command is named DENVER, it must have network authority at the node where the job is currently located.) |
Copyright IBM Corporation 1990, 2014
|