OPS/MVS - SSMGA not honoring PREREQs on resource move

book

Article ID: 209329

calendar_today

Updated On:

Products

CA OPS/MVS Event Management & Automation

Issue/Introduction

We are encountering errors with the SSMGA move process where it appears that the defined PREREQs for resources are not being honored when the resources moves. We turned on  SSMDEBUG for the data below.  

DBT1QMON should have waited for 4 resources (MQT1MSTR,MQT1CHIN,DBT1QCAP,DBT1QAPP) but waited for NONE. 

19:52:09 OPS7914T   OPS7914T SSM AUDIT: STCTBL.DBT1QMON ADDED by OPSOSF SGINSRES                            
19:52:09 OPS7913T   OPS7913T SSM GLOBAL ADD for STCTBL.DBT1QMON: RULE=SGUPPLVA ADD STCTBL.DBT1QMON          
19:52:09 OPS7913T   OPS7913T SSM PROCESS SELECT for STCTBL.DBT1QMON: PROCESS=MATCH,XSUBREQ,XPREREQ,MSUBREQ  
19:52:09 START      START DBT1QMON                                                                          
...
19:53:37 OPS7914T   OPS7914T SSM AUDIT: STCTBL.MQT1MSTR ADDED by OPSOSF SGINSRES                          
19:53:37 OPS7913T   OPS7913T SSM GLOBAL ADD for STCTBL.MQT1MSTR: RULE=SGUPPLVA ADD STCTBL.MQT1MSTR        
19:53:37 OPS7913T   OPS7913T SSM PROCESS SELECT for STCTBL.DBT1QAPP: PROCESS=MATCH,XSUBREQ,XPREREQ,MSUBREQ
19:53:37 OPS7913T   OPS7913T SSM PROCESS SELECT for STCTBL.DBT1QCAP: PROCESS=MATCH,XSUBREQ,XPREREQ,MSUBREQ
19:53:37 OPS7913T   OPS7913T SSM PROCESS SELECT for STCTBL.MQT1CHIN: PROCESS=MATCH,XSUBREQ,XPREREQ,MSUBREQ
19:53:37 OPS7913T   OPS7913T SSM PROCESS SELECT for STCTBL.MQT1MSTR: PROCESS=MATCH,XSUBREQ,XPREREQ,MSUBREQ
19:53:37 #MQT1      #MQT1 START QMGR                                                                      
...
Etc. etc. After the start attempt DBT1QMON

Environment

Release : 13.5

Component : OPS/MVS

Resolution

The STATEIGNOREMPRE parm was set to 'YES'.  This causes prereqs that are not in the table to be ignored. 

This is of value to handle deleting a resource and not updating prereqs, but it is not good for moving a group of resources that are prereqs. 

To resolve set that parm to 'NO' or move the resources in a down state then start them after they are all moved. 

Note:  Changing the STATEIGNOREMPRE will not affect the MINOF statement in your prereq. As long as one of those resources are up on that system, the MINOF will be satisfied. 

 

If this does not resolve the issue, open a support case and supply the following documentation:

1.  A copy of the archived OPSLOG

2.  Screenshots showing the values of the Stateman parms from panel =4.1.1   There should be two screens worth of parms if entering STMPARMS in the group field of that screen.