z/OS JES2 Initialization and Tuning Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Parameter Description for DESTDEF

z/OS JES2 Initialization and Tuning Reference
SA32-0992-00

LOCALNUM=nnnnn|32767
Specifies the maximum special local routing allowed on this member.

Any destination that starts with a ‘U’ followed by a number that is less than or equal to the LOCALNUM parameter specification is converted to a special local route code. JES2 assumes that a destination greater than the LOCALNUM= parameter specification has no special meaning.

Note: If you also specify Udest=USER, this parameter is ignored.

Modification: Single-member warm start.

Ndest=Node|User
Specifies whether JES2 interprets destinations of the form ‘Nnnnn’ and ‘NnnnnRmmmm’ as node ‘nnnn’(Node) or as userid destinations (User).

‘nnnn’ is a number from 1 to the value specified on the NODENUM= parameter of the NJEDEF statement. Specifying Ndest=Node makes the destination ‘Nnnnn’ synonymous with the NAME= parameter of the NODE(xxxxxxxx) initialization statement.

Modification: All-member warm start or JES2 cold start.

NODENAME=REQUIRED|OPTIONAL
NODENAME=REQUIRED indicates that when specifying a userid for a destination, it must be prefixed with a node name. This applies to JES2 commands, JCL, and dynamic allocation (SVC 99) requests. The /*NOTIFY JECL statement accepts just a userid. For example, if DESTDEF NODENAME=REQUIRED and a DEST= userid is coded on a DD statement, that statement will result in a JCL error. In order to route the SYSOUT data set to a userid, you must prefix the userid with a node name. For example, to route output to userid SMITH at node NEWYORK, even if NEWYORK is the local node, you would specify DEST=NEWYORK.SMITH.

NODENAME=OPTIONAL indicates that userids are allowed to be specified without a node specification. In order to route a data set to a userid on the local node, you do not have to specify the node name. For example, to route a data set to userid JONES at the local node, you can just code DEST=JONES.

Note: If you type in a destid for the destination incorrectly and this value conforms to the syntax rules for a userid on the local node, the value will be accepted as a userid.

Modification: All-member warm start or JES2 cold start.

Rdest=Remote|User
Specifies whether JES2 interprets destinations of the form ‘Rmmmm’ and ‘NnnnnRmmmm’ as an RJE remote workstation ‘mmmm’ (Remote) or a userid (User).
Note: Remote destinations of the form R0xxxxxx are interpreted as userids when you specify RDEST=User or when xxxxxx is greater than 32767. If xxxxxx is between 9999 and 32767 and you specify RDEST=Remote, the "0" is truncated. (That is, your remote destinations take the form of R9999 to R32767.)

Modification: All-member warm start or JES2 cold start.

RMdest=Remote|User
Specifies whether JES2 interprets destinations of the form ‘RMmmmm’ as an RJE remote workstation ‘mmmm’ (Remote) or a userid (User).

Modification: All-member warm start or JES2 cold start.

RMTdest=Remote|User
Specifies whether JES2 interprets destinations of the form ‘RMTmmmm’ as remote RJE workstation ‘mmmm’ (Remote) or a userid (User).

Modification: All-member warm start or JES2 cold start.

SHOWUSER=Nolocal|WITHlocal
Specifies whether (WITHlocal) JES2 destinations for the local node which have user routings are displayed with a ‘LOCAL.’ prefix or not (Nolocal).

SHOWUSER=WITHlocal would have output routed to a TSO/E userid of TOM at the local node display as ‘LOCAL.TOM’. For the same example, SHOWUSER=Nolocal would display only ‘TOM’.

When RDEST, NDEST, or UDEST are specified as USER, SHOWUSER=WITHlocal should be specified to avoid possible confusion when user routings conflict with special local (U3), remote workstation (R5), and node (N1) explicit routings.

SHOWUSER affects how destinations are presented to SDSF. This parameter can affect their security profiles. To evaluate the impact of SHOWUSER, see the z/OS SDSF Operation and Customization before specifying the parameter.

Modification: $T DESTDEF operator command.

Udest=Splocal|User
Specifies whether JES2 interprets destinations of the form ‘Unnnn’ as special local (Splocal) device routing ‘nnnn’ or a userid (User). ‘nnnn’ is a number from 1 to the value specified on the DESTDEF LOCALNUM= parameter.
Note:
  1. When Udest=Splocal, DESTDEF LOCALNUM= specifies the maximum number JES2 allows for a special local routing. For example, if UDEST=Splocal and LOCALNUM=5, JES2 would interpret a destination of ‘U3’ as a special local route code, but a destination of ‘U7’ as a userid.
  2. LOCALNUM= specifies the maximum number of special local routing destinations only, it is honored only if you also specify UDEST=Splocal.

Modification: All-member warm start or JES2 cold start.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014