z/OS JES2 Initialization and Tuning Guide
SA32-0991-00
Table 1. How JES2 resolves
destinations -- example 4
1
Destination
Specified at
NODE 1
2
DESTID
Specified at
NODE 1
3
Destination Sent
(NJE Header)
4
DESTID
Specified
at NODE 2
5
Destination
Resolved
NODE2.SCOTT
DESTID(SCOTT)
DEST=R5
NODE2 R5
N/A
NODE2.R5
1 The destination specified on a $TO J5,ALL,D=
JES2 command, NODE2.SCOTT, means: Send this SYSOUT data set to destination
SCOTT at Node 2.
2 JES2 determines whether Node 1 has a definition
for destination SCOTT. It finds a DESTID(SCOTT) initialization statement
definition. JES2 cannot compare first-level destinations because the
DEST= parameter provides only a symbolic second-level destination.
Therefore, JES2 uses the first-level destination from the $T O command
and combines it with the second-level destination on the DEST= parameter
from the DESTID(jxxxxxxx) initialization statement.
3 JES2 puts the destination of R5 at NODE2 into
the NJE header and sends the SYSOUT to Node 2.
4 At Node 2, because the incoming destination
is an explicit destination (referring to a specific route code) as
opposed to a symbolic destination, JES2 uses it.
5 The resolved destination is R5 (remote workstation
5) at Node 2.