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.

Automation no longer recognizing JES2 is UP when IPLing the system after maintenance applied.

book

Article ID: 226846

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

After applying 10 PTFs, OPSMVS no longer recognizing/setting JES2 to UP in the started task table when the system is IPLed.

PTFs applied: LU01174  SO10733  SO11092  SO11100  SO11877  
SO13070  SO13481  SO13791  SO13923  SO14418

If the maintenance is removed the state of JES2 is detected as it should.

When all is working the following messages can be seen in the syslog:

OPS7902H STATEMAN ACTION FOR STCTBL.JES2: UNKNOWN RULE=SSMSTATE 

TABLE(STCTBL) NAME(JES2) TYPE(JES2) JOBNAME(JES2) DESIRED(IPL  

OPS7902H STATEMAN ACTION FOR STCTBL.JES2: UP_IPL RULE=SSMUPIPL 

TABLE(STCTBL) NAME(JES2)                              

After the maintenance:

OPS7902H STATEMAN ACTION FOR STCTBL.JES2: UNKNOWN RULE=SSMSTATE       


TABLE(STCTBL) NAME(JES2) TYPE(JES2) JOBNAME(JES2) DESIRED(IPL        

OPS7902H STATEMAN ACTION FOR STCTBL.JES2: STARTING_IPL=NO ACTION FOUND

 

Environment

Release : 13.5

Component : OPS/MVS

Resolution

Solved by SO14096 plus pre-req SO12673

SO14096:  https://support.broadcom.com/download-center/solution-detail.html?aparNo=SO14096&os=z%2FOS

SO12673:  https://support.broadcom.com/download-center/solution-detail.html?aparNo=SO12673&os=z/OS