If there are multiple destids that can be used for a particular routing, one of the destids should be defined as PRIMARY=YES. Failure to do so causes output destined to that routing to display in explicit format, such as Nn, Rm, NnRm, or Un. SDSF displays the routing in this explicit format and attempts to use this format in commands. This explicit routing does not work as expected if one of the DESTDEF initialization statement options is set to ‘User’.

For example, in Figure 1, all three destids would match a piece of output routed to special local 5 at the local node (node 1). If you specify the $DO J command to list the job output for these destids, the console displays a routing of D=U5. However, with Udest=User (and no other destid), using a destination of ‘U5’ would not result in the same routing as when using a destination of ‘DAVE’. If installations define either DESTID(DAVE) or DESTID(MIKE) as PRIMARY=YES, output routed to special local 5 displays with a destination that can be used to route other output to the same place.

DESTID(DAVE) DEST=N1.U5
DESTID(MIKE) DEST=N1.U5
DESTID(TOM)  DEST=U5
 

For an example of how installations can route jobs and SYSOUT data sets through remote workstation devices, see Routing to RJE devices when Rdest=User.