Guardian Procedure Calls Reference Manual

process name consisting of more than five characters will fail with an error 20. Notification
of this failure is not sent to the process reading $RECEIVE.
• Opening an unconverted (C-series format) process from a high-PIN process.
A high-PIN process cannot open an unconverted process unless the unconverted process has
the HIGHREQUESTERS object-file attribute set. If a high-PIN prmcess attempts to open a low-PIN
process that does not have this attribute set, the high-PIN process receives file-system error
560.
DEFINE Considerations
• The filename or pathname parameter can be a DEFINE name; FILE_OPEN_ uses the file
name given by the DEFINE as the name of the object to be opened. If you specify a CLASS
TAPE DEFINE without the DEVICE attribute, the system selects the tape drive to be opened. A
CLASS TAPE DEFINE has other effects when supplied to FILE_OPEN_; see Appendix E: DEFINEs
for further information about DEFINEs.
• If a supplied DEFINE name is a valid name but no such DEFINE exists, the procedure returns
an error 198 (missing DEFINE).
• When performing a backup open of a file originally opened through the use of a DEFINE,
filename must contain the same DEFINE name. The DEFINE must exist and must have the
same value as when the primary open was performed.
Safeguard Considerations
For information on files protected by Safeguard, see the Safeguard Reference Manual.
Restricted-Access Fileset Considerations
When accessing a file in a restricted-access fileset, the super ID (255,255 in the Guardian
environment, 65535 in the OSS environment) is restricted by the same file permissions and owner
privileges as any other user ID.
Executable files that have the PRIVSETID file privilege and that are started by super ID can perform
privileged switch ID operations (for example, setuid()) to switch to another ID and then access
files in restricted-access filesets as that ID. Executable files without the PRIV_SETID file privilege that
perform privileged switch ID operations are unconditionally denied access to restricted-access
filesets.
Executable files that have the PRIV_SOARFOPEN privilege and that are started by a member of
the Safeguard SECURITY-OSS-ADMINISTRATOR (SOA) group have the appropriate privilege to
use this function on any file in a restricted-access fileset.
Network File System (NFS) clients are not granted SOA group privileges, even if these clients are
accessing the system with a user ID that is a member of the SOA security group.
If a file opened for writing has file privileges such as PRIV_SOARFOPEN or PRIV_SETID, these file
privileges are removed. Only members of the Safeguard SECURITY-PRV-ADMINISTRATOR
(SEC-PRIV-ADMIN or SPA) group are permitted to set file privileges. File privileges can be set using
the setfilepriv() function or the SETFILEPRIV command only.
For more information about restricted-access filesets and file privileges, see the Open System
Services Management and Operations Guide.
OSS Considerations
• To open an OSS file by its pathname, set options.<10> to 1 and specify the pathname
parameter.
• OSS files can be opened only with shared exclusion mode.
FILE_OPEN_ Procedure 469