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:
This left the resource in STOPPING and delayed the shutdown. This occurred during a SHUTFORCE.
Example of Log Message:
184.108.40.206 BG-SYS N1A1BSYS RMLO0099 (STC:NETMIX) 4 000249 $RMSTMS RMSTMS44 ACTUAL STATE CHANGED FROM <ACTIVE> TO <INACTIVE> BY
<END OF MEMORY CONDITION DETECTED>
220.127.116.11 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>
Release : 11.9
Component : CA SOLVE:Operations Automation for z/OS
Created Test fix LT03120 for STOPPING STATE OVERRIDES INACTIVE STATE SET BY EOM CONDITION