After an IPL, CAS9 state is ending up as TERM instead of UP:
OPS7902H STATEMAN ACTION FOR STCTBL.CAS9: DOWN_UP MVSCMD=S CAS9
S CAS9
OPS7914T SSM AUDIT: STCTBL.CAS9 UPDATED by OPSMAIN STATEMAN CURRENT_STATE=STARTING
OPS7902H STATEMAN ACTION FOR STCTBL.CAS9: STARTING_UP=NO ACTION FOUND
CAS9130I - MODULE CAS9INIT COMPLETE, RC=00
OPS7914T SSM AUDIT: STCTBL.CAS9 UPDATED by CAS9 *DYNAMIC.ASSMEZ CURRENT_STATE=UP
OPS7914T SSM AUDIT: STCTBL.CAS9 UPDATED by *MASTER* CCLXRULM.SSMEOM CURRENT_STATE=TERM
OPS7902H STATEMAN ACTION FOR STCTBL.CAS9: TERM_UP=NO ACTION FOUND
$HASP395 CAS9 ENDED - RC=0000
Release : 14.0
Component : OPS/MVS
The SSMEOM rule must be disabled if using SSMV3. The OPSLOG shows it is still enabled:
OPS7914T SSM AUDIT: STCTBL.CAS9 UPDATED by *MASTER* CCLXRULM.SSMEOM CURRENT_STATE=TERM
The instruction to disable the SSMEOM rule is in the step 2. of the instructions to implement HOOK type resource with SSMV3:
Replace Use of AOF Request Rule SSMHOOK with Policy Data
We recommend that you replace the existing use of AOF request rule SSMHOOK with the new SSM version 3 policy.
1. Remove the EVRULE("SSMHOOK …") clause from all actions in your Action table.
2. Disable the SSMEOM rule. SSM version 3 will create a dynamic EOM rule to manage resources.