CA WA ESP CCCHK statements are not processed for some jobs.

Products

• ESP Workload Automation

Issue/Introduction

Issue: 

 CCCHK statements defined at the JOB level don't get processed.  This causes the job status to be posted incorrectly.          

Environment:  

CA Workload Automation ESP Edition release 11.4

Cause: 

If the job name or job qualifier contains an ESPA*** variable, the job name will be different at processing and generation time.  This can cause some statements in the job definition to not be included.   

Example:

TIME2='%ESPAHH%ESPAMN'   

JOB DPRCCOD7.%TIME2   

RUN DAILY   

CCCHK RC(U0206) OK CONTINUE   

CCCHK RC(1:4095) FAIL CONTINUE   

ENDJOB 

 

Resolution:

Use ESPS***(Scheduled) time or date variables instead of ESPA****(Actual) variables. The time or date will resolve to when the application was scheduled.  

Example:

TIME2='%ESPSHH%ESPSMN'   

JOB DPRCCOD7.%TIME2   

RUN DAILY   

CCCHK RC(U0206) OK CONTINUE   

CCCHK RC(1:4095) FAIL CONTINUE   

ENDJOB 

 Additional Information:

 For a list of available ESPS*** variables, see the "Built-in Symbolic Variables" section in the "CA Workload Automation ESP Edition Advanced User Guide".  

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Environment

Release: ENCWLA00200-11.4-Workload Automation-Restart Option-EE
Component: