Using OPS/REXX › OPS/REXX Usage Problems › Received Message Address Space Is Not Active

Received Message Address Space Is Not Active

Symptom:

My program received the following message:

OPS3148E ADDRESS SPACE NOT ACTIVE

Solution:

OPS/REXX programs that update global variables or issue AOF, EPI, OPSCTL, TSO, or OPER commands require that the main CA OPS/MVS started task be active.

If you are running multiple copies of CA OPS/MVS, or you use a CA OPS/MVS subsystem name different from OPSS, you may have to either:

• Issue the ADDRESS AOF SUBSYS OPSx instruction to identify the correct subsystem to which subsequent ADDRESS AOF (or ADDRESS EPI, ADDRESS OPSCTL, and so in) commands will be directed, as well as subsequent global variable updates.
• Change the job step name of the TSO logon, started task, or batch job from which the REXX program is executed so that the first four characters are OPSx (the name of the correct subsystem).

If you fail to do either of the above, your program may get the message:

OPS3148E ADDRESS SPACE NOT ACTIVE

Always allocate the DD statement for the job running OPS/REXX to the subsystem where global variables reside or that will receive ADDRESS AOF, ADDRESS EPI, ADDRESS OPSCTL, ADDRESS TSO, or ADDRESS OPER commands. To do so, use JCL like that shown in the following example:

//OP$OPST DD DUMMY

The example above causes any REXX program in this subsystem to connect to subsystem OPST.