ABEND S0C3 Reason=00000003 MIMDRLOG.MIMDRLOG+335E

book

Article ID: 141244

calendar_today

Updated On:

Products

CA MIM Resource Sharing (MIM) CA MIM Data Sharing (MII) CA MIM Tape Sharing (MIA) CA MIM Message Sharing (MIC)

Issue/Introduction

Multiple ABEND S0C3  Reason=00000003 MIMDRLOG.MIMDRLOG+335E" at a system startup. MIMGR task fails to start.

 

Cause

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.

Environment

Release : 12.5
Component : MII

Resolution

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. 

 

Additional Information

How to Initialize CA Top Secret as a Subsystem

The CA MIM Logging Facility

Attachments