Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing Servers
Open System Services Management and Operations Guide—527191-002
4-6
Configuration Files
program numbers and can be used to modify the status of RPC servers available from
your node. RPCINFO provides a means to monitor and change portmap behavior;
RPCINFO is required by the same products that require portmap.
For more information about the RPCINFO process, see the rpcinfo(8) reference
page in the Open System Services Shell and Utilities Reference Manual.
Configuration Files
Each OSS server has its own configuration file requirements. Some OSS servers
share database files. Other servers use text files created in the OSS file system or
maintained in the Guardian environment.
The following subsections describe the configuration files used by each OSS server. All
these files should be secured according to site security procedures so that only a
system administrator can alter or remove them; see the recommendations in
Preventing Security Problems on page 8-28.
Configuration Files Used for the OSS Name Servers
The OSS Monitor uses the following configuration files to manage OSS name server
operation and OSS file access:
•
The ZOSSFSET File on page 4-6
•
The ZOSSPARM File on page 4-12
•
The ZOSSSERV File on page 4-14
•
The Storage-Pool Files on page 4-17
These files must be in the subvolume $SYSTEM.ZXOSSMON. Beginning with the
G05.00 release version update (RVU), all these files except the storage-pool files are
created automatically if they are missing when the OSS Monitor is started.
The ZOSSFSET File
The ZOSSFSET file is an Enscribe alternate-key file that contains the fileset
configuration database. The ZOSSFSET file contains entries that identify the storage-
pool file and operating characteristics for each fileset in the OSS file system. Entries in
this file can be displayed with the SCF INFO FILESET command.
This file must be maintained by the system manager using the SCF ADD FILESET,
ALTER FILESET, DELETE FILESET, or RENAME FILESET command. It must be
present before the root fileset is first mounted.
Caution. If any of these configuration files are accidentally deleted, the current configuration
of the OSS environment is lost. You should make frequent backups for these files.