Performance impact when VGET used excessively on CA Workload Automation ESP Edition

Products

• ESP Workload Automation

Issue/Introduction

Issue/Problem/Symptoms: 

Performance impact when VGET used excessively on CA Workload Automation ESP Edition

Environment:  

CA WA ESP Edition Z/OS 

Cause: 

The VGET command is performed to retrieve information from the Global Variable table in CA Workload Automation ESP Edition. The Table is stored in the INDEX file, so when there are 1,000's of VGETs being performed, the INDEX file will get backed up with requests and the system will slow down. Therefore excessive use of this command will cause negative performance impact.

The VGET command runs at application generation phase, and application process phase each time a job is submitted. 

Resolution/Workaround:

The following logic will make sure VGET only runs once at the application generation phase:

IF ESP_APPL_GEN THEN DO 
VGET V1 TABLE(GVT) 

……

VGET VN TABLE(GVT) 
ENDDO 
ELSE DO 
DV1=WOBDATA('SAVE','V1') 
….

DVN=WOBDATA('SAVE','VN') 
ENDDO 

DATA_OBJECT SAVE 
SETVAR V1=%DV1

…..

 SETVAR VN=%DVN

ENDJOB 

Additional Information:

See “DATA_OBJECT Statement: Set Data Repositories” on “Command Reference Guide” for more detail.

Environment

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