HP-UX SNAplus2 R7 NOF Programmer's Guide

Writing NOF Applications
Windows Considerations
This section describes operating system issues that you need to consider when writing NOF applications for use on
Windows clients.
2.2.1 NOF API Entry Points for Windows
A Windows NOF application accesses the NOF API using the following entry point function calls:
nof
Issues a NOF verb synchronously. SNAplus2 does not return control to the application until verb processing
has finished.
An application can use this entry point only if the application can suspend while waiting for SNAplus2 to
completely process a verb.
nof_async
Issues a NOF verb asynchronously. SNAplus2 returns control to the application immediately, with a returned
value indicating whether verb processing is still in progress or has completed. If the returned value indicates
that verb processing is still in progress, it will later complete asynchronously; SNAplus2 indicates the
completion by signaling an event handle supplied by the application. In cases when SNAplus2 is able
to completely process the request, the event handle will not be signaled.
An application must use this entry point if it cannot suspend while waiting for SNAplus2 to completely
process a verb.
The
nof and nof_async entry points are defined in the NOF header file winnof.h; this file is installed in
the subdirectory /sdk within the directory where you installed the Windows Client software. Parameter types
such as AP_UINT32, used in these entry points and in the NOF VCBs, are defined in the common header file
values_c.h, which is installed in the same directory and is included by the NOF header file winnof.h.
Synchronous Entry Point: nof
An application uses the nof entry point to issue a NOF verb synchronously. SNAplus2 does not return control to
the application until verb processing has finished.
Function Call
void WINAPI nof (
AP_UINT32 target_handle,
void * nofvcb
);
Supplied Parameters
An application supplies the following parameters when it uses the nof entry point:
target_handle
An identifier that the application uses to identify the target SNAplus2 node or file. This parameter is supplied
in one of the following ways:
• For the following verbs, this parameter is not supplied; set it to 0 (zero). If the verb completes successfully,
SNAplus2 returns the target handle as one of the VCB parameters. The application then uses the target
handle for subsequent verbs.
• CONNECT_NODE (to access a running node, or to access the node on a server where the SNAplus2
software is started but the node is not yet started)
• OPEN_FILE (to access the domain configuration file or the SNA network data file)
• For the following verbs, the application supplies a null value:
• QUERY_NODE_ALL (to obtain a list of running nodes)
69