Open System Services Programmer's Guide

3. Open the OSS SEEP for access-authorization requests
4. Send the handshake message, and after an OSS SEEP reply, change the OSS SEEP's state to
RUNNING
The OSS SEEP runs with a userid of SUPER.SUPER.
The backup OSS name server does a backup open of the OSS SEEP when the primary OSS name
server completes the OSS SEEP start.
Each time the OSS name server starts the OSS SEEP, it first attempts to kill any process with the
same process name. An EMS message notes this action. If the OSS name server determines that
the OSS SEEP was not started, it does not send messages to the OSS SEEP until it successfully kills
the process and restarts it. Be careful to avoid name collisions.
Stopping an OSS SEEP
When the OSS SEEP is required to be stopped, the OSS name server does a close of the OSS
SEEP and waits for the process death message. The OSS name server expects the OSS SEEP to
perform any necessary cleanup and stop itself upon receiving the final close message, but will kill
it if it does not stop in a timely manner. Each of the following conditions trigger an OSS SEEP stop:
• When the OSS name server's SEEPENABLED attribute is changed from ON to OFF
• During fileset unmount, if it is the only OSS SEEP-protected fileset mounted in the controlling
OSS name server
• When the SEEPPROTECTED attribute of a mounted fileset is changed from ON to OFF, if the
OSS SEEP is running and if there are no other OSS SEEP-protected filesets mounted under the
OSS name server
The OSS name server performs a graceful stop by closing the OSS SEEP. After receiving an OSS
SEEP death message, the OSS SEEP's state is changed to STOPPED. The OSS SEEP is killed if the
OSS SEEP death message is not received within a predefined timeout period of 30 seconds.
The backup OSS name server does a close of the OSS SEEP when the primary OSS name server
closes the OSS SEEP, which results in the graceful stop of the OSS SEEP.
OSS SEEP Consultation
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. After the path name resolution, an authorization
request containing the final resolved path name is sent to the OSS SEEP. The OSS SEEP is expected
to respond with one of the following rulings within the configured timeout period:
• YES — access approved
• NO — access denied
• NORECORD — no OSS SEEP ruling
The OSS name server communicates with the OSS SEEP by opening the OSS SEEP and then sending
messages using the file system APIs. Two message types are supported, one for the handshake
message and the other for the authorization request. (During the OSS SEEP startup, the OSS name
server sends the OSS SEEP a handshake message to determine the OSS SEEP’s readiness to accept
authorization requests.)
OSS SEEP Programming 275