DBPURGE 99A Copyright (c) 1986 by Allegro Consultants, Inc. Written by Stan Sieler DBPURGE is a utility program that eases the task of purging IMAGE databases. It can be run as a UDC or interactively. It can even handle "damaged" databases. A DBPURGE UDC can be written: dbpurge BASE, PARM=0 RUN DBPURGE;INFO"!BASE";PARM=!PARM ********** Then, to purge a database called "FOO", do: DBPURGE FOO If no root file can be found, then DBPURGE will automatically try to purge "lost" datasets that would have been associated with the root file. Note: if a file with the same name as the root file exists, but cannot be opened, then DBPURGE will *not* purge the datasets unless you specify PARM=1. This prevents accidental purging of non-inuse datasets for an in-use database. If you run DBPURGE with no INFO parameter, it will prompt for a list of databases to purge: RUN DBPURGE or: RUN DBPURGE;PARM=1 If DBPURGE is trying to purge "lost" datasets, it will look for datasets 00..199, and TPI files (names that end in that end n 0A..0Z, 1A..1Z, 9A..9Z). You can exit the interactive program by entering either the command EXIT or a //. PARM bits: Bit# BitValue Meaning ---- -------- -------------------------------------------- 15 1 DAMAGED. Search for "lost" datasets, regardless of whether or not a root file exists. 14 2 NOLOST. Don't look for "lost" datasets, unless DAMAGED is requested *and* the root file cannot be opened (or doesn't exist). 13 4 PLAIN. Purge non-privileged files if found. 12 8 QUIET. Suppress verbose output. 11 16 NOTEMP. Don't search the job/session temporary file directory. 10 32 NOTPI. Don't search for Third Party Indexing (TPI) files. 9 64 DUMB. Don't try to speed things up by checking for possible datasets. Try this option if DBPURGE seems to be skipping some datasets. 8 128 Debug1 7 256 DebugSet1 6 512 Suppress display of version/author banner DBPURGE 20140822