HP-UX SNAplus2 Diagnostics Guide

Overview of Problem Solving
Types of Diagnostic Information
Chapter 1 21
• the command-line administration program
• the 3270 emulation program
• RJE
SNAplus2 also includes manual (“man”) pages. You will find the online
help information useful both in preventing and resolving problems.
The rest of this chapter describes each kind of diagnostic information in
more detail, and explains where to find SNAplus2 online help
information.
For a list of the more common problems that are encountered by users
and the steps to take to resolve them, see Chapter 2, “Resolving Common
Problems.” For information about how to use logging and tracing, see
Chapter 3, “Using Logging and Tracing.”
Program Error Messages
The most obvious indication of a problem is the display of a program
error message. SNAplus2 generates program error messages
automatically to report serious problems. Program error messages are
reported to the screen or console. Each message describes the problem
that the program encountered. You cannot disable these messages.
The following are examples of program error messages:
Example 1-1 Node Failed to Start
$: snapadmin init_node
init_node command failed:
primary_rc = STATE_CHECK, secondary_rc = NODE_NOT_CONFIGURED
Example 1-2 The start_ls Command Failed
$: snapadmin start_ls, ls_name=TESTLS
start_ls command failed:
primary_rc = STATE_CHECK, secondary_rc = PORT_INACTIVE
If a user using the Motif administration program tried to start the link
station illustrated in “The start_ls Command Failed”, a pop-up message
would be displayed similar to the following:
Example 1-3 Link Station Failed to Start
Link Station TESTLS failed to start because port TESTPORT is
inactive.