Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Routing output to devices at another node z/OS JES2 Initialization and Tuning Guide SA32-0991-00 |
|
There are two ways to route output to devices at another node:
To illustrate this process, see the initialization parameters defined in Figure 1. Figure 1. Sample JES2 DESTID(jxxxxxxx) Initialization Values on Three Nodes
Output at WASH1 routed to destination FIRST is sent to Remote 1 at BOST1. The destination is resolved at BOST1. Because a BOST1 remote number is defined in the initialization statement shown for WASH1, the destid FIRST need not be defined at BOST1. Output at WASH1 routed to destination SECOND is sent to BOST1 and the output sent to remote 2. The destination SECOND must be defined on both nodes. WASH1 does not need to know which remote on BOST1 represents SECOND. If SECOND was not defined at BOST1, JES2 would send output to userid SECOND. If there were no such user on the system, the output would remain on the userid queue at BOST1 until an operator changed its destination or the data set was purged. Output at WASH1 routed to destination THIRD is sent to BOST1, where it is rerouted to THIRD at DET1. Finally, DET1 receives the output and routes the job to remote workstation 1 at DET1. If no destid had been defined as DESTID(THIRD), JES2 would have routed the data to userid ‘THIRD’ at DET1. |
Copyright IBM Corporation 1990, 2014
|