How to increase the space for purge and report GDGs.

Products

• CA-11

Issue/Introduction

 Need to increase the space for the Purge and report GDG dataset

Environment

Release: ELEVEN00200-11-Workload Automation-Restart Option-for Z/OS Schedulers
Component:

Resolution

You can increase the space for the purge and report GDG files by specifying a higher value for PURGSPACE and RPRTSPACE respectively .   Below is information on these parms:

PURGSPACE
Specifies the space to allocate for the PURGE data set. All the parameters are positional.
The first subparameter specifies the following:

CYL
Allocates space in cylinders.

TRK
Allocates space in tracks.

nnnnn
Specifies block size for the purge file. The size must be a valid block size for your DASD device type, a value higher than 370, and evenly divisible by 370. The second subparameter specifies the number of cylinders, tracks, or blocks to allocate.
The third subparameter specifies the number of additional space units to allocate if more space is required. This subparameter is optional. When the purge file is allocated in CYL or TRK, the block size used is 5550. If the PURGSPACE keyword is not specified in the configuration file, the default is PURGSPACE=(05550,(01000,00000)).

 

 

RPRTSPACE
Specifies the space to allocate for RPRTSPACE data set.

All the subparameters are positional.
The first subparameter specifies the following:

CYL
Allocates space in cylinders.

TRK
Allocates space in tracks.

nnnnn
Specifies block size for the report file. The size must be a valid block size for your DASD device type, a value higher than 80, and evenly divisible by 80.
The second subparameter specifies the number of cylinders, tracks, or blocks to allocate.
The third subparameter specifies the number of additional space units to allocate if more space is required. This subparameter is optional.
When the report file is allocated in CYL or TRK, the block size used is 8000.
If the RPRTSPACE keyword is not specified in the configuration file, the default is RPRTSPACE=(08000,(01000,00000)).

 

Many config file parms can be dynamically change using the REFRESH command.   To see if  PURGSPACE and RPRTSPACE are eligible to be dynamically updated, issue the following DBAS command: 

comchar REFRESH CONFDD=*FIELDS

If PURGSPACE and RPRTSPACE show  as being eligible to be refreshed then  issue the following DBAS command to make the change dynamically:

comchar REFRESH CONFDD=SYSIN

You can verify the change has taken place by issuing DBAS command COMCHAR DIS CONF to display current config values in use.

If the parms do not show as being eligible for refresh, CA 11 will have to be cycled to pick up the change.

 

For additional information regarding the config file parms, see  DBAS MAIN Task