STC 'WSEWSSTC' couldn't be started via CCI: com.ca.endevor.eapi.exception.CCIException: INIT: (RC: 4 DRC: 0 ERC: 0)

Products

• Endevor

Issue/Introduction

WSTOMSTC output show the following error:

com.ca.endevor.eapi.exception.CCIException: INIT:  (RC: 4 DRC: 0 ERC: 0)
  at com.ca.endevor.eapi.STC.init(STC.java:192)
  at com.ca.endevor.eapi.STCPool.spawnSTC(STCPool.java:294)
...

Environment

Endevor Web Services

Endevor 18.1 -19.0

Cause

CCI is not active on the LPAR where WSTOMSTC is running

Resolution

Verify that the CAIENF parameter file contains a DCM(CAS9DCM3) statement. This statement should have been added during CAICCI configuration.

 For CCI to be active in a LPAR, the response from ENF STATUS command must include the message CAS9626I - CAICCI Subsystem is operational

For Example:

CAS9757I - CAICCI Spawn Manager now active        
CAS9649I - CAICCI Interface Manager now active    
CAS9641I - CAICCI Communication Manager now active
CAS9767I - CAICCI Spawn Server now active        
CAS9626I - CAICCI Subsystem is operational     

 

 

Additional Information

Configure the CAICCI SPAWN Facility