Open System Services Porting Guide (G06.29+, H06.06+, J06.03+)

The GROUP_GETINFO_ procedure retrieves information about a group specified either by group
name or by group ID. A textual description of the group and information as to whether the group
is automatically deleted when the last member is deleted can be obtained using this procedure.
The GROUPMEMBER_GETNEXT_ procedure retrieves a user name or alias associated with a group
ID. All user names and aliases associated with a group ID can be obtained with successive calls
of the procedure.
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.
The following Guardian procedures support some actions on OSS files:
DescriptionProcedure
Completes one previously initiated I/O operation for a Guardian file or
returns ready information for one OSS file.
FILE_COMPLETE_
Enables a set of Guardian and OSS files for completion by subsequent calls
to the FILE_COMPLETE_ procedure.
FILE_COMPLETE_SET_
Provides information about the set of files that are enabled for completionFILE_COMPLETE_GETINFO_
Returns a limited set of information on a file, identified by a file numberFILE_GETINFO_
Returns a limited set of information on a file, identified by a filenameFILE_GETINFOBYNAME_
Returns detailed information about a file, identified by a file numberFILE_GETINFOLIST_
Returns detailed information about a file, identified by a filenameFILE_GETINFOLISTBYNAME_
Returns information about the last message read on the $RECEIVE fileFILE_GETRECEIVEINFO_
Establishes a communication path between an application process and a
file
FILE_OPEN_
144 Migrating Guardian Applications to the OSS Environment