Data Collector Abends with S0C1

book

Article ID: 144463

calendar_today

Updated On:

Products

CA Sysview Performance Management Option for DB2 for z/OS CA Database Management for DB2 for z/OS - Performance Suite CA Database Management for DB2 for z/OS - SQL Performance Suite CA-Insight Performance Monitor for DB2 UDB for z/OS

Issue/Introduction

Data collector abended with the following message:

DBG11017I DB33 00:00:10 ESTAE EXIT IN NADCPPRM INVOKED BY ABEND
 ABEND CODE IS 140C1000 - EC PSW AT ABEND IS 078C2000 AC8AEAC4 - PRIMARY MODE, S
 ILC, INTERRUPT CODE 00060001 - TRANSLATE EXCEP 7EB00801
 EYECATCHER POINTED BY R12 - COMPDERM
 OFFSET TO ABEND ADDRESS FROM R12 IS 04992874
   R0  00000000  R1  2D925010  R2  283241A4  R3  29DA4758
   R4  000114E0  R5  0002AE1C  R6  00125680  R7  283241A4
   R8  00000000  R9  00125698  R10 0006B000  R11 0012E000
   R12 27F1C250  R13 00125768  R14 A7F1C2A4  R15 2C8AEABC
  AR0  009EE370 AR1  00000000 AR2  00000000 AR3  00000000
  AR4  00000000 AR5  00000000 AR6  00000000 AR7  00000000
  AR8  00000000 AR9  00000000 AR10 00000000 AR11 00000000
  AR12 00000000 AR13 00000000 AR14 00000000 AR15 00000000

Environment

Release : 20.0

Component : CA Insight Database Performance Monitor for DB for z/OS

Resolution

The problem is a basic serialization problem. The stopping of a request results in the rebuilding of the code to handle the DECLARE statement. At the same time, an accounting record was being processed for a thread, and we branched to the storage that contained the code to process the DECLARE, which had been freed. If you have requests that are regularly stopped and restarted, and they contain DECLARE statements, you can create a separate request containing only the DECLARE statements. Then, remove the DECLAREs from the requests that get stopped and restarted regularly.