Multiple ABEND S0C3 Reason=00000003 MIMDRLOG.MIMDRLOG+335E" at a system startup. MIMGR task fails to start.
19293 19:06:29.67 STC05369 00000291 IEF196I IEA995I SYMPTOM DUMP OUTPUT
19293 19:06:29.67 STC05369 00000291 IEF196I SYSTEM COMPLETION CODE=0C3 REASON CODE=00000003
19293 19:06:29.67 STC05369 00000291 IEF196I TIME=19.06.28 SEQ=00011 CPU=0000 ASID=000A
19293 19:06:29.67 STC05369 00000291 IEF196I PSW AT TIME OF ERROR 478C2000 8009E35E ILC 4 INTC 03
19293 19:06:29.67 STC05369 00000291 IEF196I ACTIVE MODULE ADDRESS=00000000_0009B000
19293 19:06:29.67 STC05369 00000291 IEF196I OFFSET=0000335E
19293 19:06:29.67 STC05369 00000291 IEF196I NAME=MIMDRLOG
19293 19:06:29.67 STC05369 00000291 IEF196I DATA AT PSW 0009E358 - EAF74400 906AA775 EC0ABF6F
19293 19:06:29.67 STC05369 00000291 IEF196I GR 0: 04700000 1: 7EA97000
19293 19:06:29.67 STC05369 00000291 IEF196I 2: 0009B7B8 3: 00000000
19293 19:06:29.67 STC05369 00000291 IEF196I 4: 17D03950 5: 00000000
19293 19:06:29.67 STC05369 00000291 IEF196I 6: 000ADC68 7: 8009E35A
19293 19:06:29.67 STC05369 00000291 IEF196I 8: 0009C000 9: 0009E2F0
19293 19:06:29.67 00000291 TSS7000I DUMPSRV Last-Used 08 Oct 19 13:42 System=SYSZ Facility=STC
19293 19:06:29.67 00000291 IEF196I TSS7000I DUMPSRV Last-Used 08 Oct 19 13:42 System=SYSZ
19293 19:06:29.67 00000291 IEF196I Facility=STC
19293 19:06:29.67 STC05369 00000291 IEF196I A: 19D506C0 B: 0000F000
19293 19:06:29.67 STC05369 00000291 IEF196I C: 8009B000 D: 00097460
19293 19:06:29.67 STC05369 00000291 IEF196I E: 0000D4C9 F: 00000004
19293 19:06:29.67 STC05369 00000291 IEF196I END OF SYMPTOM DUMP
19293 19:06:29.67 STC05369 00000291 IEA995I SYMPTOM DUMP OUTPUT 219
219 00000291 SYSTEM COMPLETION CODE=0C3 REASON CODE=00000003
219 00000291 TIME=19.06.28 SEQ=00011 CPU=0000 ASID=000A
219 00000291 PSW AT TIME OF ERROR 478C2000 8009E35E ILC 4 INTC 03
...
19293 19:06:29.68 STC05369 00000291 IEC130I MIMLOG DD STATEMENT MISSING
19293 19:06:29.68 STC05369 00000291 IEF196I IEC130I MIMLOG DD STATEMENT MISSING
Release : 12.5
Component : MII
MIM unable to allocate the MIMLOG file.
By default, CA MIM provides a message log named MIMLOG, defined as a class A SYSOUT data set. CA MIM automatically directs messages to this log unless you remove the log (through a REMOVELOG command) or
you provide a different message log.
In this example, this was the result of security problem caused by security not being completely initialized prior to CA MIMGR startup. This resulted in the following security violations:
TSS7250E 151 J=CAMIMGR A=CAMIMGR TYPE=JESSPOOL RESOURCE=PERSTEST.+CAMIMGR.CAMIMGR.STC05369.D0000101.
TSS7257E Unauthorized Access Level for JESSPOOL <PERSTEST.+CAMIMGR.CAMIMGR.STC05369.D0000101.>
Not having access to the spool caused the two S0C3 abends.
There are a couple of options available:
1. Start TSS as subsystem, which would cause TSS to start earlier in the IPL sequence.
2. Define ADDLOG MIMLOG DSNAME=NULLFILE to the MIMINIT member to prevent the MIMLOG from being allocated.