It's probably convenient to just delete the files and clean up the FOF.
SELECT FOF WITH A18 "D"
DELETE FOF
A18 is a record of some stuff that happened to the file referred to by the FOF item. If A18 is blank, the file was already there when the FOF file was refreshed ( like a restore ). Any files created after that time will contain an "N" for new. Then you may see a bunch of "C"s in there. That's a record that someone did a CLEAR-FILE on that file. If the last value in A18 is "D", the file was deleted, so you don't need that FOF item anymore.
On another note, if you have some files that get CLEAR-FILE'd a lot, you'll get a ton of values in A18-A20 in the FOF item. A19 is a date*time*?? stamp of when, and A20 is user*pib who cleared it. If you don't use the FOF to audit CLEAR-FILE activity ( and I haven't met anyone yet who has ), you should execute this command at TCL and add it to your coldstart:
LOG-CLEAR-FILE-OFF
This will prevent the CLEAR-FILE logging in A18, A19, and A20 of the FOF. And if you want to clear out the CLEAR-FILE activity in your existing FOF, let me know. I wrote a program to do it, but I'll need to go find it.
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
Original Message:
Sent: 06-20-2022 18:45
From: Danny Ruckel
Subject: Creating/deleting/RESIZE-ing data sections from a files dictionary
Good afternoon D3 folks!
What is best D3 DBMS practice when it comes to deleting or RESIZE-ing data sections from a files dictionary?
If we don't delete these data sections (we use them as work files when compiling report data) we end resizing too many of these data sections/work files. If I delete them, FOF gets populated with much meaningless data.
Thank you in advance for your helpful reply/ies!
~Doc