Example 2

Table 1. How JES2 resolves destinations -- example 2
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.JACK	DESTID(JACK) DEST=NODE3.R5	NODE2 JACK	DESTID(JACK) DEST=NODE3.R5	NODE3.R5

1 The destination specified on an SDSF over-type field, NODE.JACK, means: Send this SYSOUT data set to destination JACK at Node 2.
2 JES2 determines whether Node 1 has a definition for destination JACK. It finds a DESTID(JACK) initialization statement definition. Comparing the first-level identifiers, JES2 finds no match (that is, NODE2 specified on the SDSF over-type and the DEST= parameter specifies NODE3). JES2 ignores the DEST= specification.
3 JES2 puts the destination of JACK at NODE2 into the NJE header and sends the SYSOUT to Node 2.
4 At Node 2, JES2 takes the incoming destination of JACK and determines if it is defined as a destination identifier. There is a DESTID(JACK) initialization statement. Its DEST= parameter specifies NODE3.R5. Because this is the specification defined at Node 2 (the destination node), JES2 uses it.
5 The resolved destination is R5 (remote workstation 5) at Node 3.