Check ESP Operational data sets and increase their SIZE when needed

Products

• ESP Workload Automation

Issue/Introduction

We are seeing some ESP operational data sets filling up in message log

Environment

Component: ESP Workload Automation
Release:   12.0

Cause

Review maintenance best practices to ensure optimal product performance.

Resolution

1. For VSAM files, include HISTFILE, JOBINDEX, RESFILE, INDEX, COMMQ, EVENTSET, JOBSTATS:

 - Should use IDCAMS LISTCAT with ALL option to check the usage of files
 - For better performance, make sure not use any secondary allocation in INDEX and DATA of the file
 - CYBESUT7 should run periodically (like yearly) to remove aged information from JOBINDEX file
 - CYBESUT8 should run periodically (like yearly) to remove aged information from JOBSTATS file

2.For non-VSAM files:

 - APPLFILE: use OPER LISTAPTF to check the current usage, and run CYBESUT3 to increase
 - TRAKFILE: use OPER LISTTRAK to check the current usage, and run CYBESUT4 to increase
 - EXHFILE: use CYBRMQRY to check the current usage and run CYBRMALC/CYBRMCPY to increase

3. QUEUE: use LISTQ to check the current usage. If need to allocate a bigger one:
 - Stop ESP master and proxies
 - Rename the current QUEUE file to *.old
 - Allocate a bigger one with the name specified in ESPPARM
 - Start ESP Master with parm=QFORM and warm start ESP Proxies

4. CKPT: use LISTCKPT to check the current usage, and run CYBESUT9 to increase.