What causes a symptom dump for GSS STC and a S502 abend?
Article ID: 16200
Updated On:
Products
Issue/Introduction
A symptom dump has been produced for the GSS STC.
There is an S502 abend in the GSS STC output:
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=502 REASON CODE=00000000
TIME=22.12.56 SEQ=04925 CPU=4000 ASID=0115
PSW AT TIME OF ERROR 070C1000 81579A08 ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
How this S502 abend in GSS can be fixed?.
Environment
Common Services 15.0 - z/OS supported releases -
Resolution
The S502 abend indicates that the EVENTS table is too small.
The GSS dispatcher is constructed around the z/OS EVENTS facility.
The EVENTS table must allow a slot for each pending (unprocessed) event.
Depending on dispatching priorities and selected options, the EVENTS table needs room to buffer deferred work.
The EVENTS value is used to determine how many separate internal processes can take place for IMODs in SYSVIEW for DB2. The EVENTS table is allocated in GSS stated task region and it is a reusable table that cycles so that it can appear to be larger than it is. Once a slot is vacated it is available for use when needed. It works in a circle and using the slots that have not been used sequentially until it finds one that has been used but not used currently.
When the EVENTS table is exhausted GSS is not designed to getmain an additional set of tables. So when the EVENTS table overflows due to a high activity in IMODs you will get the Abend S502. The Max value for the EVENTS parameter is 32767. If you will not use all the slots then it is not necessary to increase to this value but I have found some of our customer works with the Max value without problem.
The EVENTS value has to be increased in the RUNPARM member.
Additional Information
You can check the information for the GSS EVENTS settings for in the Common Services 15.0 documentation
Feedback
