CSA/ECSA storage is not being released upon OPSMAIN termination

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Why isn't OPS/MVS releasing storage from CSA/ECSA during main task termination?

 

Environment

OPS/MVS-Event Management & Automation-for JES2

Resolution

The following messages caused concern: 

OPS0039E n process block(s) still in use                
OPS0018W storage not released - ECSA X'00004B6A' bytes  
OPS0017I OPS/MVS-JES2 subsystem OPSS termination complete

The OPS0039E message by itself does not indicate that storage related to the 'n' in-use process blocks was not freed.  The storage is freed unconditionally. The message is just a warning that there are still 'n' number of rules executing and OPS/MVS has given up waiting for them to complete.

Also, the 19K+ bytes of ECSA reported by message OPS0018W that were left behind is normal as well. The first 16K contains permanent data needed across restarts of OPS/MVS to allow the start of command processors (OI, OPSCMD, OPSWTO, etc.) even when the main address space is down. The small additional piece of ECSA contains system control blocks allocated by OPSMAIN that can never be freed for the life of the last system IPL. The fact that the messages were issued prior to OPSMAIN being down indicates that it has terminated normally.