Load Module TNSLOAD abends with a S0C4 Reason Code 10 at Offset 4F04 in Started Task MATUNER when first attaching to DB2 Version 910 after issuing 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
Please verify that in the TUNSSP00 Parm member, DB2HVEXT=YES & DB2HVE EXT=DB2E1.
It could be that these CA MAT 9.0 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 CA MAT tries to connect to this moved DB2 Subsystem that one is testing with.
If these are not the symptoms, please open a new case through CA Support Online. Please provide CA Support with the S0C4 captured as an SVC dump, the complete MATUNER STC LOG, and please provide your maintenance level (last PTF applied, or run an SMP/E LISTMODS against the CA MAT CSI and send in the complete job output).