$HASP310 stcTERMINATED AT END OF MEMORY

Products

• Bind Analyzer for DB2 for z/OS
• SQL-Ease for DB2 for z/OS
• SYSVIEW Performance Management Option for DB2 for z/OS
• Plan Analyzer for DB2 for z/OS
• Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

At the stop of the CA DB2 Tools of our LPAR ( KPA1XNET, KPA1KBA1 (Insight) and KPA1MAN, the STC KPA1KBA1 ends with message $HASP310 KPA1KBA1 TERMINATED AT END OF MEMORY. 
We had several LPARs with the message and others without.
They have the same configuration parameters.
We stop KPA1XNET, then KPA1KBA1 and the KPA1MAN.
 

Environment

Z/OS DB2

Cause

Cancelling data collector threads manually 

Resolution

We have been through the supplied dump and now understand what caused the problem. From the syslog we can that several data collector threads were manually cancelled.
You should never cancel data collector threads in this way, because it does not allow the data collector to stop in a normal and controlled manner.
Also there are unpredictable results caused by the cancelling of Threads in this manner.
Also we can see Automation is being used to stop the CA DB2 Tools.
From the syslog it seems that both the DC and DB2 are being stopped at the same time.
This again can cause unpredictable results We recommend to change your automation process:
To stop the data collector first (thru STOP MVS command), wait till it gets down, and only then stop the DB2 subsystem.