Preparing installations to alter destination processing

Before changing how JES2 interprets destinations, installations should review their JCL and automated commands to ensure that they are notusing the prefixes being affected. For example, before changing Ndest to ‘USER’, ensure that there are no JCL references to N123, N0123, N000123.

Destids can be used to support cases where it is not practical to change JCL statements. However, the subscript on the DESTID(jxxxxxxx) initialization statement must match the DEST= parameter specification on the JCL statement exactly. For example, an installation with the following initialization statement can route data to node 1 using OUTPUT JCL statements that specify DEST=N1.

DESTID(N0000001)

To route the data to Node 2, you must specify DESTDEF Ndest=User on a warm start, add the following DESTID,

DESTID(N1) DEST=N2

and add DEST=N2 to the DESTID(N0000001) initialization statement. If you change any DESTDEF initialization statement parameters to specify User, the processing of explicit destids can be altered. Use the DESTDEF initialization statement to alter destination processing only after carefully preparing the initialization stream definitions and JCL statements carefully. For more information on how to prepare an installation for such a change, see both Specifying TSO/E userIDs on a JES2 system and Altering destination processing through DESTDEF.

An installation can specify whether JES2 displays a destid or an explicit route code for jobs and SYSOUT through the PRIMARY= parameter on both the DESTID(jxxxxxxx) initialization statement and the $ADD DESTID operator command. For example, by specifying ‘DESTID(NYWK),DEST=U2,PRIMARY=YES’, an installation ensures that the destid ‘NYWK’ is displayed instead of the explicit special local route code of ‘U2’.

Use of PRIMARY=YES can aid both operators and system programmers in tracking jobs and SYSOUT across a network, as illustrated in Figure 1. An installation specifies that destids beginning with the ‘RMT’ prefix should be processed as userids (RMTdest=USER), then creates the following destids in its initialization stream.

Figure 1. DESTID(jxxxxxxx) and DESTDEF Initialization Stream Definitions

DESTDEF      RMTDEST=User,SHOWUSER=WITHlocal
DESTID(RMT6) DEST=R6,PRIMARY=YES
DESTID(DR1)  DEST=R1,PRIMARY=NO
DESTID(DR2A) DEST=R2,PRIMARY=NO
DESTID(DR2B) DEST=R2,PRIMARY=NO
DESTID(DR3A) DEST=R3,PRIMARY=YES
DESTID(DR3B) DEST=R3,PRIMARY=NO
DESTID(DR4A) DEST=R4,PRIMARY=YES
DESTID(DR4B) DEST=R4,PRIMARY=YES
DESTID(DR5)  DEST=N1.R2,PRIMARY=NO
        :
        :
NJEDEF       OWNNODE=1

In Table 1, you can see how these destinations are resolved.

Table 1. How JES2 resolves destinations from DESTDEF initialization statements
Destid Routing	Console Display	Reason
DR1	DR1	Displays the destid because no other destids specify this routing.
DR2A	R2	Displays explicit destination because neither destid with this routing specified PRIMARY=YES.
DR3A	DR3A	Displays the destid because PRIMARY=YES.
DR3B	DR3A	Displays alternate destid because DR3A shows PRIMARY=YES.
DR4A	DR4A	Displays the destid because PRIMARY=YES.
DR4B	DR4A	Displays alternate destid because both show PRIMARY=YES. and DR4A is first alphabetically. in the initialization stream.
DR5	R2	Displays explicit destination because PRIMARY=NO.
R5	R5	Displays explicit remote workstation routing.
RM5	R5	Displays explicit remote workstation routing.
RMT5	LOCAL.RMT5	Displays user destination because RMTdest=User.
RMT6	RMT6	Displays destid because PRIMARY=YES. and RMTdest=User.

The PRIMARY= parameter on the DESTID(jxxxxxxx) initialization statement allows an installation to specify how JES2 resolves multiple destid displays. As Table 1 shows, specifying PRIMARY=YES allows an installation to specify which destid appears in displays when two statements specify the same DEST= routing. For example, destid ‘DR3B’ will never display on the console because destid ‘DR3A’ is routed to remote workstation 3 too, and it specifies PRIMARY=YES.

Because the PRIMARY= parameter defaults to NO, you must remember to specify which destid takes precedence when defining two or more with the same DEST= route code.

By specifying SHOWUSER=WITHlocal on the DESTDEF initialization statement, this installation provides a level of clarification in the RMT5 destid routing that displays the first-level identifier ‘LOCAL’ in front of the userid ‘RMT5.’