HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
OPEN_FILE
For all other values of requested_role, this parameter is undefined.
file_info.system_name
Name of the SNAplus2 computer where the file is located.
file_info.file_name
Name of the file. This parameter is an ASCII string of 1–80 characters, followed by a null (
0x00) character.
3.85.4 Returned Parameters: Parameter Check
If the verb does not execute because of a parameter error, SNAplus2 returns the following parameters:
primary_rc
AP_PARAMETER_CHECK
secondary_rc
Possible values are:
AP_INVALID_FILE_NAME
The file_name parameter did not specify a valid configuration file name.
AP_INVALID_FILE_INFO
One of the parameters in the
file_info structure was not valid.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_PARAMETER_CHECK,
which are common to all NOF verbs.
3.85.5 Returned Parameters: State Check
If the verb does not execute because of a state error, SNAplus2 returns the following parameters.
primary_rc
AP_STATE_CHECK
secondary_rc
Possible values are:
AP_CONNECTION_NOT_MADE
SNAplus2 could not set up the local communications path to the file.
AP_FILE_BAD_RECORD
SNAplus2 detected an error in the configuration file. Check the error log file for a message giving more
details of the error.
AP_FILE_ROLE_UNAVAILABLE
The application requested a master or backup configuration file, or the sna.net file, but no master or
backup server was available. This is normally a temporary condition, occurring when a new server is
taking over as master.
If the application is registered to receive server indications, it can check the flags parameter on these
indications to determine when a new server has successfully taken over as master, and then retry the
OPEN_FILE verb. For more information, see Section 4.24, SERVER_INDICATION. Alternatively, it
can simply retry OPEN_FILE at intervals until it succeeds.
AP_INVALID_VERSION
One of the following has occurred:
328