AOF GLV rules don't fire when Sysplex Variable is created, updated or deleted via the OPSVASRV function, after dynamically turning on the GLVNOTIFYRULES parameter

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Why are OPS/MVS AOF GLV rules are not firing when a Sysplex Variable is created, updated or deleted via the OPSVASRV function, after a dynamic change to turn on the GLVNOTIFYRULES parameter is implemented?  They are not getting triggered. 

 

Environment

OPS/MVS-Event Management & Automation-for JES2

Resolution

When parameter GLVNOTIFYRULES is not set at initialization time via the OPSSPAxx parameter deck, the OPSVASREX exit doesn't get implanted.

To determine if this is the case issue the following z/OS display command:

/D PROG,EXIT,EXITNAME=CA_VARDATA_CHG,DIAG

If the exit was not in place, then you should see the following message as a result:

CSV463I NO MODULES ARE ASSOCIATED WITH EXIT CA_VARDATA_CHG

To dynamically load the exit use the following z/OS modify command against the OPS/MVS subsystem:

/F OPSS,RELOAD(OPVASREX)

A message similar to this should be posted by the OPSMAIN Address Space:

OPS3257I Module name (OPVASREX) reloaded at X'yyyyyyyy'

Also as a result of all above the z/OS display command should now show this:

D PROG,EXIT,EXITNAME=CA_VARDATA_CHG,DIAG
CSV464I hh.mm.ss PROG,EXIT DISPLAY nnn
EXIT CA_VARDATA_CHG
MODULE STATE EPADDR LOADPT LENGTH JOBNAME PARAM
OPVASREX A yyyyyyyy 00000000 00000000 *

AOF GLV rules should now start triggering on the designated system when CREATE, UPDATE, and DELETE functions are performed against Sysplex Variables via the OPSVASRV command. When using multiple  OPS/MVS systems only the instances using the same SUBSYS id will see the updates to the Sysplex Variables.