Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)
For J06.03 and later J-series RVUs, H06.08 and later H-series RVUs, and G06.30 and later G-series
RVUs, the other values are the same as the preceding table, but these default values are used for
INODECACHE and LINKCACHE:
Multiple-Enclosure SystemPreconfigured or Single-Enclosure
System
Attribute
6400064000INODECACHE
6400064000LINKCACHE
For J06.15 and later J-series RVUs and H06.26 and later H-series RVUs, the other values are the
same as the two preceding tables, and these default values are used for OSS SEEP-related attributes:
Multiple-Enclosure SystemPreconfigured or Single-Enclosure
System
Attribute
OFFOFFSEEPENABLED
55SEEPRESPONSETIMEOUT
NULLNULLSEEPPROGFILENAME
NULLNULLSEEPPROCESSNAME
NULLNULLSEEPSWAPVOL
ANYANYSEEPCPU
199199SEEPPRI
NULLNULLSEEPPARAMTEXT
If your system has been upgraded from a G05.00 or later G-series RVU, the OSS Monitor
automatically creates an initial ZOSSSERV file containing the information from the older system’s
ZPOSSERV file.
If your system has been upgraded from a G-series RVU preceding G05.00, the OSS Monitor
automatically creates an initial ZOSSSERV file containing the information from the older system’s
ZPCONFIG and ZPMNTTAB files.
If your system is upgraded to a G06.17 or later G-series RVU, the OSS Monitor automatically
upgrades an existing ZOSSSERV file.
Figure 15 shows how the OSS name server entries in the ZOSSSERV file correspond to processes,
disk files, and disk volumes. The entries control:
• OSS name server caching
• Request timeout between an OSS name server and an SQLCAT
• Processor in which each member of the process pair normally runs
• OSS SEEP creation and communication
NOTE:
Beginning with the J06.15 and H06.26 RVUs, if an OSS SEEP is configured, the OSS name server
creates and manages it based on its ZOSSSERV file attributes. The OSS name server consults the
OSS SEEP for operations on files in OSS SEEP-protected Version 3 catalog filesets if the OSS SEEP
is running. For more information about OSS SEEP, see “Using an OSS Security Event-Exit Process
(SEEP)” (page 231).
Configuration Files 109