HPlogo SNA NRJE Node Manager's Guide: HP 3000 MPE/iX Computer Systems > Chapter 5 SNA NRJE Troubleshooting

Using NMDUMP for SNA NRJE

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Glossary

 » Index

When NMDUMP displays the list of subsystems and IDs, and prompts you for the IDs you want to select, specify the SNA NRJE ID: 2. Then, proceed normally with NMDUMP. Note that NMDUMP is described in more detail in the SNA Link Services Reference Manual (for MPE V) and in Using the Node Management Services Utilities (for MPE XL). If you are not familiar with NMDUMP, you should read the information in the appropriate manual before running NMDUMP.

SNA NRJE Formatting Options Menu

For SNA NRJE, NMDUMP displays a formatting options menu, as shown in Figure 5-1 “ NMDUMP Formatting Options Menu for SNA NRJE” that allows you to specify how you want the tracing or logging records to be displayed:

Figure 5-1  NMDUMP Formatting Options Menu for SNA NRJE

NMDUMP Formatting Options Menu for SNA NRJE
  • Option 1 specifies the numerical representation for the unformatted data dumps.

  • Option 2 specifies whether the unit to be represented as one number is the byte or the word. In the formatted output, hexadecimal numbers are preceded by an exclamation point ( !), and octal numbers are preceded by a percent sign (%). All the other numbers are decimal, except in cases where the digits 0 and 1 are used to indicate the setting of a specific bit.

  • Option 3 specifies whether character mode is to be on or off. If character mode is on, each unformatted hexadecimal or octal output line is followed by a line containing the corresponding printable characters in the character code specified by option 4. Nonprintable characters are represented as periods.

  • Option 4 specifies the character code the data is to be printed in: ASCII or EBCDIC.

  • Option 5 allows the user to disable or enable unformatted data dumps (that is, lines with hexadecimal or octal numbers only [no text]). If the data dumps are enabled, the data of the formatted sections is also represented as unformatted raw data (as it appears in the input record). If the dumps are disabled, only formatted sections appear in the output (except for the Request Unit sections in some SNA Transport records, which are always printed).

In Figure 5-1 “ NMDUMP Formatting Options Menu for SNA NRJE”, the values shown for the options are the default values. To change the value of an option, type the option number and press [RETURN]. If all the values are as you want them, you can exit the menu by pressing [RETURN] without specifying an option number.

SNA NRJE Output Formats

For SNA NRJE, NMDUMP formats tracing records and logging records. The format for each type of record is described below.

Tracing Records

Tracing records are identified by a type and a subtype. In a formatted trace record, the type and subtype numbers are shown in parentheses, on the first line of information after the "Info section."

The data in the "Info section" is displayed in either hexadecimal (preceded by a pound sign) or octal (preceded by a percent sign), according to what was specified for option 1 on the NMDUMP Formatting Options menu.

LU Trace Records

@LU trace records are type 0, and are formatted according to five subtypes:

  • Called by CI or intrinsics:

    • Subtype 0: workstation number

    • Subtype 1: wsid and number

  • Called from an LU process:

    • Subtype 4: LU number and workstation number

    • Subtype 6: LUID and number, and workstation number

    • Subtype 7: LUID and number, and wsid and number

Intrinsic Trace Records

Intrinsic trace records are type 1, and are formatted according to two subtypes:

  • Subtype 0: workstation number

  • Subtype 1: wsid and number

SNA NRJE produces a subtype 1 intrinsic trace record for the first intrinsic trace record in a trace file for a given workstation. (Any continuation records for subtype 1 intrinsic trace records are also subtype 1.) A subtype 1 trace record header shows the type of tracing, the version ID, the workstation number (used to identify the workstation within a trace file), the workstation ID (wsid), the user ID, and the intrinsic number.

The intrinsic names and their corresponding numbers are shown below.

INTRINSIC NAME       MODULE #        INTRINSIC NAME        MODULE #
 
NRJEQUEUE              1              NRJESTARTWS             9
NRJEALTER              2              NRJEWSINFO              10
NRJECANCEL             3              NRJEWRITER              11
NRJERDRFENCE           4              NRJELULIST              12
NRJEDRACCESS           5              NRJECONSOLE             13
NRJEJOBINFO            6              NRJETRACE               14
NRJESUBMIT             7              NRJELUSTATUS            15
NRJESTOPWS             8 

This is an example of a subtype 1 intrinsic trace record header.

     **********************************************************************
     *  Subsystem NRJE (2)                        Intrinsic tracing data  *
     *           TUE, APR  3, 1984,  4:07 PM, TIMER= 58021.707            *
     *                                                                    *
     *  ------------------------- Info section -------------------------  *
     *  #:  0101    0000    0000    0000    0000    5232    3020    2020  *
     *      2020    0001    4B45    5649    4E20    2020    4B4F    5242  *
     *      2020    2020    4E52    4A45    2020    2020    000E          *
     *                                                                    *
     *  Intrinsic tracing: Workstation header record  (1/1)               *
     *  Version          : A.00.00.000                                    *
     *  Workstation      :  1 , ID = R20                                  *
     *  User             : MANAGER.SYS, NRJE                              *
     *  Intrinsic        : 14                                             *
     **********************************************************************

Logging Records

Logging records that reflect an error (logging class CLAS0010 [noncritical errors] or CLAS0012 [critical errors]) are formatted with a border of asterisks. This distinguishes them from logging records that do not reflect an error (which do not have a border).

The first 16 bits of a logging record are printed in the "Logging word" field. This word is reserved and is displayed in hexadecimal (preceded by a pound sign) or octal (preceded by a percent sign), according to what was specified for option 1 on the NMDUMP Formatting Options menu. The SNA NRJE version number is in the format v.uu.ff.iii, where v = version, uu = update, ff = fix, and iii = internal fix. This is followed by SNA NRJE logging. This is an example of the format for SNA NRJE logging record information. The message text associated with the message number (number 4009 in the example) is found in the SNA NRJE User/Programmer Reference Manual. The parameters for a specific message (R20, LU01, and the console message [8.13.06 through E=N], in the example), up to 5, are taken from the logging record.

     **********************************************************************
     *  Subsystem NRJE (2)                                  logging data  *
     *                    Sun, NOV 13, 1983, 8:14 AM                      *
     *                                                                    *
     *  Logging word     : #0000                                          *
     *  Version          : A.00.00.000                                    *
     *                                                                    *
     *  NRJE(R20     ;LU01     ):  CONSOLE MESSAGE:  8.13.06              *
     *  $HASP628 LINE13    SNA ACTIVE    (RMT20)  E=N     (FMD=4009).     *
     **********************************************************************
Feedback to webmaster