OSI/FTAM Programming Guide

FTAM Application Management
HP NonStop OSI/FTAM Programming Guide—528612-001
6-6
Checking Association Status
For more information on troubleshooting user applications and interoperability
problems, refer to the OSI/FTAM Configuration and Management Manual.
Checking Association Status
The next several pages provide an example of how you can use SCF to get
information about a specific association. When you issue the STATUS SU command
for an FTAM subdevice of a given initiator, you receive addressing information that
shows whether an association has been established. You can also examine the
functional units negotiated over the association to ascertain that these functional units
are acceptable based on what you requested in your program. Examining an
association’s negotiated functional units might be helpful if the responder does not
successfully perform a requested service. An unacceptable set of functional units could
result from a protocol error; you should also check the part of your application that
requested the functional units to make sure that the request is exactly what you
intended.
To obtain status information, issue the SCF STATUS SU command. To issue that
command, you need the name of the subdevice of the initiator, which can be obtained
through the application or through SCF.
To obtain the subdevice name programmatically, call APS_STATUS_ in your program,
specifying as input the CEPI returned on the initialize request for this association, and
print out the device-name parameter. The procedure call returns the full subdevice
name in the format initiator-name.subdevice-name (for more information on
subdevices and CEPIs, see Section 3, NonStop FTAM Programming).
To obtain the subdevice name through the management interface, issue the SCF
command NAMES SU for the associated initiator process. All subdevices returned for
the initiator are active. The subdevice with the highest number in its name was created
most recently. If you are running more than one program, this subdevice name might
not correspond to the association whose status you wish to check. In this case, it is
better to obtain the subdevice name programmatically, as described in the above
paragraph.
Example 6-1 on page 6-8 shows a typical screen display returned by a STATUS SU
command requesting information about an FTAM initiator subdevice.
The addressing information is most significant because it tells you whether or not an
association has been established with the remote system. The Calling Address
contains the local address, or common name, specified in the initialize request; the
Called Address field, the remote address specified in the initialize request; and the
Responding Address field, the actual address the responding system is using for the
communication. (For more information on common names, see Section 3, NonStop
FTAM Programming.) If the association has been established, the values in the Called
Address and Responding Address fields are most likely the same. However, the
responding system can designate another address to use for the communication, in
which case the Responding Address field contains a different value from the one in the