Standalone Logtool for MPE/iX: Summary In this section of the Standalone Logtool document: Introduction Defects and Enhancements Minimum Configuration Operating Instructions Starting LOGTOOL Test Execution Other sections in this document: Commands Records Error and Warning Messages This document explains how to use the standalone version of Logtool, available on MPE/iX 6.5 and later.
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.
******************************************************************* Welcome, Today is THU, OCT 14, 1999 at 4:30 PM LOGTOOL initializing, please wait ... LOGTOOL> The LOGTOOL> prompt is displayed. The user is now free to enter commands. To exit LOGTOOL, the user types EXIT . The message LOGTOOL Exiting ... will be displayed to confirm that LOGTOOL completed properly. Control will then be returned to the operating system.
Name Category ALTFIELD (SFL) DISPLAYLOG (SFL) EXIT (MC) HELP (MC) LAYOUT (SLF) LIST (SLF) MEMCLR (MLF) MEMRPT (MLF) MEMTIMER (MLF) PURGESYSLOG (SLF) PURGEWORK (SLF) REDO (MC) SELECT (SLF) STATUS (SLF) SUMMARIZE (SLF) SUSPEND (MC) SWITCHLOG (SLF) TYPES (SLF) Description Specifies which fields of a log record should be displayed in a report generated by LIST . Displays I/O entries as information is logged. Exits LOGTOOL and returns user to the MPE/iX user interface. Gives help on running LOGTOOL.
Typing a user interrupt while LOGTOOL is performing a lengthy task (i.e., producing a report or selecting out a subset of error log records) will cause that task to be interrupted. The user may be asked in some cases to choose either to abort or to continue the current task. If the user decides to terminate the task and there was output being directed to a disk file (a report, for example), that file will be closed and preserved as is.
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. ::= | , ::= /.. | /.. | /. | / | .. | .. | . | ::= | / ::= An integer giving the bus converter address.
::= 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 This section explains the standard set of LOGTOOL commands available to the user.
I/O RESULT: RETRY COUNT: TRANS. NUM. : HARDWARE STATUS: I/O Failed 5 1279 RUN AUTODIAG: MGR PORT NUM.: # HDWR BYTES: NO -82 20 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 STATUS INFORMATION: 0 1 2 3 4 5 == == == == == 1: 40 01 00 0A 20 13: 34 34 34 18 00 MSG DESCRIPTOR: 4 TRANSACTION NUM.
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.
be displayed in a report generated by the LIST command. Quotes are only required for field labels which contain embedded blanks. ::= | , | ALL | / ::= text | "text" Ex: DISABLE="NL CHECKSUM"/"SL CHECKSUM" ENABLE = - Specifies which fields are to be displayed in a report generated by the LIST command.
Optional Parameters: FILES - 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. ::= Example: APPEND - | , FILE=laympexl, layio If given, specifies that the record definitions given are to be saved permanently in LOGTOOL's record decoding file.
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= | FILES= [;OUTFILE=] [;TYPE=] [;=] [;DATE] [;TIME] [;WIDE] [;HEXDUMP] Parameters: LOG= - The LOG keyword specifies which log files to base the report on.
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.
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.
TUE, APR 10, 1990 9:11 AM NM FILE CLOSE NUM. LOGICAL READS: 0 NUM. LOGICAL WRITES:0 FILE NAME: O124 ACCOUNT NAME: HPSPOOL USER NAME: MGR USER ACCOUNT: FVSTEST 1 2 3 4 5 6 == == == == == == 1: 05 5A 00 03 06 0E 13: 32 02 08 26 01 F8 LOG0039.PUB.SYS 7 == 6A A2 8 == 13 3A #J4 (PIN 42) NUM. BYTES READ: 0 NUM. BYTES WRITTEN: 268 GROUP NAME: OUT CREATOR NAME: MGR FVSTEST USER GROUP: SU UFID: 9 10 11 12 == == == == 00 0D 9E B4 . Z . . . . j . . . . . 2 . . & . . . : CLOSE DISP.
The following is a list of the types of error information displayed: Slot Bit number/Bank number Error address Chip ID This will identify the slot where the memory board, which produced the error, can be found. Error type Identifies the type of error. Possible settings are: This is the data bit number and bank number where the error occurred. This is the physical address where the error occurred. This is the ID of the chip where the error occurred.
::= 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.
MEMTIMER SECONDS=<#seconds> Optional Parameters: SECONDS= <#seconds> - The time between memory log scans Example: SEC=3600 Example LOGTOOL>memtimer sec=9600 LOGTOOL> PURGESYSLOG The PURGESYSLOG command will delete from disc the specified system log file(s). Included is a verify mode ( default ) which will ask the user to confirm the deletion of each file specified before the program actually purges it from the system. The user must possess at least diagnostic security 1 to execute this instruction.
Optional Parameters: FILES= Example: - The FILES keyword is used to specify the names of the work files to purge. 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. Limitations: Example: LOGTOOL>purgework file=subset1,subset2,junkfile,logtool Purge SUBSET1.DIAG.SYS (Y/N) [N] ? Y ...Deleted SUBSET1.DIAG.
c CHANGE: Change all occurrences of one string to another in the current line when the search string and replace string are properly delimited. A proper delimiter is a non-alpha- betic character: ', ", /, etc. The substitution is specified as: c search-string [replace-string [
[;DATE] [;TIME] [;APPEND] Parameters: LOG= - 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. ::= | , ::= | / ::= integer value Ex: LOG=100/105, 150 OUTFILE= - The OUTFILE keyword lets the user specify the work file name.
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 []? 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. Command Example: LOGTOOL>select log=1,2 type=100,105 outf=subset1 Processing LOG0001.PUB.SYS ... Processing LOG0002.PUB.SYS ...
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 The TYPE keyword can be used to indicate that only log records of the types specified are to be displayed. keyword The LOGTOOL command TYPES can be used to obtain a list of the log record types available.
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). ::= ::= Ex: | , Alpha-numeric text (starting with an alpha) FILES=file1,file8,junk,work OUTFILE= - The OUTFILE keyword lets the user direct the report to a file or the line printer.
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 []? 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.
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.
LOGTOOL> TYPES The TYPES command lists all the record identifiers currently defined within LOGTOOL. This command is useful for users who wish to display specific types of log records, or need specific information concerning how a log record will be formatted. When this command is executed without any options or keyword, the record ID number and the record label used when the log entry is displayed, will be listed. If the DETAIL option is given, the full definition of the record ID will be given.
141 143 144 146 148 150 151 152 160 205 227 228 229 234 236 238 240 241 242 244 245 305 344 PROCESS CREATION CHGROUP FILE OPEN MAINTENANCE REQUEST UPS MONITOR LOG DIAGNOSTIC INFO HPMC LPMC CM FILE CLOSE NM FILE CLOSE CHDIR PROCESS ADOPTION FILE OWNER CHANGE PASSWORD CHANGES RESTORE ACD CHANGE USER LOGGING PROCESS CREATION SECURITY CONFIG CHG FILE OPEN CI COMMAND LOG NM FILE CLOSE FILE OPEN LOGTOOL> Standalone Logtool for MPE/iX: Records Record Definition Files Record Definition Commands COMMENT RECORD`ID
contains the record definition command that identifies the remainder of the data and the "specification field" that contains all of the parameters and arguments required by a particular control command. The specification field may span multiple lines. The terminator of a specification field is another command. Commands must be the first character of a line with no preceding white space (i.e., they must start at column 1). Comments can be embedded within the specifications field by using braces { }.
RECORD`ID RECORD`ID 1 123 TAG`ID This command defines the variant tag portion of a previously defined RECORD`ID or TAG`ID. For example, refer to the following PASCAL record definition: TYPE my_record = RECORD field1 : integer; CASE select : boolean OF true : (true_case : some_other_type); false : (false_case : yet_another_type); END; It has a tag field called "select" and two possible variant parts.
RECORD`LENGTH 220 N`FIELDS This command specifies the number of fields (pieces of data) in the current RECORD`ID. Variant tags are considered as 1 field. The subfields are defined with subsequent TAG`ID commands. This value must be equal to the number of entries on the FIELD`FORMAT command. Syntax: N`FIELDS <# of fields> Example: N`FIELDS 5 RECORD`LABEL This command assigns a label to the log record. The label is restricted to 20 characters and must be enclosed by either double or single quotes.
MPEXLSTAT Specifies this field to be interpreted as an MPE/iX Operating System status. LOGTOOL will display a text message from the system message catalog corresponding to the value obtained. If a message cannot be found in the catalog, the value will be displayed in the report. This type requires that the <#bits> parameter given is 32. LLIOSTAT Specifies this field is to be interpreted as an MPE/iX Low Level I/O status.
- 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 This command provides the ability to give each field a label.
printed as numeric data as indicated in the FIELD`FORMAT command. Examples: VALUE`LABELS [ 2 ] (1, "one"; 2, "two"; 3, "three") [ 3 ] (-1, "Unlimited"; 1/14 "Half power") [ 8 ] (-32768/-1, "Negative"; 0/32767, "Positive") VARIANT This command must be provided for a TAG`ID definition. This command indicates which field of the RECORD`ID or TAG`ID the current TAG`ID definition is to be used. The RECORD`ID definition must contain a field declared as a tag.
NAME x4.0 @ C.0 <- Note compiler added 32 bits for string header and 32 bits for string trailer. x10.0 @ 4.0 x14.0 @ 4.0 x14.0 @ 1.0 STUFF F1 F2 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 FIELD1 SELECT MAX RECORD SIZE = x20 BYTES x0.0 @ 4.0 x4.0 @ 1.0 <- Note: compiler padded to next word. x8.0 @ 4.0 x8.
FIELD`FORMAT VAR`LABELS (32,INT,10) [ 1 ] "F1:" COMMENT " This defines the case variant "1" of (YET_ANOTHER_TYPE) from the above record TAG`ID RECORD`LENGTH RECORD`LABEL VARIANT 1 32 [ 2 ] (0) [ 4 ] (1) " {This tag is to be used with RECORD`ID 1} {Must match length given in FIELD`FORMAT} {Use this TAG`ID when field 3 of} {previous TAG`ID has a value of zero} N`FIELDS 2 FIELD`FORMAT VAR`LABELS (8,INT,10) (24,junk) [ 1 ] "F2:" As in the above example, TAG`IDs may be nested.
end; false : (buff : packed array [1..io_var_len-4] of char); {io_var_rec_type} The previous record structure is used when logging information to the system log file. This record must be translated into a LOGTOOL record definition file which will be processed by LOGTOOL and incorporated into its data base. The following is a listing of a file named LAYLLIO, which contains the record definition for the above PASCAL record.
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 . . . . . . .
1 == FF 1: 2 == 3 == 4 == 5 == 6 == 7 == 8 == 9 == 10 == 11 == 12 == . 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 . . . . .
************************************************************ 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.
subsystem. Each of the error messages is followed by CAUSE/ACTION explanations. These explanations will not be displayed to the user. 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.
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# !.
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.
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.
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.
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.
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.
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.
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.
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=" 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.
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 "!".
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.
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".
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 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.
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.
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.
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.
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.
