OSI/FTAM Programming Guide

Using FTM Procedure Calls
HP NonStop OSI/FTAM Programming Guide—528612-001
4-7
Setting Procedure Parameters
code, to obtain the details of an error at this stage, call APS_STATUS_, specifying
as input the CEPI returned by the FTM_INITIALIZE_REQ_ procedure for this
association.
a. If the association is in nowait mode, call MFM_AWAITIOX_ to wait for
completion of the APS_EVENT_RECEIVE_ call and to obtain the status code.
A status code of ZAPS-VAL-STATUS-EVENT means you have received an
event.
3. If you have received an event, call APS_STATUS_ to determine which event. If the
event code is ZFTM-VAL-EVT-INITIALIZE-CNF, you have received an initialize
confirm.
4. Next, call FTM_INITIALIZE_CNF_ to retrieve the data sent in the confirm.
If the state-result value is ZFTM-VAL-STATE-SUCCESS and the
action-result value is ZFTM-VAL-ACTION-SUCCESS, the association has
been successfully established, and you can start to use it.
Check any negotiable parameters (service-class, func-units,
attrib-groups, and contents-type-list). Determine whether during the
negotiation process, the responder removed or reset any functional units from the
func-units parameter. If it did, the application must determine whether it can
continue under the current constraints.
If the state-result value is not ZFTM-VAL-STATE-SUCCESS or if you receive
notice of an event other than an initialize-confirm event (an abort event, for
example), the association has not been established although a CEPI exists. Clear
the context information for the association by calling APS_DISCARD_. Then, if you
wish to request another association, start the sequence again by calling the
FTM_INITIALIZE_REQ_ procedure.
Setting Procedure Parameters
To give details about the association to establish, use these parameters of the
FTM_INITIALIZE_REQ_ procedure:
1. The aplmgr-name (ZAPS-DDL-FILENAME) parameter is the Guardian process
name of the APLMGR used when establishing an association. You must know the
name of the APLMGR process being used to establish the FTAM associations in
your program.
2. The local-appl (ZAPS-DDL-APPL-ADDR) and remote-appl
(ZAPS-DDL-CHAR32) parameters identify the common name or OSI address of
the local or remote application entity, respectively.
You must provide a value for the remote-appl parameter, which specifies the
common name or OSI address of the called FTAM responder.
The local-appl parameter is optional. If you do not supply the local-appl
parameter, the value defaults to the common name configured for the initiator when
it was started. If your system has several initiators associated with different OSI