Pathway/iTS System Management Manual (G06.24+)

Maintaining Pathway/iTS Objects
HP NonStop Pathway/iTS System Management Manual—426748-002
4-23
Terminal-Specific Problems
PATHMON Configuration and TCP Object Information
Make the PATHCTL file available to your service provider. Also, use PATHCOM
commands to display information about the TCP at the time of the problem, as follows:
>PATHCOM $<pm>
=INFO tcp
=EXIT
where pm is the name of your PATHMON process and tcp is the name of a TCP.
Requester Object Files and SCREEN COBOL or User
Conversion Source Code
Include the requester object (POBJ) file or files when collecting data about a TCP
problem. Also provide the SCREEN COBOL source code, including copy libraries, if
the problem deals with TCP logic handling within a program unit.
If the TCP problem involves user conversions, include the source code for the user
conversion routine.
Terminal-Specific Problems
Collect the following information if you detect a problem with a terminal or other TERM
object:
•
The PATHMON configuration file, PATHCTL
•
A PATHMON process dump and a TCP dump
•
Status detail; at the system prompt, perform the following:
STATUS TERM *, DETAIL
•
The requester source code and object module or modules
•
Terminal or device type and access method
SCREEN-COBOL-Specific Problems
Collect the following information if you detect a problem with SCREEN COBOL:
•
Server source code and object modules for run-time errors.
•
For problems involving SEND processing, descriptions of screens to access and
function keys to press to execute the SEND statement.
•
The SCOBOLX, COBOLX2, and SYMSERV object files used to compile the
requester.
•
The SCREEN COBOL source code files for the requester.
•
The SCREEN COBOL object code (POBJ) file or files.