ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

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

book

Article ID: 210245

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

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

 

Environment

Release : 13.5

Component : 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 HVTPROC
)Proc JOB = EOS.JOBNAME
if EOS.STEPNAME <> 'HVTPROC' then return
if EOS.PROCSTEP <> 'HVTPROC' 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 HVTPROC resource from SSM Policy Manger