HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
OPEN_FILE
sense_data
The SNA sense data associated with the allocation failure.
3.84.7 Returned Parameters: CNOS Processing Errors
If the verb does not execute because of an error, SNAplus2 returns the following parameters.
primary_rc
AP_CONV_FAILURE_NO_RETRY
The session limits could not be initialized because of a condition that requires action (such as a
configuration mismatch or a session protocol error). Check the SNAplus2 log file for information about
the error condition, and correct it before retrying this verb.
primary_rc
AP_CNOS_PARTNER_LU_REJECT
secondary_rc
AP_CNOS_COMMAND_RACE_REJECT
The verb failed because the specified mode was being accessed by another administration program
(or internally by the SNAplus2 software) for session activation or deactivation, or for session limit
processing. The application should retry the verb, preferably after a timeout to allow the race condition
to be cleared.
3.84.8 Returned Parameters: Other Conditions
Appendix B, Common Return Codes lists further combinations of primary and secondary return codes that are
common to all NOF verbs.
3.85 OPEN_FILE
An application uses this verb to access the SNAplus2 domain configuration file in order to manage domain resources,
or to access the sna.net file in order to manage backup master servers on the SNAplus2 LAN.
This verb must be issued with a null target handle. If it completes successfully, SNAplus2 returns a handle
identifying the file, which the application can then use on other NOF verbs to indicate the target for the verb.
3.85.1 VCB Structure
typedef struct open_file
{
AP_UINT16 opcode; /* verb operation code */
unsigned char reserv2; /* reserved */
unsigned char format; /* reserved */
AP_UINT16 primary_rc; /* primary return code */
AP_UINT32 secondary_rc; /* secondary return code */
CONFIG_FILE file_info; /* definition of file requested */
AP_UINT32 target_handle; /* handle for subsequent verbs */
unsigned char reserv3[4]; /* reserved */
} OPEN_FILE;
326