CMOD makes use of the Dynamic Exit Facility available in z/OS.
Unfortunately, every so often an error will occur and a dynamic exit will become disabled.
When that happens the exit has to be dynamically deleted and then dynamically re-added.
Example from a PROGxx on one of our test systems that's running 4 ARSSOCKD's each with its own security exit:
EXIT DELETE
EXITNAME=ARS.SECURITY,MODNAME=ARSUSECZ
EXIT DELETE
EXITNAME=ARS.SECURITY,MODNAME=ARSUSEZ1
EXIT DELETE
EXITNAME=ARS.SECURITY,MODNAME=ARSUSEZ2
EXIT DELETE
EXITNAME=ARS.SECURITY,MODNAME=ARS4SECZ
EXIT ADD EXITNAME=ARS.SECURITY,MODNAME=ARSUSEZ1,
DSNAME=ARS.ARSV841.USERLOAD,JOBNAME=ARSSOCK1
EXIT ADD EXITNAME=ARS.SECURITY,MODNAME=ARSUSEZ2,
DSNAME=ARS.ARSV850.USERLOAD,JOBNAME=ARSSOCK2
EXIT ADD EXITNAME=ARS.SECURITY,MODNAME=ARSUSECZ,
DSNAME=ARS.ARSV900.USERLOAD,JOBNAME=ARSSOCK3
EXIT ADD EXITNAME=ARS.SECURITY,MODNAME=ARS4SECZ,
DSNAME=ARS.ARSV950.USERLOAD,JOBNAME=ARSSOC95
Unfortunately, the message for a dynamic exit becoming unavailable is an informational message and not an error message.
Also, it's usually just one line - very easy to miss.
I highly recommend having the automation group send a notification to the CMOD support team whenever the following message occurs:
CSV430I MODULE modname FOR EXIT exitname HAS BEEN MADE INACTIVE DUE TO ABEND=compcode REASON=rsnPreferable, of course, would be if the automation can filter on exits that start with "ARS" or can have exitname be from a list of exits exploited by CMOD on that system.
Ref:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieam400/m006244.htmEd
