Using the ROUTE command

Your operators can use the ROUTE command to send commands to other systems not specified on CMDSYS without changing the CONSOLE statement values in the CONSOLxx Parmlib member. In the following example, an operator wants to route the CANCEL command to SYB to cancel the job JOBPRINT:

ROUTE syb,CANCEL JOBPRINT

The ROUTE command directs a command to the system you specify, to all systems in a sysplex, to all systems but the system, or to a group of systems in a sysplex. ROUTE with the specified command overrides but does not change the values you code for CMDSYS on the CONSOLE statement. In a sysplex, both systems invoke the command installation exits if they are installed. The exit on the issuing system handles the ROUTE part of the command; the command installation exit on the receiving system processes the command that ROUTE specifies.

For complete syntax information on the ROUTE command, and for the list of commands you should not route to multiple systems, see z/OS MVS System Commands.

The aggregated command response is logged on the system that processes the ROUTE *ALL, ROUTE *OTHER or ROUTE systemgroupname command. This aggregated response is seen by the same system's MPF exits or user exits, and can be automated. The system that processes the ROUTE command is the system where the ROUTE command is issued, unless the ROUTE command was transported using CMDSYS (command association) or CPF (command prefix facility). The responses to the individual command that is imbedded inside of ROUTE *ALL, ROUTE *OTHER or ROUTE systemgroupname are logged on the systems where the command is processed. The individual responses are seen by each target system's MPF exits or user exits, and can be automated. While the aggregated command response is logged with the issuing console's name, each individual response is logged with a system generated console name.

Setting up a System Group Name

You can define groups of systems to MVS™ by placing a list of systems in ECSA, and addressing the list using the name/token services. A ROUTE command that specifies the name of this group will cause a command to be routed to all active systems in the group.

For more information on setting up name/token pairs, see z/OS MVS Programming: Authorized Assembler Services Guide.

The program that creates the list can be set up in PROCLIB, and can be run on each system in a sysplex at IPL using a START command in a COMMNDxx parmlib member. For ease of use, the COMMNDxx parmlib member can be shared by all systems.

To define a new or changed set of named system groups on all systems in the sysplex, use the command ROUTE *ALL,START jobname, where jobname is the name of the procedure that runs the program that creates or deletes the groups.

IBM® provides a SYS1.SAMPLIB member to define named system groups.

For more information, see the comments in SYS1.SAMPLIB member IEEGSYS.