OSI Troubleshooting Guide, May 1997

16 Chapter 1
Interoperability Testing
Interpreting FTAM Errors
Interpreting FTAM Errors
Table 1-1 may help you to find what caused your FTAM test to fail.
1. Check the field labeled “Diagnostic”.
If this field is present, look for a text string labeled “further details”
for the cause.
2. Look at the line after “FAILED”. The operation that failed is listed.
Table 1-1 FTAM Call Errors
FTAM Call Reason Corrective Action
ft_aeactivation() FTAM not correctly
installed.
Run swverify on the FTAM
fileset to verify that all
components are installed.
OTS stack not up. Run the Status operation
under Session or Transport to
verify.
ft_connect() Incorrect address
specified.
Recheck the value of the
Presentation address specified
and the value configured for
the remote.
Incorrect User ID. Check user name and
password, usually corresponds
to the remote.
Remote stack not up. Recheck stack.
Responder not running. Repeat the verification
described in the pre-test
section.
Lower Layer Problem. Go back to the step you were
on and continue.
ft_select() Incorrect source file
name.
Check the source file name
and correct.