Parameter Description for DEStid(xxxxxxxx)

(xxxxxxxx)

The 1-8 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 nodename. For example, if NODE(10) is defined with NAME=ALBANY, 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):

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 associated with the device through which the job entered the member.

For example, DEStid(REMOTE5) DEST=R5 defines a second-level destination. Using the DEStids DEStid(NYCAP) DEST=ALBANY and DEStid(NYCAP) DEST=N10, 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 workstation 17.
Unnnn: Specify U followed by a numeric value in the range of 1 through the value specified on the LOCALNUM= parameter of the DESTDEF 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 userids.
userid: Specifies a 1- to 8-character string that is interpreted on the destination node. For example, the string 'TANYA' represents a userid (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.

Note that you can use existing DEStids or node names (those previously defined in the initialization stream) to create new DEStids. However, if you create a DEStid using a symbolic DEST= parameter, and that name is used as:

a subscript in a subsequent DEStid initialization statement or node name in a subsequent NODE initialization statement.

JES2 will consider the first DEStid statement specified to be in error. In general, whenever an initialization statement changes the destination that a previous DEStid statement would resolve to, JES2 marks the DEStid statement as an error.

For example, assume that the following DEStids are defined:

DEStid(ALBANY)   DEST=N10
DEStid(REMOTE5)  DEST=R5
DEStid(BIGAPPLE) DEST=N7
DEStid(TWINTOWR) DEST=TALLBLDG

You can define:

DEStid(CAPITOL) DEST=ALBANY.REMOTE5

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

You can define:

DEStid(NYC)      DEST=BIGAPPLE

The routing associated with 'NYC' is N7.

If you define:

DEStid(TALLBLDG) DEST=R10
        or
NODE(5) NAME=TALLBLDG

JES2 treats the DEStid(TWINTOWR) statement as an error, and issues error message $HASP512. To route TWINTOWR output to R10, place the DEStid(TALLBLDG) statement before the DEStid(TWINTOWR) statement in the initialization stream.

A DEStid pointing to itself does not change the status of the destination:

DEStid(PRT5) DEST=PRT5

This is considered redundant. The status of PRT5 is not changed.

PRIMARY={Yes|No}

Specifies whether (Yes) or not (No) to display this DEStid for job and SYSOUT routing. 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, JES2 selects:

Node name (DEStid with STATUS=NODENAME) if routed to a node.
First DEStid found that specifies PRIMARY=YES.
If only one DEStid is found, that DEStid is used.
If multiple DEStids are found, no DEStid is used (and routing is displayed 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 may 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 the z/OS SDSF Operation and Customization before using this parameter.