Using different CA 7 instances with OPS/MVS
Article ID: 276734
Updated On:
Products
Issue/Introduction
We use ADDRESS CA7 statement in OPS/REXX programs to issue commands to the instance CA71.
How to send commands to other instances like CA72?
Resolution
What determines what CA7 instance is used by each ADDRESS environment is the value of the variable &CA7x_SSCT.
The actual instance corresponding to which ADDRESS xxxx environment is defined in the GSSA parameter deck.
For example:
ADDRESS CA7 CAL2X2WR 15 DETACH TYPE 0
GLOBVAL &CA7_SSCT 'CA71'
Address CA7 is sending commands to the instance CA71.
ADDRESS CA72 CAL2X2WR 15 DETACH TYPE 0
GLOBVAL &CA72_SSCT 'CA72'
ADDRESS CA72 is sending commands to the CA7 instance CA72 and so on.
OPS/MVS can also communicate with CA-7 via the U7SVC facility. This facility does not depend on the GSSA definitions. You can know if you are using it by checking your REXX programs by the presence of calls to the function OPSCA7. For example:
RC = OPSCA7("CA7=CA72;/LOGON UID001;DEMAND,JOB=ACTJ001;/LOGOFF")
See that the first keyword (CA7=CA72) is indicating what is the CA7 instance to which the command is being sent.
This facility has a drawback in relation to the normal ADDRESS CA7x host environment provided by GSS as it does not return the responses from the commands. You have a return code for the execution to know if the command was successfully executed or not but you are not able to read the actual response of the command in the REXX that issued it.
Documentation of the OPSCA7 function can be seen in the link below:
Feedback
