|
|
|
There is no limit on the number of distinct destination names JES3 can support. JES3 also allows destination names to be specified either directly or generically.
Unlike JES2, JES3 provides no default destinations. Destinations are defined using the RJPWS macro. When RJPWS is used, the CONSOLE statement is also required.
Destinations are created using the N=name and G=group parameters of the RJWPS statement. The N parameter must be five characters long. The G parameter can be from one to eight characters long, and defaults to the value of the name parameter.
If the group name is five or more characters, it is considered to define a generic destination. We recommend using generic destinations because this approach is likely to significantly decrease the number of times that the JES3 INISH deck must be updated.
For the exact format of the JES3 definitions (because parameters that are not discussed here may be required for your particular release of JES3), see the JES3 Systems Program Library Initialization and Tuning manual.
Note: CA XCOM Data Transport does not support RJE remote numbers or NJE node numbers as DESTIDs for either JES2 or JES3.
| Copyright © 2012 CA. All rights reserved. |
|