$G R, XEQ

Function

To route a job, located at another node, to yet another node for execution.

Syntax


>>-$G--R--+---------+--,XEQ--,'jobname'--(--,J--|--JOB--n--)---->
          +-N--nnnn-+                                          
          +-name----+                                          
          '-destid--'                                          

>--,O=--+-LOCAL--|--ANYLOCAL---+-------------------------------->
        +-N--nnnn--|--nodename-+   
        '-destid---------------'   

>--,D=--+-LOCAL--|--ANYLOCAL--+--------------------------------><
        +-N--nnnn-------------+   
        +-destid--------------+   
        +-nodename------------+   
        +-N--nnnn--.--R--mmmm-+   
        +-U--mmmm-------------+   
        +-node--.--remote-----+   
        +-node--.--destid-----+   
        '-remote--------------'

Parameters

D=

The node to which the job is routed.

If you specify Nnnnn, Nnnnn is converted to an 8-byte EBCDIC node name that is placed in the global route command record for the receiving node.

If you specify an installation-defined node name, the name is right-padded with blanks and then placed in the global route command record for the receiving node. Symbolic node names are validated and converted to internal route codes at the receiving node, not the node at which the $G R command is entered. The value for all routing numbers can range from 1 to 32767. The valid specifications:

LOCAL|ANYLOCAL

Indicates that jobs are to be run at the local node.

destid

Indicates that jobs are to be run at the specified node(s). You can specify this location by an alias for the name of a node. If destid is specified alone, it refers to both the node and the remote.

Nnnnn|nodename

Indicates that jobs are to be run at the specified node(s). You can specify a node using the decimal node identifier or an EBCDIC nodename.

NnnnnRmmmm|node.remote

Indicates routing to the remote Rmmmm at the node Nnnnn. Rmmmm can also be specified as RMmmmm or RMTmmmm.

Ummmm

Indicates special local routing.

node.destid

Indicates a destination at the specified node. The destid refers to both the node and the remote. The node specified in the destid must be the same as the node portion of the route code. If the number of the remote is reassigned, you can use the destid to send to this node.

remote

Indicates routing to a remote. Remote can be specified in any of the following ways:

LOCAL|ANYLOCAL: Indicates that jobs are to be run at the local node.
Rmmmm: Indicates routing to the specified remote. Rmmmm can also be specified as RMmmmm or RMTmmmm. The value specified for mmmm can range from 1 to 32767.
destid: Indicates routing to a destid referring to a remote.

For more information about specifying userids as remotes, see Route codes.

J|JOBn

The job ID (Job n) assigned to the job by its originating node.

‘jobname'

The name of the job that is routed for execution. The name must appear as coded on the JOB statement and must be enclosed in apostrophes. If the job did not originate at the sending node (or have default print and/or punch output for the sending node), the destination node must have the sending node flagged as having network authority.

Nnnnn|name|destid

The destination node to which JES2 sends this command. You can specify the location by an alias for the name of a node. The destination node must have the sending node flagged as having job authority.

O=

The node on which the job originated. You must specify this parameter if the originating node is not the node at which the $G R command is entered. If you fail to identify the originating node, JES2 issues the $HASP693 message indicating that the job was not found. The valid specifications:

LOCAL|ANYLOCAL: Indicates that jobs are to be run at the local node.
Nnnnn|nodename: Indicates that jobs are to be run at the specified node(s). You can specify a node using a decimal node identifier from 1 to 32767 EBCDIC nodename.
destid: Indicates that jobs are to be run at the specified node(s). You can specify this location by an alias for the name of a node.

Note: This parameter requires that the destination node has the sending node flagged as having network authority.

XEQ

The job is routed for execution.

Authority Required

This command requires job 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 update 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

The receiving node rejects the $G R command if the specified job is currently being received on a reader, is currently being received or transmitted on an NJE or RJE line, has already executed, or is currently in execution.
If you do not know the job ID of the job with this jobname, use the $G D command to display the job IDs of all jobs with this jobname at a specific node.
The $T NODE,Auth= command sets the command authority for a specified node.

Scope

Network-wide. This command only needs to be issued from a single member; the command has an effect across the entire MAS.

Messages

The $HASP000 message indicates the command was accepted.

Example

 1   $g r n3,xeq,'jobc',d=n4

  $HASP000 OK

JES2 sends a global route command record through the network to node 3. Node 3 routes the job named JOBC to node 4 for execution.