Previous Topic: OPS/REXX Host Environments and Built-in FunctionsNext Topic: OPS/REXX Built-in Functions


OPS/REXX Host Environments

OPS/REXX host environments let you perform common automation and system operations, such as issuing messages (WTOs), z/OS commands, and UNIX System Services commands. You can also use OPS/REXX host environments in AOF rules to control various CA OPS/MVS facilities.

You can use the following OPS/REXX host environments in AOF rules:

ADDRESS AOF

Programmatically control rules and create dynamic AOF rules

ADDRESS EPI

Programmatically interact with any VTAM application

ADDRESS MIM

Display information managed and collected by the CA MIM product

ADDRESS NETMAN

Open, update, or close records in CA Netman

ADDRESS OPSCTL

Control COF, ECF, OSF, MSF, and OPSLOG components

ADDRESS OPER

Issue z/OS, JES, VM, subsystem commands

ADDRESS OSF

Schedule TSO commands, CLISTs, or REXX EXECs to CA OPS/MVS OSF TSO servers

ADDRESS OSFTSL

Schedule TSO commands, CLISTs, or REXX EXECs to CA OPS/MVS OSF TSL servers

ADDRESS OSFTSP

Schedule TSO commands, CLISTs, or REXX EXECs to CA OPS/MVS OSF TSP servers

ADDRESS SOF

Provide a user interface for managing devices attached through ESCON directors and FICON switches

ADDRESS SQL

Create and maintain SQL tables in the CA OPS/MVS RDF component

ADDRESS SYSVIEWE

Retrieve output from CA SYSVIEW commands

ADDRESS USS

Issue UNIX System Services commands

ADDRESS WTO

Issue system messages in the form of WTOs, or WTORs

Note: For complete descriptions and coding guidelines for each OPS/REXX host environment, see the Command and Function Reference.

More information:

Coding Each AOF Rule Type