The new Common Services (CCS) 15.0 was installed on an LPAR with z/OS 2.4 and upon executing CAIRIM (CAS9)
messages CAS9125E--CAS9105E plus AOF571I occurred:
START CAS9,,,AUTOCMDS .HASP100 CAS9 ON STCINRDR IEF695I START CAS9 WITH JOBNAME CAS9 IS ASSIGNED TO USER CAS9.HASP373 CAS9 STARTED CAS9075I - SERVICE(CA-RIM/BASE ) VERS(1500) GENLVL(F000AS900) AOF571I 09:21:27 : CAS9 SUBSYSTEM STATUS FOR JOB CAS9 IS ACTIVE - 627 ACTIVE MESSAGE RECEIVED CAS9125E - INVALID DATA: * PARMLIB SERVICE FAILURE. CAMASTER NOT INITIALIZED. CAS9105E - INITIALIZATION ERROR - DYNAMIC PRODUCT INITIALIZATION ABORTEDCAS9173E - ERRORS DETECTED DURING CAIRIM INITIALIZATION AOF571I 09:21:27 : CAS9 SUBSYSTEM STATUS FOR JOB CAS9 IS BREAKING 631 - SUBSYSTEM HAS SUFFERED A NON RECOVERABLE ERROR
Most likely an older Common Services library was concatenated ahead of the updated r15.0 library in the system linklist
Additional items that were suggested/checked prior to discovering the Linklist mismatch:
1. As the message says, CAMASTER is not running. So, could you check what happened with CAMASTER? Did it ever start?
It should be starting early in the IPL. No JCL is needed, but you should add the CAW0LINK and CAW0PLD into the LINKLIST.
By doing this CAMASTER will start during the IPL.
Common Components and Services for z/OS 15.0 Target Libraries--see "CAI.CAW0LINK" and "CAI.CAW0PLD":