ROUTING Command: Route Proxy Requests

The ROUTING command instructs the connected z/OS Agent where to process requests. The ROUTING command also displays the current routing status.

Type: CA WA High Availability ESP Edition or CA WA Service Governor ESP Edition command

This command has the following format:

ROUTING [LOCAL|MASTER|STATUS|HELP]

LOCAL: Instructs the connected z/OS Agent to process requests itself.
MASTER: Instructs the connected z/OS Agent to route requests to the master.
STATUS: Displays the current ROUTING status of the client. STATUS is the default.
HELP: Displays the ROUTING command options.

Note:

When a TSO session is connected to the master, the ROUTING command is not meaningful, as the LOCAL and MASTER options mean the same thing.
When a TSO session is connected to a proxy, entering ROUTING LOCAL instructs the proxy to process subsystem requests (for example, z/OS Agent commands) itself. Entering ROUTING MASTER instructs the proxy to route subsystem requests to the master.
Routing is local by default.
When a TSO session is connected to the local proxy, subsystem requests can only be forwarded to the master if an active XCF ROUTING connection exists between the local proxy and the master.

Example: Route Subsystem Requests to the Master

This example shows how to instruct the connected subsystem to route subsystem requests to the master.

ROUTING MASTER

Example: Process Subsystem Requests

This example shows how to instruct the connected subsystem to process subsystem requests itself.

ROUTING LOCAL