Open System Services Porting Guide (G06.24+, H06.03+)

Migrating Guardian Applications to the OSS
Environment
Open System Services Porting Guide—520573-006
8-11
Guardian File System Procedures
The USER_AUTHENTICATE_ procedure is used to verify that a user exists and
optionally to log a user on. Also, USER_AUTHENTICATE_ can get the initial working
directory and the initial program in the OSS environment for the specified user.
The USER_GETINFO_ procedure returns the default attributes of a user specified by
user name, Guardian user ID, or alias. Also, USER_GETINFO_ can get the initial
working directory and the initial program in the OSS environment for the specified user.
The USER_GETNEXT_ procedure obtains the next user name or alias following the
specified name, in the order in which they are stored by the security mechanism in
effect.
Guardian File System Procedures
OSS files can be manipulated using Guardian procedures as well as OSS functions.
This makes OSS files accessible from the Guardian environment using Guardian
procedures, although file access is limited to odd-unstructured files. One reason to use
the Guardian procedures on OSS files is to perform asynchronous (nowait) I/O on OSS
files, an operation that cannot be done using OSS functions. Another reason is to
obtain more detailed information about OSS files than is available using OSS
functions.
Two Guardian procedures map OSS pathnames and Guardian filenames:
•
The PATHNAME_TO_FILENAME_ procedure maps an OSS pathname to the ZYQ
filename of the corresponding regular file. As a special case, if the pathname is in
the Guardian name space (/G), then the pathname is syntactically changed to
Guardian format.
•
The FILENAME_TO_PATHNAME_ procedure maps a Guardian filename to the
corresponding OSS pathname. The pathname returned is the first one found that
the caller has access to. If the resulting pathname represents a file in /G, the
transformation is only syntactic.
For more information on ZYQ names, refer to the Open System Services
Programmer’s Guide.
Access to OSS files using Guardian procedures is limited. In all cases, the filename
parameter (if appropriate) of the underlying object is a Guardian filename, not an OSS
pathname. The only exception to this rule is FILE_OPEN_. Most Guardian procedures
fail with an error code when the file is referenced as an OSS file.