Routing codes appear to the right of the message identifiers in the Routing Code column. The column can also contain the following special characters or notes:

*

The message will be routed back to the consoles that initiated the associated requests.

/

The message will be routed to different locations according to the task issuing it. For example, */2/3 means the message is routed back to the console that initiated the request, to the console with master authority, or to the tape pool.

#

The message will be routed in one of the following ways:

• According to the routing indicators specified by the operator
• According to the default routing instructions previously specified by the operator
• Back to the console that initiated the associated request

—

The message has no routing code.

Note 2

The message is issued by a WTO or WTOR macro, but has no routing or descriptor codes (old format WTO or WTOR macro).

Note 3

The message has a routing code of 1, which sends it to the console with master authority, and is also routed to the console that the message describes.

Note 4

The message is sent to all active consoles; this is a broadcast message.

Note 5

The message has a routing code of 2, which sends it to the console with master authority, and is also routed to the consoles that are assuming the duties of the failing console. (This message indicates that console switching has occurred.)

Note 6

The message is routed only to non-printer consoles. This message is not issued by a WTO or WTOR macro.

Note 7

The message is routed to consoles where one or more of the following are active:

• MONITOR JOBNAMES
• MONITOR SESSIONS
• MONITOR STATUS

Note 8

The message is also routed to the MSS space manager's console specified by an alternate console routing code on the MSFMSG parameter in the MVIKEY00 parmlib member.

Note 9

The message is issued during the nucleus initialization program (NIP) processing.

Note 10

The message is issued by the WTL macro.

Note 11

The message is routed to a SYSPRINT data set by data management.

Note 12

The message is issued by a WTO or WTOR macro with SYNCH=YES. See z/OS MVS Initialization and Tuning Reference for more information.

Note 13

The message is routed only to receivers of the hardcopy message set.

Note 14

The message is routed back to the console that initiated the request and to all associated consoles.

Note 16

The message is routed to the IPCS print file IPCSPRNT.

Note 17

The message is issued by JES3. A JES3 destination class is specified either by the initialization stream or by operator commands.

Note 18

The message is sent in response to a command to the console where the command was entered.

Note 19

The message is written to a data set. If routing and descriptor codes are also included for the message, the message might also be displayed according to the specified routing and descriptor codes. (The descriptor code does not apply to writing the message to the data set.)

Note 20

JES3 does not issue the message. JES3 sends the message to another subsystem for processing.

Note 21

This message is a trailer attached to multiple messages previously issued. It has the same routing and descriptor codes as the first line of the conglomerate.

Note 22

This message is routed to the transaction program (TP) message log.

Note 23

This message is issued by the device controller. The routing code will vary according to the device controller's task.

Note 24

This message is routed to the assembly listing.

Note 25

When this message is issued during IPL, the routing codes are 2 and 10 and the descriptor code is 12. When it is issued after IPL, it has no routing code and the descriptor code is 5.

Note 26

When this message is issued during NIP processing, the descriptor code is 12. When it is issued after NIP processing, the descriptor code is 4.

Note 27

The indicated route codes are used only if this message is issued in response to a reply of CKPTDEF during a JES2 checkpoint reconfiguration. This message might be issued to a specific console ID rather than directed by route code. For further information concerning the routing of JES2 messages issued during a reconfiguration, see z/OS JES2 Initialization and Tuning Guide.

Note 28

These routing and descriptor codes apply only when SMS issues the message. If SMS returns the message to its caller and the caller issues the message, the codes do not apply.

Note 29

This message is written to the JES3OUT data set.

Note 30

This message is issued by JES3. The message is written to the *MODIFY CONFIG (*F MODIFY) log, the issuer of the *F CONFIG command, or both.