IDB2 abends with CCSR010E NMSPRMVC S0C4 at 2D94A48C LMOD NSIGHTPR CSECT NDFMTSEC

book

Article ID: 195291

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 abend with below dump message applying some recent maintenance. 
DBG21009E DSNR 06:32:04 HISTORY: DIAGNOSTIC HIST TYP UNKNOWN
 CCSR010E NMSPRMVC S0C4 at 2D94A48C LMOD NSIGHTPR CSECT NDFMTSEC +00038C N/A N/A
 CCSR021I OWNER = CA SYSVIEW for DB2 R20.0
 CCSR022I MODULE = NDFMTSEC FMID = ~ZAPFMID RMID = SO12769
 CCSR060I BREAKING EVENT ADDRESS: 00000000 2D94A44A
 CCSR061I PSW: 07842000 80000000 00000000 2D94A48C
 CCSR062I ILC: 02 INTERRUPT CODE: 11
 CCSR067I COMPLETION CODE S0C4 REASON CODE 00000011
 CCSR063I TRANSLATION EXCEPTION ADDRESS: 00000000_1407B800
 CCSR064I DATA AT PSW 2D94A486 : D09C50E0 D0A00E0E 5EE0D0A4
 CCSR065I HOME = 00A0  PRIMARY = 00A0  SECONDARY = 00A0
 CCSR070I GR00 - GR01  00000000_3BD1BE30 00000000_000005C4
 CCSR070I GR02 - GR03  00000000_00000001 00000000_3BD1AC7C           

Environment

Release : 20.0

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

Resolution

The problem was due to the fact that you PTF SO12769 was applied. This PTF introduces support for new secondary latch contentions fields in the QTXA section. In order to have those fields in DB2 V11 though you would need to apply IBM  PI93817 APAR:

https://www.ibm.com/support/pages/apar/PI93817

This APAR changes the QTXA section size significantly, which can cause problems during processing.