OPS/MVS Permanent sysplex variable couldn't be backed up to VSAM dataset
search cancel

OPS/MVS Permanent sysplex variable couldn't be backed up to VSAM dataset

book

Article ID: 367494

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

Permanent Sysplex Variables created with OPSVASRV function couldn't be backed up to VSAM datasets. 

Cause

CSV463I NO MODULES ARE ASSOCIATED WITH EXIT CA_VARDATA_CHG

Resolution

Issue the following command to display the dynamic exit used by the CAVARSRV component :

D PROG,EXIT,EXITNAME=CA_VARDATA_CHG,DIAG 

if the response is 

CSV463I NO MODULES ARE ASSOCIATED WITH EXIT CA_VARDATA_CHG

then 

Set the GLVNOTIFYRULES OPS parm to YES from OPSVIEW 4.1.1 and issue the following command:

/F OPSS,RELOAD(OPVASREX)

Reissue the  D PROG,EXIT,EXITNAME=CA_VARDATA_CHG,DIAG command. 

You should now see the OPVASREX module associated with the exit. 

Try to update or create a new GLVPLXP variable and see if it's written to the VSAM file.