MFT agent generates another IEF403I message and 2 other rules, SSMIEF4 and SSMINDD, update the resource current state to DUPE and STARTING again In CA OPS/MVS

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

We installed the MFT agents under System State Manager (SSM) control but...
1. The agents only give some messages in the joblog. Not on the console. Can SSM track these messages?
2. As a bypass I installed the Action STARTING -> UP -> SETCOL(CURRENT_STATE,UP) But, that bypass seems not to work because a rule SSMIEF updates the current_state a second time.

Q30TAG01 IEF695I START
Q30TAG01 WITH JOBNAME
Q30TAG01 IS ASSIGNED TO USER userID, GROUP STCGROUP
Q30TAG01 $HASP373 userID STARTED
OPSMAIN OPS7914T SSM AUDIT: STCTBL.userID UPDATED by userID STATEMAN.SSMHASP3 CURRENT_STATE=STARTING
OPSMAIN OPS7902H STATEMAN ACTION FOR STCTBL.userID: STARTING_UP SETCOL=CURRENT_STATE,UP OPSMAIN OPS7914T SSM AUDIT: STCTBL.userID UPDATED by OPSMAIN STATEMAN CURRENT_STATE=UP userID IEF403I userID - STARTED
OPSMAIN OPS7914T SSM AUDIT: STCTBL.userID UPDATED by userID STATEMAN.SSMINSDD CURRENT_STATE=DUPE
OPSMAIN OPS7914T SSM AUDIT: STCTBL.userID UPDATED by userID STATEMAN.SSMIEF4 CURRENT_STATE=STARTING

What the best way to solve this problem?

Environment

CA OPS/MVS 13.0
SSM Version 2
z/OS

Cause

The STARTING state is set by SSM when SSM see the $HASP373 message. At that moment the states are ... STARTING ... UP. Then the action kicks in ... SETCOL(CURRENT_STATE,UP). Works fine... BUT... Then the MFT agent generates another IEF403I message and 2 other rules are kicked in by SSM 'SSMIEF4' and 'SSMINDD'. They actually update the current state to DUPE and STARTING again.  So, in the end, the resource is in STARTING ... UP... state.

If you have rules firing on $HASP373 and IEF403I that are both setting current_state to STARTING, then that can cause this problem.

Resolution

The IEF403 and 404 messages are only issued if an MVS Monitor command has been issued on that system, if that helps in choosing which one to keep. Choose one message or the other, but not both to set Current_state to STARTING.
Disabled two rules that check for the IEF messages: SSMIEF4 and SSMINSDD.

Additional Information

Lesson 5 How to Enable and Disable Rules and Rule Sets

See hlq.CCLXRULM.RULES  dataset for the rules you need to disable.