OPS/REXX programs (but not AOF rules) can send commands to any CA product that interacts with the CA GSS product, including all currently supported releases of CA Jobtrac and CA Scheduler (Release 8.0 and higher). A future release of CA 7 will also support this interface. CA GSS is packaged as part of CA Common Services (CCS) for z/OS.
When an ADDRESS statement issues a command to any host environment that exists outside of CA OPS/MVS, OPS/REXX passes the command to CA GSS. CA GSS then forwards the command to the appropriate product for execution. For example, if you issue a command through an ADDRESS JOBTRAC statement, CA Jobtrac executes that command. The command output goes into the external data queue of the OPS/REXX program containing the ADDRESS statement.
When the ADDRESS statement executes, OPS/REXX sets the RC variable to one of the following:
|
RC has this value... |
When... |
|
-20 |
CA GSS fails or is not active when the program containing the ADDRESS statement executes. |
|
-3 |
CA GSS is active but does not recognize the host environment. |
|
The return code from the host command |
In all other cases. |
To use ADDRESS CASCHD, you must allocate the CA Scheduler Master and tracking files to the CA GSS address space. The following example shows how to send a command to CA Scheduler and retrieve the responses:
address CASCHD "STATUS" SAY "RC is:" RC do while queued() > 0 pull line say line end
The output should resemble the following:
RC is: 0
SC STATUS
SCHEDULE JOB NAME JNO ST RC JCNT SYSID S T A T U S
DB2DAILY 01 0002 XAE1 STARTED
DB31DAY4 01 40 01 WAIT START TIME 12/31 01:00
DB31DLY4 01 40 01 WAIT START TIME 12/31 01:00
For more information on the CCS for z/OS components that are required to run ADDRESS CASCHD and ADDRESS JOBTRAC, see the appendix “CCS for z/OS Component Requirements” in the Administration Guide.
|
Copyright © 2014 CA.
All rights reserved.
|
|