Understanding the Interfaces to CA Automation Point › Configure the CA Automation Point Interface › Functions Available after Establishing Communication

Functions Available after Establishing Communication

After communication is established between CA OPS/MVS and CA Automation Point, CA OPS/MVS can initiate the following functions to run on CA Automation Point:

• REXX program execution-CA OPS/MVS can send REXX programs to the CA Automation Point workstation.
• Write to PPQ (Program-to-Program Queue) functionality-CA OPS/MVS can issue a write to a PPQ on the CA Automation Point workstation.
• NMFIND request execution-CA OPS/MVS can send NMFIND requests to contact personnel to the CA Automation Point workstation. The NMFIND requests executed on the CA Automation Point workstation determine the personnel to be contacted based on time-oriented and method-of-contact policies specified in the CA Automation Point Notification Manager database.
• Message line execution-CA OPS/MVS can use the ADDRESS WTO or OPSWTO TSO command processors to send single line messages to the CA Automation Point workstation. The messages are eligible for rule processing by the CA Automation Point workstation.

CA Automation Point can initiate the following functions to run on CA OPS/MVS:

• Message execution-CA Automation Point sends messages to one or all of your CA OPS/MVS hosts. The messages are eligible for AOF processing and also appear in the OPSLOG.
• REXX program execution-CA Automation Point launches the execution of REXX programs on one or more of the CA OPS/MVS hosts. The REXX programs need to be located in either the SYSEXEC or OPSEXEC library concatenation of the OSF TSO servers used by the CA OPS/MVS hosts.
• Command execution-CA Automation Point sends the z/OS subsystem or pseudo commands to CA OPS/MVS hosts for execution and return the command responses to the issuing CA Automation Point workstation.