Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

The following fileset attribute is supported for OSS SEEP management:
SEEPPROTECTED { ON | OFF } — Specifies whether the fileset has OSS SEEP protection set
or not. The default value is OFF. OSS SEEP consultation for access authorization happens
only if the SEEPENABLED attribute of the OSS name server is set to ON.
The following OSS name server attributes are supported for OSS SEEP management:
SEEPENABLED { ON | OFF } — Specifies whether the OSS SEEP needs to be running or not.
If ON, the OSS name server starts the OSS SEEP and sends the access-authorization requests
to the process if an OSS SEEP-protected fileset has been mounted. If the value is OFF, the OSS
name server does not start the OSS SEEP. If the OSS SEEP is running when the attribute is set
to OFF, the process is stopped.
SEEPRESPONSETIMEOUT [ nseconds ] — Specifies the number of seconds that the OSS
name server waits for the OSS SEEP to respond to an authorization request. nseconds can
have a value in the range 1 through 900. There is no option to wait indefinitely. The default
value is 5 seconds, and a null entry for nseconds resets this attribute to the default value.
SEEPPROGFILENAME [ prog-filename ] — Specifies the name of a Guardian local file
containing the Guardian program to be run when the OSS SEEP needs to be started. This
attribute must be defined before the SEEPENABLED attribute can be set to ON. If the
SEEPENABLED attribute is set to ON and an attempt is made to set this field to null, the SCF
command is rejected. The SEEPENABLED attribute must be set to OFF before this field can be
set to null. The default value is no program file, and a null entry for prog-filename resets
this attribute to the default value.
SEEPPROCESSNAME [ process-name ] — Specifies the process name to be assigned to
the OSS SEEP when it is started. process-name must be a local process name. Avoid using
an existing process name because the OSS name server will kill that process before it starts
the OSS SEEP. The default value is no process name, which indicates that the OSS name
server is to generate a process name. If you omit this attribute, it is set to the default value.
SEEPSWAPVOL [ swap-vol | swap-file ]— Specifies a swap volume or file name for the
OSS SEEP. This must be a local name. The default setting is to use KMSF swap space, and a
null entry for swap-vol or swap-file resets this attribute to the default value.
SEEPCPU [ cpu-number | ANY ] — Specifies the CPU in which the primary OSS SEEP runs.
cpu-number can have a value in the range 0 through 15 and ANY. If the value is ANY, the
primary OSS name server’s CPU is chosen. The default value is ANY, and a null entry for
cpu-number resets this attribute to the default value.
SEEPPRI [ priority ] — Specifies the priority at which the OSS SEEP runs. priority can
have a value in the range 1 through 199. The default value is 199, and a null entry for
priority resets this attribute to the default value.
SEEPPARAMTEXT [ startup-param-text ] — Specifies the startup parameter text in the
startup message sent to the OSS SEEP. All text after the attribute’s name is assumed to be part
of “any-text, so this must always be the last attribute value specified in the SCF command
string. The default value is no text, and a null entry for startup-param-text resets this
attribute to the default value. A backup CPU may be specified at the beginning of
startup-param-text. The valid values are 0 through 15. Additional text may be provided
after a semicolon. The maximum length for startup-param-text is 255 characters.
NOTE: Alteration of the OSS SEEP (OSS name server) attributes SEEPPROGFILENAME,
SEEPPROCESSNAME, SEEPSWAPVOL, SEEPCPU, SEEPPRI, and SEEPPARAMTEXT come into effect
only at the start of the OSS SEEP.
Starting and Stopping an OSS SEEP
The OSS name server manages the starting and stopping of the OSS SEEP.
232 Managing Security