The AOFACTIVEREXX parameter specifies the name of an OPS/REXX program that you have written to validate your AOF environment and to perform any processing that you want after the auto enable process has completed and before the OPx0123O message is issued indicating that the AOF is active. One purpose of this OPS/REXX EXEC is to validate that those AOF rule sets and rules, which are absolutely required for your automation to function correctly, are enabled.
The program that you specify as the value of AOFACTIVEREXX must be in a PDS library that is allocated to the OPSMAIN STC JCL under the SYSEXEC ddname.
Important! For the AOFACTIVEREXX parameter to take effect, the value of the AOFACTIVE parameter must be ON. For details, see AOFACTIVE Parameter in this chapter.
Note: Using the ADDRESS AOF ENABLE command in the AOFACTIVEREXX program to enable individual rules is slower than using the AUTOENABLE process, which processes an entire rule set at a time.
REXX execs specified in AOFINITREXX and AOFACTIVEREXX will execute in the OPSMAIN address space. They cannot execute any Address OSF or TSO commands at AOF initialization time since the TMPs are not yet active.
For details on tailoring CA OPS/MVS startup procedures, see the Administration Guide.
Blanks (indicating that there is no OPS/REXX program to execute)
Any valid OPS/REXX program name
At initialization
Example: AOFACTIVEREXX
This function names AOFACTV as the OPS/REXX program that CA OPS/MVS executes to validate the AOF environment, perform post auto-enablement processing, or both.
OPSPRM('SET','AOFACTIVEREXX','AOFACTV')
|
Copyright © 2014 CA.
All rights reserved.
|
|