OPS/MVS - SSM status goes to FAILED when multiple jobs and task use the same name of a Virtual Tape System PROC

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

We have a started task called XXXPROC that we defined to OPS/MVS and started on IPL but XXXPROC some times will start another started task with the same name to perform utilities and some times the XXXPROC utility ends with a return code 8. How can we prevent OPS/MVS on flagging the started task as FAILED? The XXXPROC that was started during IPL is what we are more concerned about going down.

 

Environment

OPS/MVS

Resolution

1) Disable the SSM.EOM rule

2) Disable the SSM.SSMHASP3 rule. This rule should be disable of all tasks if SSMV3 is in use. 

3) Create the following EOS rule: 

)EOS XXXPROC

)Proc JOB = EOS.JOBNAME

if EOS.STEPNAME <> 'XXXPROC' then return

if EOS.PROCSTEP <> 'XXXPROC' then return

address SQL "Update STCTBL set current_state='DOWN'",

    "where name='"JOB"'"

return 0

 

Enable this rule, update the "Inactivation Completion Rule" to inform the name of this rule and load the XXXPROC resource from SSM Policy Manger