CAIRIM r14.1 fails to initialize and issues message - CAS9125E - INVALID DATA: * SEVERE ERROR PARMLIB DD. CHECK CAIRIM USAGE

Products

• COMMON SERVICES FOR Z/OS
• Common Services
• Xpertware
• Datacom/AD

Issue/Introduction

After the application of PTF RO52581, which is included in the CA Common Services r14.1 Service Level, CAIRIM initialization can fail if the CAMASTER address space is not active.

 

Should the CAMASTER address space fail to initialize correctly, CAIRIM will fail at startup and generate the following messages:

 CAS9075I - SERVICE(CA-RIM/BASE ) VERS(1400) GENLVL(E100AS900)       
 CAS9125E - INVALID DATA: * SEVERE ERROR PARMLIB DD. CHECK CAIRIM USAGE* 
 CAS9105E - INITIALIZATION ERROR - DYNAMIC PRODUCT INITIALIZATION ABORTED
 *CAS9173E - ERRORS DETECTED DURING CAIRIM INITIALIZATION

 

Environment

Common Services r14.1 executing the S1401 Service Level in a z/OS environmment.  

Resolution

To correct this specific error condition, ensure the CAMASTER Address space is successfully initialized prior to CAS9 execution. In general, the only requirements in getting the CAMASTER address space started are:
(1) install the function
(2) define CAW0LINK and CAW0PLD to the system linklist 
(3) If If you are running z/OS releases prior to z/OS 1.13, it is also necessary to define CAW0LPA to LPALSTxx. 

PTF RO52581 provides a Common Service Address Shell and moves early IPL feature checks, formerly performed by CAIRIM, to CAMASTER. During this process, CAMASTER also sets up control blocks that are necessary for successful CAIRIM initialization.

Currently, the CAMASTER address space is required by Datacom v14.0 and CAIENF/USS v14.0. It is anticipated that other CA products will follow suit in the near future. The CAMASTER FMID, CEI0E10, is included in the Common Services r14.1 BASE PAX file and it is a requirement that all BASE FMIDs be installed.

As part of the enhancements introduced with PTF RO52581, it is a good time to update the program properties table to account for CA Common Service Address Space shell. This is done by defining a program properties table entry for the CASERV main program. This PPT entry resides in the SCHEDxx member of the logical PARMLIB concatenation. Place the following PPT statement in the SCHEDxx PARMLIB member:

PPT PGMNAME(CASRVASI)      /* CA-SERV Address Space Control Program */ 
    KEY(4)                 /* EXECUTION KEY                         */ 
    NOSWAP                 /* NON-SWAPPABLE                         */ 
    PRIV                   /* PRIVILEGED                            */ 
    SYST                   /* SYSTEM TASK                           */ 
    LPREF                  /* Long-term PGFIX in non-reconfig stg   */ 
    NOPREF                 /* Short-term PGFIX in reconfig stg      */

 

Note: The above PPT statement will be made available in CAW0OPTN member CASRVASI of the CAW0OPTN data set after the application of PTF RO52583.

You can apply this update dynamically with an operator SET SCH=(xx,yy,zz,L) command, which does not require a z/OS IPL to implement the change. If you do not choose to perform the dynamic update steps specified above, an IPL is necessary to effect this change.

To verify that CAMASTER is active, check the syslog for the following messages:

 CAMS100I CAMASTER INITIALIZATION IN PROGRESS       
 CAMS101I CAMASTER INITIALIZATION COMPLETE 

 

These messages are the only indication you will receive that CAMASTER is initialized and active. It should also be seen that a CAMASTER address space is active on the system.

Additional Information

Details about the CAMASTER Address Space itself as well as the Common Address Space Shell can be found in
the "Address Space" Chapter of the CA Common Services r14.1 Component Reference.