Command routing enables an administrator to send commands for processing to one or more servers at the same time. The output is collected and displayed at the server that issued the routed commands.
If you set up your servers as described in Setting up communications for command routing, you can route Tivoli® Storage Manager administrative commands to one or more servers. A system administrator can configure and monitor many different servers from a central server by using command routing.
You can route commands to one server, multiple servers, servers that are defined to a named group, or a combination of these servers. A routed command cannot be further routed to other servers; only one level of routing is allowed.
Each server that you identify as the target of a routed command must first be defined with the DEFINE SERVER command. If a server is not defined, that server is skipped and the command routing proceeds to the next server in the route list.
Tivoli Storage Manager does not run a routed command on the server from which you issue the command unless you also specify that server. To be able to specify the server on a routed command, you must define the server just as you did any other server.
Commands cannot be routed from the SERVER_CONSOLE ID.
Routed commands run independently on each server to which you send them. The success or failure of the command on one server does not affect the outcome on any of the other servers to which the command was sent.
For more information on command routing and return codes that are generated by command processing, refer to Administrator's Reference.