Standalone Logtool for MPE/iX: All the files

You can print it out from your browser to get a hardcopy version of the document.

Standalone Logtool for MPE/iX: Summary

• Introduction
• Defects and Enhancements
• Minimum Configuration
• Operating Instructions
  • Starting LOGTOOL
  • Test Execution

• Commands
• Records
• Error and Warning Messages

To print the entire document: All the files

The standalone version of Logtool is almost the same as the "old" Logtool that ran under the SYSDIAG online diagnostic platform which was replaced by STM as of MPE/iX 6.5.

The main difference between the "old" and "new" versions of Logtool is how you start the new standalone version: just type logtool at the MPE/iX prompt.

Text for this document was taken from the Support Tools Manual: Volume 7, Utilities, edition 3, released in April 1994 with HP Part No. 5960-3161. Only minor changes have been made to adapt it for the standalone version of logtool.

Introduction

System log files contain information generated by the host operating system. The LIST command will display the contents of the system log files based on selection criteria given by the user. A summary report of the contents of the system log files can be generated using the SUMMARIZE command. The ALTFIELD command can be used to specify that only a portion of certain log records found within the system log files are to be displayed by the LIST command. Commands are also available to purge log files, create new log files, and to create LOGTOOL "work" files, which will contain a subset of log files. When new log entries are developed, the LAYOUT command with a record definition file will allow code developers to "tell" LOGTOOL how to format the information they have sent to the system log files.

The memory error log file contains memory error information gathered by the memory error logging process (MEMLOGP). The MEMRPT command will produce a summary report based on the information from the memory log file. The MEMCLR command will give the user the ability to clear all the information in the memory log file. In addition, the MEMTIMER command allows the user to change the time interval in which the MEMLOGP process will scan all the memory controllers to see if any memory errors occurred.

In addition to the various log file commands, LOGTOOL contains commands which aid the user during a LOGTOOL session.

HELP	Displays detailed and syntax summary information to the user upon request.
REDO	Allows the user to edit/recycle previous input.
SUSPEND	Allows the user to temporarily suspend LOGTOOL and return control to the Diagnostic User Interface (DUI).

Defects and Enhancements

Minimum Configuration

Operating Instructions

Starting LOGTOOL

MPE_PROMPT>  LOGTOOL
              | 
       no parameters required to load 

Test Execution

HPDST240-BICKLE->PUB.SYS#logtool 

*******************************************************************
******                                                       ******
******                      LOGTOOL                          ******
******                                                       ******
******         (C) Copyright Hewlett Packard Co.             ******
******       1989,1990,1991,1992,1993,1994,1995,1999         ******
******               All Rights Reserved.                    ******
******                                                       ******
******  HP shall not be liable for any damages resulting     ******
******  from the use of this program.                        ******
******                                                       ******
******                  Version  A.03.05                     ******
******                                                       ******
*******************************************************************

Welcome, Today is THU, OCT 14, 1999 at  4:30 PM

LOGTOOL initializing, please wait ...

LOGTOOL>

To exit LOGTOOL, the user types EXIT. The message

LOGTOOL  Exiting ...

Standalone Logtool for MPE/iX: Commands

• Command Summary
• Definitions and Conventions
• Parameters
• Command Descriptions
  • DISPLAYLOG
  • EXIT
  • HELP
  • ALTFIELD
  • LAYOUT
  • LIST
  • MEMCLR
  • MEMRPT
  • MEMTIMER
  • PURGESYSLOG
  • PURGEWORK
  • REDO
  • SELECT
  • STATUS
  • SUMMARIZE
  • SUSPEND
  • SWITCHLOG
  • TYPES

Command Summary

• System Log File Commands (SFL)
• Memory Log File Commands (MLF)
• Miscellaneous Commands (MC)

Command Name	Command Category	Description
ALTFIELD	(SFL)	Specifies which fields of a log record should be displayed in a report generated by LIST.
DISPLAYLOG	(SFL)	Displays I/O entries as information is logged.
EXIT	(MC)	Exits LOGTOOL and returns user to the MPE/iX user interface.
HELP	(MC)	Gives help on running LOGTOOL.
LAYOUT	(SLF)	Reads in a layout file.
LIST	(SLF)	Lists contents of a system log file.
MEMCLR	(MLF)	Clears the memory logging process log files.
MEMRPT	(MLF)	Displays the contents of the memory log file.
MEMTIMER	(MLF)	Alters the timer value of the memory error logging process.
PURGESYSLOG	(SLF)	Deletes the specified system log files from the disc.
PURGEWORK	(SLF)	Deletes the specified work files from the disc.
REDO	(MC)	Edits any of the last four lines of text entered.
SELECT	(SLF)	Selects specified records from the system log files.
STATUS	(SLF)	Reports on the status of all system log files.
SUMMARIZE	(SLF)	Allows user to generate summary report based on contents of system log files.
SUSPEND	(MC)	Suspends LOGTOOL and returns control to the MPE/iX user interface.
SWITCHLOG	(SLF)	Causes the system to start a new system log file.
TYPES	(SLF)	Describes the system log file "types."

Definitions and Conventions

The user may be prompted from time to time for certain data. If one of several specific responses is required (a YES or NO question, for example), the valid responses will be indicated in parentheses. In all instances, a default response is indicated in square brackets. This response may be selected simply by pressing Return. For example, a user who is deleting a system log file might be asked the question:

     Purge LOG3251.pub.sys (Y/N) [N] ? 

     LOGTOOL>select log=100/400, 234/599 ;type= 101, 105, 109 &
     LOGTOOL>name=hp7935,hp7933

Command lines may include comments if desired. The beginning of a comment is indicated by the "{" character. A "}" or Return terminates the comment (i.e., For Return everything after the "{" is ignored). The continuation character "&" within a comment is ignored. For example:

   LOGTOOL>status  { This is a comment } 
   LOGTOOL>select log=1,2  { This is line 1's comment } & 
   LOGTOOL>ldev=4    { Note the "&" above was recognized! } 

The following notation appears throughout the remainder of this document. This notation is also used when performing the HELP HELP command.

Notations Table

[ ]	An element inside brackets is optional.
<>	Items within angle brackets will be replaced with user-supplied information. Do NOT type the angle brackets.
{}	Items within curly brackets are required. (Usually you must choose one of several options).
...	A horizontal ellipsis indicates that the previous element may be repeated, or that elements have been omitted.
|	A vertical bar means "or." For example, (YES | NO) means (YES or NO).
::	Means "is defined as."

Parameters

log list	Specifies a list of log file ranges. All system log files are named "LOGxxxx" where "xxxx" is a 4-digit number.
	<log_list> ::= <log_range> | <log_range> , <log_list>
	<log_range> ::= <log#> | <log#> / <log#>
	<log#> ::= (Any 4 digit integer)
	Example: LOG=1/5, 253/1004
file list	Specifies a list of file names used as input or output to LOGTOOL. LP can be specified if output is to be directed to the system printer. All input and output files are assumed to be located in the diagnostic directory (DIAG.SYS for MPE/iX)
	<file_list> ::= <file_name> | <file_name> , <file_list>
	<file_name> ::= Alpha-numeric text (starting with an alpha) |
	Example: FILE=file1,file8,junk,work
type list	The system error logs contain several different "types" of log records. These record types may be referred to by a type number. (The LOGTOOL command TYPES gives the user a list of the types known to LOGTOOL.)
	<type list> ::= <type number range> | <type number range> , <type list>
	<type number range> ::= <type number> | <type number>/
	<type number>
	<type number> ::= integer value
	Example: TYPE=101, 104, 106
ldev list	A list of logical names for devices.
	<ldev_list> ::= <ldev> | <ldev> , <ldev_list>
	<ldev> ::= (Any positive integer) (For MPE/iX)
	Example:
	LDEV=1,2,5,10 {For MPE/iX}
pdev list	A list of physical devices. Please note that bus converters are applicable to some HPPA systems only.
	<pdev_list> ::= <pdev> | <pdev> , <pdev_list>
	<pdev> ::= <BUSCONV>/<CA>.<DA>.<device> |
	<BUSCONV>/<CA>.<DA>.<device> |
	<BUSCONV>/<CA>.<DA> |
	<BUSCONV>/<CA> |
	<CA>.<DA>.<device> |
	<CA>.<DA>.<device> |
	<CA>.<DA> |
	<CA>
	<BUSCONV> ::= <BUSNUM> | <BUSNUM>/<BUSNUM>
	<BUSNUM> ::= An integer giving the bus converter address.
	<CA> ::= An integer giving the channel address
	<DA> ::= An integer giving the DA address
	<device> ::= An integer giving the device address
	Example: PDEV=1.1, 1.2, 1.2.3, 1.2.1, 3.2.1
Field label keywords	Field label keywords allow the user to select log records based on the data present in the log record. Quotes are only required for field labels and data items which contain embedded blanks or LOGTOOL reserved words used as part of the command syntax. If a quote is needed as part of the field label, entering a quote twice ("") will be interpreted as a single quote as part of the field label. For fields which are always displayed as hex arrays or can be displayed as hex arrays by using the HEXDUMP option, the index construct will allow users to select log records by individual array elements. To use the index construct, the field label must be followed by the array element index number enclosed in square brackets. Please note that all arrays start with an element index of 1. The selection criteria specified by a field label keyword will only be met if the data item and the data found in the log record match exactly. All field labels and text data items will be upshifted before the evaluation is performed.
	<field label> ::= text | "text" | text[<index>] | "text"[<index>]
	<index> ::= integer value starting at 1
	<data list> ::= <data item> | <data item> , <data list>
	<data item> ::= integer value | text | "text"
	Ex: Ldev=1,7 "PRODUCT NAME"=HP7935 JSNAME=JREPORT
	"Hardware status"[1]=4
DATE & TIME	Date and time formats are language dependent. Machines which support language localization may support numerous date and time formats at one time. The format expected will correspond to the language custom the program is run in.
	Standard USA formats are:
	<date> ::= <month#> / <day#> / <year>
	<day#> ::= 1 .. 31
	<month#> ::= 1 .. 12
	<year> ::= 1800 .. 2000
	<time> ::= <hours> : <minutes> AM | PM
	<hours> ::= 0 .. 12
	<minutes> ::= 0 .. 59
integer	Any integer value. Any time an integer is expected, that value can be entered in any of 4 bases by preceding the value with one of the base indication characters. If no base character is present, decimal is assumed.
	$ = Hex
	% = Octal
	B = Binary
	Example:
	%12 is 10 base ten.
	B1001 is 9 base ten.
	$1A is 26 base ten.

Command Descriptions

Each description contains the command explanation, syntax definition, parameter definition and an example.

DISPLAYLOG

Syntax:

     DISPLAYLOG [;LDEV=<LDEV_list>] 
                [;PDEV=<PDEV_list>] 

LDEV= <DEV_list>  -  This is a list of logical names for I/O devices 
                     for which the user would like to see log entries 
                     displayed. 

                     Example:  LDEV=1,2,5,10       {For MPE/iX}

PDEV= <PDEV_list> -  This is a list of PDEV numbers for I/O devices 
                     for which the user would like to see log entries 
                     displayed. 

                     Example: PDEV=1.1, 1.2, 1.2.3, 1.2.1, 3.2.1.1 

LOGTOOL>displaylog

I/O ERROR 
PRODUCT NAME:       HP7935H            PDEV:               8.0.1 
LDEV:               2                  DEVICE CLASS:       Hard Disc 
I/O EVENT CLASS:    Software           LLIO STATUS:        $DFD700C6

MPE/XL I/O Status: Proc. Num. = -41,  Error Num. = -33,  Subsystem = 198

RETRY SCHEME:       Summarized Retries WILL RETRY:         NO
I/O RESULT:         I/O Failed         RUN AUTODIAG:       NO
RETRY COUNT:        5                  MGR PORT NUM.:      -82
TRANS. NUM. :       1279               # HDWR BYTES:       20                 
HARDWARE STATUS: 

   Status = 
   Unit = 0   Volume = 0 
   No units with status pending 
   >>>>>>>>>> Access Errors <<<<<<<<<< 
   Drive is not ready for access 
   New target address is : 
      Vector address = 
         Cylinder = 0   Head = 0   Sector = 0 
      Block address = 0 

DATA LEN:           52                  MGR CODE:           121
STATUS INFORMATION: 0                   COMMAND BUFFER:
      1   2   3   4   5   6   7   8   9   10  11  12
      ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==
  1:  40  01  00  0A  20  10  00  00  00  00  00  08  @ . . .   . . . . . . .
 13:  34  34  34  18  00  00  00  00  02  00  00  00  4 4 4 . . . . . . . . .
MSG DESCRIPTOR:     4                   MESSAGE ID:         -1000
TRANSACTION NUM.:   1277                PORT NUMBER:        -82
COMMAND RESIDUE:    0                   DATA RESIDUE:       -1
STATUS RESIDUE:     0

<hit user interrupt>
LOGTOOL>

EXIT

Syntax: EXIT

Example:

     LOGTOOL >EXIT
     LOGTOOL Exiting .... 

HELP

Syntax:

     HELP [<command name> [;SYNTAX]] 

   LOGTOOL>HELP

         The System and Memory Log Analysis Tool (LOGTOOL) enables the 
   user to perform numerous functions on the various system log files. 
   These functions include deleting/clearing of log files and displaying 
   the contents of log files.  LOGTOOL will allow the user to manipulate 
   two types of log files. 

   o  System log files:  Contains information logged by the host 
      operating system. 

   o  The Memory log file:  contains information concering memory 
      errors obtained from memory controller hardware. 

   LOGTOOL is available in multi-user mode, but the user will 
   be required to execute at diagnostic security 1 to 
   perform some functions. 

   LOGTOOL command summary: 

   Command Name      Description 
   ================= ================================================= 
   SUSPEND           Return control to MPE/iX - Suspend LOGTOOL 
   EXIT              Exit LOGTOOL - return to MPE/iX
   REDO              Edit the last line of text entered 
   HELP              Gives help on running LOGTOOL
   LIST              List contents of a system error log 
   DISPLAYLOG        Display I/O entries as information is logged 
   PURGESYSLOG       Delete from disc the specified system error logs 
   PURGEWORK         Delete from disc the specified "work" files 
   LAYOUT            Read in layout file 
   ALTFIELD          Specify which fields are to be displayed in report
   SELECT            Select specified records from system log files 
   STATUS            Report on status of all system log files 
   SUMMARIZE         Summarize contents of a system log file.
   SWITCHLOG         Cause the system to start a new system log file 
   MEMCLR            Clears MEMLOGP log file. 
   MEMTIMER          Alter timer value of MEMLOGP process. 
   MEMRPT            Display contents of Memory Log File. 
   TYPES             Describes System Log File "types" 
   ================= ================================================= 

   Any command, keyword, or option may be entered by specifying the 
   shortest number of characters which makes the name unambiguous. 

   Keywords and options may be separated by spaces and/or semicolons. 

LOGTOOL> 

ALTFIELD

Syntax:

   ALTFIELD TYPE=<type list>
            ;DISABLE = <field label list> | ENABLE = <field label list>

   TYPE=<type list>    - The TYPE keyword is used to specify which log
                         record types (id's) the fields given in the
                         DISABLE or ENABLE parameter applies to.
                         Log record Id's range from 0 to 255. If this
                         TYPE is not used, all log record types will be
                         considered.


        <type list> ::= <type number range> | <type number range>,<type list>
        <type number range> ::= <type number> | <type number>/<type number>
        <type number> ::= integer value

        Ex: TYPE=101,104,106


   DISABLE = <field label list> - Specifies which fields are not to
                         be displayed in a report generated by the
                         LIST command.  Quotes are only required
                         for field labels which contain embedded
                         blanks.


        <field label list> ::= <field label range> |
                 <field label range>,<field label list> | ALL
        <field label range ::= <field label> | <field label>/<field label>
        <field label> ::= text | "text"

        Ex:  DISABLE="NL CHECKSUM"/"SL CHECKSUM"


   ENABLE = <field label list> - Specifies which fields are to
                         be displayed in a report generated by the
                         LIST command.  Quotes are only required
                         for field labels which contain embedded
                         blanks.


        <field label list> ::= <field label range> |
                 <field label range>,<field label list> | ALL
        <field label range ::= <field label> | <field label>/<field label>
        <field label> ::= text | "text"

        Ex:  ENABLE = PDEV/"LLIO STATUS"

LOGTOOL> altfield type=111 disable="retry scheme"/"mgr code"
LOGTOOL>

LAYOUT

Once the record definitions have been accepted, LOGTOOL will display the record entry as specified when performing a LIST command. If any syntax errors are detected by the LAYOUT command, the errors will be displayed to the user and the record definition will not be accepted. Upon completion of the record definition file processing, LAYOUT will display the number of errors detected, the number of record definition accepted and the number of tag definitions accepted. If the APPEND option is given, LOGTOOL will append the new record definitions to the record decoding files (LAYOUTF and LAYMSG). These decoding files are used as a data base of record definitions. The record definitions in the record decoding files will be used by all users when performing a LIST command. If the APPEND option is not given, the record definitions given will be used only by the current session of LOGTOOL and will be lost upon exiting LOGTOOL.

During the processing of a record definition file, if a record definition already exists, the user will be prompted to determine if the previous definition should be overwritten. If the answer YES is given, the previous definition will be destroyed. This prompting can be disabled by giving the NOVERIFY option and the overwrite case is assumed.

To execute this command, the user must possess at least diagnostic security 1. (It is assumed that the record definition files given are located in the diagnostic directory -- DIAG.SYS on MPE/iX.)

Syntax:

     LAYOUT FILES=<file_list> 
           [;VERIFY | ;NOVERIFY] 
           [;APPEND] 

FILES  -  <file_list> The FILES keyword is used to specify the names 
           of the record definition files to be processed.  File is 
           assumed to reside in the diagnostic directory -- 
           DIAG.SYS on MPE/iX. 

          <file_list> ::=  <file_name> | <file_name> , <file_list> 

           Example:  FILE=laympexl, layio 

APPEND  -  If given, specifies that the record definitions given 
           are to be saved permanently in LOGTOOL's 
           record decoding file. 

VERIFY|NOVERIFY  -  Specifies if the user is to be asked to 
                    overwrite record definitions which already exist. 

      LOGTOOL>layout file=laytemp;noverify
         Processing ID 101 ... 
         Processing ID 102 ... 
         Processing ID 103 ... 
      ========================================= 

      End processing of layout file LAYTEMP.DIAG.SYS 

      0 Errors encountered 
      3 out of 3 record'IDs were accepted. 
      0 out of 0 tag'IDs were accepted. 

      LOGTOOL> 

LIST

In order for a log record to be included in the report, it must match all of the selection criteria specified. The user can define the selection criteria by using the TYPE keyword, DATE or TIME options, or field label keywords.

TYPE keyword	The TYPE keyword can be used to indicate that only log records of the types specified are to be displayed. The LOGTOOL command TYPES can be used to obtain a list of the log record types available.
DATE or TIME options	The DATE or TIME options can be used to indicate that only the log records generated between the date and time entered are to be displayed.
Field Label Keywords	Field label keywords allow the user to select log records based on the data present in the log record. Whenever the LIST command displays a data item from a log record, a field label is shown before the data item to identify what the item represents. This field label is usually a text abbreviation. Field label keywords allow the user to use this text abbreviation as a selection keyword. For example, if the user wishes to see all log records with a field label of "LDEV" and a logged data value of 1, the parameter of "LDEV=1" can be entered as part of the LIST command. NOTE: In the preceding example, if the record does not contain an "LDEV" field, the record will not be displayed.

If no selection criteria are given, all log records found will be included in the report. After all the selected log records have been displayed, this report will be terminated with a summary indicating the number of log records selected. Please note that if LOGTOOL cannot find a record definition for a log record type, the entire log record will be displayed in HEX.

To execute this command, the user must posses at least diagnostic security level 1.

Syntax

   LIST LOG=<log list> | FILES=<file list>
        [;OUTFILE=<file name>]
        [;TYPE=<type list>]
        [;<field label>=<data list>]
        [;DATE]
        [;TIME]
        [;WIDE]
        [;HEXDUMP]

  LOG=<log list>      - The LOG keyword specifies which log files to
                         base the report on.  Use the STATUS
                         command to obtain a list of the system log files
                         available on the host system.

  <log list> ::= <log number range> | <log number range> , <log list>
  <log number range> ::= <log number> | <log number>/<log number>
  <log number> ::= integer value

   Ex:  LOG=100/105, 150

  FILES=<file list> -   The FILES keyword is optionally used in place
                         of the LOG keyword. The file list must be a
                         list of "work" files (created by the SELECT
                         command).  Note: All "work" files are created
                         in the diagnostic directory (DIAG.SYS on MPE/iX).

  <file list> ::=  <file name> | <file name> , <file list>
  <file name> ::=  Alpha-numeric text (starting with an alpha)

   Ex:  FILE=file1,file8,junk,work

   OUTFILE=<file name> - The OUTFILE keyword lets the user direct the
                          report to a file or the line printer.
                          Note: All files created by using the OUTFILE
                          parameter will reside in the diagnostic directory 
                          (DIAG.SYS on MPE/iX).

   <file name> ::=  Alpha-numeric text (starting with an alpha)  |

                         LP

        Ex: OUTFILE=listfile    or

            OUTFILE=lp          {Output to printer}

   TYPE=<type list>    - The TYPE keyword is used to specify which log
                         record types (id's) to select for the report.
                         Log record Id's range from 0 to 255. If this
                         TYPE is not used, all log record types will be
                         considered.


        <type list> ::= <type number range> | <type number range>,<type list>
        <type number range> ::= <type number> | <type number>/<type number>
        <type number> ::= integer value

        Ex: TYPE=101,104,106


   <field label>=<data list> - Field label keywords allow the user to
                               select log records based on the data present
                               in the log record.  Quotes are only required
                               for field labels and data items which contain
                               embedded blanks or reserved words used as
                               part of the LIST command syntax.  If a quote
                               is needed as part of the field label, entering
                               a quote twice ("") will be interpreted as a
                               single quote as part of the field label.  For fields 
                               which are always displayed as hex arrays or can be
                               displayed as hex arrays by using the HEXDUMP option,
                               the index construct will allow users to select
                               log records by individual array elements.  To
                               use the index construct, the field label must
                               be followed by the array element index number
                               enclosed in square brackets.  Please note that
                               all arrays start with an element index of 1.
                               The selection criteria specified by a field label 
                               keyword will only be met if the data item and the data
                               found in the log record match exactly.  
                               If the selection criteria are not met, the
                               record will not be displayed.  All
                               field labels and text data items will be
                               upshifted before the evaluation is performed.


        <field label> ::= text | "text" | text[<index>] | "text"[<index>]
        <index> ::= integer value starting at 1
        <data list> ::= <data item> | <data item> , <data list>
        <data item> ::= integer value | text | "text"

        Ex: Ldev=1,7  "PRODUCT NAME"=HP7935 JSNAME=JREPORT
            "Hardware status"[1]=4



   DATE                - The DATE option will cause the user to be
                       prompted for a range of dates. Only those log
                       records falling into one of the specified date
                       ranges will be included in the report. Default
                       is the current day.


      Ex:  Enter the starting date [01/01/86] ?  02/02/86
           Enter the ending date [<starting date>]? 02/03/86
           Do you have more dates (Y/N) [N] ? n


   TIME                - The TIME option will cause the user to be
                         prompted for a range of times. Only those log
                         records falling into one of the specified time
                         ranges will be included in the report.
                         Default is the current time.


      Ex:  Enter the starting time [12:47 PM]? 1:00 PM
           Enter the ending time [<starting time>]? 5:00 PM
           Do you have more to enter (Y/N) [N] ? n


   WIDE                - The WIDE option is used when the output is
                         directed to a device which has 120 or more
                         columns.  If the output device is LP, this
                         option is automatically set.

   HEXDUMP             - The HEXDUMP option is applicable only for I/O
                         and diagnostic records. If used, the hardware
                         status and diagnostic error stack is
                         dumped in HEX rather than being decoded into
                         text statements.

LOGTOOL> list log=1 out=demo
    Processing LOG0001.PUB.SYS ...

    Total records checked = 52.   Records selected = 52.
LOGTOOL>

The following is an example display of a log file (LOG0039.PUB.SYS) through the LOGTOOL LIST command.

                             SYSTEM ERROR LOG REPORT
                             =======================


 Report Date/Time:  FRI, APR 27, 1990 -  5:09 PM


===============================================================================
TUE, APR 10, 1990    9:11 AM       LOG0039.PUB.SYS              SYSTEM (PIN 19)
CONSOLE LOG
(OUTPUT)SYSTEM LOG FILE #39 IS ON
USER:               MANAGER             GROUP:              PUB
ACCOUNT:            SYS                 JSNAME:
===============================================================================
TUE, APR 10, 1990    9:11 AM       LOG0039.PUB.SYS               SYSTEM (PIN 2)
NM FILE CLOSE
NUM. LOGICAL READS: 3                   NUM. BYTES READ:    2048
NUM. LOGICAL WRITES:1                   NUM. BYTES WRITTEN: 256
FILE NAME:          PEGCMD              GROUP NAME:         PEGASUS
ACCOUNT NAME:       FVSTOOLS            CREATOR NAME:       MGR
USER NAME:          MANAGER             USER GROUP:         PUB
USER ACCOUNT:       SYS                 UFID:
      1   2   3   4   5   6   7   8   9   10  11  12
      ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==
  1:  05  5A  00  03  06  0E  6A  13  00  01  B0  B4   . Z . . . . j . . . . .
 13:  0C  04  2C  A7  03  97  D3  96                   . . , . . . . .

CLOSE DISP.:        No Change           OPEN DOMAIN:        Old Perm File
FILE SIZE (BYTES):  8192                FILE OPEN COUNT:    2
===============================================================================
TUE, APR 10, 1990    9:11 AM       LOG0039.PUB.SYS              SYSTEM (PIN 19)
I/O ERROR
PRODUCT NAME:       HP7935H            PDEV:               8.0.1
LDEV:               2                  DEVICE CLASS:       Hard Disc
I/O EVENT CLASS:    Software           LLIO STATUS:        $DFD700C6

MPE/XL I/O Status: Proc. Num. = -41, Error Num. = -33, Subsystem = 198

RETRY SCHEME:       Summarized Retries WILL RETRY:         NO
I/O RESULT:         I/O Failed         RUN AUTODIAG:       NO
RETRY COUNT:        5                  MGR PORT NUM.:      -82
TRANS. NUM. :       1279               # HDWR BYTES:       20
HARDWARE STATUS:

   Status =
   Unit = 0   Volume = 0
   No units with status pending
   >>>>>>>>>> Access Errors <<<<<<<<<<<\esc>
   Drive is not ready for access
   New target address is :
      Vector address =
         Cylinder = 0   Head = 0   Sector = 0
      Block address = 0

DATA LEN:           52                  MGR CODE:           121
STATUS INFORMATION: 0                   COMMAND BUFFER:
      1   2   3   4   5   6   7   8   9   10  11  12
      ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==
  1:  40  01  00  0A  20  10  00  00  00  00  00  08  @ . . .   . . . . . . .
 13:  34  34  34  18  00  00  00  00  02  00  00  00  4 4 4 . . . . . . . . .
MSG DESCRIPTOR:     4                   MESSAGE ID:         -1000
TRANSACTION NUM.:   1277                PORT NUMBER:        -82
COMMAND RESIDUE:    0                   DATA RESIDUE:       -1
STATUS RESIDUE:     0
===============================================================================
TUE, APR 10, 1990    9:11 AM       LOG0039.PUB.SYS              SYSTEM (PIN 19)
CONSOLE LOG
(OUTPUT)SYSTEM LOG FILE #38 IS 4% FULL
USER:               MANAGER             GROUP:              PUB
ACCOUNT:            SYS                 JSNAME:
===============================================================================
TUE, APR 10, 1990    9:11 AM       LOG0039.PUB.SYS                 #J4 (PIN 40)
PROCESS CREATION
PROGRAM FILE NAME:  PEGCMD.PEGASUS.FVSTOOLS
PID INITIATED:      180388626434        PRIORITY:           6911
SPACE ID:           561                 PARENT ID:          171798691842
NM_HEAP_SIZE:       81920000            PROCESS CAP BA:     YES
PROCESS CAP IA:     YES                 PROCESS CAP PM:     NO
PROCESS CAP MR:     NO                  PROCESS CAP DS:     NO
PROCESS CAP PH:     NO                  USER:               MGR
GROUP:              SU                  ACCOUNT:            FVSTEST
JSNAME:             SUSLG01J
===============================================================================
TUE, APR 10, 1990    9:11 AM       LOG0039.PUB.SYS                 #J4 (PIN 42)
NM FILE CLOSE
NUM. LOGICAL READS: 0                   NUM. BYTES READ:    0
NUM. LOGICAL WRITES:0                   NUM. BYTES WRITTEN: 268
FILE NAME:          O124                GROUP NAME:         OUT
ACCOUNT NAME:       HPSPOOL             CREATOR NAME:       MGR     FVSTEST
USER NAME:          MGR                 USER GROUP:         SU
USER ACCOUNT:       FVSTEST             UFID:
      1   2   3   4   5   6   7   8   9   10  11  12
      ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==
  1:  05  5A  00  03  06  0E  6A  13  00  0D  9E  B4   . Z . . . . j . . . . .
 13:  32  02  08  26  01  F8  A2  3A                   2 . . & . . . :

CLOSE DISP.:        No Change           OPEN DOMAIN:        Old Perm File
FILE SIZE (BYTES):  524288              FILE OPEN COUNT:    6
===============================================================================
TUE, APR 10, 1990    9:11 AM       LOG0039.PUB.SYS                 #J4 (PIN 42)
PROCESS TERMINATION
CPU TIME(MILLI-SEC):458                 STACK SIZE (8 BITS):393216
HEAP SIZE ( 8 BITS):81920000            CM STACK (16 BITS): 4686
TERMINATION TYPE:   Normal              USER:               MGR
GROUP:              SU                  ACCOUNT:            FVSTEST
JSNAME:             SUSLG01J
===============================================================================
TUE, APR 10, 1990    9:11 AM       LOG0039.PUB.SYS                 #J4 (PIN 40)
PROCESS CREATION
PROGRAM FILE NAME:  PEGCMD.PEGASUS.FVSTOOLS
PID INITIATED:      94489280515         PRIORITY:           6911
SPACE ID:           561                 PARENT ID:          171798691842
NM_HEAP_SIZE:       81920000            PROCESS CAP BA:     YES
PROCESS CAP IA:     YES                 PROCESS CAP PM:     NO
PROCESS CAP MR:     NO                  PROCESS CAP DS:     NO
PROCESS CAP PH:     NO                  USER:               MGR
GROUP:              SU                  ACCOUNT:            FVSTEST
JSNAME:             SUSLG01J
===============================================================================

 TYPE       DESCRIPTION         COUNT
======  ====================  ==========
   115           CONSOLE LOG         2
   105         NM FILE CLOSE         2
   111             I/O ERROR         1
   141      PROCESS CREATION         2
   104   PROCESS TERMINATION         1
======  ====================  ==========

MEMCLR

Syntax:

     MEMCLR 

      LOGTOOL>memclr
      LOGTOOL> 

MEMRPT

The following is a list of the types of error information displayed:

Slot	This will identify the slot where the memory board, which produced the error, can be found.
Bit number/Bank number	This is the data bit number and bank number where the error occurred.
Error address	This is the physical address where the error occurred.
Chip ID	This is the ID of the chip where the error occurred.
Error type	Identifies the type of error. Possible settings are: Single/Hard Error A solid, repeatable single bit error. Single/Soft Error An unrepeatable single bit error. A soft error occurring at the same location within 24 hours will result in page deallocation. Single/Unconfirmed A single bit error that could not be confirmed as being either soft or hard. Double bit error A soft or hard, repeatable or unrepeatable double bit error.
Page Status	Possible statuses are: Active: Page is active and can be used. Pending: Page has been marked for deallocation, but has not yet been deallocated. Deallocated: Page is no longer being used.
Logged by	This indicates how the error was found. The possible settings are MEMLOGP, MEMDIAG, HARDWARE, and FOUND IN PDT.
Error count	The number of times the error occurred. First detected: The date and the time when the error was first detected. Last detected: The date and the time when the error was last detected.

The default memory report will only show entries for errors which caused a page of memory to be deallocated (to be no longer used by the system). For a full report, the DETAIL option must be used. A full report will display the entire contents of the memory log file, including entries for errors that are not severe enough to cause page deallocation. Since the full report tracks errors by a combination of error address and error type, it may contain multiple entries for one error address. For example, if an error address starts as a single/unconfirmed error, turns into a single/soft error, and is then deallocated when the error becomes a single/hard error, there will be three entries displayed in the full report. The time stamps with each entry can be used when an error address transitions from one error type to another. Only the entry for the single/hard error will be displayed in the default report.

For systems that do not support memory page deallocation, this command will always display the entire contents of the memory log file, even if the DETAIL option is not used.

Syntax:

     MEMRPT [OUTFILE=<file name>] 
               [;DETAIL]   [;WIDE] 

OUTFILE=<file name> - The output from the command is directed to the 
                      user's terminal unless the OUTFILE keyword is 
                      present. 

   <file_name> ::= Alphanumeric text (starting with an alpha)  |  LP 

   Example: OUTFILE=listfile 

DETAIL -  Display the entire contents of the memory log file, including
          data for errors that did not cause a memory page to be deallocated.

WIDE  -   The WIDE option is used when the output is directed 
          to a device which has 120 or more columns.  If the 
          output device is LP, this option is automatically set. 

     LOGTOOL>memrpt outfile=lp
     LOGTOOL> 

The following memory report will be generated from an HP3000/930 system with three memory controllers:

                    MEMORY ERROR LOGGING REPORT

SYSTEM START TIME             --  WED, JUL 22, 1989,  2:36 PM
LAST ERROR CHECK TIME         --  WED, JUL 22, 1989,  3:29 PM

LOGGING TIME INTERVAL         --  3600 seconds


MEMORY CONTROLLER #  1
-----------------------------------------------------------------------------
|SLOT| CHIP | BIT |    1 ST ERROR     |    LAST ERROR     | ERROR | LOG BY  |
| NUM|  ID  | NUM |    DETECTED AT    |    DETECTED AT    | COUNT | PROCESS |
|---------------------------------------------------------------------------|
|              *** NO MULTI BIT ERRORS HAVE BEEN DETECTED ***               |
----------------------------------------------------------------------------
|              *** NO SINGLE BIT ERRORS HAVE BEEN DETECTED ***              |
-----------------------------------------------------------------------------


MEMORY CONTROLLER #  2
-----------------------------------------------------------------------------
|SLOT| CHIP | BIT |    1 ST ERROR     |    LAST ERROR     | ERROR | LOG BY  |
| NUM|  ID  | NUM |    DETECTED AT    |    DETECTED AT    | COUNT | PROCESS |
|---------------------------------------------------------------------------|
|  A |u3105 |20/ 7| 07/22/87  3:04 PM | 07/22/87  3:05 PM |     3 | MEMLOGP |
-----------------------------------------------------------------------------
|              *** NO MULTI BIT ERRORS HAVE BEEN DETECTED ***               |
-----------------------------------------------------------------------------


MEMORY CONTROLLER #  3

----------------------------------------------------------------------------
|SLOT| CHIP | BIT |    1 ST ERROR     |    LAST ERROR     | ERROR | LOG BY  |
| NUM|  ID  | NUM |    DETECTED AT    |    DETECTED AT    | COUNT | PROCESS |
|---------------------------------------------------------------------------|
|              *** NO MULTI BIT ERRORS HAVE BEEN DETECTED ***               |
----------------------------------------------------------------------------
|              *** NO SINGLE BIT ERRORS HAVE BEEN DETECTED ***              |
-----------------------------------------------------------------------------

MEMTIMER

Syntax:

     MEMTIMER SECONDS=<#seconds> 

SECONDS= <#seconds>  -  The time between memory log scans 

    Example: SEC=3600 

     LOGTOOL>memtimer sec=9600
     LOGTOOL> 

PURGESYSLOG

Syntax:

     PURGESYSLOG LOG=<log list> 
                 [;VERIFY | ;NOVERIFY] 

LOG= <log_list> - The LOG keyword specifies which log files to purge. 

    Example:  LOG=1000/1400,3418/3590,3400,4 

VERIFY|NOVERIFY - The VERIFY option is default for this command. 
                  It causes the user to be prompted before each log file 
                  is deleted.  If NOVERIFY is selected, the specified log 
                  files will be purged without query. 

Example:

     LOGTOOL>purgesyslog log=4232/4235

        Purge LOG4232.PUB.SYS  (Y/N) [N] ? Y 
              ...Deleted LOG4232.PUB.SYS 
        Purge LOG4233.PUB.SYS  (Y/N) [N] ? Y 
              ...Deleted LOG4233.PUB.SYS 
        LOG4234.PUB.SYS was missing 
        Purge LOG4235.PUB.SYS  (Y/N) [N] ? N 
              ...Kept 
     LOGTOOL> 

PURGEWORK

Syntax:

     PURGEWORK FILES=<file list> 
           [;VERIFY | ;NOVERIFY] 

FILES= <file_list>  -  The FILES keyword is used to specify the names 
                          of the work files to purge. 

    Example:  FILE=stuff,junk,foo 

VERIFY|NOVERIFY  -  The VERIFY option is default for this command. 
                    It causes the user to be prompted before each 
                    work file is deleted.  If NOVERIFY is selected, 
                    the specified work files will be purged without query. 

Example:

     LOGTOOL>purgework file=subset1,subset2,junkfile,logtool

         Purge SUBSET1.DIAG.SYS  (Y/N) [N] ? Y 
               ...Deleted SUBSET1.DIAG.SYS 
         SUBSET2.DIAG.SYS does not exist 
         Purge JUNKFILE.DIAG.SYS (Y/N) [N] ? N 
               ...Kept 
         LOGTOOL.DIAG.SYS is not a work file - skipped 

     LOGTOOL> 

REDO

Syntax:

     REDO [? | <index> | <offset>] 

?        - Will display redo stack to user. 

<index>  - A positive number of the command to be modified. 

<offset> - A negative number indicating the offset from 
             the last command given.  "redo -1" is equivalent to "redo." 

Command Example:

     LOGTOOL>sel log=1,,4,5 type=11 ldev=1,2 outfile=myoutfile

     LOG FILE NUMBER EXPECTED.  (LTERR 614) 
     LOGTOOL>redo
            >sel log=1,,4,5 type=11 ldev=1,2 outfile=myoutfile 
            >          d 
            >sel log=1,4,5 type=11 ldev=1,2 outfile=myoutfile 
            >                              i,3 
            >sel log=1,4,5 type=11 ldev=1,2,3 outfile=myoutfile 
            >                                           ddd 
            >sel log=1,4,5 type=11 ldev=1,2,3 outfile=myfile 
            >                   12 
            >sel log=1,4,5 type=12 ldev=1,2,3 outfile=myfile 
            > 
     LOGTOOL>sel log=1,4,5 type=12 ldev=1,2,3 outfile=myfile

            ( Logtool now processes the corrected "select" command ... ) 

SELECT

In order for a log record to be included in the work file, it must match all of the selection criteria specified. The user can define the selection criteria by using the TYPE keyword, DATE or TIME options, or field label keywords.

TYPE keyword	The TYPE keyword can be used to indicate that only log records of the types specified are to be included. The LOGTOOL command TYPES can be used to obtain a list of the log record types available.
DATE or TIME options:	The DATE or TIME options can be used to indicate that only the log records generated between the date and time entered are to be included.
Field Label Keywords:	Field label keywords allow the user to select log records based on the data present in the log record. Whenever the LIST command displays a data item from a log record, a field label is shown before the data item to identify what the item represents. This field label is usually a text abbreviation. Field label keywords allow the user to use this text abbreviation as a selection keyword. For example, if the user wishes to see all log records with a field label of "LDEV" and a logged data value of 1, the parameter of "LDEV=1" can be entered as part of the LIST command.

If no selection criteria are given, all log records found will be included in the work file.

To execute this command, the user must possess at least diagnostic security level 1.

Syntax:

   SELECT LOG=<log list>
          ;OUTFILE= <file name>
          [;TYPE=<type list>]
          [;<field label>=<data list>]
          [;DATE]
          [;TIME]
          [;APPEND]

   LOG=<log list>      - The LOG keyword specifies which log files to
                         base the report on.  Use the STATUS
                         command to obtain a list of the system log files
                         available on the host system.

        <log list> ::= <log number range> | <log number range> , <log list>
        <log number range> ::= <log number> | <log number>/<log number>
        <log number> ::= integer value

        Ex:  LOG=100/105, 150

   OUTFILE=<file name> - The OUTFILE keyword lets the user specify the
                         work file name.

        <file_name> ::=  Alpha-numeric text (starting with an alpha)

        Ex: OUTFILE=listfile


   TYPE=<type list>    - The TYPE keyword is used to specify which log
                         record types (id's) to select for the report.
                         Log record Id's range from 0 to 255. If this
                         TYPE is not used, all log record types will be
                         considered.

        <type list> ::= <type number range> | <type number range>,<type list>
        <type number range> ::= <type number> | <type number>/<type number>
        <type number> ::= integer value

        Ex: TYPE=101,104,106

        <field label>=<data list> - Field label keywords allow the user to
                         select log records based on the data present
                         in the log record.  Quotes are only required
                         for field labels and data items which contain
                         embedded blanks or reserved words used as
                         part of the SELECT command syntax.  If a quote
                         is needed as part of the field label, entering
                         a quote twice ("") will be interpreted as a
                         single quote as part of the field label. For fields
                         which are always displayed as hex arrays or can be
                         displayed as hex arrays by using the HEXDUMP option,
                         the index construct will allow users to select log
                         records by individual array elements.  To use the
                         index construct, the field label must be followed
                         by the array element index number enclosed in
                         square brackets.  Please note that all arrays start
                         with an element index of 1.  The selection
                         criteria specified by a field label keyword
                         will only be met if the data item and the data
                         found in the log record match exactly.  All
                         field labels and text data items will be
                         upshifted before the evaluation is performed.

        <field label> ::= text | "text" | text[<index>] | "text"[<index>]
        <index> ::= integer value starting at 1
        <data list> ::= <data item> | <data item> , <data list>
        <data item> ::= integer value | text | "text"

        Ex: Ldev=1,7  "PRODUCT NAME"=HP7935 JSNAME=JREPORT
            "Hardware status"[1]=4


   DATE                - The DATE option will cause the user to be
                         prompted for a range of dates. Only those log
                         records falling into one of the specified date
                         ranges will be included in the report.
                         Default is the current date.

      Ex:  Enter the starting date [01/01/86] ?  02/02/86
           Enter the ending date [<starting date>]? 02/03/86
           Do you have more dates (Y/N) [N] ? n

   TIME                - The TIME option will cause the user to be
                         prompted for a range of times. Only those log
                         records falling into one of the specified time
                         ranges will be included in the report

      Ex:  Enter the starting time [12:47 PM]? 1:00 PM
           Enter the ending time [<starting time>]? 5:00 PM
           Do you have more to enter (Y/N) [N] ? n

   APPEND              - The APPEND option will append data to the file
                         specified in the OUTFILE parameter.

LOGTOOL>select log=1,2 type=100,105 outf=subset1
    Processing LOG0001.PUB.SYS ...
    Processing LOG0002.PUB.SYS ...

    Total records checked = 109.   Records selected = 2.
LOGTOOL>

STATUS

Syntax:

     STATUS [DETAIL] 

DETAIL - Causes detailed information (# of records and date/time 
         of first log entry) for all of the system log files 
         to be displayed. 

     LOGTOOL>status

     System Log Files: 
     ================= 
     LOG0001    LOG0002    LOG0003    LOG0004    LOG0005* 
     LOGTOOL>status detail

     Log File    Rec #1        Rec #1    Total 
     Name        Date          Time      #Records 
     ==========  ============  ========  ======== 
     LOG0001     11/10/86      10:49 PM       52 
     LOG0002     11/17/86      12:46 PM       57 
     LOG0003                                   0 
     LOG0004     11/22/86       7:22 AM       10 
     LOG0005*    12/01/86       8:30 AM       10 

     LOGTOOL> 

SUMMARIZE

In order for a log record to be considered during the generation of a summary report, it must match all of the selection criteria specified. The user can define the selection criteria by using the TYPE keyword, DATE or TIME options, or field label keywords.

TYPE keyword	The TYPE keyword can be used to indicate that only log records of the types specified are to be displayed. The LOGTOOL command TYPES can be used to obtain a list of the log record types available.
DATE or TIME options	The DATE or TIME options can be used to indicate that only the log records generated between the date and time entered are to be displayed.
Field Label Keywords	Field label keywords allow the user to select log records based on the data present in the log record. Whenever the LIST or SUMMARIZE command displays a data item from a log record, a field label is shown before the data item to identify what the item represents. This field label is usually a text abbreviation. Field label keywords allow the user to use this text abbreviation as a selection keyword. For example, if the user wishes to have all log records with the field label of "LDEV" and a logged data value of 1 considered during the generation of the summary report, the parameter of "LDEV=1" can be entered as part of the SUMMARIZE command.

If no selection criteria is given, all log records present in the system log files will be considered during the generation of the summary report. The SUMMARIZE command can produce two types of summary report.

Simple summary report

If the user does not use the FIELD keyword, a simple summary report will be generated. A simple summary report will display the number of each type of log record present in the specified log files.

Summary report

To generate a summary report using the FIELD keyword, the user must specify which fields of a log record are to be summarized. LOGTOOL will display each unique value found for the fields specified and the number of log records in the log files which have that unique value. If the user specifies more than one field, LOGTOOL will display each unique combination of field values found and the number of log records in the log files which have that unique combination. The summary report will contain the first log record with the unique value found. Please note that the summary report will only display the fields specified by the FIELD keyword.

To execute this command, the user must posses at least diagnostic security level 1.

Syntax:

   LIST LOG=<log list> | FILES=<file list>
        [;OUTFILE=<file name>]
        [;TYPE=<type list>]
        [;<field label>=<data list>]
        [;FIELD=<field label list>]
        [;DATE]
        [;TIME]
        [;WIDE]
        [;HEXDUMP]

   LOG=<log list>      - The LOG keyword specifies which log files to
                         base the report on.  Use the STATUS
                         command to obtain a list of the system log files
                         available on the host system.


        <log list> ::= <log number range> | <log number range> , <log list>
        <log number range> ::= <log number> | <log number>/<log number>
        <log number> ::= integer value

        Ex:  LOG=100/105, 150

   FILES=<file list> -   The FILES keyword is optionally used in place
                         of the LOG keyword. The file list must be a
                         list of "work" files (created by the SELECT
                         command).  Note: All "work" files are created
                         in the diagnostic directory (DIAG.SYS on MPE/iX).


        <file list> ::=  <file name> | <file name> , <file list>
        <file name> ::=  Alpha-numeric text (starting with an alpha)

        Ex:  FILES=file1,file8,junk,work

   OUTFILE=<file name> - The OUTFILE keyword lets the user direct the
                         report to a file or the line printer.
                         Note: All files created by using the OUTFILE
                         parameter will reside in the diagnostic directory
                         (DIAG.SYS on MPE/iX)

        <file name> ::=  Alpha-numeric text (starting with an alpha)  |

                         LP

        Ex: OUTFILE=listfile    or

            OUTFILE=lp          {Output to printer}

   TYPE=<type list>    - The TYPE keyword is used to specify which log
                         record types (id's) to select for the report.
                         Log record Id's range from 0 to 255. If this
                         TYPE is not used, all log record types will be
                         considered.


        <type list> ::= <type number range> | <type number range>,<type list>
        <type number range> ::= <type number> | <type number>/<type number>
        <type number> ::= integer value

        Ex: TYPE=101,104,106


   <field label>=<data list> - Field label keywords allow the user to
                         select log records based on the data present
                         in the log record.  Quotes are only required
                         for field labels and data items which contain
                         embedded blanks or reserved words used as
                         part of the SUMMARIZE command syntax.  If a quote
                         is needed as part of the field label, entering
                         a quote twice ("") will be interpreted as a
                         single quote as part of the field label.
                         For fields which are always displayed as hex arrays
                         or can be displayed as hex arrays by using the
                         HEXDUMP option, the index construct will allow
                         users to select log records by individual array
                         elements. To use the index construct, the field
                         label must be followed by the array element index
                         number enclosed in square brackets.  Please note
                         that all arrays start with an element index of 1.
                         The selection criteria specified by a
                         field label keyword will only be met if the data
                         item and the data found in the log record match
                         exactly.  All field labels and text data items
                         will be upshifted before the evaluation is performed.


        <field label> ::= text | "text" | text[<index>] | "text"[<index>]
        <index> ::= integer value starting at 1
        <data list> ::= <data item> | <data item> , <data list>
        <data item> ::= integer value | text | "text"

        Ex: Ldev=1,7  "PRODUCT NAME"=HP7935 JSNAME=JREPORT
            "Hardware status"[1]=4


   FIELD=<field label list> - The FIELD keyword is used to specify which
                         fields of a log record are to be summarized by
                         the SUMMARIZE command.  Quotes are only required
                         for field labels which contain embedded blanks.


        <field label list> ::= <field label list>,<field label> |
                               <field label>
        <field label>      ::= text | "text"

        Ex: FIELD=ldev,"Hardware status",jsname



   DATE                - The DATE option will cause the user to be
                         prompted for a range of dates. Only those log
                         records falling into one of the specified date
                         ranges will be included in the report. Default
                         is the current day.


      Ex:  Enter the starting date [01/01/86] ?  02/02/86
           Enter the ending date [<starting date>]? 02/03/86
           Do you have more dates (Y/N) [N] ? n


   TIME                - The TIME option will cause the user to be
                         prompted for a range of times. Only those log
                         records falling into one of the specified time
                         ranges will be included in the report.
                         Default is the current time.


      Ex:  Enter the starting time [12:47 PM]? 1:00 PM
           Enter the ending time [<starting time>]? 5:00 PM
           Do you have more to enter (Y/N) [N] ? n


   WIDE                - The WIDE option is used when the output is
                         directed to a device which has 120 or more
                         columns.  If the output device is LP, this
                         option is automatically set.

   HEXDUMP             - The HEXDUMP option is applicable only for I/O
                         and diagnostic records. If used, the hardware
                         status and diagnostic error stack is
                         dumped in HEX rather than being decoded into
                         text statements.

LOGTOOL> summarize log=9/10


                     SUMMARY SYSTEM ERROR LOG REPORT
                     ===============================


 Report Date/Time:  TUE, MAR 31, 1990 - 10:34 AM

 TYPE       DESCRIPTION         COUNT
======  ====================  ==========
   103       JOB TERMINATION         1
   105            FILE CLOSE         3
   108              SPOOLING         1
   111             I/O ERROR        45
   115           CONSOLE LOG        12
======  ====================  ==========


LOGTOOL> summarize log=9/10;type=111;field="hardware status","ldev"


                     SUMMARY SYSTEM ERROR LOG REPORT
                     ===============================


 Report Date/Time:  TUE, MAR 31, 1990 - 10:34 AM


=============================================================================
TUE, MAR 31, 1990   10:34 AM       LOG0009.PUB.SYS            SYSTEM (PIN 28)
I/O ERROR  (NUMBER OF RECORDS = 44)
LDEV:               2
HARDWARE STATUS:

   Status =
   Unit = 0   Volume = 0
   No units with status pending
   >>>>>>>>>> Access Errors <<<<<<<<<<<\esc>
   Drive is not ready for access
   New target address is :
      Vector address =
         Cylinder = 0   Head = 0   Sector = 0
      Block address = 0

=============================================================================
TUE, MAR 31, 1990   10:36 AM       LOG0009.PUB.SYS            SYSTEM (PIN 28)
I/O ERROR  (NUMBER OF RECORDS = 1)
LDEV:               2
HARDWARE STATUS:

   Status =
   Unit = 0   Volume = 0
   No units with status pending
   >>>>>>>>>> Access Errors <<<<<<<<<<<\esc>
   Received an address which exceeds device bounds
   New target address is :
      Vector address =
         Cylinder = 0   Head = 0   Sector = 0
      Block address = 0

=============================================================================


 TYPE       DESCRIPTION         COUNT
======  ====================  ==========
   111             I/O ERROR         45
======  ====================  ==========


LOGTOOL>

SUSPEND

Syntax:

     SUSPEND 

     LOGTOOL>suspend
         LOGTOOL in SUSPEND - [Type EXIT to continue]
     MPE_PROMPT> (any MPE/iX commands)
     MPE_PROMPT> exit
         LOGTOOL resuming from SUSPEND mode ...
     LOGTOOL>

SWITCHLOG

Syntax:

     SWITCHLOG 

     LOGTOOL>switchlog
     LOGTOOL> 

TYPES

Syntax:

   TYPES [TYPE=<type list>]
            [;DETAIL | ;SUMMARY]

   TYPE=<type list>    - The TYPE keyword is used to specify which log
                         record types (id's) to display information for.
                         Log record Id's range from 0 to 255. If this
                         TYPE is not used, all log record types will be
                         displayed.

        <type list> ::= <type number range> | <type number range>,<type list>
        <type number range> ::= <type number> | <type number>/<type number>
        <type number> ::= integer value

        Ex: TYPE=101,104,106

   DETAIL     - Causes detailed information for each record ID
                to be displayed.

   SUMMARY    - Causes the field label keywords and data field
                labels to be displayed for each field of a record ID.

LOGTOOL> types

   Type         Description
  ------    ---------------------
   100      LOG FAILURE
   101      SYSTEM UP
   102      JOB INITIATION
   103      JOB TERMINATION
   104      PROCESS TERMINATION
   105      NM FILE CLOSE
   106      SYSTEM SHUTDOWN
   107      POWER FAILURE
   111      I/O ERROR
   112      PHY. MOUNT/DISMOUNT
   113      LOG. MOUNT/DISMOUNT
   114      TAPE LABEL
   115      CONSOLE LOG
   116      PROGRAM FILE EVENT
   120      NM SPOOLING
   121      FILE QUARANTINE EVNT
   130      AIFs
   131      ADD PROCESSOR LAUNCH
   134      PASSWORD CHANGE
   135      SYS LOGGING CONFIG
   136      RESTORE
   137      PRINTER ACCESS FAIL
   138      ACD CHANGE
   139      STREAM INITIATION
   140      USER LOGGING
   141      PROCESS CREATION
   143      CHGROUP
   144      FILE OPEN
   146      MAINTENANCE REQUEST
   148      UPS MONITOR LOG
   150      DIAGNOSTIC INFO
   151      HPMC
   152      LPMC
   160      CM FILE CLOSE
   205      NM FILE CLOSE
   227      CHDIR
   228      PROCESS ADOPTION
   229      FILE OWNER CHANGE
   234      PASSWORD CHANGES
   236      RESTORE
   238      ACD CHANGE
   240      USER LOGGING
   241      PROCESS CREATION
   242      SECURITY CONFIG CHG
   244      FILE OPEN
   245      CI COMMAND LOG
   305      NM FILE CLOSE
   344      FILE OPEN

LOGTOOL>

Standalone Logtool for MPE/iX: Records

• Record Definition Files
• Record Definition Commands
  • COMMENT
  • RECORD`ID
  • TAG`ID
• Record Description Commands
  • RECORD`LENGTH
  • N`FIELDS
  • RECORD`LABEL
  • FIELD`FORMAT
  • VAR`LABELS
  • VALUE`LABELS
  • VARIANT
• Tag Usage Example
• RECORD`ID Installation Example

Record Definition Files

     <record id X control statements> 
     <record id Y control statements> 
     <record id Z control statements> 

           _________________________________________________ 
          |                        |                        |
                 Command Field        Specification Field 

COMMENT      The "COMMENT" is a record definition command. 
             The body of the comment is called the specification 
             field (that is what you are reading now).  Notice that 
             this field can span as many lines as desired. 
             A new control command ends the specification field. 

RECORD`ID    23     {This is a comment too} 

COMMENT      The above line has "RECORD`ID" as the Command 
             and "23" as the specification field. 

Record Definition Commands

COMMENT

Syntax:

     COMMENT         <anything may follow> 

      COMMENT         This is a comment. 
                      It spans several lines. 

RECORD`ID

Syntax:

     RECORD`ID       <record id #> 

     RECORD`ID       1 
     RECORD`ID       123 

TAG`ID

     TYPE my_record = RECORD 
             field1 : integer; 
             CASE select : boolean OF 
                true  : (true_case : some_other_type); 
                false : (false_case : yet_another_type); 
          END; 

Syntax:

     TAG`ID       <record id # this definition is used with> 

     TAG`ID       100 

Record Description Commands

     RECORD`LENGTH 
     N`FIELDS 
     RECORD`LABEL 
     FIELD`FORMATS 

RECORD`LENGTH

Syntax:

     RECORD`LENGTH   <# of bits> 

Example:

     RECORD`LENGTH   220 

N`FIELDS

Syntax:

     N`FIELDS        <# of fields> 

     N`FIELDS        5 

RECORD`LABEL

Syntax:

     RECORD`LABEL    "<name>" 

      RECORD`LABEL    "I/O" 
      RECORD`LABEL    

FIELD`FORMAT

  [current length]     [ASCII data]       [String trailer] 
|__________________|___________________|__________________|
          |                    |                 |
  String Overhead        String Data       String Overhead 

 XX XX XX XX XX XX XX XX  ..hello.. 
 XX XX XX XX XX XX XX XX  ..w....4. 

Syntax:

     FIELD`FORMAT    <field list> 

     <field list>    ::= <repeat factor> (<field def>) | 
                            <repeat factor> (<field def>) <field list> 
     <repeat factor> ::= an integer | <nil> 
     <field def>     ::= <#bits>, JUNK | 
                         <#bits>, STRING | 
                         <#bits>, ARRAY | 
                         <#bits>, ASCII | 
                         <#bits>, LLIOSTAT | 
                         <#bits>, MPEXLSTAT | 
                         <#bits>, TIME | 
                         <#bits>, DATE | 
                         <#bits>, INTEGER, <base> | 
                         <#bits>, INTEGER, <base>, TAG, <#bits> 
     <#bits>         ::= 0 .. 16256 
     <base>          ::= 2 | 8 | 10 | 16 

• The total # of bits must match the record length specification.
• The number of fields must match the N`FIELDS specifications.
• ARRAY, ASCII, & STRING data must start on byte boundaries.
• ARRAY, ASCII, & STRING data must be multiples of 8 bits in length.
• ARRAY, ASCII, & STRING data can have a maximum of 132 bytes.
• ARRAY data will always print out in whole bytes.
• Integer data is at most 64 bits long.
• The length given for string data should include the overhead bytes value.

        FIELD`FORMAT    2(32,INTEGER,16) (160,ASCII)(3,INT,8)(13,JUNK) 
                        (64,STRING) (64,ARRAY) (12,INTEGER,10,TAG,20) 

            - TWO (2) 32 bit integer fields printed in HEX 
            - 160 bits (32 chars) of printed in ascii. 
            - A 3 bit integer printed in octal 
            - 13 bits of junk which it not printed 
            - A 64 bit (8 char max) string - only valid chars printed. 
            - A 64 bit (8 bytes) array printed as HEX/ASCII 
            - A 12 bit integer tag field printed in decimal 
              20 additional bits [identified by the tag] follow. 
              A TAG`ID must be used to describe the data. 

VAR`LABELS

Syntax:

     VAR`LABELS      <label def> 

     <label def>     ::= <label index> "<label>" <label def> | 
                         <label index> "<label>" |  <nil> 
     <label index>   ::= [ <field#> ] 
     <label>         ::= ASCII<\esc> text (up to 20 chars) 
     <field#>        ::= an integer 

• Single or double quotes may be used to bracket the label.
• The maximum # of characters is 20.

        VAR`LABELS      [ 1 ]     "Name for field 1 : " 
                        [ 2 ]     "field 2 name : " 
                        [ 4 ]     "field 3 is unlabeled" 

VALUE`LABELS

Syntax:

     VALUE`LABELS  <label def> 

         <label def>     ::= <label index> (<label list>) <label def> | <nil> 
         <label index>   ::= [ <field#> ] 
         <label list>    ::= <value range>, "<label>" | 
                             <value range>, "<label>" ; <label list> | <nil> 
         <value range>   ::= <value> | <value>/<value> 
         <value>         ::= an integer 
         <label>         ::= ASCII<\esc> text (up to 20 chars) 
         <field#>        ::= an integer 

• Single or double quotes may be used to bracket the label.
• The maximum number of characters is 20.
• If a value label is given and data in the log file does not match one of the indicated values, it will simply be printed as numeric data as indicated in the FIELD`FORMAT command.

     VALUE`LABELS    [ 2 ] (1, "one"; 2, "two"; 3, "three") 
                     [ 3 ] (-1, "Unlimited"; 1/14 "Half power") 
                     [ 8 ] (-32768/-1, "Negative"; 
                           0/32767, "Positive") 

VARIANT

     FIELD`FORMAT    (8,INT,10,TAG,64) 

Error checking is performed to ensure that only TAG data types have variants. The value associated with a tag is not limited to a single value, but a range of values may be specified for a tag. All ranges must be unique and may not overlap with any other value or range.

Syntax:

     VARIANT   <variant def> 

    <variant def>   ::= <label index> ( <variant list> ) <variant def> | <nil> 
    <label index>   ::= [ <field#> ] 
    <variant list>  ::= <value range> 
    <value range>   ::= <value> | <value>/<value> 
    <value>         ::= an integer 
    <field#>        ::= an integer 

     VARIANT         [ 1 ] (1/100) 
                     [ 3 ] (-5 )    {This example is for a TAG`ID which 
                                     has a variant field} 

Tag Usage Example

     TYPE 
        some_other_type = integer;       { 32 bits } 

        yet_another_type = RECORD 
           count : integer;              { 32 bits } 
           name  : string[4];            { (4 " 8 bits) + 64 bit overhead } 
           CASE stuff : integer OF       { 32 bits } 
              0 : ( f1 : integer );      { 32 bits } 
              1 : ( f2 : bit8 );         { 8 bits } 
        END;                             { SIZEOF = 192 bits } 

     YET_ANOTHER_TYPE                   MAX RECORD SIZE = x18 BYTES 
        COUNT                              x0.0 @ 4.0 
        NAME                               x4.0 @ C.0 <- Note compiler added 
                                                        32 bits for string 
                                                        header and 32 bits 
                                                        for string trailer. 
     STUFF                             x10.0 @ 4.0 
        F1                              x14.0 @ 4.0 
        F2                              x14.0 @ 1.0 

        my_record = RECORD 
           field1 : integer;                          { 32 bits } 
           CASE select : boolean OF                   { 8 bits + 12 bits pad} 
              true  : (true_case : some_other_type);  { 32 bits } 
              false : (false_case : yet_another_type);{ 192 bits (max) } 
        END;                                          { SIZEOF = 256 bits } 

     MY_RECORD                          MAX RECORD SIZE = x20 BYTES 
        FIELD1                             x0.0 @ 4.0 
        SELECT                             x4.0 @ 1.0  <- Note: compiler padded 
                                                          to next word. 
        TRUE_CASE                        x8.0 @ 4.0 
        FALSE_CASE                       x8.0 @ 18.0 

   COMMENT             This defines MY_RECORD " 

   RECORD`ID           1 
   RECORD`LENGTH       256 
   RECORD`LABEL        "MY_REC" 
   N`FIELDS            2 

   FIELD`FORMAT        {field1} (32,INT,10) 
                       {select} (8,INT,10,TAG,216) 

   VAR`LABELS          [ 1 ] "field 1 :" 
                       [ 2 ] "select code : " 

   VALUE`LABELS        [ 2 ] (0,"False";  1, "True" ) 

   COMMENT             " This defines the case variant "TRUE" 
                         (SOME_OTHER_TYPE) from the above record 

   TAG`ID              1     {This tag is to be used with RECORD`ID 1} 
   RECORD`LENGTH       216   {Must match length given in FIELD`FORMAT} 
   RECORD`LABEL 
   VARIANT             [ 2 ] (1) 
   N`FIELDS            3 

   FIELD`FORMAT        {compiler filler} (24,junk) 
                       {some_other_type} (32,INT,10) 
                       (160, junk)       {Total # bits must match RECORD`LENGTH} 
   VAR`LABELS          [ 1 ] "True Case" 

   COMMENT             " This defines the case variant "FALSE" 
                         (YET_ANOTHER_TYPE) from  the above record  " 

   TAG`ID              1     {This tag is to be used with RECORD`ID 1} 
   RECORD`LENGTH       216   {Must match length given in FIELD`FORMAT} 
   RECORD`LABEL 
   VARIANT             [ 2 ] (0)   {Use this TAG`ID for RECORD`ID 1, when} 
                                   {the second field has a value of zero} 
   N`FIELDS            4 

   FIELD`FORMAT        (24,junk) (32,INT,10) (96,STRING) (32,INT,16,TAG,32) 
   VAR`LABELS          [ 1 ] "Count :" 
                       [ 2 ] "Name : " 
                       [ 3 ] "Stuff tag : " 

   COMMENT             " This defines the case variant "0" of 
                         (YET_ANOTHER_TYPE) from  the above record  " 

   TAG`ID              1            {This tag is to be used with RECORD`ID 1} 
   RECORD`LENGTH       32           {Must match length given in FIELD`FORMAT} 
   RECORD`LABEL 

   VARIANT             [ 2 ] (0) 
                       [ 4 ] (0)     {Use this TAG`ID when field 3 of} 
                                     {previous TAG`ID has a value of zero} 
   N`FIELDS            1 

   FIELD`FORMAT        (32,INT,10) 
   VAR`LABELS          [ 1 ] "F1:" 

   COMMENT             " This defines the case variant "1" of 
                         (YET_ANOTHER_TYPE) from  the above record  " 

   TAG`ID              1             {This tag is to be used with RECORD`ID 1} 
   RECORD`LENGTH       32            {Must match length given in FIELD`FORMAT} 
   RECORD`LABEL 
   VARIANT             [ 2 ] (0) 
                       [ 4 ] (1)      {Use this TAG`ID when field 3 of} 
                                      {previous TAG`ID has a value of zero} 
   N`FIELDS            2 

   FIELD`FORMAT        (8,INT,10) (24,junk) 
   VAR`LABELS          [ 1 ] "F2:" 

     TYPE 
        some_record = RECORD 
           case integer of 
              0 : (f1 : type1); 
              1 : (f2 : type2); 
              2 : (f3 : type3); 
        END; 

RECORD`ID Installation Example

For the following example, the log entry will be that of the MPE/iX low-level I/O (LLIO) system which consists of many software modules called "I/O managers." This log entry has the unique attribute that the record definition is written in parts. The log entry itself is written in two parts. A main header which displays information common to all "I/O managers" and a LLIO software dependent portion, which contains information specific to one software module.

The PASCAL declaration for the log entry header information is as follows:

type 
 io_fixed_rec_type = record 
    product_name    : dac_prodnum_type;  { Name: i.e. "HP7933" } 
    pdev            : pdev_str;          { Physical path i.e. "1.1.3" } 
    ldev            : ldev_str;          { Logical device name } 
    dev_class_code  : shortint;          {`ID for DISC, TAPE, etc } 
    diag_msg_class  : bit8;              { Indicates HW/SW/OTHER I/O err } 
    llio_stat       : integer;           { HPE status } 

    log_all_retries : boolean;           { TRUE if retries not summarized } 
    retry_again     : boolean;           { TRUE if log_all_entries&will retry } 
    io_worked       : boolean;           { Did I/O finally work ? } 
    run_autodiag    : boolean;           { Were Auto diagnostics run? } 
    retry_count     : shortint;          { N'th retry OR Total retries } 
    mgr_port_num    : integer;           { port number of manager } 
    tran_num        : integer;           { transaction number } 
    hdwr_len        : shortint;          { # of valid bytes in the HDWR_STAT} 
    hdwr_stat       : hdwr_stat_type;    { Hardware status bytes } 
 end;   {io_fixed_rec_type} 

 io_event_array = packed array [ 1..max_buff_bytes ] of char; 

 io_var_rec_type = record 
    data_len    : shortint;              { # of valid bytes in DATA } 
    mgr_code    : shortint;              { Uniquely IDs the mgr } 
    case boolean of                     
       true  : (data : packed array [1..max_event_count] of io_event_array); 
       false : (buff : packed array [1..io_var_len-4] of char); 
 end;    {io_var_rec_type} 

RECORD`ID       111 
RECORD`LENGTH   16224 
N`FIELDS        25 
RECORD`LABEL    "I/O ERROR" 
FIELD`FORMAT    {1 product_name}      (320,string) 
                {2 pdev}              (320,string) 
                {3 ldev}              (320,string) 
                {4 dev_class_code}    (16,int,10) 
                {5 diag_msg_class}    (8,int,10) (8,junk) 
                {7 llio_stat}         (0,int, 10 ) (32,lliostat) 
                {9 log_all_retries}   (7,junk) (1,int,10)
                {11 retry_again}      (7,junk) (1,int,10) 
                {13 io_worked}        (7,junk) (1,int,10) 
                {15 run_autodiag}     (7,junk) (1,int,10) 
                {17 retry_count}      (16,int,10) 
                {18 mgr_port_num }    (16,junk) (32,int,16) 
                {20 tran_num}         (32,int,16) 
                {21 hdwr_len}         (16,int,10) 
                {22 reserved}         (16,junk)
                {23 hdwr }            (320,hardstat)
                {24 datalen}          (16,int,10) 
                {25 mgrcode}          (16,int,10,tag,14688) 
                {---IO_VAR portion } 

VAR`LABELS      [ 1 ] "PRODUCT NAME:" 
                [ 2 ] "PDEV:" 
                [ 3 ] "LDEV:" 
                [ 4 ] "DEVICE CLASS:" 
                [ 5 ] "I/O EVENT CLASS:" 
                [ 8 ] "LLIO STATUS:"
                [ 10 ] "RETRY SCHEME:" 
                [ 12 ] "WILL RETRY:" 
                [ 14 ] "I/O RESULT:" 
                [ 16 ] "RUN AUTODIAG:" 
                [ 17 ] "RETRY COUNT:" 
                [ 19 ] "MGR PORT NUM.:" 
                [ 20 ] "TRANS. NUM. :" 
                [ 21 ] "# HDWR BYTES:" 
                [ 23 ] "HARDWARE STATUS:"
                [ 24 ] "DATA LEN:" 
                [ 25 ] "MGR CODE:" 

VALUE`LABELS 
                [ 5 ] (0,"Hardware";        1,"Software";     2,"Other") 
                [ 4 ] (0,"Hard Disc";       1,"Mag Tape";     2,"Terminal"; 
                       4,"Plotter";         7,"Bus Converter" 13,"Crd Rdr";
                      16,"DTC";            19,"Term. Mux.";   21,"Printer";
                      22,"CA";             23,"DA")
                [ 10 ] (1,"Log Each Retry";  0,"Summarized Retries") 
                [ 12 ] (1,"YES"; 0,"NO" ) 
                [ 14 ] (1,"I/O Successful";  0,"I/O Failed") 
                [ 16 ] (1,"YES"; 0,"NO" ) 

:logtool

     ************************************************************ 
     *****                                                  ***** 
     *****                       LOGTOOL                    ***** 
     *****                                                  ***** 
     *****          (C) Copyright Hewlett Packard Co. 1987  ***** 
     *****                 All Rights Reserved.             ***** 
     *****                   Version A.00.00                ***** 
     *****                                                  ***** 
     ************************************************************ 

     Welcome, Today is MON, August 10, 1987 at 12:30 PM 

LOGTOOL>list log=23;type=111  {Display the log entry 
                                without a record definition} 

                             SYSTEM ERROR LOG REPORT 
                             ======================= 

 Report Date/Time:  TUE, JAN  1, 1987 -  2:25 AM 

=============================================================================== 
TUE, JAN  1, 1987    2:22 AM       LOG0023.PUB.SYS              SYSTEM (PIN 27) 
RECORD TYPE 111 
      1   2   3   4   5   6   7   8   9   10  11  12 
      ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  == 
  1:  00  00  00  07  48  50  49  42  44  41  4D  00   . . . . H P I B D A M . 
 13:  00  00  00  00  00  00  00  00  00  00  00  00   . . . . . . . . . . . . 
 25:  00  00  00  00  00  00  00  00  00  00  00  00   . . . . . . . . . . . . 
 37:  00  00  00  00  00  00  00  03  38  2E  32  00   . . . . . . . . 8 . 2 . 
 49:  00  00  00  00  00  00  00  00  00  00  00  00   . . . . . . . . . . . . 
 61:  00  00  00  00  00  00  00  00  00  00  00  00   . . . . . . . . . . . . 
 73:  00  00  00  00  00  00  00  00  00  00  00  00   . . . . . . . . . . . . 
 85:  00  00  00  00  00  00  00  00  00  00  00  00   . . . . . . . . . . . . 
 97:  00  00  00  00  00  00  00  00  00  00  00  00   . . . . . . . . . . . . 
109:  00  00  00  00  00  00  00  00  00  00  00  00   . . . . . . . . . . . . 
121:  00  06  00  00  5A  00  00  74  00  00  00  00   . . . . Z . . t . . . . 
133:  00  00  00  00  FF  FF  FF  AE  00  00  00  00   . . . . . . . . . . . . 
145:  00  01  00  00  01  02  00  00  00  00  00  00   . . . . . . . . . . . . 
157:  00  00  00  00  00  00  00  00  00  00  00  00   . . . . . . . . . . . . 
169:  00  00  00  00  00  00  00  00  00  00  00  00   . . . . . . . . . . . . 
181:  00  00  00  00  00  00  00  00  00  18  00  74   . . . . . . . . . . . t 
193:  02  00  00  00  00  00  00  0C  00  45  45  45   . . . . . . . . . E E E 
205:  00  00  00  0C  00  67  46  94  00  00  00  09   . . . . . g F . . . . . 

DEVICE HARDWARE STATUS: 
      1   2   3   4   5   6   7   8   9   10  11  12 
      ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  == 
  1:  FF                                               . 
=============================================================================== 

 TYPE       DESCRIPTION         COUNT 
======  ====================  ========== 
   111                               1 
======  ====================  ========== 

LOGTOOL>layout file=layllio; append     {Update data base file} 
   Processing ID 111 ... 
================================================ 

End processing of layout file LAYLLIO.DIAG.SYS 
0 Errors encountered 
1 out of 1 record ID's were accepted. 
0 out of 0 tag ID's were accepted. 

Number of messages in LAYMSG = 287 
Header records in LAYOUTF = 25 
Total record in LAYOUTF = 799 

LOGTOOL> list log=23; type=111   {Display log entry with header} 

                             SYSTEM ERROR LOG REPORT
                             =======================


 Report Date/Time:  TUE, JAN  1, 1987 -  2:26 AM

TUE, JAN  1, 1987    2:22 AM       LOG0023.PUB.SYS              SYSTEM (PIN 27)
I/O ERROR
PRODUCT NAME:       HPIBDAM             PDEV:               8.2
LDEV:                                   DEVICE CLASS:       6
I/O EVENT CLASS:    Hardware            LLIO STATUS:        $5A000074

MPE/XL I/O Status: Proc. Num. = 0, Error Num. = 90, Subsystem = 116

RETRY SCHEME:       Summarized Retries WILL RETRY:         NO
I/O RESULT:         I/O Failed         RUN AUTODIAG:       NO
RETRY COUNT:        0                  MGR PORT NUM.:      -82
TRANS. NUM. :       0                  # HDWR BYTES:       1
HARDWARE STATUS:
      1   2   3   4   5   6   7   8   9   10  11  12
      ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==
  1:  FF                                               .

DATA LEN:           24                 MGR CODE:           116
TAG DEFINITION NOT GIVEN - FIELD WILL BE DISPLAYED IN HEX:
      1   2   3   4   5   6   7   8   9   10  11  12
      ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==
  1:  02  00  00  00  00  00  00  0C  00  45  45  45   . . . . . . . . . E E E
 13:  00  00  00  0C  00  67  46  94  00  00  00  09   . . . . . g F . . . . .

 TYPE       DESCRIPTION         COUNT
======  ====================  ==========
   111             I/O ERROR         1
======  ====================  ==========

LOGTOOL> 

   TYPE 
     dam_log_info_type = PACKED RECORD 
        hw_status      : bit8; 
        dam_mgr_ptr    : srv_ptr_type; 
        dam_msg_ptr    : msg_ptr_type; 
        dam_uid_num    : integer; 
     END; 

   DAM_LOG_INFO_TYPE                    MAX_RECORD_SIZE = x18 BYTES 
     HW_TSTATUS                           x0.0 @ 1.0 
     DAM_MGR_PTR                          x4.0 @ 8.0 
     DAM_MSG_PTR                          xC.0 @ 8.0 
     DAM_UID_NUM                         x14.0 @ 4.0 

TAG`ID 111                       {HP-IB device adapter manager} 
RECORD`LENGTH 192 
N`FIELD 7 
RECORD`LABEL 
VARIANT  [25] (116) 
FIELD`FORMAT  (8,int,16)         {Hardware status} 
              (24,junk)          {Compiler filler} 
              (32,int,16)        {Port data area address} 
              (32,int,16) 
              (32,int,16)        {Message pointer} 
              (32,int,16) 
              (32,int,10)        {UID} 

VAR`LABEL [ 1 ] "HDWR STATUS:" 
          [ 3 ] "PDA SPACE`ID:" 
          [ 4 ] "PDA OFFSET:" 
          [ 5 ] "MSG SPACE`ID:" 
          [ 6 ] "MSG OFFSET:" 
          [ 7 ] "UID:" 

:logtool

     ************************************************************ 
     *****                                                  ***** 
     *****                     LOGTOOL                      ***** 
     *****                                                  ***** 
     *****         (C) Copyright Hewlett Packard Co.        ***** 
     *****                All Rights Reserved.              ***** 
     *****                  Version A.00.00                 ***** 
     *****                                                  ***** 
     ************************************************************ 

     Welcome, Today is MON, August 10, 1987 at 12:30 PM 


LOGTOOL>layout file=layport;append
     Processing TAG`ID 111 ... 
============================================== 

End processing of layout file LAYPORT.DIAG.SYS 

0 Errors encountered 
0 out of 0 record`IDs were accepted. 
1 out of 1 tag`IDs were accepted. 

Number of messages in LAYMSG = 292 
Header records in LAYOUTF=26 
Total records in LAYOUTF = 819 

LOGTOOL>list log=14;type=111    {Display log entry} 

                             SYSTEM ERROR LOG REPORT
                             =======================


 Report Date/Time:  TUE, JAN  1, 1987 -  2:27 AM


===============================================================================
TUE, JAN  1, 1987    2:22 AM       LOG0023.PUB.SYS              SYSTEM (PIN 27)
I/O ERROR
PRODUCT NAME:       HPIBDAM             PDEV:               8.2
LDEV:                                   DEVICE CLASS:       6
I/O EVENT CLASS:    Hardware            LLIO STATUS:        $5A000074

MPE/XL I/O Status: Proc. Num. = 0, Error Num. = 90, Subsystem = 116

RETRY SCHEME:       Summarized Retries WILL RETRY:         NO
I/O RESULT:         I/O Failed         RUN AUTODIAG:       NO
RETRY COUNT:        0                  MGR PORT NUM.:      -82
TRANS. NUM. :       0                  # HDWR BYTES:       1
HARDWARE STATUS:
      1   2   3   4   5   6   7   8   9   10  11  12
      ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==  ==
  1:  FF                                               .

DATA LEN:           24                 MGR CODE:           116
HDWR STATUS:        $2                 PDA SPACE ID:       $C
PDA OFFSET:         $454545            MSG SPACE ID:       $C
MSG OFFSET:         $674694            UID:                9
===============================================================================


 TYPE       DESCRIPTION         COUNT
======  ====================  ==========
   111             I/O ERROR         1
======  ====================  ==========

LOGTOOL>

Standalone Logtool for MPE/iX: Error and Warning Messages

NOTE: To find a given error message, use the Search feature on your browser. For example, search on the string "1000" to find error 1000.

401	*** PASCAL CASE STATEMENT OVERFLOW IN ! (LTERR 401)
CAUSE	LOGTOOL has hit the otherwise clause of an CASE statement. This is a software error.
ACTION	Please submit a service request indicating the following: a) The exact text of the above error message including the parameter. b) Any other error messages displayed with this error message. c) The sequence of LOGTOOL commands which were being performed when this error message was encountered. d) The version (A.nn.nn) of the LOGTOOL being executed.
404	*** UNABLE TO OBTAIN MESSAGE ! FROM DIAG. CATALOG (LTERR 404)
CAUSE	LOGTOOL was not able to obtain a text message from LOGTOOL's message set in the diagnostic message catalog.
ACTION	Please submit a service request indicating the following: a) The exact text of the above error message including the parameter. b) Any other error messages displayed with this error message. c) The sequence of LOGTOOL commands which were being performed when this error message was encountered. d) The version (A.nn.nn) of the LOGTOOL being executed.
405	*** ERROR ATTEMPTING TO DELETE FILE !. (LTERR 405)
CAUSE	LOGTOOL encountered an error while attempting to purge a file. The file name will be displayed in this error message.
ACTION	Error messages containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.
406	*** ERROR ATTEMPTING TO OPEN FILE !. (LTERR 406)
CAUSE	LOGTOOL encountered an error while attempting to open a file. The file name will be displayed in this error message.
ACTION	Error messages containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.
407	*** ERROR ATTEMPTING TO CLOSE FILE !. (LTERR 407)
CAUSE	LOGTOOL encountered an error while attempting to close a file. The file name will be displayed in this error message.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.

408	****** ERROR ATTEMPTING TO READ FROM FILE !. (LTERR 408)
CAUSE	LOGTOOL encountered an error while attempting to read from a file. The file name will be displayed in this error message.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.
409	****** ERROR ATTEMPTING TO WRITE TO FILE !. (LTERR 409)
CAUSE	LOGTOOL encountered an error while attempting to write to a file. The file name will be displayed in this error message.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.
410	****** ERROR ATTEMPTING TO CREATE FILE !. (LTERR 410)
CAUSE	LOGTOOL encountered an error while attempting to create a file. The file name will be displayed in this error message.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.
414	****** FILE "LAYOUTF" CORRUPTED. ID !. EXPECTED !. REC# !. (LTERR 414)
CAUSE	LOGTOOL discovered some inconsistencies while it was reading its data base file LAYOUTF.
ACTION	Contact support personnel to get new LAYOUTF and LAYMSG files.
417	****** COULD NOT DECODE STATUS FOR ! DEVICE (LTERR 417)
CAUSE	LOGTOOL issued a request to the diagnostic system to have the appropriate diagnostic program initiated for decode of hardware status. That request was not granted. Therefore, the hardware status is displayed as a HEX dump.
ACTION	Messages indicating why the request was not granted will be displayed with this error message. Please refer to the ACTION clause for those messages for further information.
418	****** COULD NOT KILL ! AFTER STATUS DECODE FINISHED (LTERR 418)
CAUSE	LOGTOOL was not able to abort a diagnostic program which was initiated for decoding of hardware status.
ACTION	Messages indicating why the diagnostic program could not be aborted will be displayed with this error message. Please refer to the ACTION clause for those messages for further information.
421	****** ERROR ATTEMPTING TO READ RECORD ! FROM "!" (LTERR 421)
CAUSE	LOGTOOL encountered an error while attempting to read from a file. The file name will be displayed in this error message.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.

429	****** SWITCHLOG COMMAND WAS NOT PERFORMED ( LTERR 429 )
CAUSE	LOGTOOL requested that a switchlog command be performed by the operating system. That request returned an error.
ACTION	Error messages containing further information will be displayed with this message. Please refer to the ACTION clause for those error messages.
430	****** UNABLE TO DETERMINE CURRENT LOG FILE. ( LTERR 430 )
CAUSE	LOGTOOL requested that a showlog command be performed by the operating system. That request returned an error.
ACTION	Error messages containing further information will be displayed with this message. Please refer to the ACTION clause for those error messages.
446	****** UNABLE TO OBTAIN PDEV FOR LDEV !. (LTERR 446)
CAUSE	LOGTOOL was not able to convert a physical device specifier into a logical device number.
ACTION	Error messages giving further detail as to the type of problem encountered will be displayed with this message. Please refer to the ACTION clause for those error messages for further information.
452	****** WARNING: SYSTEM LOGGING IS SUSPENDED (LTWARN 452)
CAUSE	The host operating system indicates that the system logging facility has been suspended. Therefore, the SWITCHLOG request was not performed.
ACTION	Resume the system logging facility.
453	****** WARNING: SYSTEM LOGGING IS DISABLED (LTWARN 453)
CAUSE	The host operating system indicates that the system logging facility has been disabled. Therefore, the SWITCHLOG request was not performed.
ACTION	Start the system logging facility.
455	****** UNABLE TO COMMUNICATE WITH MEMORY LOGGING PROCESS (LTERR 455)
CAUSE	The user has issued either a MEMTIMER, MEMCLR, or MEMRPT command to LOGTOOL. To perform these commands, LOGTOOL must communicate with the memory logging process. LOGTOOL is not able to locate MEMLOGP.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
456	****** UNABLE TO OBTAIN MEMORY REPORT DATA (LTERR 456)
CAUSE	The user has issued a MEMRPT command to LOGTOOL. LOGTOOL was not able to successfully obtain memory report information from the memory logging process (MEMLOGP).
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.

457	****** UNABLE TO START DISPLAYLOG COMMAND (LTERR 457)
CAUSE	LOGTOOL was not able to notify the diagnostic system that DISPLAYLOG was to start.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
458	****** UNABLE TO STOP DISPLAYLOG COMMAND (LTERR 458)
CAUSE	LOGTOOL was not able to notify the diagnostic system that DISPLAYLOG was to stop.
ACTION	Enable error tracing by rerunning the program with the TRACE=ERROR parameter at the DUI command line, and file a service request with the trace information generated when performing the LOGTOOL command again.
459	****** LOGTOOL ABORTING DUE TO AN UNRECOVERABLE ERROR. FURTHER ERROR INFORMATION HAS BEEN LOGGED IN THE SYSTEM LOG FILE. (LTERR 459)
CAUSE	LOGTOOL encountered an error it could not recover from. Further error information has been logged into the system log file as a diagnostic log record. Depending on the error, this message may not make it to the users terminal, but LOGTOOL is try to tell the user that it is aborting.
ACTION	Please find the diagnostic log record containing the detailed error information on why LOGTOOL aborted. In most cases, a service request may need to be submitted.
460	****** LOGTOOL ERROR NUMBER IS !. (LTERR 460)
CAUSE	LOGTOOL encountered an error it could not recover from. The number given will identify the type of error encountered.
ACTION	Enable error tracing by rerunning the program with the TRACE=ERROR parameter at the DUI command line, and file a service request with the trace information generated when performing the LOGTOOL command again.
461	****** LOGTOOL ABORTED DUE TO AN ERROR IN PROCEDURE ! (LTERR 461)
CAUSE	LOGTOOL encountered an error it could not recover from. The procedure name given will identify the location in LOGTOOL code where the error occurred.
ACTION	Please submit a service request indicating the following: a) The exact text of the above error message including the parameter. b) Any other error messages displayed with this error message. c) The sequence of LOGTOOL commands which were being performed when this error message was encountered. d) The version (A.nn.nn) of the LOGTOOL being executed.

462	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO CONVERT A LOG NUMBER ***TO A PASCAL STRING (LTERR 462)
CAUSE	After obtaining a log number from the user, LOGTOOL needs to convert that number from an integer to a PASCAL string. This string is later used to form a log file name.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
463	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO FULLY QUALIFY A LOG ***FILE NAME (LTERR 463)
CAUSE	After LOGTOOL has formed a log file name from the log file number given, it must fully qualify the file name to access the file. An unexpected error occurred while trying to fully qualify the log file name with the directory where log files are stored.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
464	****** UNABLE TO START PROGRAM TRACE (LTERR 464)
CAUSE	LOGTOOL was not able to notify the diagnostic system that tracing of program procedures is to begin.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
465	****** UNABLE TO START PROGRAM AND LIBRARY TRACE (LTERR 465)
CAUSE	LOGTOOL was not able to notify the diagnostic system that tracing of program and diagnostic library procedures is to begin.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
466	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO WRITE THE LOGTOOL ***FILE HEADER TO THE WORK FILE (LTERR 466)
CAUSE	The first record of each work file create by LOGTOOL contains a unique header. LOGTOOL uses this header to identify work files from other disk files found in the diagnostic directory. In this situation, LOGTOOL encountered an unexpected error while trying to write the header information to the work file.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.

467	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO APPEND FILE PATH ***TO LOG FILE NAME (LTERR 467)
CAUSE	After LOGTOOL has formed a log file name from the log file number given, it must fully qualify the file name to access the file. An unexpected error occurred while trying to fully qualify the log file name with the directory where log files are stored.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
468	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO OBTAIN LIST OF
	***LOG FILES (LTERR 468)
CAUSE	The user entered the STATUS command in LOGTOOL. LOGTOOL encountered an unexpected error while trying to obtain the list of log files available on the system.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
470	****** UNABLE TO OBTAIN THE SIZE OF A LOG FILE (LTERR 470)
CAUSE	LOGTOOL encountered an unexpected error while trying to determine how many records were in a log file.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
471	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO ABORT A MEMORY ***REPORT (LTERR 471)
CAUSE	The user entered a user interrupt while a memory report was being generated. In response to the user interrupt, LOGTOOL tried to abort the memory report and encountered an error.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
472	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO DETERMINE IF ***A USER INTERRUPT WAS ENTERED (LTERR 472)
CAUSE	An unexpected error status was returned from a diagnostic procedure which determines if a user interrupt was entered.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
473	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO DECODE A SECOND ***HARDWARE STATUS (LTERR 473)
CAUSE	LOGTOOL encountered an unexpected error while trying to request that a diagnostic program decode a second hardware status.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.

474	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO OBTAIN HARDWARE ***STATUS TEXT (LTERR 474)
CAUSE	LOGTOOL issued a request to the diagnostic system that a diagnostic program be launched to decode hardware status. LOGTOOL encountered an unexpected error while trying to obtain the text from the diagnostic program.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
475	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO SEND DATA TO ***THE SYSTEM PRINTER (LTERR 475)
CAUSE	LOGTOOL encountered an unexpected error while trying to send one line of a report to the system line printer.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
476	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO END THE PRINT ***JOB (LTERR 476)
CAUSE	LOGTOOL encountered an unexpected error while trying to end the print job, which contained either a log report or a memory report.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
477	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO AN OBTAIN THE NEXT ENTRY FROM THE DIAGNOSTIC ERROR STACK (LTERR 477)
CAUSE	While translating a diagnostic record from the system log file, LOGTOOL was not able to obtain an entry from the logged diagnostic error stack.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
478	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO TRANSLATE AN ENTRY *** FROM THE DIAGNOSTIC ERROR STACK TO TEXT (LTERR 478)
CAUSE	While translating a diagnostic record from the system log file, LOGTOOL was not able to obtain text for the entry obtained from the logged diagnostic error stack.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
479	****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO FULLY QUALIFY A ***DIAGNOSTIC FILE NAME (LTERR 479)
CAUSE	LOGTOOL is required to fully qualify the names of all files it needs to access in the diagnostic directory. In this situation, it was not able to successfully perform that task.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.

502	****** INVALID LOG RECORD TYPE ! RECORD SKIPPED (LTWARN 502)
CAUSE	LOGTOOL encountered a log record with an invalid record type. This log record will be skipped and will not appear in the report.
ACTION	Please submit a service request indicating the following: a) The exact text of the above error message including the parameter. b) Any other error messages displayed with this error message. c) The sequence of LOGTOOL commands which were being performed when this error message was encountered. d) The version (A.nn.nn) of the LOGTOOL being executed.
503	****** USER INTERRUPTS COULD NOT BE ENABLED. (LTWARN 503)
CAUSE	LOGTOOL will not be able to enable user interrupts (CONTROL-Y for MPE/iX) during initialization. LOGTOOL will execute, but user interrupts will be ignored.
ACTION	Enable error tracing by rerunning the program with the TRACE=ERROR parameter at the DUI command line, and file a service request with the trace information.
506	****** LAYOUT FILE EMPTY OR HAS FEWER RECORDS THAN HEADER SAYS. ***(LTWARN 506)
CAUSE	LOGTOOL has encountered an unexpected end of file while reading its data base file LAYOUTF.
ACTION	Contact support personnel to get new LAYOUTF and LAYMSG files.
507	****** NO LAYOUT ENTRY FOR LOG TYPE ! WITH VALUE ! (LTWARN 507)
CAUSE	During the generation of a log report, LOGTOOL was not able to locate a "TAG" definition for the log record type indicated.
ACTION	Since LOGTOOL cannot find the definition, the data will be displayed as a HEX dump, and the report will continue.
508	****** NO VALUE LABEL FOR LOG TYPE ! [VALUE= !] (LTWARN 508)
CAUSE	During the generation of a log report, LOGTOOL was not able to locate a "TAG" definition for the log record type indicated.
ACTION	Since LOGTOOL cannot find the definition, the data will be displayed as a HEX dump, and the report will continue.
510	****** STRING IN A LOG TYPE ! WITH LENGTH ! IS LARGER THAN MAX SIZE ***IN LAYOUT (SKIPPING DECODE OF THIS FIELD). (LTWARN 510)
CAUSE	During the generation of a log report, LOGTOOL encountered a string to be displayed which was larger that the buffer allocated within LOGTOOL.
ACTION	Please submit a service request indicating the following: a) The exact text of the above error message including the parameters. b) Any other error messages displayed with this error message. c) The version (A.nn.nn) of the LOGTOOL being executed. A copy of the log file containing the log record producing this error should also be submitted with the service request.

512	****** CONSOLE TEXT LENGTH OF ! IS INVALID. TEXT NOT DISPLAYED (LTWARN 512)
CAUSE	LOGTOOL was not able do display the console logging record because the text was larger that the buffer allocated within LOGTOOL.
ACTION	Please submit a service request indicating the following: a) The exact text of the above error message including the parameters. b) Any other error messages displayed with this error message. c) The version (A.nn.nn) of the LOGTOOL being executed. A copy of the log file containing the log record producing this error should also be submitted with the service request.
601	****** ILLEGAL INPUT - UNEXPECTED CHARACTER(S) OR NON UNIQUE TOKEN ***( LTERR 601 )
CAUSE	LOGTOOL has encountered a problem while parsing the input text given by the user. The problem can be any of the following: Unknown token or a token which did not have enough characters specified to make it unique. Extra characters on a line. User entered non-printable characters.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
602	****** VALUE INDICATING NUMBER OF SECONDS EXPECTED ( LTERR 602 )
CAUSE	The user did not specify a mandatory parameter which is the number of seconds to be used.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
603	****** THIS OPTION HAS ALREADY BEEN SPECIFIED OR CONFLICTS WITH ANOTHER ***( LTERR 603 )
CAUSE	The user has specified an option more than once. This includes the situation where one of two types of parameters are needed but not both.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
604	****** OPTION INVALID FOR THIS COMMAND ( LTERR 604 )
CAUSE	The option given by the user is not appropriate for the command.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
605	****** NO SUCH TOPIC. TYPE HELP FOR LIST OF COMMANDS AND TOPICS
	***( LTERR 605 )
CAUSE	The command given by the user does not exist within LOGTOOL.
ACTION	Entering HELP alone will cause LOGTOOL to display a list of all commands within LOGTOOL.

606	****** KEYWORD PARAMETER IS INVALID FOR THIS COMMAND ( LTERR 606 )
CAUSE	The keyword parameter given by the user is not appropriate for the command.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
607	****** OUTPUT FILE NAME DESIGNATOR EXPECTED ( LTERR 607 )
CAUSE	The user has given the OUTFILE keyword, but did not specify a file name, or gave an invalid file name.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
609	****** FORMAT OF THE DATE IS INVALID ( LTERR 609 )
CAUSE	The date given by the user was not in the expected format.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
610	****** FILE IDENTIFIER EXPECTED ( LTERR 610 )
CAUSE	User has given the keyword FILE, but did not give a file name, or gave an incorrectly formatted file name.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
612	****** LDEV IDENTIFIER EXPECTED ( LTERR 612 )
CAUSE	User has given the keyword LDEV, but did not give a logical device number.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
613	****** LOG FILE NUMBERS MUST BE BETWEEN 0 AND 9999 ( LTERR 613 )
CAUSE	User has given the keyword LOG, but gave a log file number which was not between 0 and 9999.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
614	****** LOG FILE NUMBER EXPECTED ( LTERR 614 )
CAUSE	User has given the keyword LOG, but did not give a log number.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
616	****** PDEV IDENTIFIER EXPECTED ( LTERR 616 )
CAUSE	User has given the keyword PDEV, but did not give physical device specifier.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.

617	****** INVALID RECORD ID (TYPE) ( LTERR 617 )
CAUSE	User specified a type number which was outside the valid range of 0 to 255.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
618	****** LOG RECORD TYPE IDENTIFIER EXPECTED ( LTERR 618 )
CAUSE	The user specified the keyword TYPE, but did not give a type number.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
619	****** THIS KEYWORD HAS ALREADY BEEN SPECIFIED ( LTERR 619 )
CAUSE	The keyword parameter specified by the user has already been found in the input text.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
620	****** INVALID RANGE - ENDING VALUE IS LESS THAN STARTING VALUE ***( LTERR 620 )
CAUSE	User has specified a range of values where the ending value is less than the starting value.
ACTION	Please consult the LOGTOOL help facility for further information on the command.
622	****** VALUE MUST BE BETWEEN ! AND ! ( LTERR 622 )
CAUSE	The user specified a numeric parameter which was not between the values indicated in the error message.
ACTION	Please consult the LOGTOOL help facility for further information on the command.
623	****** LDEV NUMBER ALREADY GIVEN ( LTERR 623 )
CAUSE	In the LDEV= parameter, the user has specified a logical device number more than once. LOGTOOL will display a carat indicating the duplicate data.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
624	****** PDEV ALREADY GIVEN ( LTERR 624 )
CAUSE	In the PDEV= parameter, the user has specified a physical device specifier more than once. LOGTOOL will display a carat indicating the duplicate data.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.

626	****** WORK FILE ALREADY GIVEN ( LTERR 626 )
CAUSE	In the FILE= parameter, the user has specified a work file name more than once. LOGTOOL will display a carat indicating the duplicate data.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
628	****** TYPE ID ALREADY GIVEN ( LTERR 628 )
CAUSE	In the TYPE= parameter, the user has specified a type number more than once. LOGTOOL will display a carat indicating the duplicate data.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
629	****** LOG NUMBER OR LOG RANGE ALREADY GIVEN OR OVERLAP ( LTERR 629 )
CAUSE	In the LOG= parameter, the user has specified a log number more than once. LOGTOOL will display a carat indicating the duplicate data.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
630	****** FORMAT OF THE TIME IS INVALID ( LTERR 630 )
CAUSE	The user gave the ;TIME option on the input text. When the user was prompted for the time, it was entered in an incorrect format.
ACTION	Please consult the LOGTOOL help facility for further information on the command.
632	****** CLOSE BRACKET EXPECTED (LTERR 632)
CAUSE	The user did not give a close bracket character when giving an index with a field label keyword.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
633	****** INDEX FOR FIELD LABEL KEYWORDS MUST BE GREATER THAN ZERO (LTERR 633)
CAUSE	The index given in the field label keyword was less than one, which is illegal.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
634	****** INDEX FOR FIELD LABEL KEYWORD EXPECTED (LTERR 634)
CAUSE	The user did not given a value to be used as the index for a field label keyword.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.

635	****** FIELD LABEL GIVEN IN EXCEEDS MAXIMUM LENGTH OF 20 CHARACTERS
	***(LTERR 635)
CAUSE	The user give a field label which exceeded 20 character.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
636	****** DATA ITEM ALREADY GIVEN. (LTERR 635)
CAUSE	The user gave the same data item in a field label keyword parameter twice.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
637	****** DATA ITEM FOR FIELD LABEL KEYWORD EXPECTED. (LTERR 637)
CAUSE	The user did not give a data item for the field label keyword.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
638	****** INVALID TO GIVE BOTH 'DETAIL' and 'SUMMARY' OPTIONS (LTERR 638)
CAUSE	The user entered both the detail and summary options in the TYPES command, which is illegal.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the TYPES command.
639	****** THIS KEYWORD PARAMETER HAS ALREADY BEEN GIVEN OR CONFLICTS
	***WITH ANOTHER ( LTERR 603 )
CAUSE	The user has specified an keyword parameter more than once, or specified a second keyword which is not allowed with a keyword parameter already given.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
640	****** THE FIELD LABEL RANGE HAS ALREADY BEEN GIVEN ( LTERR 640 )
CAUSE	The user has entered the same field label range twice.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
641	****** EXPECTING "ALL" RESERVED WORD ( LTERR 641 )
CAUSE	A reserved word other than "ALL" was found. This is invalid for the command entered.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.

642	****** FIELD LABEL RANGE EXPECTED ( LTERR 642 )
CAUSE	The user entered the DISABLE= or ENABLE= keyword, but the parameters are not valid field label ranges.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
643	****** INVALID FIELD LABEL GIVEN ( LTERR 643 )
CAUSE	The user entered an invalid field label. Field labels must be in the format of "text" or text, where text cannot be a empty string or a number.
ACTION	Please consult the LOGTOOL help facility for the correct syntax of the desired command.
651	****** REQUIRED "LOG=<LOG RANGE LIST>" PARAMETER WAS NOT FOUND ***( LTERR 651 )
CAUSE	The user did not give a mandatory parameter of LOG= in the input text.
ACTION	Please consult the LOGTOOL help facility for further information on the command.
652	****** REQUIRED "FILES=<WORK FILE LIST>" PARAMETER WAS NOT FOUND ***( LTERR 652 )
CAUSE	The user did not give a mandatory parameter of FILES= in the input text.
ACTION	Please consult the LOGTOOL help facility for further information on the command.
653	****** REQUIRED "OUTFILE=<WORK FILE NAME>" PARAMETER WAS NOT FOUND ***( LTERR 653 )
CAUSE	The user did not give a mandatory parameter of OUTFILE= in the input text.
ACTION	Please consult the LOGTOOL help facility for further information on the command.
655	****** THE LINE PRINTER IS AN INVALID OUTPUT FILE FOR THIS COMMAND ( LTERR 655 )
CAUSE	The user has specified the line printer with the OUTFILE= parameter. But the product of the command is not a printable file.
ACTION	Please consult the LOGTOOL help facility for further information
656	****** COMMAND NAME EXPECTED. ( LTERR 656 )
CAUSE	The first token given on the input text was not a command.
ACTION	Please consult the LOGTOOL help facility for a list of commands available within LOGTOOL.

657	****** REQUIRED "SECONDS=<#SECONDS>" PARAMETER WAS NOT FOUND
	***( LTERR 657 )
CAUSE	The command given by the user requires a SECONDS= parameter. This parameter indicates the number of seconds that the operation should be performed, or the number of seconds between operations.
ACTION	Please consult the LOGTOOL help facility for further information.
658	****** REQUIRED "TYPE=<TYPE LIST>" PARAMETER WAS NOT FOUND ( LTERR 658 )
CAUSE	The user did not give a mandatory parameter of TYPE= in the input text.
ACTION	Please consult the LOGTOOL help facility for further information on the command.
659	****** REQUIRED "ENABLE=<FIELD LABEL LIST>" OR "DISABLE=<FIELD LABEL LIST>" PARAMETER WAS NOT FOUND ( LTERR 659 )
CAUSE	The user did not give a mandatory parameter of ENABLE= or DISABLE= in the input text.
ACTION	Please consult the LOGTOOL help facility for further information on the command.
702	****** INSUFFICIENT CAPABILITIES TO PERFORM THIS COMMAND ( LTERR 702 )
CAUSE	The user does not have a high enough diagnostic security level to execute the requested command.
ACTION	Please consult the diagnostic user interface manual for detail concerning diagnostic security levels.
713	****** FILE ! HAS NO MORE ROOM FOR DATA ( LTERR 713 )
CAUSE	The file specified in the OUTFILE= parameter has been filled to capacity.
ACTION	Select a smaller set of data to be placed in the outfile.
720	****** THE LINE PRINTER MAY NOT BE ACCESSED IN APPEND MODE ( LTERR 720 )
CAUSE	The user has selected the system printer as the outfile, and also gave the APPEND option. This is not allowed.
ACTION	Please consult the LOGTOOL help facility for further information on the command.
731	****** UNABLE TO FIND FIELD LABEL "!" ALTFIELD FOR "!"/"!" WAS NOT PERFORMED ( LTERR 731 )
CAUSE	LOGTOOL was not able to locate the field label give in the format for the record type given in the TYPE= parameter. Therefore, the ALTFIELD command could not be performed.
ACTION	Please consult the TYPES SUMMARY command to verify that the field label is appropriate for the desired record type.

732	****** UNABLE TO FIND FIELD LABEL "!". ALTFIELD WAS NOT PERFORMED (LTERR 732)
CAUSE	LOGTOOL was not able to locate the field label give in the format for the record type given in the TYPE= parameter. Therefore, the ALTFIELD command could not be performed.
ACTION	Please consult the TYPES SUMMARY command to verify that the field label is appropriate for the desired record type.
900	****** THIS ID HAS ALREADY BEEN DEFINED ( LTERR 900 )
CAUSE	LOGTOOL has already encountered a RECORD`ID command for the current record definition.
ACTION	Please consult the LOGTOOL manual for the correct usage of the RECORD`ID command.
903	****** ONLY 16 BIT VALUES ARE VALID ( LTERR 903 )
CAUSE	The record id number given is outside the range of a 16 bit value.
ACTION	Please consult the LOGTOOL manual for the correct usage of the RECORD`ID command.
904	****** CLOSING PARENTHESIS EXPECTED ( LTERR 904 )
CAUSE	User did not give the closing parenthesis. The carat will indicate that expected location of the parenthesis.
ACTION	Please consult the LOGTOOL manual for the correct format of the command.
905	****** CLOSING BRACKET EXPECTED ( LTERR 905 )
CAUSE	User did not give the closing bracket. The carat will indicate that expected location of the bracket.
ACTION	Please consult the LOGTOOL manual for the correct format of the command.
906	****** INDEX IS GREATER THAN NUMBER OF FIELDS ( LTERR 906 )
CAUSE	The field index given by the user is greater than the number of fields given in the FIELD`FORMAT command of the current record definition.
ACTION	Please consult the LOGTOOL manual for the correct format of the VAR`LABEL command.
907	****** INDEX FOR FIELD NUMBER EXPECTED ( LTERR 907 )
CAUSE	The expected field number was not found. LOGTOOL will display a carat indicate where it was expecting to find the field number.
ACTION	Please consult the LOGTOOL manual for the correct format of the VAR`LABEL or VARIANT command.

908	****** OPENING BRACKET EXPECTED ( LTERR 908 )
CAUSE	LOGTOOL is encountered a token other than a open bracket. LOGTOOL will display a carat to indicate where the bracket was expected.
ACTION	Please consult the LOGTOOL manual for further information on the VAR`LABEL or VARIANT command.
909	****** ENDING RANGE VALUE EXPECTED HERE ( LTERR 909 )
CAUSE	LOGTOOL encountered a value range structure, but the ending value was not in the correct format. LOGTOOL will display a carat indicating where it expecting the ending range value to be.
ACTION	Please consult the LOGTOOL manual for further information on the VALUE`LABEL command.
910	****** STARTING VALUE MUST BE LESS THAN ENDING VALUE ( LTERR 910 )
CAUSE	LOGTOOL encountered a value range specifier, but the ending value was greater than the starting value. This is incorrect.
ACTION	Please consult the LOGTOOL manual for further information on the VALUE`LABEL command.
911	****** STARTING RANGE VALUE EXPECTED HERE ( LTERR 911 )
CAUSE	LOGTOOL was expecting the next token to be a value range specifier. LOGTOOL will display a carat to indicate where it was expecting the string range value to be.
ACTION	Please consult the LOGTOOL manual for further information. on the VALUE`LABEL command.
912	****** RECORD OR TAG ID IS OUT OF RANGE ( LTERR 912 )
CAUSE	LOGTOOL encountered a record id number which was outside the range of 0 to 255.
ACTION	Please consult the LOGTOOL manual for further information on the RECORD`ID or TAG`ID command.
913	****** RECORD OR TAG ID IS EXPECTED HERE ( LTERR 913 )
CAUSE	LOGTOOL is expecting a record id number if the command is RECORD`ID, or a tag id number if the command is TAG`ID. This error message will be displayed is the if number is not present or is in an incorrect format.
ACTION	Please consult the LOGTOOL manual for further information on the appropriate command.
914	****** RECORD OR TAG ID STATEMENT NOT ALLOWED HERE. COMMAND IGNORED ( LTERR 914 )
CAUSE	The user has already specified a RECORD`ID or TAG`ID command for the current record definition. The RECORD`ID or TAB`ID command encountered will be ignored.
ACTION	Please consult the LOGTOOL manual for further information on the RECORD`ID or TAG`ID command.

915	****** UNRECOGNIZED TOKEN IN COMMAND FIELD ( LTERR 915 )
CAUSE	LOGTOOL was expecting a command name. LOGTOOL will display a carat indicating where it was expecting the command name.
ACTION	Please consult the LOGTOOL manual for further information on record definition files.
916	****** NUMBER OF BITS TOO LARGE FOR THIS TYPE OF FIELD ( LTERR 916 )
CAUSE	The number of bits specified in the field format is too large for the type of field.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
917	****** ARRAY DATA MUST START ON A 8 BIT BYTE BOUNDARY ( LTERR 917 )
CAUSE	LOGTOOL requires array data to start on a 8 bit byte boundary.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
918	****** ARRAY DATA MUST BE A MULTIPLE OF 8 BITS ( LTERR 918 )
CAUSE	LOGTOOL requires that array data be defined in multiples on 8 bits.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
919	****** ASCII DATA MUST START ON AN 8 BIT BOUNDARY ( LTERR 919 )
CAUSE	LOGTOOL requires that all ascii data start on a 8 bit byte boundary.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
920	****** ASCII DATA MUST BE A MULTIPLE OF 8 BITS ( LTERR 920 )
CAUSE	LOGTOOL required that all ascii data be defined in multiples of 8 bits.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
921	****** TAB FIELD TOO LARGE FOR SPECIFIED RECORD LENGTH ( LTERR 921 )
CAUSE	The tab field given along with the other field defined will exceed the bit count given in the RECORD`LENGTH command of the current record definition.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.

922	****** TAG LENGTH IN BITS EXPECTED ( LTERR 922 )
CAUSE	LOGTOOL encountered a token other than a value which is to be used as the tag length. LOGTOOL will display a carat where it expected the tag length value.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
923	****** COMMA EXPECTED HERE ( LTERR 923 )
CAUSE	LOGTOOL encountered a token other than a comma. LOGTOOL will display a carat at the location where it was expecting the comma.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
924	****** "TAG" EXPECTED HERE ( LTERR 924 )
CAUSE	LOGTOOL encountered a token other than the reserved word "TAG". LOGTOOL will display a carat where it expected the "TAG".
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
925	****** FIELD BASE MUST BE IN [2,8,10,16] ( LTERR 925 )
CAUSE	LOGTOOL encountered a value other that a valid base value. LOGTOOL will display a carat indicating where the incorrect base value was found.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
926	****** FIELD BASE EXPECTED HERE [2,8,10,16] ( LTERR 926 )
CAUSE	LOGTOOL encountered a token other that a valid base value. LOGTOOL will display a carat indicating where the base value was expected.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
927	****** COMMA FOLLOWED BY FIELD BASE EXPECTED HERE ( LTERR 927 )
CAUSE	LOGTOOL encountered a token other that a comma followed by a field base. LOGTOOL will display a carat indicating where the comma was expected.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
928	****** STRING DATA MUST START ON A 8 BIT BYTE BOUNDARY ( LTERR 928 )
CAUSE	LOGTOOL requires that string data start on a 8 bit byte boundary. Fields declared before this field must end on a 8 bit byte boundary.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.

929	****** STRING DATA MUST A MULTIPLE OF 8 BITS ( LTERR 929 )
CAUSE	LOGTOOL requires that string data be declared in multiples of 8 bits.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
930	****** FIELD FORMAT #BITS SUM EXCEEDS RECORD LENGTH ( LTERR 930 )
CAUSE	The number of bits specified in the FIELD`FORMAT command exceeds the number of bits specified in the RECORD`LENGTH command for the current record definition. LOGTOOL will display the field format of the entry which exceeds the bit length.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
931	****** FIELD TYPE EXPECTED ( LTERR 931 )
CAUSE	LOGTOOL was expecting a field type identifier. LOGTOOL will display a carat indicating where it was expecting the field type to be.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
932	****** FIELD BIT COUNT EXPECTED HERE ( LTERR 932 )
CAUSE	LOGTOOL encountered a token other than a field bit count value. LOGTOOL will display a carat at the location where it is expecting the field bit count.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
933	****** MORE FIELDS IN FIELD FORMAT THEN IN N FIELDS ( LTERR 933 )
CAUSE	The number of fields specified in the FIELD`FORMAT is larger that the value specified in the N`FIELDS command for the current record definition.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
934	****** INVALID REPEAT FACTOR SPECIFIED ( LTERR 934 )
CAUSE	The value given for the repeat factor is greater the than the value given in the N`FIELDS command.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
935	****** EXPECTED A REPEAT FACTOR OR "(" ( LTERR 935 )
CAUSE	LOGTOOL is expecting the next token to be a repeat factor, which is represented as a number, or a "(".
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.

936	****** FIELD FORMAT IS INVALID HERE OR HAS ALREADY BEEN SPECIFIED
	***( LTERR 936 )
CAUSE	A FIELD`FORMAT command has already been given for the current record definition, or commands which must proceed the FIELD`FORMAT command were not given.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
937	****** NUMBER OF FIELD FORMATS DOES NOT MATCH N`FIELDS VALUE ( LTERR 937 )
CAUSE	The number of fields given in the FIELD`FORMAT command does not match the value given in the N`FIELD.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
938	****** TOTAL BITS IN FIELD FORMAT DOES NOT MATCH RECORD LENGTH VALUE ( LTERR 938 )
CAUSE	The total number of bits defined in the FIELD`FORMAT command does not match the RECORD`LENGTH value for the current record definition.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
939	****** N FIELDS VALUE EXPECTED HERE ( LTERR 939 )
CAUSE	LOGTOOL encountered the N`FIELD command but did not find the number of fields parameter. Either the user did not give a value, or the value was given in an incorrect format.
ACTION	Please consult the LOGTOOL manual for further information on the N`FIELDS command.
940	****** N`FIELDS IS INVALID HERE OR HAS ALREADY BEEN SPECIFIED ( LTERR 939 )
CAUSE	A N`FIELD command has already been given for the current record definition, or the commands which must proceed the N`FIELD command were not given.
ACTION	Please consult the LOGTOOL manual for further information on the N`FIELD command.
945	****** QUOTED RECORD LABEL EXPECTED HERE ( LTERR 945 )
CAUSE	LOGTOOL did not encounter a quoted string, which is to be used as the record label, or the string was not given in the proper format.
ACTION	Please consult the LOGTOOL manual for further information on the RECORD`LABEL command.
946	****** RECORD LABEL IS INVALID HERE OR HAS ALREADY BEEN SPECIFIED
	***( LTERR 946 )
CAUSE	The RECORD`LABEL command has already been given for the current record definition, or commands which must proceed the RECORD`LABEL command were not given.
ACTION	Please consult the LOGTOOL manual for further information on the RECORD`LABEL command.

947	****** RECORD LENGTH VALUE ( # BITS ) IS OUT OF RANGE ( LTERR 947 )
CAUSE	A RECORD`LENGTH command has been encountered, but the user specified a record length value outside of the valid range.
ACTION	Please consult the LOGTOOL manual for further information on the RECORD`LENGTH command.
948	****** RECORD LENGTH VALUE ( # BITS ) EXPECTED HERE ( LTERR 948 )
CAUSE	A RECORD`LENGTH command has been encountered, but the user either did not give the number of bits parameter, or gave an invalid token for the number of bits parameter.
ACTION	Please consult the LOGTOOL manual for further information on the RECORD`LENGTH command.
949	****** RECORD LENGTH IS INVALID HERE OR HAS ALREADY BEEN SPECIFIED ( LTERR 949 )
CAUSE	The RECORD`LENGTH command has already been given for the current record definition, or the commands which must proceed the RECORD`LENGTH command were not given.
ACTION	Please consult the LOGTOOL manual for further information on the RECORD`LENGTH command.
951	****** QUOTED VALUE LABEL EXPECTED ( LTERR 951 )
CAUSE	LOGTOOL is expecting a quoted string which it will use as a value label. LOGTOOL will display a carat indicating where it expected the quoted string to be.
ACTION	Please consult the LOGTOOL manual for further information on the VALUE`LABEL command.
952	****** COMMA FOLLOWED QUOTED VALUE LABEL EXPECTED ( LTERR 952 )
CAUSE	LOGTOOL was expecting a comma followed by a quoted string which will be used as a value label. LOGTOOL will display a carat indicating where it was expecting the comma to be.
ACTION	Please consult the LOGTOOL manual for further information on the VALUE`LABEL command.
953	****** OPENING PARENTHESIS EXPECTED ( LTERR 953 )
CAUSE	LOGTOOL was expecting the next token to be an open parenthesis. LOGTOOL will display a carat indicating where it was expecting the open parenthesis to be.
ACTION	Please consult the LOGTOOL manual for further information on the VALUE`LABEL or VARIANT command.
954	****** VALUE LABELS MAY BE SPECIFIED FOR INTEGER FIELDS ONLY ( LTERR 953 )
CAUSE	VALUE`LABELS may only be used for fields which have been defined as of type INTEGER within the FIELD`FORMAT command.
ACTION	Please consult the LOGTOOL manual for further information on the VALUE`LABEL command.

955	****** VALUE`LABEL IS INVALID HERE OR HAS ALREADY BEEN SPECIFIED ( LTERR 955 )
CAUSE	The VALUE`LABEL command has already been given or commands which must proceed the VALUE`LABEL command were not given.
ACTION	Please consult the LOGTOOL manual for further information on the VALUE`LABEL command.
956	****** LABEL ALREADY SPECIFIED FOR THIS INDEX ( LTERR 956 )
CAUSE	A label has already been given for the field specified by the field index.
ACTION	Please consult the LOGTOOL manual for further information for the VAR`LABEL command.
957	****** INDEX FOR THIS LABEL IS OUT OF RANGE ( LTERR 957 )
CAUSE	The field for the VAR`LABEL cannot be located in the FIELD`FORMAT command.
ACTION	Please consult the LOGTOOL manual for further information on the VAR`LABEL command.
958	****** QUOTED VAR`LABEL STRING EXPECTED ( LTERR 958 )
CAUSE	LOGTOOL was expecting a quoted string, which will be used as a var label. LOGTOOL will display a carat indicating the location where it was expecting the quoted string.
ACTION	Please consult the LOGTOOL manual for further information on the VAR`LABEL command.
959	****** VALUE LABEL IS INVALID HERE OR HAS ALREADY BEEN SPECIFIED ( LTERR 959 )
CAUSE	The VALUE`LABEL command has already been given, or commands which must proceed the VALUE`LABEL command were not given.
ACTION	Please consult the LOGTOOL manual for further information on the VALUE`LABEL command.
963	****** VARIANT IS INVALID HERE OR HAS ALREADY BEEN SPECIFIED ( LTERR 963 )
CAUSE	The VARIANT command has already been given, or commands which must proceed the VARIANT command were not given.
ACTION	Please consult the LOGTOOL manual for further information on the VARIANT command.
964	****** LABEL ON LINE ! TO LONG - TRUNCATED TO ! CHARACTERS "!" ( LTERR 964 )
CAUSE	User has specified a record label longer that 20 characters. The label was truncated to 20 characters. The resulting string will be displayed to the user.
ACTION	Please consult the LOGTOOL manual for further information on the RECORD`LABEL command.

966	****** INTERNAL ERROR - DUMP VAL_LABELS LABEL COUNTS DO NOT MATCH. EXPECTED = ! : ACTUAL = ! ( LTERR 966 )
CAUSE	LOGTOOL encountered an error while trying to save the layout file for the :APPEND option.
ACTION	Please submit a service request indicating the following: a) The exact text of the above error message including the parameters. b) Any other error messages displayed with this error message. c) The version (A.nn.nn) of the LOGTOOL being executed. A copy of the record definition file used in the LAYOUT LOGTOOL command should also be submitted with the service request.
967	****** INTERNAL ERROR - DUMP=ENTRY VAR COUNTS DO NOT MATCH. EXPECTED = ! : ACTUAL = ! ( LTERR 967 )
CAUSE	LOGTOOL encountered an error while trying to save the layout file for the :APPEND option.
ACTION	Please submit a service request indicating the following: a) The exact text of the above error message including the parameters. b) Any other error messages displayed with this error message. c) The version (A.nn.nn) of the LOGTOOL being executed. A copy of the record definition file used in the LAYOUT LOGTOOL command should also be submitted with the service request.
968	****** INTERNAL ERROR DELETING FILE ! ( LTERR 968 )
CAUSE	LOGTOOL encountered an error while trying to delete the file indicated in the message.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.
969	****** INTERNAL ERROR CLOSING FILE ! ( LTERR 969 )
CAUSE	LOGTOOL encountered an error while trying to close the file indicated in the message.
ACTION	Error messages containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.
978	***WARNING: TRUNCATING THE FOLLOWING STRING TO ! CHARACTERS ( LTERR 978 )
CAUSE	LOGTOOL was forced to truncate the indicated string by the number of characters indicated inorder to perform the ;APPEND option of the LAYOUT command.
ACTION	Please consult the LOGTOOL manual for further information on the format of a record definition files

979	****** INTERNAL ERROR - MESSAGE SET FILE ! HAS OVERFLOWED. ( LTERR 979 )
CAUSE	LOGTOOL has encountered an file overflow while trying to create the new LAYMSG file. The old copy of the file will be returned.
ACTION	Please submit a service request indicating the following: a) The exact text of the above error message including the parameters. b) Any other error messages displayed with this error message. c) The version (A.nn.nn) of the LOGTOOL being executed. A copy of the record definition file used in the LAYOUT LOGTOOL command should also be submitted with the service request.
980	****** INTERNAL ERROR - LAYOUT FILE OVERFLOW WRITING TO RECORD ! CURRENT MAXIMUM RECORD = ! ( LTERR 980)
CAUSE	LOGTOOL has encountered a file overflow while trying to create a new LAYOUTF file. The old copy of the file will be returned.
ACTION	Please submit a service request indicating the following: a) The exact text of the above error message including the parameters. b) Any other error messages displayed with this error message. c) The version (A.nn.nn) of the LOGTOOL being executed. A copy of the record definition file used in the LAYOUT LOGTOOL command should also be submitted with the service request.
981	****** FILE ! DOES NOT EXIST ( LTERR 981 )
CAUSE	The file given by the user for the LAYOUT command cannot be found by LOGTOOL.
ACTION	Verify that the file was placed in the diagnostic directory (DIAG.SYS on MPE/iX)
984	****** UNABLE TO READ FILE ! ( LTERR 984 )
CAUSE	LOGTOOL was not able to read the file indicated by the user in the LAYOUT command.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.
986	****** UNABLE TO OPEN FILE ! ( LTERR 986 )
CAUSE	LOGTOOL was not able to open the file specified in the LAYOUT command.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.
987	****** UNABLE TO WRITE TO FILE ! ( LTERR 987 )
CAUSE	LOGTOOL was not able to write to the temporary file indicated to process the ;APPEND option of the LAYOUT command.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of those error messages for further information.

992	****** LABEL ALREADY GIVEN FOR RANGE ( LTERR 992 )
CAUSE	A value label has already been given for the field specified by the field index for the given value range.
ACTION	Please consult the LOGTOOL manual for further information on the VALUE`LABEL command.
993	****** RECORD ID FOR TAG DOES NOT EXIST ( LTERR 993 )
CAUSE	The RECORD`ID for which the current TAG definition is to be used does not exist.
ACTION	Verify that the RECORD`ID number is correct. Please consult the LOGTOOL manual for further information on the TAG`ID command.
994	****** ONE OR MORE FIELD SPECIFIED IN VARIANT IS NOT A TAG FIELD ( LTERR 994 )
CAUSE	The field indicated by the VARIANT command is not defined as a TAG field in the FIELD`FORMAT command.
ACTION	Please consult the LOGTOOL manual for further information on the VARIANT command.
995	****** TAG RECORD SPECIFIED IN VARIANT CANNOT BE FOUND ( LTERR 995 )
CAUSE	The field indicated by the VARIANT command cannot be located within the FIELD`FORMAT command for the record id indicated by the TAG`ID command.
ACTION	Please consult the LOGTOOL manual for further information on the VARIANT command.
996	****** TAG RECORD SPECIFIED IN VARIANT HAS NOT BE DEFINED ( LTERR 996 )
CAUSE	The field indicated by the VARIANT command cannot be located within the FIELD`FORMAT command for the record id indicated by the TAG`ID command.
ACTION	Please consult the LOGTOOL manual for further information
997	****** FIELD SPECIFIED IN VARIANT IS NOT A TAG ( LTERR 997 )
CAUSE	The field specified to be used with the current TAG`ID is not a tag field.
ACTION	Please verify that the field number and the record id number are correct. Please consult the LOGTOOL manual for correct usage of the VARIANT command.
998	****** FIELD SPECIFIED IN VARIANT CANNOT BE FOUND ( LTERR 998 )
CAUSE	LOGTOOL was not able to locate the field in the record definition for which the current TAG`ID is to be used with.
ACTION	Please verify that the field number and record id number are correct. Please consult the LOGTOOL manual for the correct usage of the VARIANT command.

1000	****** LLIOSTAT TYPE REQUIRES 32 BITS ( LTERR 1000 )
CAUSE	The FIELD`FORMAT command contained an entry with a type of LLIOSTAT and a parameter which was not a value of 32. A Low level I/O status as defined by the MPE/iX operating system requires 32 bits.
ACTION	Please consult the LOGTOOL manual for correct usage of the FIELD`FORMAT command.
1002	****** DATE TYPE REQUIRES 16 BITS ( LTERR 1002 )
CAUSE	The FIELD`FORMAT command contained an entry with a type of DATE and a length which was not a value of 16. A datestamp as defined by the MPE/iX operating system requires 16 bits.
ACTION	Please consult the LOGTOOL manual for correct usage of the FIELD`FORMAT command.
1003	****** MPEXLSTAT TYPE REQUIRES 32 BITS ( LTERR 1003 )
CAUSE	The FIELD`FORMAT command contained an entry with a type of MPEXLSTAT and a length which was not a value of 32. An MPE/iX status as defined by the MPE/iX operating system requires 32 bits.
ACTION	Please consult the LOGTOOL manual for correct usage of the FIELD`FORMAT command.
1004	****** TIME TYPE REQUIRES 32 BITS ( LTERR 1004 )
CAUSE	The FIELD`FORMAT command contained an entry with a type of TIME and a length which was not a value of 32. A timestamp as defined by the MPE/iX operating system requires 32 bits.
ACTION	Please consult the LOGTOOL manual for correct usage of the FIELD`FORMAT command.
1005	****** LAST RECORD`ID OR TAG`ID IS NOT COMPLETE ( LTERR 1005 )
CAUSE	LOGTOOL has encountered a RECORD`ID or TAG`ID command before all required information for the previous record definition has been given. The partial record definition will be ignored.
ACTION	Please consult the LOGTOOL manual for the correct format of a record definition.
1006	****** VALUE GIVEN IN N`FIELDS CANNOT BE NEGATIVE ( LTERR 1006 )
CAUSE	The number of fields for the current record definition number be equal to or greater than zero. This value must match the number of entries given in the FIELD`FORMAT command.
ACTION	Please consult the LOGTOOL manual for the correct usage of the N`FIELD command.
1007	****** UNABLE TO COPY FILE ! TO SYSTEM DISK ( LTERR 1007 )
CAUSE	LOGTOOL was not able to copy the layout files to the main system disk.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.

1008	****** UNABLE TO FULLY QUALIFY LAYOUT FILE NAME ( LTERR 1008 )
CAUSE	LOGTOOL was not able to fully qualify the file name for the layout files. LOGTOOL cannot create the layout files with fully qualifying the file name.
ACTION	An error message containing further information will be displayed with this message. Please refer to the ACTION clause of that error message for further information.
1009	****** LENGTH OF FIELD CONTAINING HARDWARE STATUS COUNT EXPECTED ( LTERR 1009 )
CAUSE	LOGTOOL was expecting value which is the length of the field containing the hardware status count. LOGTOOL will display a carat indicating the location where it was expecting the value.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
1010	****** INDEX TO THE FIELD CONTAINING HARDWARE STATUS COUNT EXPECTED ( LTERR 1010 )
CAUSE	LOGTOOL was expecting value which is the index where the field containing the hardware status count can be found. LOGTOOL will display a carat indicating the location where it was expecting the value.
ACTION	Please consult the LOGTOOL manual for further information on the FIELD`FORMAT command.
30011	***WARNING: LOGTOOL DOES NOT USE "ERRCOUNT" PARAMETER. (LTWARN 30011)
CAUSE	The user gave the ERRCOUNT parameter when initiating LOGTOOL through the diagnostic user interface. LOGTOOL does not use this parameter.
ACTION	LOGTOOL will ignore the ERRCOUNT parameter and will continue execution.
30012	***WARNING: LOGTOOL DOES NOT USE "LOOPCOUNT" PARAMETER. (LTWARN 30011)
CAUSE	The user gave the LOOPCOUNT parameter when initiating LOGTOOL through the diagnostic user interface. LOGTOOL does not use this parameter.
ACTION	LOGTOOL will ignore the LOOPCOUNT parameter and will continue execution.
30013	***WARNING: LOGTOOL DOES NOT USE "ERRONLY" PARAMETER. (LTWARN 30012)
CAUSE	The user gave the ERRONLY parameter when initiating LOGTOOL through the diagnostic user interface. LOGTOOL does not use this parameter.
ACTION	LOGTOOL will ignore the ERRONLY parameter and will continue execution.
30014	***WARNING: LOGTOOL DOES NOT USE "ERRPAUSE" PARAMETER. (LTWARN 30013)
CAUSE	The user gave the ERRPAUSE parameter when initiating LOGTOOL through the diagnostic user interface. LOGTOOL does not use this parameter.
ACTION	LOGTOOL will ignore the ERRPAUSE parameter and will continue execution.