RMFGAT being started by State Manager twice or not started at all

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

When OPS/MVS issues the MODIFY command,  RMF writes out a START command in the log which is being intercepted by SSM and another start action is issued.

From OPSLOG:

OPS0997T *-* 58:return                                                                                                    
START RMFGAT MONITOR III SESSION III                                                                                      
OPS1370T RMF      X'0000' X'0000' X'0000' INTERNAL  300 OPSNOTIFY  Start request of SSM managed resource RMFGAT processed.
OPSNOTIFY Start request of SSM managed resource RMFGAT processed.                                                         
OPS7914T SSM AUDIT: STCTBL.RMFGAT UPDATED by RMF SSM.SSMSTART CURRENT_STATE=UNKNOWN                                       
OPS7902H STATEMAN ACTION FOR STCTBL.RMFGAT: UNKNOWN RULE=SSMSTATE TABLE(STCTBL) NAME(RMFGAT) TYPE() JOBNAME(RMFGAT) DESIRE
OPS7914T SSM AUDIT: STCTBL.RMFGAT UPDATED by OPSMAIND STATESET CURRENT_STATE=DOWN                                         
OPS7902H STATEMAN ACTION FOR STCTBL.RMFGAT: DOWN_UP MVSCMD=F RMF.4006,S III,MEMBER(05)                                    
OPS1181T OPSMAIND      (*Local*) MVS N/A OPSYSTZS F RMF.4006,S III,MEMBER(05)                                             
F RMF.4006,S III,MEMBER(05)                                                                                               
OPS1450T ZUCLA01  OPSS OPSLOG                                                                                             

OPS7914T SSM AUDIT: STCTBL.RMFGAT UPDATED by RMF SSM.SSMSTART CURRENT_STATE=UNKNOWN                                       
OPS7902H STATEMAN ACTION FOR STCTBL.RMFGAT: UNKNOWN RULE=SSMSTATE TABLE(STCTBL) NAME(RMFGAT) TYPE() JOBNAME(RMFGAT) DESIRE
OPS7914T SSM AUDIT: STCTBL.RMFGAT UPDATED by OPSMAIND STATESET CURRENT_STATE=DOWN                                         
OPS7902H STATEMAN ACTION FOR STCTBL.RMFGAT: DOWN_UP MVSCMD=F RMF.4006,S III,MEMBER(05)                                    
OPS1181T OPSMAIND      (*Local*) MVS N/A OPSYSTZS F RMF.4006,S III,MEMBER(05)                                             
F RMF.4006,S III,MEMBER(05)                                                                                               

Another reported symptom is that the RMFGAT task is set to a CURRENT_STATE of UNKNOWN and is not started.

 

 

 

 

Environment

Release : 14.0

Component : OPS/MVS

Cause

At z/OS 2.5 or z/OS 2.4 with certain PTFs, the load module for RMF that processes the start of RMFGAT has changed names; the SSMSTART rule checks for the name of the load module.

Resolution

PTF LU04168 is the fix. It has an update to support RMFGAT at z/OS 2.5. There is also a circumvention:

CIRCUMVENTION:
Add the new RMFGAT load module name of GRB3CGAT to the list of modules
in the local variable name, 'allow_modules', for the SSMSTART rule.

Link to the PTF LU04168:

LU04168

After having applied this PTF the rule SSMSTART must be deployed:

1) Copy the member SSMSTART from the CCLXRULM library to the ruleset that contains the SSM rules

2) Enable and set the auto-enable flag for this rule