$ADD DESTID - Define a symbolic destination

Function

To dynamically define a symbolic name for a JES2 route code.

Parameters

xxxxxxxx

Specifies the 1 to 8 alphanumeric or special ($, #, or @) character symbolic destination name affected by this statement.

DEST=

Specifies a route code JES2 can use to route data.

When specifying only the node (first-level destination):

nodename|Nnnnn

References only the nodal portion (first-level destination) of a JES2 route code.

nodename

Specify a symbolic node name. For example, if NODE(10) is defined as NAME=ALBANY on the DESTID(jxxxxxxx) initialization statement, then an installation can create a DESTID(NYCAP) with DEST=ALBANY.

Nnnnn

Specify N followed by a numeric value (1-32767). For example, DESTID(NYCAP),DEST=N10.

When specifying only the destination at a node (second-level destination):

LOCAL|ANYLOCAL|Rmmmm|RMmmmm|RMTmmmm|Ummmm|userid

References only the destination at a node (second-level destinations).

When these destids are referenced, users must specify either an explicit first-level destination or allow JES2 to assign a default first-level destination. JES2 determines the first-level portion of the destination from one of the following:

• /*ROUTE PRT JES2 control statement
• /*ROUTE PUN JES2 control statement
• The output route code that is associated with the device through which the job entered the system.

For example, DESTID(REMOTE5),DEST=R5 defines a second-level destination. Using the destids DESTID(NYCAP) DEST=ALBANY and DESTID(NYCAP) DEST=N10 as specified on DESTID(jxxxxxxx) initialization statements, JCL can route a data set to R5 at N10 by specifying DEST=NYCAP.REMOTE5.

However, if the JCL only specifies DEST=REMOTE5, the nodal portion of the destination is obtained from the default routing of the job. (A job submitted from N10 without any /*ROUTE JES2 control statements has a default nodal routing of N10, regardless of where in the network it executes.)

Valid destinations:

LOCAL|ANYLOCAL

Data is not associated with any specific routing.

Rmmmm|RMmmmm|RMTmmmm

Specify R, RM, or RMT, followed by a numeric value (0-32767). For example, ‘R17' represents remote work station 17.

Ummmm

Specify U followed by a numeric value in the range of 1 through the value specified on the LOCALNUM= parameter of the DESTDEF initialization statement. For example, ‘U19' represents special local routing 19.

Use the LOCALNUM= parameter on the DESTDEF initialization statement to specify the highest number for a special local route code. JES2 assumes that numbers beyond this range are user IDs.

userid

Specify a 1 to 8 character string that is interpreted on the destination node. For example, the string ‘TANYA' represents a user ID (assuming that there are no destids that define TANYA at the destination node).

When specifying both the node and a destination at that node (first and second level destinations):

NnnnnRmmmm|node.destination

Allows an installation to define the complete JES2 route code (destination at a specified node). JES2 does not use information from the default routing.

NnnnnRmmmm

Specify ‘N' followed by a numeric value (1-32767), then ‘R' followed by a numeric value (0-32767). For example, N5R7 indicates remote 7 at node 5.

node.destination

Specify a first-level destination, followed by a period (.), followed by either a second-level destination or a complete destination.

If ‘destination' is a second-level destination, the routing associated with this destid is the composite of ‘node' and ‘destination'.

For the following examples, assume that node 1 is the local node:

• ‘N1.R3' indicates data routed to remote 3 at the local node.
• ‘N2.R5' indicates data routed to whatever ‘R5' is at node 2.
• ‘N5.BOB' indicates data is routed to whatever ‘BOB' is at node 5.

If ‘destination' is a complete destination, the final routing associated with this destid depends on ‘node'.

For the following examples, assume that node 1 is the local node:

• ‘N2.N2R3' indicates data routed to remote 3 at node 2 because the first-level destination of ‘destination' matches ‘node'.
• ‘N5.N2R3' indicates data routed to 'N2R3' at node 5 because the first-level destination of ‘destination' does not match ‘node' and ‘node' is not the local node. If node 5 has not explicitly defined ‘N2R3', node 5 routes the data to destination ‘R3' at node 2.
• ‘N1.N5R3' results in an error because the first-level destination of ‘destination' does not match ‘node' and ‘node' is the local node.

You can use existing destids to define additional destids. For example, assume that the following destids were defined through the DESTID(jxxxxxxx) initialization statement:

DESTID(ALBANY)  DEST=N10
DESTID(REMOTE5) DEST=R5

You can define on the $ADD DESTID(jxxxxxxx) command:

DESTID(CAPITOL),DEST=ALBANY.REMOTE5

The routing that is associated with ‘CAPITOL' is N10.R5.

PRIMARY={No|Yes}

Specifies whether (YES) or not (NO) to display this destid for job and SYSOUT routing. The PRIMARY option can be used for display purposes and to pass the respective DESTid across system interface calls such as FSI. Use this parameter if multiple destids have the same routing.

When searching for a destid to display for a job's or SYSOUT's routing or when searching for the DESTid that is provided across a subsystem invocation, JES2 selects:

1. Node name (destid with STATUS=NODENAME) if routed to a node.
2. First destid found that specifies PRIMARY=YES.
3. If only one destid is found, that destid is used.
4. If multiple destids are found, no destid is used, and routing is both displayed and provided explicitly.

If USER is specified for either the Ndest=, Udest=, or R|RM|RMTdest= parameters on the DESTDEF initialization statement and multiple destids can match the routing of a job or SYSOUT data set, then at least one of these multiple destids must specify PRIMARY=YES. If not, products such as SDSF might have problems altering the routing of a job or SYSOUT data set to any of these multiply defined destids.

Because PRIMARY=YES can affect SDSF's security procedures, consult SDSF Guide and Reference before using this parameter.

Authority Required

This command requires system 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 control security access authority. For a description of assigning command input authority, see z/OS JES2 Initialization and Tuning Guide.

Processing Considerations

When you dynamically define a JES2 symbolic destination (destid), JES2 carries it across a restart only if you perform a hot start. To permanently define the symbolic destination, add a new DEStid initialization statement before restarting JES2.

Scope

Single member. The values supplied for this command is in effect for this member only.

Depending on your installation's setup, however, you might want this command to be applied to all members of the MAS (to ensure a consistent environment across the MAS). If so, you can use the MVS ROUTE *ALL command to issue this command to all active members (if the JES2 command character is the same on all members). See z/OS MVS System Commands for more information on using the ROUTE *ALL command.

Messages

The $HASP822 message displays the current values of all the parameters that define this DEStid. The STATUS= parameter displays whether the DEStid is associated with a particular node. This parameter cannot be altered by command or initialization statement because it is display-only.