CAS9125E--CAS9105E STARTING CAS9 ON Z/OS 2.4 REOCCURRED--BUT AFTER IPL

Products

• COMMON SERVICES FOR Z/OS
• Common Services

Issue/Introduction

We have received this text from customer (note: customer agreed on opening this new case      in-

stead of reopening a previous case--since the problem reoccurred but after IPL):

-

 

I request the reopening of said case or the opening of a new case, as CAIRIM (CAS9) had already

been activated (without IPL) according to manual and past guidelines, but after an IPL          CAS9

presented an error:

SYSLOG:

S CAS9
.HASP100 CAS9     ON STCINRDR
IEF695I START CAS9     WITH JOBNAME CAS9     IS ASSIGNED TO USER CAS9
, GROUP group_ID
.HASP373 CAS9     STARTED
AOF571I 08:34:50 : CAS9 SUBSYSTEM STATUS FOR JOB CAS9 IS ACTIVE - 890
ACTIVE MESSAGE RECEIVED
CCSI200I CCSAAA - INITIALIZATION STARTED
IEE252I MEMBER CAIMST00 FOUND IN SYS1.PARMLIB
CCSI201I CCSAAA - INITIALIZATION COMPLETED
CAS9075I - SERVICE(CA-RIM/BASE ) VERS(1500) GENLVL(F000AS900)
CAS9125E - INVALID DATA: * PARMLIB SERVICE FAILURE. CAMASTER NOT
INITIALIZED.
CAS9105E - INITIALIZATION ERROR - DYNAMIC PRODUCT INITIALIZATION ABORTED
*CAS9173E - ERRORS DETECTED DURING CAIRIM INITIALIZATION
AOF571I 08:34:51 : CAS9 SUBSYSTEM STATUS FOR JOB CAS9 IS BREAKING 898
- SUBSYSTEM HAS SUFFERED A NON RECOVERABLE ERROR

-
 

Note: group_ID is masked out from the original.

Environment

OS : z/OS
   
Release : 15.0

Component : CA Resource Initialization Manager (Comm)

Cause

-

Resolution

a. Customer changed on member CAIMST00 in SYS1.PARMLIBX as follows--for CAMASTER to start at IPL time:

From:

CAMSINIT NOSTART, 
 JOBNAME (CAMASTER)
    
To:
    
CAMSINIT START, 
 JOBNAME (CAMASTER)
   
-
   
b. Customer used the instructions on this page to override the CAHCHECK component address space so it does not start automatically at  IPL time:

Optional CAIMST20 Logical Parmlib Concatenation Member


Note: 'b.' was a secondary problem resolved at the end of case history.