Problem Solving
Common Configuration Mistakes
•Incorrect interface name. Specifying an interface name that is not configured will result in warnings, but OTS will still start. If otsstat indicates any links are “NOT RUNNING,” verify these names.
ots_parms Common Mistakes
•If close to the limit of connections available (448 over LAN, 4096 over X.25) through OTS, the ses_reuse_tp_con flag may hold open connections you need to recycle.
•If using CONS/X.25, ensure that the Transport class OTS requests is acceptable to the remote. The tpcons_pref_mux_class parameter determines whether you use class 2 or 4. The parameter tpcons_tp0_only forces class 0.
•Some vendors do not accept the OSI Transport protocol ID carried on X.25 connection requests. This can be disabled with tpcons_null_pid.
local_app Common Mistakes
•Setting the maximum invocations, or inbound associations too low can result in your failing to receive or create connections with remote FTAM applications.
•If you manually edit these files rather than using osiadmin, you should be sure that all FTAM application titles match the ftam_ddn_lookup_path parameter.
remote_app Common Mistakes
•Mistyping a remote application title or alias for FTAM will result in your connection failing.
•Mistyping a remote presentation address for FTAM will result in your connection failing.
66 | Chapter 2 |
