OSI/FTAM Configuration and Management Manual

FTAM Troubleshooting
OSI/FTAM Configuration and Management Manual—421944-001
6-12
Types of Problems
These SCF commands are most useful for troubleshooting when an association has not
yet been established and when you are troubleshooting capacity or performance
problems. Possible problems that can be indicated by the information returned by SCF
commands are incorrect common name or address information, no activity on the
association, or product version incompatibilities.
For general information concerning SCF (including a description of the LISTDEV
command), see the Subsystem Control Facility (SCF) Reference Manual (for D-series
releases) or the SCF Reference Manual for G-Series Releases. For descriptions of the
SCF commands for the FTAM and APLMGR subsystems, see the OSI/FTAM and
OSI/APLMGR SCF Reference Manual. For descriptions of the SCF commands for
processes in underlying subsystems (OSI/AS for TAPS processes, OSI/TS for TSP
processes, and X25AM, TLAM, PAM, or TCP/IP for NSP processes), refer to the
manuals listed in FTAM Manuals
on page xviii and Related Manuals on page xx.
Types of Problems
Following are descriptions of the main types of problems you might encounter when
using Tandem FTAM:
•
Configuration Errors on this page
•
Interoperability Problems on page 6-19
•
System Problems on page 6-20
•
Capacity and Performance Problems on page 6-20
•
Tandem Software Internal Errors on page 6-20
When troubleshooting, the steps you should take and the tools you should use depend on
the type of problem. The following pages suggest strategies and tools for
troubleshooting each type of problem.
Configuration Errors
Configuration errors are a common cause of problems in running Tandem FTAM
applications. Configuration of the underlying OSI layers is very flexible and, therefore,
complex. Because SCF provides no automatic semantic checking of OSI configurations,
such errors often are not detected until you try to run your application.
Most of the complexity of a configuration for Tandem FTAM is in the underlying
OSI/AS configuration, which is where configuration errors are most likely to occur.