OSI/FTAM Programming Guide

NonStop FTAM Programming
HP NonStop OSI/FTAM Programming Guide—528612-001
3-2
APLMGR Process Name
Programmers familiar with Guardian programming concepts will find it useful to know
that a CEPI is a file number, as defined by the NonStop operating system, but has a
negative value.
A CEPI remains allocated until you call the APS_DISCARD_ procedure, one of the four
general-support APS procedures provided by the FTAM API. (For additional
information on these APS procedures, see the OSI/FTAM Programming Reference
Manual.) If the call to the FTAM association establishment procedure
(FTM_INITIALIZE_REQ_) fails to initialize an association, the FTAM API returns a
CEPI value of -1. To obtain error-status information on the condition, call the
APS_STATUS_ procedure with the CEPI parameter defined as -1.
A CEPI and the memory allocated to it can be reused if your application discards the
association context after terminating each association. You use the APS_DISCARD_
procedure for this purpose. You need not use APS_DISCARD_ if you received a CEPI
of -1, because in that case no association was established and no memory was
allocated.
APLMGR Process Name
When establishing an FTAM association in your program, you must provide the name
of the application manager (APLMGR) process in the aplmgr-name parameter of the
FTM_INITIALIZE_REQ_ procedure. The APLMGR process handles several of the
details of establishing the association. The FTAM API, on behalf of the application,
sends the APLMGR process register requests for FTAM associations. The APLMGR
process then determines the subdevices to be used for the associations and the
initiator that will service the association requests. After the APLMGR process selects
the initiator and manages the addition of an initiator subdevice, your program connects
with the designated initiator by way of the FTAM API.
The process of configuring subdevices and requesting associations is outlined in
greater detail in the subsections Subdevices on page 3-3 and How an Association Is
Established on page 3-5.
OSI Addresses and Common Names
NonStop initiators use OSI addresses to establish communication with remote FTAM
responders. In establishing an FTAM association using the FTM_INITIALIZE_REQ_
procedure, you must provide the necessary OSI addresses or common names for the
local initiator and remote responder via the local-appl and remote-appl
parameters. Common names simplify specification of the four OSI address
components: presentation selector (PSEL), session selector (SSEL), transport selector
(TSEL), and network service access point (NSAP). A common name allows you to
specify the OSI address components with a single identifier. The NonStop Subsystem
Note. An FTAM CEPI identifies associations with an initiator rather than with a TAPS process.
As such, FTAM and OSI/AS CEPIs are not equivalent and should not be used in the same
program. NonStop FTAM applications should not combine FTAM API and OSI/AS API
procedures.