OPSINFO('CAS9STATUS') = INIT When CAS9 Had Errors

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

We had the following errors within CAS9:

CAS9125E - INVALID DATA: xxxxxx

CAS9173E - ERRORS DETECTED DURING CAIRIM INITIALIZATION

When the OPSINFO('CAS9STATUS') command was executed, the result was INIT and we are curious to know if this is to be expected.

 

OPSMVS issued the OPSINFO(‘CAS9STATUS’), the response came back INIT so the SSM flag was set to UP and tasks attempted to initialize unsuccessfully.   Should the response have been NOTINIT due to CAS9 errors or was the INIT response correct?

 

Environment

Release : 14.0

Component : OPS/MVS

Resolution

The status of "INIT" is correct from the OPSINFO('CAS9STATUS') function. This function is verifying LMP services are available, which they are. In your case it was only the CA 7 initialization that was not completed properly.
If you start OPS before CAS9 you can even monitor if the specific products have been initialized. For example, CAS9 issues this message and API event for CA-7:

Message event that can be intercepted with a message rule )MSG CAS9130I:

CAS9130I - MODULE L2B3INIT COMPLETE, RC=00

API event that can be intercepted with an API rule )API CASTATE: 

 State of CA-7 is INITDONE