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.

STOPPING State overriding End of Memory (EOM) condition setting INACTIVE

book

Article ID: 226768

calendar_today

Updated On:

Products

SOLVE:Operations Automation

Issue/Introduction

Experienced an issue around EOM condition and standard event messages (IEF404I and $HASP395) that traditionally use to set a resource to INACTIVE. The end of memory condition triggered before the IEF404I trap. This caused the resource to go from INACTIVE to STOPPING.

What was observed:

  1. Request to stop
  2. EOM condition (we set it to INACTIVE)
  3. Resource stops with IEF404I (we set it to STOPPING)
  4. Final Actual State = STOPPING

 

This left the resource in STOPPING and delayed the shutdown. This occurred during a SHUTFORCE.

Example of Log Message:

23.37.53.72 BG-SYS   N1A1BSYS RMLO0099 (STC:NETMIX) 4 000249 $RMSTMS  RMSTMS44 ACTUAL STATE CHANGED FROM <ACTIVE> TO <INACTIVE> BY

                              <END OF MEMORY CONDITION DETECTED>

23.37.53.73 BG-SYS   N1A1BSYS RMLO0099 (STC:NETMIX) 4 000241 $RMSTMS  RMSTMS44 ACTUAL STATE CHANGED FROM <INACTIVE> TO <STOPPING> B

                              Y <IEF404I NETMIX - ENDED - TIME=23.37.50>

Environment

Release : 11.9

Component : CA SOLVE:Operations Automation for z/OS

Resolution

Created Test fix LT03120 for  STOPPING STATE OVERRIDES INACTIVE STATE SET BY EOM CONDITION