Thread Terminator, Option 'VZ View DSNZPARM Data', Abend S0C4 LMOD: *UNKNOWN

Products

• Thread Terminator for DB2 for z/OS

Issue/Introduction

Applied maintenance over Database Management Solutions for DB2 for z/OS and suddenly got the following Abend S0C4 in Thread Terminator Option 'VZ View DSNZPARM Data'. 

PXM0800 ABEND INCURRED/RETRY IN PROGRESS
PXM0810 CA/XMANAGER RECOVERY IN PROGRESS (TCB 00AC35E8)
PXM0811 PSW: 070C4001 AAFEFB2E LMOD: *UNKNOWN OFFSET: N/A ABEND: S0C4
PXM0812 GPRS 0 1 00000000 00000040 00000001 26CDFE2B
PXM0812 2 3 00000000 00000000 00000000 00000000
PXM0812 4 5 00000000 2AFEE854 00000000 28A55818
PXM0812 6 7 00000000 2AFEFE7C 00000000 2AFEFB68
PXM0812 8 9 00000000 26CDFE00 00000000 2B065568
PXM0812 10 11 00000000 2AFEF6E0 00000000 2B09ADE0
PXM0812 12 13 00000000 2B09B88B 00000000 2B0B2C48
PXM0812 14 15 00000000 26CDFE2C 00000000 FFFFFFFF
PXM0812 ARS 0-3 00000000 00000000 00000000 00000000
PXM0812 4-7 00000000 00000000 00000000 00000000
PXM0812 8-11 00000001 00000001 00000000 00000002
PXM0812 12-15 00000002 00000000 00000000 00000002
PXM0801 ABEND INCURRED/RETRY SUCCESSFUL
***

Environment

Release : 2.0

Component : Thread Terminator

Resolution

The Abend S0C4 might be caused because the DSNZPARM module was not Assemble/Link-edit correctly for this particular DB2 Subsystem.  
This problem was fixed after an old DSNZPARM module was identified and it was Assemble/Link-edit again. 
  
Additionally after maintenance has been applied you have to double check you work with the right PTILIB and PTIPARM DDnames in your TSO session. The PTILIB DDname CDBALOAD library should be the same as in the Xmanager JCL or at same level of software maintenance.

When you are in the Thread Terminator menu issue the command TSO ISRDDN and you can double check the DDNames and libraries. 

DDname   Data Set Name
PTILIB   R200.CDBALOAD
PTIPARM  R200.CDBAPARM