Got a S0C4 abend reason code 10 in TNSLOAD at offset 4F04 in the MATUNER started task. What could be the cause?

Products

• Mainframe Application Tuner

Issue/Introduction

Got a S0C4 abend after first attaching to DB2 Version 910 after issuing the following Modify Command:

F MATUNER,HARVESTER,START,DSN4,DB2E1
 
STC08785  IEA995I SYMPTOM DUMP OUTPUT  506
          SYSTEM COMPLETION CODE=0C4  REASON CODE=00000010
           TIME=12.52.56  SEQ=00781  CPU=0000  ASID=002E
           PSW AT TIME OF ERROR  070C2000   8000CF04  ILC 4  INTC 10
             ACTIVE LOAD MODULE           ADDRESS=00008000  OFFSET=00004F04 
             NAME=TNSLOAD
             DATA AT PSW  0000CEFE - 1244A784  000F5584  0034A774
             GR 0: 00000000_85998599   1: 00000000_00000000
                2: 00000000_00000006   3: 00000000_0000DBC0
                4: A39699A8_4000001C   5: 00000000_00F86020
                6: 00000000_00F86045   7: 00000000_000B7C10
                8: 00000000_04A88600   9: 00000000_00029000
                A: 00000000_000B7BE8   B: 00000000_0000D198
                C: 00000000_0000A6A8   D: 00000000_00080278
                E: 00000000_0000030B   F: 00000000_00000000e 
           END OF SYMPTOM DUMP

 

 

Environment

Release:
Component: MATUNE

Resolution

Verify that in the TUNSSP00 Parm member, DB2HVEXT=YES & DB2HVE EXT=DB2E1.

It could be that these MAT R9 S0C4 abends are caused by the DB2 Group moving an already active DB2 Subsystem from one z/OS LPAR to another z/OS LPAR without an IPL. The abends occurred when MAT tries to connect to this moved DB2 Subsystem that one is testing with.