Routing code meaning
Routing codes appear within the associated message. The routing
code field can contain the following numeric values, special characters,
or notes:
- Code
- Meaning
- 1
- Operator Action The message indicates a change in the system status. It demands action by a primary operator.
- 2
- Operator Information The message indicates a change in system status. It does not demand action; rather, it alerts a primary operator to a condition that might require action. This routing code is used for any message that indicates job status when the status is not requested specifically by an operator inquiry. It is also used to route processor and problem program messages to the system operator.
- 3
- Tape Pool The message gives information about tape devices, such as the status of a tape unit or reel, the disposition of a tape reel, or a request to mount a tape.
- 4
- Direct Access Pool The message gives information about direct access storage devices (DASD), such as the status of a direct access unit or volume, the disposition of a volume, or a request to mount a volume.
- 5
- Tape Library The message gives tape library information, such as a request by volume serial numbers for tapes for system or problem program use.
- 6
- Disk Library The message gives disk library information, such as a request by volume serial numbers for volumes for system or problem program use.
- 7
- Unit Record Pool The message gives information about unit record equipment, such as a request to mount a printer train.
- 8
- Teleprocessing Control The message gives the status or disposition of teleprocessing equipment, such as a message that describes line errors.
- 9
- System Security The message gives information about security checking, such as a request for a password.
- 10
- System/Error Maintenance The message gives problem information for the system programmer, such as a system error, an uncorrectable I/O error, or information about system maintenance.
- 11
- Programmer Information This is commonly referred to as write to programmer (WTP). The message is intended for the problem programmer. This routing code is used when the program issuing the message cannot route the message to the programmer through a system output (SYSOUT) data set. The message appears in the JESYSMSG data set.
- 12
- Emulation The message gives information about emulation. (These message identifiers are not included in this publication.)
- 13-20
- For customer use only.
- 21-28
- For subsystem use only.
- 29
- Disaster recovery.
- 30-40
- For IBM® use only.
- 41
- The message gives information about JES3 job status.
- 42
- The message gives general information about JES2 or JES3.
- 43-64
- For JES use only.
- 65-96
- Messages associated with particular processors.
- 97-128
- Messages associated with particular devices.
- *
- 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 a primary operator, 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.
- N/A
- A routing code is not applicable for the message.
- 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 the message to a primary operator, and the message is also routed to the console that it 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 the message to a primary operator.
- 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 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 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 and/or the issuer of the *F CONFIG command.
- Note 31
- The routing and descriptor codes for this message are dependent on the setting of indicator bits within the S99EOPTS field in the SVC 99 Request Block Extension (S99RBX). See the z/OS MVS Programming: Authorized Assembler Services Guide, Processing Messages and Reason Codes from Dynamic Allocation for additional information.
- Note 32
- Routing code 2 is only applicable if message IYP050D was issued.
- Note 33
- Routing code 2 is only applicable if message IZP050D was issued.
- Note 34
- This message is only displayed on the SMCS Console Selection screen, and is not issued via WTO support.
- Note 35
- By default, IBM Health Checker for z/OS® messages does not use routing codes, but the installation can override the default to use routing codes using either the MODIFY hzsproc command or in the HZSPRMxx parmlib member. See IBM Health Checker for z/OS User's Guide for more information.
- Note 36
- This message is written to the JESYSMSG data set.