Using destination identifiers to route output
JES2 allows users to specify where output should go by using destination identifiers. These destination identifiers (destids), together with JES2 route codes, allow installations a method of sending output to different nodes, remote workstations, and special local devices.
- A first-level destination indicating a particular node.
- A second-level destination indicating a remote workstation, special local route code, or userid at that node.
Each node in a JES2 network automatically receives a destination identifier through the NAME= parameter on the NODE initialization statement and the $T NODE command. If you do not specify a destination identifier for the NAME= parameter, JES2 provides a default value. For example, the NODE(1) NAME= parameter defaults to‘N1’where‘N’is a special prefix indicating this is a node.
Installations can specify a symbolic name as a destid through the DESTID initialization statement subscript (jxxxxxxx). The DESTID subscript (jxxxxxxx) specifies the 1- to 8-character name that installations can use to refer to these JES2 destinations.
The DEST= parameter on the DESTID(jxxxxxxx) initialization statement specifies a route code that JES2 uses to send both jobs and SYSOUT from one destination to another. These route codes can be defined as numbers preceded by a prefix that has special meaning. For example, the prefix ‘N’ can indicate that the destination identifier represents a particular node. Other prefixes represent a remote workstation (‘R’, ‘RM’, or ‘RMT’) or a special local route code (‘U’) defined across a number of installations.