CAMASTER address space not started after IPL

Document ID : KB000124398
Last Modified Date : 17/01/2019
Show Technical Document Details
Introduction:
After IPL,  CAMASTER address space is not started. 
There are no messages related to CAMASTER in the IPL joblog.



 
Question:
Why CAMASTER address space is not started at IPL time? 
Environment:
COMMON SERVICES 14.1 or 15.0 - z/OS supported releases - 
Answer:
1. Check if the CEI0E10 fmid (CAMASTER) is installed in CA Common Services 14.1 environment.

2. Check if you have a CAIMST00 member in your logical PARMLIB concatenation with the statement NOSTART for CAMASTER as: 
CAMSINIT NOSTART, /* Start up at IPL time */ 
JOBNAME(CAMASTER) /* Job name to use */ 
 
If this is the case, please change it to: 
CAMSINIT  START,      /* Start up at IPL time */ 
JOBNAME(CAMASTER) /* Job name to use */  

3. Check that CAW0LOAD, CAW0PLD and CAW0LINK datasets for COMMON SERVICES 14.1 are accessible and in LINKLIST. 

4. Do IPL again to start CAMASTER.


 
Additional Information:
You can check this documentation at the links: 

https://docops.ca.com/ca-common-services-for-z-os/14-1/en/component-reference/address-spaces/camaster-address-space/optional-caimst00-parmlib-member

https://docops.ca.com/ca-common-services-for-z-os/14-1/en/component-reference/address-spaces/camaster-address-space