Host Environment Commands › Host Environments

Host Environments

OPS/REXX supports these host environments:

• ADDRESS AOF instructions send commands to the CA OPS/MVS Automated Operations Facility.
• ADDRESS AP instructions allow you to send commands to Unicenter Automation Point.
• ADDRESS EPI instructions send commands to VTAM applications accessed by the CA OPS/MVS EPI facility.
• ADDRESS ISPEXEC instructions issue commands controlling ISPF dialogs.
• ADDRESS LINKMVS instructions enable an OPS/REXX program to invoke user-written and standard z/OS utility programs that support only the standard z/OS batch parameter list. Rules cannot use the LINKMVS environment. Invoke this environment without running under the TSO TMP.
• ADDRESS LINKPGM instructions enable an OPS/REXX program to invoke user-written and standard z/OS utility programs that support a standard z/OS parameter list. Rules cannot use the LINKPGM environment. You can invoke this environment without running under the TSO TMP.
• ADDRESS LXCON instructions enable an OPS/REXX program to issue commands to VM and Linux systems that are connected to the local system by the Linux Connector component.
• ADDRESS MIM interfaces with the MIM API to retrieve environment, qname, and tape information that CA MIM collects and maintains.
• ADDRESS MESSAGE instructions enable you to debug host commands in rules or REXX programs without actually issuing any live commands.
• ADDRESS NETMAN instructions enable you to open, update, or close records in CA Netman.
• ADDRESS NETMASTR instructions enable you to create alerts on the CA NetMaster NM for SNA Alert Monitor screen.
• ADDRESS OPER instructions issue operator commands (system, JES, or VM/CP commands).
• ADDRESS OPSCTL instructions issue commands to control CA OPS/MVS facilities.
• ADDRESS OPSDYNAM instructions provide dynamic allocation, unallocation, concatenation, deconcatenation, and information retrieval functions for data sets in the current address space.
• ADDRESS OSF instructions enable REXX programs and rules to issue TSO commands and CLIST commands to an OSF TSO server.

  Note: Use the ADDRESS OSF environment instead of the ADDRESS TSO environment, except in request rules. This request makes certain that the command is sent to an OSF TSO server for execution. Using ADDRESS TSO, the environment to which the command is sent is dependent upon the environment in which ADDRESS TSO is executing.

• ADDRESS OSFTSL instructions enable REXX programs and rules to issue TSO commands and CLIST commands to an OSF TSL server. TSL servers are intended for work that runs for relatively long periods of time.
• ADDRESS OSFTSP instructions enable REXX programs and rules to issue TSO commands and CLIST commands to an OSF TSP server. TSP servers are intended for high priority work.
• ADDRESS SERVDESK instructions enable you to create new requests using CA Service Desk.
• ADDRESS SOF interfaces with the IBM I/O subsystem to provide advanced management capabilities for devices that are attached through the ESCON directors and FICON switches.
• ADDRESS SQL instructions issue SQL commands to create, modify, and delete the relational tables where the CA OPS/MVS Relational Data Framework stores information about your system. For detailed descriptions of ADDRESS SQL instructions and their syntax, see the chapter “Relational Data Framework Reference.”
• ADDRESS SYSVIEWE instructions issue commands directly to CA SYSVIEW and return the results of the commands. Rules cannot use the SYSVIEWE Command.
• ADDRESS TSO instructions issue TSO commands and invoke CLISTs.
• ADDRESS USS instructions send UNIX or CCS for z/OS API commands to USS servers.
• ADDRESS WTO instructions issue WTO messages synchronously.

OPS/REXX always issues host commands to the host environment named in the last ADDRESS instruction that executed. For instance, in the following example, OPS/REXX issues the D A,L command to the operating system and the LISTBC command to TSO:

address OPER
"D A,L"
address TSO
"LISTBC"