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


Routing to RJE devices when Rdest=User

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

An installation with RJE devices that needs to set Rdest=User must ensure that SYSOUT can still be routed to the RJE device. By default, RJE devices are set up so that SYSOUT from jobs submitted from the RJE device is routed back to the RJE workstation. But if a job submitted on remote 5 is routed to another node to execute, when the SYSOUT returns, it will be routed to destination ‘R5’. With Rdest=User, ‘R5’ will not be interpreted as remote 5 but rather as user routing ‘R5’. The remote printer will be unable to print the SYSOUT. To prevent this problem, create a DESTID(Rm) DEST=NxRm where ‘x’ is the local node number (NJEDEF OWNNODE=) and ‘m’ is the remote number.

When an RJE device signs on, JES2 attempts to interpret the workstation name sent from the remote while honoring the value specified on the DESTDEF initialization statement. First, JES2 searches the destids for a match to determine the actual remote number. If there is no match, JES2 ignores the values set on DESTDEF (assuming that Ndest=, R|RM|RMTdest=, and Udest= have all been set to USER) while interpreting the workstation name. This would allow a remote to sign on using RMT5, even if RMTdest=USER and there is no DESTID(jxxxxxxx) initialization statement with a subscript of RMT5. If a remote tries to sign on as RMT5 and there is a DESTID(jxxxxxxx) initialization statement with a subscript of ‘RMT5’ with a DEST= that does not specify a remote on the local node, then the sign on attempt will fail.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014