CAIRIM initialization can fail if the CAMASTER address space is not active

Products

COMMON SERVICES FOR Z/OS Common Services Datacom/AD

Issue/Introduction

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(1500) GENLVL(F000AW100)       
 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 r15.0 executing in a z/OS environmment.

Cause

Possible problem with Linklist is preventing proper execution of Common Services initiation at IPL.

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

Currently, the CAMASTER address space is required by the latest Datacom releases as well as CAIENF/USS v15.0. It is anticipated that other CA products will follow suit in the near future. The CAMASTER is one of several CCS components included in FMID, CAS9F00, which is included in the Common Services r15.0 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 can be found under the "Common Components " section of the Common Services r15.0 documentation.