OSI/FTAM Programming Guide

NonStop FTAM Programming
HP NonStop OSI/FTAM Programming Guide—528612-001
3-7
Wait and Nowait Modes
9. The OSI manager chooses a TAPS subdevice name and sends a request to the
local TSP server process to add a subdevice using this name. This request
includes the name of the local NSP server process.
10. The TSP process builds a TSP subdevice name from the TAPS subdevice name,
adds the TSP subdevice, and responds to the OSI manager.
11. The OSI manager then sends a request to the local TAPS server process to add a
subdevice, using the name chosen in Step 9. This request includes the name of
the TSP process.
12. The TAPS process adds the subdevice and responds to the OSI manager.
13. The OSI manager returns the subdevice name and the local and remote OSI
addresses to the initiator’s OSI/AS API.
14. On behalf of the initiator, the OSI/AS API opens the TAPS subdevice and sends a
message, including the OSI address, to request a connection through that
subdevice.
15. TAPS sends a “connect” register request to the selected TSP process.
16. The TSP process establishes a connection through the NSP process. If the
FTM_INITIALIZE_REQ_ call was made in wait mode, the FTAM API returns to the
application a connection endpoint identifier (CEPI) in the cepi output parameter of
the FTM_INITIALIZE_REQ_ procedure.
17. The NSP process forwards the request for an association via the appropriate
controller over the network to the responding system where it is received as an
indication.
18. The responding system processes the indication and sends back a response,
which the NonStop initiating system receives as a confirm. Your application
program first calls the APS_EVENT_RECEIVE_ procedure to determine that an
initialize-confirm event has been received; it calls APS_STATUS_ and then the
FTM_INITIALIZE_CNF_ procedure to retrieve the results of the association
request.
Wait and Nowait Modes
An OSI association can be established in either of two modes: wait mode or nowait
mode. When you identify wait mode or nowait mode for an association, you specify the
way in which I/O operations in procedure calls are to be handled. To set wait or nowait
operation for your application, use the wait-mode parameter in the
FTM_INITIALIZE_REQ_ procedure.
Note. It is essential to the success of your application that you understand the operating mode
you are using in your application and that programming remains consistent with the wait mode
or nowait mode of each association.