The DEStid subscript (xxxxxxxx) specifies the 1- to 8-character name that users and operators may use to refer to the JES2-defined destinations. The characters in the name must not be a valid explicit destination unless you specify USER on the corresponding DESTDEF initialization statement parameters. That is, the name must not be in a form that looks like a valid explicit destination. Consider the following example definition:

If you code:
            DESTDEF RMTDEST=USER
then:       DEStid(RMT5) DEST=R5
is valid and possibly useful.

RMTDEF=USER defines destinations such as R5 as a userid rather than a remote workstation name of the form RMT5. DEStid(RMT5) points to R5, a route code defined by initialization statement RMT(5), ROUTECDE=5. RMT5 is then interpreted as remote number 5 instead of userid RMT5. All other destinations of the form RMTmmmmm would be considered as a userid, unless there was a DESTid statement of the form DESTid(RMTmmmmm) DEST=Rmmmmm to define RMTmmmmm as a remote workstation.

If you do not specify USER for the DESTDEF initialization statement parameters, IBM suggests that you avoid potential confusion when routing SYSOUT from one destination to another by not specifying the following forms of TSO/E userid names on a JES2 member:

• Nnnnn
• Rmmmm
• RMmmmm
• RMTmmmm
• NnnnnRmmmm
• Unnnn
• ANYLOCAL|LOCAL
• Any DEStid name defined on a DEStid(xxxxxxxx) initialization statement
• Any DEStid name added through a $ADD DEStid(xxxxxxxx) operator command
• Any name specified on the NAME= parameter of the NODE(xxxxxxxx) initialization statement
• Any name specified on the NAME= parameter of the $T NODE(xxxxxxxx) operator command.