The the following information was shown after a "CA11 DIS SPACE" was issued:
AREA TOTAL TOTAL USED
NAME DBID TRACKS BLOCKS BLOCKS FULL
---- ---- -------- -------- -------- ----
IXX 0601 2625 31500 24029 76%
JOB 0601 900 6300 120 1%
STP 0601 2175 15225 332 2%
DSN 0601 9000 63000 584 0%
JHF 0601 3000 21000 8333 39%
AREA FREE
NAME CYLINDERS VOLUME EX DSN
---- --------- ------ -- ---
IXX t 1282 PPA118 01 P.CA11.IXX601
JOB t 1282 PPA118 01 P.CA11.JOB601
STP t 1282 PPA118 01 P.CA11.STP601
DSN t 1282 PPA118 01 P.CA11.DSN601
JHF t 1282 PPA118 01 P.CA11.JHF601
What are the options to manage the index space?
The first step, which is usually the best choice, is to run the DBUTLTY program with a DEFRAG DBID=601 command. This command can run while the application is being actively used.
In addition, CA 11 recommends the use of the MANT process to lead out unneeded records from the various CA 11 tables, and the DEFRAG command is most beneficial following the MANT processing. A common approach is to run a CXX report before and after the DEFRAG, to see the net changes to the index space utilization. Note, however, that once the DEFRAG command is initiated, all the work is done as an asynchronous process by the MUF itself, and not in the job's address space, so do not run the "After" CXX report in the same step as the Defrag, but wait a minute or so to do this. A first DBUTLTY step with this input could be run:
//SYSIN DD *
COMM DBID=601,OPTION=STATS
REPORT DBID=601,AREA=CXX,TYPE=A
DEFRAG DBID=601
/*
Then a "Wait" step that sleeps 40 or 60 seconds could be added, and then run the final CXX report after that.
This method will usually provide the best method for managing the index space for a Datacom database. If this does not resolve the problems, please open a support case for assistance.
As always, please contact Broadcom support for Datacom if you have further questions.