The
spdsclean utility uses the libnames.parm and spdsserv.parms files as input:
libnames.parm
the libnames.parm
parameter file establishes the names and file storage locations of
SPD Server domains that are available on an SPD Server host. The domains are defined in LIBNAME=
specifications. At a minimum, a LIBNAME= specification specifies the
domain name and a file system in a PATHNAME= attribute. The administrator can also specify
path options for SPD Server data files, index files, work files, and metadata files.
For more information
about the libnames.parm parameter file, see Configuring Server Domains.
spdsserv.parm parameter file
The spdsserv.parm parameter file defines the SPD Server operating parameters. The
WORKPATH= statement in this file lists the directories
that SPD Server uses for transient or working disk storage.
The spdsclean utility operates on the following files:
When you create SPD Server access control lists (ACLs), hidden ACL files are created
in the primary directory of the domain. The hidden files are named .spres11* and .sppro11*.
The hidden ACL files retain
the state of the ACLs that were defined for the domain resources. Typically, you should
not delete ACL files.
domain state file
The domain state file is also known as .spdslib11. The domain state file retains the
set of
directory paths that are configured for the domain. The directory path information
is stored as an ordered list for each of the following domain storage classes:
As you make path assignments over the life of the domain, the new directories are
appended to the end of the ordered lists for METAPATH=,
DATAPATH=, and INDEXPATH= storage classes. The order of directories listed in the
.spdslib11 file defines the order of data cycling and overflow sequencing for each
of the respective classes.
residual lock file
When SPD Server accesses a
data resource or table that is within a domain, it creates a lock file. The local operating environment
uses the locking mechanism
to ensure that proper member-level locking is observed by all SPD Server processes
that access the named data resource. If a server domainproxy process terminates unexpectedly,
the residual lock files remain in the domain. Residual lock files do not cause problems
when the files are accessed again because the lock belongs to the operating environment.
The lock is cleared when the process terminates and does not depend on the presence
of the file itself. However, unused residual lock files can accumulate and create
clutter in your primary domain directory.
residual temporary file
SPD Server creates temporary files when you create a new resource in a domain. If
the SPD Server server domainproxy process terminates unexpectedly while you are
creating a new file, the residual temporary files remain in the domain directories.
These temporary files contain a leading dollar sign character ($) in the name, which
prevents the residual temporary files from appearing in a PROC DATASETS directory
listing. You should periodically remove old or abandoned residual temporary files
that unexpected proxy process terminations created.
system-specific temporary files
SPD Server uses pre-assigned directories (which vary by operating environment) that
are designated
for temporary files. The pre-assigned directories hold files, logs, and other temporary
entities that SPD Server creates while it is running. SPD Server usually cleans up
these temporary files when it exits. If SPD Server terminates abnormally, these temporary
files might be left in the temporary directory. In UNIX operating environments, the
temporary files usually appear in directories such as /tmp or /var/tmp.
In Windows operating environments, the temporary files are usually
stored in C:/TEMP (or wherever the
user profile is configured to store temporary files).