Changing MVS message routing *MODIFY,M

Function

Use the *MODIFY,M command to change the routing of MVS™ messages associated with a specific processor in your JES3 installation. This command can change the message routing to more than one console. The *MODIFY,M command changes the MVS message routing table that is created from the MSGROUTE initialization statement.

Note:

All parameters on the *MODIFY,M command are positional. You must include a comma if you omit an optional parameter.
Use of this command affects the JES3 Destination class in the JES3DLOG if the added destination class meets one of the following conditions:
1. Results in the message having a higher routing code when the new routing code is greater than the current routing code, and the new code is less than or equal to 16.
2. Results in the message having a lower routing code when the new routing code is less than the current routing code and the current routing code is greater than or equal to 17.

Syntax


>>-+-*MODIFY-+--,--M--,--main--+-,--code-----------+------------>
   '-*F------'                 |       .-,----.    |   
                               |       V      |    |   
                               '-,--(----code-+--)-'   

>--,--+-----+--,--+------+--+------+---------------------------><
      '-con-'     '-dest-'  '-,--J-'

Parameters

These keywords are positional and must be specified in order. If a keyword is not being used, you must still specify the comma.

main: Identifies the main that contains the message routing table that you want to modify.
code or (code[,code]...): Identifies the MVS routing code(s) (1 to 128). If you specify multiple routing codes, you must enclose them in parentheses.
con: Specifies the name of the console that is to receive messages associated with the MCS routing code you specify on the code parameter.
dest: Specifies the console destination class to which messages of the designated MVS routing code are to be mapped. (See Table 1 for the names of the console destination classes.)
J: Specifies that the routing specified on the MSGROUTE statement should replace the message's original routing information.

Examples

Map all messages that are assigned MVS routing code 8 to JES3 destination class TP, and have the messages displayed only on the global JES3/MCS console (messages originate from main SY2):

*MODIFY,M,SY2,8,,TP,J

Send MVS messages with routing code 14 that originate on main SY1 only to the console receiving the hardcopy destination.

*F,M,SY1,14,,,J