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 |
CTORMT target-smfid |
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 |
|
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 |
|
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 |
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 |
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. |
Parent Topic |