z/OS MVS Planning: Operations
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Defining routing codes

z/OS MVS Planning: Operations
SA23-1390-00

Most messages have one or more routing codes. The system uses these codes, decimal numbers from 1 to 128, to determine which console or consoles should receive a message. You can assign routing codes to consoles in a system or sysplex so that the appropriate messages are routed to the right console. In a sysplex, messages are routed from any system to consoles with the matching routing characteristics. To limit the messages a console receives in a sysplex, you can use the MSCOPE keyword on the CONSOLE statement. See Directing messages from other systems to a console in a sysplex.

Use the following keyword on the CONSOLE statement to define routing codes for an MCS or SMCS console:
ROUTCODE
Defines the routing codes in effect for the console.

The default is NONE; ROUTCODE(NONE) means that the system assigns no routing codes to the console. If you specify ALL, the system sends messages with routing codes 1 to 128 to the console. For a description of routing codes, see any volume of z/OS® MVS System Messages

For every routing code (except routing code 11), you should ensure that there is a receiving console. (Operator consoles should not need to receive routing code 11, which indicates programmer information.)

Routing codes do not appear with a message at a console; routing codes 1 through 28 do, however, appear on the hardcopy log. To see the routing codes each console receives in a system or sysplex, operators can use the DISPLAY CONSOLES command.

To route all messages with routing codes 1, 2, 9, and 10 to CONS2, code the following CONSOLE statement in the CONSOLxx member:
CONSOLE DEVNUM(81D) NAME(CONS2) AUTH(MASTER) ROUTCODE(1,2,9,10)

Notice in the example that the console has master authority and that an operator can issue any MVS™ command from it. This console is not required to receive tape, DASD, or teleprocessing messages so the routing codes for those messages are omitted. In a sysplex, this console receives messages with defined routing codes 1, 2, 9, and 10 from all active systems unless MSCOPE limits the scope.

For users of extended MCS consoles on TSO/E, the security or TSO/E administrator can define routing codes 1 through 128. See Controlling extended MCS consoles using RACF.

Operators can use the VARY CN command to change routing codes for active MCS, SMCS, and extended MCS consoles.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014