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


Example 1

z/OS JES2 Initialization and Tuning Guide
SA32-0991-00

Table 1. How JES2 resolves destinations -- example 1
 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.TOM DESTID(TOM)

DEST=NODE2.FRED

NODE2 FRED DESTID(FRED)

DEST=BOB

NODE2.BOB
  •  1  The destination specified on a //OUTPUT JCL statement, NODE2.TOM, means: Send this SYSOUT to destination TOM at Node 2.
  •  2  JES2 determines whether Node 1 has a definition for destination TOM. It finds a DESTID(TOM) initialization statement. Comparing the first-level destinations and finding that they match (that is, NODE2 on the OUTPUT JCL statement and the DEST= parameter specifies NODE2), JES2 uses the second-level destination (FRED).
  •  3  JES2 puts the destination of FRED at NODE2 into the NJE header and sends the SYSOUT to Node 2.
  •  4  At Node 2, JES2 takes the incoming destination of FRED and checks to see if it is defined as a destination identifier. There is a DESTID(jxxxxxxx) initialization statement definition for FRED. Its DEST= parameter specifies only a second-level identifier of BOB. Therefore, the first-level identifier is assumed to be Node 2.
  •  5  The resolved destination is BOB at Node 2.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014