Dynamic work data sets that are allocated to the ENF started task
search cancel

Dynamic work data sets that are allocated to the ENF started task

book

Article ID: 65957

calendar_today

Updated On:

Products

COMMON SERVICES FOR Z/OS

Issue/Introduction

What are the work data sets that are allocated to the ENF started task?. 

Environment

Release:
Component: ENF

Resolution

The dynamically allocated work data sets are required by the CAIENF database. They are primarily used as SORTWORK files during the CAIENF backup/archive process. The database work data sets are controlled by the WORKDS parameter in the ENF parameter file (ENFPARM) and must remain allocated for the duration of the CAIENF started task. As an alternative to having these work data sets dynamically allocated, they can be hardcoded as part of the CAIENF started task JCL. This can be accomplished by adding the following DD statements to the ENF procedure:

//CASRT01 DD UNIT=SYSDA,SPACE=(CYL,(20,5))
//CASRT02 DD UNIT=SYSDA,SPACE=(CYL,(20,5))
//CASRT03 DD UNIT=SYSDA,SPACE=(CYL,(20,5))
//CASRT04 DD UNIT=SYSDA,SPACE=(CYL,(20,5))
//CASRT05 DD UNIT=SYSDA,SPACE=(CYL,(20,5))

The space requests for WORKDS are represented in cylinder quantities. Please note the primary space allocation of the work data sets may be decreased if not recording event data to the CAIENF database. If using WORKDS as opposed to hard-coding the DD statements, the minimum primary space request allowed is 5 cylinders. If you specify a lower value, the routines which internally process WORKDS will reset the primary value to 5. If you hardcode the work data sets in the CAIENF started task procedure, the space values can be broken down into tracks. No DCB information is required for allocation of the database work data sets.

If it is decided at a later date to activate event recording and the work data sets are hardcoded with a small space allocation, the allocation must be increased to avoid performance problems with backup/archive routines. Larger work data sets allow the backup/archive routines to sort potential backup/archive event data quicker.