TPX took 0C1 dumps multiple times without any observable reason.

Products

• TPX - Session Management

Issue/Introduction

02.10.41 STC19850  TPX991I SDUMP IN PROGRESS
02.10.41 STC19850  CCSR010E ESTAPROG S0C1 at 2CD0A154 LMOD N/A CSECT N/A +N/A TPXSTC N/A TPX54
02.10.41 STC19850  CCSR061I PSW: 00000000 00000000 070C3000 ACD0A154
02.10.41 STC19850  CCSR062I ILC: 04 INTERRUPT CODE: 01
02.10.41 STC19850  CCSR067I COMPLETION CODE S0C1 REASON CODE 00000001
02.10.41 STC19850  CCSR064I DATA AT PSW 2CD0A14E : 00006184 82F299A2 A4C26184


02.10.42 STC19850  IEA794I SVC DUMP HAS CAPTURED:  146                         
   146             DUMPID=002 REQUESTED BY JOB (TPXSTC  )  
02.10.42 STC19850  TPX992I RECOVERY WILL BE ATTEMPTED                          
   146             DUMP TITLE=TPX990E ABEND S0C1  - MODULE=ACT1PTIX, TASK=RTEPROG

Environment

Release 5.4
Component TPX for Z/OS

Cause

This is symptomatic of a TSS restart/recycle. 

A TSS SAF REFRESH may also cause the S0C1. 
24012 00:52:03.88 M278BW1  00000280  F TSS,REFRESH(SAF)       
24012 00:52:03.97 E S26300 00000080  TSS1310I SAF MODULE(S) REFRESH COMPLETE

Resolution

Any time TSS is bounced, TPX must be recycled as well. 
Since this can be a reoccurring issue, it would be good practise to update 
the internal procedures suggesting that every time TSS is recycled, a TPX
restart should be enforced.