OSI/TS Configuration and Management Manual

Introduction
OSI/TS Configuration and Management Manual—424831-001
1-13
PTrace
PTrace
PTrace selects, formats, and displays trace data that has been gathered by the SCF
TRACE command. More detailed information on the PTrace displays for the OSI/TS
subsystem is in the OSI/TS SCF Reference Manual.
Inspect
Inspect is a tool for debugging program code. It is used to check application program
code when troubleshooting problems in your OSI/TS subsystem. More detailed
information on Inspect is in the INSPECT Manual.
NonStop Programming Considerations
For NonStop operation, a TSP process can be configured to have a backup process. If
the primary process fails, control automatically passes to the backup. A CPU switch
aborts and releases all active transport connections. Pending file-system requests are
completed with a file-system error. OSI/TS maintains subdevice configurations and
opens, so the application can immediately re-establish a lost connection and retry
unsuccessful requests.
The following events cause a CPU switch:
•
User issues an SCF PRIMARY command
•
Primary CPU fails
•
Primary process fails
The transport protocol and the internet protocol are implemented in nonprivileged
processes.
G-Series Compatability
The Network Service Provider of OSI/TS are X25AM, TCPIP and TLAM (PAM in G06
and above release). An application running over OSI/TS can use any of these Network
Service Providers.
Some Expand networks may have some D-series systems, some G-series systems. It is
possible that the application, OSI/AS, OSI/TS and either X25AM, TCP/IP or TLAM
(PAM in G06 and above release) are running on different nodes.
Figure A-9, D to G Communication
shows an OSI/AS running on a D-series system
communicating with a OSI/TS running on a G-series system through the Expand lines.
The NSP on D-series can be X25AM, TCP/IP or TLAM (but, TLAM can be used only if
OSI/AS running on G-series is a D40 release , that is, T9570D4x).