File Utility Programming (FUP) Reference Manual
FUP Commands
File Utility Program (FUP) Reference Manual—523323-015
2-153
PURGEDATA Guidelines
PARTONLY
purges data in any primary or secondary extents of partitioned files that reside in
fileset-list. If you omit PARTONLY, data is purged from all partitions of
partitioned files—but only if the primary partitions of the files reside in
fileset-list.
PURGEDATA Guidelines
To use PURGEDATA and purge data from a file, you must have write access to
that file or be a super-group user (255, n).
If you try to purge data from an audited file, TMF must be running, and the disk
containing the file must be enabled for TMF.
For a PURGEDATA operation, the FUP process attempts to open the specified file
with exclusive access. If the file cannot be opened with exclusive access, the
PURGEDATA command fails; for example, if the file is already open.
The CLEARONPURGE option set with the FUP SECURE command has no effect
on PURGEDATA. After the PURGEDATA command is executed, the data is
physically present on the disk (but inaccessible) until it is overwritten by new data
or deallocated with the DEALLOCATE command.
PURGEDATA cannot purge SQL files that are not SQL object files. Instead, you
must use SQLCI PURGEDATA.
PURGEDATA command purges the data of a key-sequenced file with increased
limits (EKS file with increased limits) starting from the first secondary partition.
PURGEDATA command purges the data of a key-sequenced file with increased
limits (LKS2 file with increased limits) starting from the primary partition.
PURGEDATA command when executed with fileset-list as primary partition
of a key-sequenced file with increased limits (EKS file with increased limits) and
PARTONLY option, does not purge data in the primary partition.
PURGEDATA Example
To logically purge the data from MYFILE in the current default subvolume:
-PURGEDATA MYFILE
Commands Related to PURGEDATA
COMMAND Function Page
PURGE Deletes a file 2-147
DEALLOCATE Deallocates unused file extents 2-65