CTORMT

Solutions in SolveWare subject CTORMT are designed to facilitate cross system automation communications. With the rules in this SolveWare solution, Control-O rules can now issue commands to remote systems. Optionally, the rules can wait for the response to the remote command and analyze the response for further automation processing. Control-O users can easily implement automation procedures that span multiple systems.

Solutions Provided

SolveWare subject CTORMT contains the Remote Operations solution. This solution provides an easy method for issuing commands to another system and optionally receiving the command response back in the local system.

Remote Operations

This solution provides an easy method for issuing commands to another system and optionally receiving the command response back in the local system. The response is provided in the rule’s local variables and can be analyzed for further automation.

The solution requires Control-O to be active and the CTORMT rules loaded, on all relevant systems (that is, the system on which the command originates and the system on which the command must be issued).

NJE or MAS connection between the systems is required.

Some rules in this solution can be considered as internal rules. They do not interface with the user’s rules and operations and they require no customization. These rules are marked "Internal" in the list below and no further documentation details are provided for them.

Rules

The Remote Operations solution includes the following rules:

Issue Cross System Commands
CTORMT Initialization
Receive Remote Request (Internal)
Pass Back Response (Internal)
Suppress Remote Response From Console (Internal)

Rules Structure

The following tables describe the structures of the Remote Operations solution rules.

Table 151 Issue Cross-System Commands Rule Structure

Item	Description
Title	Issue Cross-System Commands
Name	CTORMT
Table	CTORMT
Command	Copy `CTORMT target-smfid WMODE=Y (Yes), N (No) [WRESP=Y (Yes), N (No)] [RMSG=response-message-ID] [TOUT=timeout-value]CMD=remote-command-text`
Command Description	Issue cross system commands according to rule arguments.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%RMT_ROUTE_smfid Command routing information. For more details, see customization instructions of rule RMTINIT in Table 152 CTORMT Initialization Rule Structure. %%CTORMT_CNT Remote command request counter. Used to assign a unique request ID to each request.
Rule Logic	The rule arguments are parsed. And the command is issued to the remote system according to these arguments. Response messages are stored in local variables in the originating rule.
Rule Actions	Parse rule arguments and perform validity checks. If the command must be issued without waiting for a response, issue the command to the remote system and terminate. If the rule is to issue the command and then wait to receive the response, do the following: Obtain a unique request ID by increasing counter %%CTORMT_CNT. Issue the command to Control-O on the remote system, including request ID and response parameters. command is issued in command-response mode and the expected response message ID is CTORP<rid> where <rid> is the unique request ID. Set local variable %%RLINEn to the nth response line. Set local variable %%RLINES to the total number of response lines.
Activating the Rule	Once scheduled, the rule remains active until deleted from Control-O.
Recommended Mode or Category	During the testing period activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for the rule. SolveWare Category for this rule is 1—minimal or no customization is required.

Table 152 CTORMT Initialization Rule Structure

Item	Description
Title	CTORMT Initialization
Name	RMTINIT
Table	CTORMT
Event	RMTINIT
Event Description	This Event rule initializes solution CTORMT.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%RMT_ROUTE_smfid Command routing information. For more details, see the Customization item in this table.
Rule Logic	This rule instructs the CTORMT solution how to communicate from one system to another in a given MVS complex. The rule is triggered following the loading of the CTORMT rule table to the Control-O Active environment. Command routing information is stored in global variables according to the target system SMF ID. This information is then used by other rules for cross-system communication.
Rule Actions	For each system in the complex, sets global variable %%RMT_ROUTE_smfid to the appropriate command routing information.
Activating the Rule	The rule is activated once upon loading to the Active environment.
Recommended Mode or Category	During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for the rule. The SolveWare Category for this rule is 2—some customization is required before implementation.
Customization	In JES2 sites, routing variables (%%RMT_ROUTE_smfid) must contain the NJE node and (optionally) MAS member according to the syntax of JES2 command $N. For instance, MAS member 3 in NJE node 2 must have the value 2M3. In JES3 sites, these variables must contain system name according to the *SEND JES3 command.