Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
DESTDEF - Defining How Destinations Are Processed z/OS JES2 Initialization and Tuning Reference SA32-0992-00 |
|
SYSOUT and jobs can be directed to various devices and nodes by JES2 destination processing. How those destinations are interpreted and displayed is controlled by the DESTDEF initialization statement. Some destination prefixes have special meanings to JES2, which can cause difficulties for installations that may want to define userids that use these prefixes. JES2 recognizes a special meaning for destinations of the form ‘Nnnnn’, ‘Rmmmm’, ‘RMmmmm’, ‘RMTmmmm’, ‘Unnnn’, ‘NnnnnRmmmm’ (where ‘nnnn’ and ‘mmmm’ represent numbers from 0 to 32767 unless otherwise defined). Destinations of this form are called explicit destinations. DESTDEF applies to all destinations that JES2 processes except those specified through the DEST= parameter of the DESTID initialization statement. JES2 destinations are composed of two parts:
The Rdest= and Ndest= parameters also apply to JES2 destinations that specify both a node and a remote (NnnnnRmmmm). Destinations displayed for SYSOUT routed to a user routing at the local node can be confused with other destinations. To eliminate confusion, specify the SHOWUSER=WITHlocal parameter so that destinations with user routings are displayed with a ‘LOCAL.’ prefix. For example, at the destination node, ‘,LOCAL.JOHN’ is displayed as the routing for SYSOUT with a user routing of ‘JOHN’. If an installation is using RJE devices and has specified Rdest=USER, at least one DESTID statement must be defined for each RJE device. If more than one destid is defined with any particular RJE routing, at least one of the destids must be defined with PRIMARY=YES. For example, if remote 5 is defined, then ‘DESTID(xxxxxxxx) DEST=N1.R5,PRIMARY=YES’ must also be defined so that JES2 displays the route code ‘N1.R5’ consistently. For more examples of how JES2 resolves the display of multiple destids with the same routing, see z/OS JES2 Initialization and Tuning Guide. |
Copyright IBM Corporation 1990, 2014
|