Standalone Logtool for MPE/iX: Error and Warning Messages
The following are general error messages which may be encountered during the execution of LOGTOOL. Please note that system dependent error messages may be displayed from the On-Line diagnostic system before any error message generated by this diagnostic. All error messages without the ( LTERR # ) trailer are generated by the online diagnostics 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. |
| 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:
|
| 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. |
| Summary | Records | All the files |
| Commmands | Err Msgs | Diagnostics HOME |