RSC/MP Installation and Configuration Guide

Installation Troubleshooting Step 6. Interpret the Workstation and Host E rror
Mes s ag es
6. Messages from the workstation can reach the target TDP process on the NonStop
host. This requires that the NIF is communicating with the correct port in the
NonStop communications subsystem and that the port is started.
7. The TDP process is able to open and communicate with the designated server
process on the NonStop system. This requires that an RscConnect be established
between the RSC/MP client and the TDP TERM object, that the TERM object is
started, and that the TERM is passing messages to the host server.
Proper interpretation of RSC/MP error messages should help you determine where in
the previous list of conditions the error occurred.
To understand an error message, you must first be able to read the message number.
A typical error contains an error number and extension; these are coded in both
decimal and hexadecimal; for example:
Error 901-0 (2385-0000 Hex)
To find the description of an error, first look at its hex number; for example, 2385. This
is composed of a base value of 2000 plus the hex va lue of 385 (385 is equivalent to a
decimal error number 901). The base number, 2000, indicates that this is a Pathsend
error message.
The error extension (in this example, -0 or -0000) may contain an extended error code
reported by an underlying subsystem: Guardian File System, API, Pathway/TS, and
Pathsend messages have extended error numbers. Look up the extended error codes
in the appropriate documents.
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration G uide — 52235 8- 013
B - 6