The client received the following messages:
SARDBI23 VIEW.SYSTEM1 Data file(s) at 91% utilization
SARDBI23 VIEW.SYSTEM1 Data file(s) at 92% utilization
SARDBI23 VIEW.SYSTEM1 Data file(s) at 93% utilization
The database has 9 data extents (view_hlq.SARDBASE.D0000001 -D0000009) and 13 index extents(view_hlq.SARDBASE.I0000001 - I0000013).
It is understood of needing to use SARDBASE ADDDS DATA ... to add a new data extent.
1) Is there an issue with having more indices than data?
2) Is this a dynamic ADD?
Is a SARSTC task recycle needed with an ADD?
3) Can data extents be allocated with different space allocations?
Is there a limit or constraint?
Running a SARDBASE STATUS FULL, will provide information regarding Database space usage:
//XXXXXXXX JOB ...
//STEP1 EXEC PGM=SARDBASE,PARM='view_hlq' <=== Modify DB bname
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD <=== Modify, if used
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
It is possible to have more index extents than data extents if the database primarily holds job run JCL output.
In this case, a file will not be large, but it will still need to have all of the requisite index records.
Runs of SARDBASE ADDDS DATA/INDEX can be done "on the fly" and do not require a recycle of the SARSTC task.
View knows what kind of extents (data or index) the database has and how many of each, so an ADDDS statement adds one more extent of that type.
You can vary the number of cylinders that are done with each allocation, depending on what space is available.
The limit of the number of cylinders per extent is 32,760.
The limit of database data extents is 255.
The limit of database index extents is 255.