JOB failed with CC 32 "THE ESP AUXILIARY ADDRESS IS NOT YET ACTIVE" on CA Workload Automation ESP Edition

Products

• ESP Workload Automation

Issue/Introduction

ESPM  ------------------------------------------------------- ESP ENCORE ACTIVE
OPER ENCPARM STATUS

 

In JOB's output:

 SEVERE ERROR
============
 
        ESP ENCORE IS NOT AVAILABLE.
 
        THE ESP AUXILIARY ADDRESS IS NOT YET ACTIVE.
 
        PLEASE CHECK TO SEE IF ESP HAS BEEN STARTED
        AND HAS COMPLETED ITS INITIALIZATION.
 
        HOWEVER, UNTIL ESP HAS INITIALIZED, IT IS STILL
        POSSIBLE TO RUN JOBS WITH ESP ENCORE AS LONG AS
        MODE=SCAN AND TYPE=INITIAL ARE SPECIFIED.
 
 
 ********************************** End of Data *

 

Environment

Release : 12.0

Component : CA ESP Encore Workload Automation

Resolution

Commonly known causes of :ESP ENCORE IS NOT AVAILABLE. THE ESP AUXILIARY ADDRESS IS NOT YET ACTIVE" are:
- The affecting ESP subsystem does not have "SMFINT ON". This is an initialization statement and is found in the ESP parmlib.
- The master subsystem and its proxies do not share the same ESPGROUP value. This is an initialization statement and is found in the ESP parmlib. In this case, the solution is to set SMFINT ON because this is a tracking system.
- The auxiliary address space is not allowed by security or system setting.