HP 3000 Manuals HP 3000 Manuals
Appendix D Error Messages
Table D-1 lists all the error messages that might appear when you are
using INFORM/V. Table D-2 contains a list of fatal processing error
messages; i.e., those messages that are identified by the message FATAL
PROCESSING ERROR number at your terminal. The information in Table D-2
will be of particular value to your database administrator if you should
get a fatal processing error message.
Table D-1. User Error Messages
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| ACCOUNT CAPABILITIES DO NOT ALLOW A JOB TO | The user's account does not have batch (BA) |
| BE STREAMED | capability. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ACCOUNT PASSWORD EXPECTED | An account password must be entered. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ARGUMENT REGISTER OVERFLOW | Report error to DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ARITHMETIC CONVERSION FOR ITEM: item-name | Report error to DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ARITHMETIC CONVERSION FOR TABLE LITERAL | A program constant cannot be converted to |
| | the binary equivalent as the current |
| | statement requires. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| ARITHMETIC TRAP | Processor has detected an arithmetic trap |
| | condition in its internal processing. |
| | Report the error to the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ATTEMPT TO ASSIGN NEGATIVE VALUE TO ITEM: | The processor has detected an attempt to |
| item-name | assign a negative value to a positive-type |
| | field. |
| | |
---------------------------------------------------------------------------------------------
| | |
| BAD PASSWORD - GRANTS ACCESS TO NOTHING | An invalid password was entered. |
| | |
---------------------------------------------------------------------------------------------
| | |
| BASE DOES NOT EXIST IN DICTIONARY | The database selected does not exist in the |
| | data dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| BATCH FILE INTERNAL SET UP ERROR | MPE/V cannot set up the batch job. |
| | |
---------------------------------------------------------------------------------------------
| | |
| BATCH FILE INTERNAL WRITE ERROR | MPE/V cannot set up the batch job. |
| | |
---------------------------------------------------------------------------------------------
| | |
| BROKEN WORKSPACE CHAIN | Processor has detected a break in a work |
| | space link list. Report the error to the |
| | DBA. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| CANNOT ACCESS REPORT FILE, ERROR=number | The report file cannot be found or |
| | accessed-an MPE File System error number is |
| | indicated. |
| | |
---------------------------------------------------------------------------------------------
| | |
| CANNOT CREATE A REPORT FILE | The report file cannot be created, e.g., |
| | not enough disc space. |
| | |
---------------------------------------------------------------------------------------------
| | |
| CANNOT OPEN DATA BASE: basename | Data base needed by INFORM/V cannot be |
| | accessed. Report error to DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| CANNOT OPEN PRINT FILE | The processor is unable to open the print |
| | file. |
| | |
---------------------------------------------------------------------------------------------
| | |
| CHILD ITEMS ARE NOT VALID IN COMPARISON | The data name chosen cannot be used in a |
| EXPRESSION | data-name to data-name comparison. |
| | |
---------------------------------------------------------------------------------------------
| | |
| COMMAND INTRINSIC ERROR PLEASE REPORT | INFORM/V cannot create or stream the batch |
| | job. |
| | |
---------------------------------------------------------------------------------------------
| | |
| COMPUTATION WORKSPACE OVERFLOW | Internal error. Report the error to DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| COMPUTE ITEMS ARE NOT VALID IN COMPARISON | Temporary data names cannot be used in |
| EXPRESSIONS | data-name to data-name comparisons. |
| | |
---------------------------------------------------------------------------------------------
| | |
| COMPUTED NAMES CANNOT BE USED FOR | A computed data name added to the group |
| SELECTION CRITERIA | with "+" cannot be used with selection |
| | criteria. |
| | |
---------------------------------------------------------------------------------------------
| | |
| CURRENT REPORT HAS NOT BEEN SPECIFIED | To produce a report, a report must be |
| | defined or specified (option 1, 2, or 3 of |
| | the Main Menu). |
| | |
---------------------------------------------------------------------------------------------
| | |
| DATA DICTIONARY INACCESSIBLE | The dictionary database cannot be accessed; |
| | see the DBA. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| DATA DICTIONARY INFORMATION ERROR: number | Report error to the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DATA NAMES MUST BE SPECIFIED TO PRODUCE A | No data names have been specified. Since |
| REPORT | there is nothing to report, no report can |
| | be produced. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DATA NAME MUST BE 20 CHARACTERS OR FEWER | Check length of data name; cannot be |
| | greater than 20 characters. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DATA NAMES SELECTED MUST BE IN SORT LIST | Sorted data names are the only ones that |
| | can be used to subdivide a report. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DATA NOT NUMERIC | Data must be of numeric type to be used in |
| | a computational expression. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DATA SET DOES NOT EXIST IN DICTIONARY | The data selected does not exist in the |
| | data dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DECIMAL DIVIDE BY ZERO | Processor has detected a divide by zero in |
| | a packed decimal computation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DECIMAL LENGTHS OF ITEMS IN COMPARISON | Data names used in comparisons must be |
| EXPRESSION MUST BE EQUAL | defined with the same length. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DECIMAL OVERFLOW | Processor has detected an overflow in a |
| | packed decimal computation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DELETE NOT CONFIRMED - REPORT UNCHANGED | User indicated that report was not to be |
| | purged. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| DISC SPACE NOT AVAILABLE FOR SORT FILE | Not enough space available for SORT |
| | operation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DISPLAY FORMAT LEVEL OVERFLOW | Processor has detected an overflow in |
| | managing format levels. Report the error |
| | to the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DISPLAY FORMAT LEVEL UNDERFLOW | Processor has detected an underflow in |
| | managing format levels. Report the error |
| | to the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DUPLICATE ENTRY IGNORED | Data name has been specified more than |
| | once. |
| | |
---------------------------------------------------------------------------------------------
| | |
| EDIT MASK CANNOT BE GREATER THAN 30 | Edit mask entered was greater than 30 |
| CHARACTERS | characters. |
| | |
---------------------------------------------------------------------------------------------
| EDIT MASK WORKSPACE OVERFLOW | The total number of characters allowed for |
| | all edit masks for new data names is too |
| | large. The total must be less than 512 |
| | characters. Calculate the total number of |
| | |
| | characters with the following formula: |
| | |
| | (number of characters in edit mask 1 +` 4) |
| | + |
| | (number of characters in edit mask 2 + 4) |
| | +...+ |
| | (number of characters in edit mask n + 4) |
| | < 512 characters. |
---------------------------------------------------------------------------------------------
| | |
| EMPTY REPORT FILE | The report selected is empty, possibly |
| | because of an internal error. Report the |
| | error to the DBA. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| ENTRY CANNOT BE NEGATIVE | The data name is defined in the data |
| | dictionary as being positive. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ENTRY NOT NUMERIC | Data type is integer, floating point, or |
| | numeric ASCII and a nonnumeric character |
| | has been detected in the data entry field. |
| | |
---------------------------------------------------------------------------------------------
| | |
| *ERROR DETECTED IN SELECTION EXPRESSION | An error has been detected in the selection |
| AT FIELD n | criteria at the position indicated. |
| | |
---------------------------------------------------------------------------------------------
| | |
| *ERROR: ILLEGAL DATA TYPE FOUND, DATA | A data name with unsupported data type is |
| NAME: data name | found. |
| | |
---------------------------------------------------------------------------------------------
| | |
| *ERROR: INTERNAL ERROR number PLEASE REPORT | An unexpected error occurred. |
| | |
---------------------------------------------------------------------------------------------
| | |
| *ERROR: MPE ERROR number IN MESSAGE CATALOG | A MPE error occurred. |
| | |
---------------------------------------------------------------------------------------------
| | |
| *ERROR: MPE FILE SYSTEM ERROR number ON | An error occurred while prompting or |
| TERMINAL | writing a message. |
| | |
---------------------------------------------------------------------------------------------
| | |
| * ERROR: WORKSPACE ENTRIES FULL | Ran out of entries of an internal table, |
| | report the error to the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| *ERROR: WORKSPACE FULL | An internal table is full, report the error |
| | to the DBA. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| EXCEED MAXIMUM PERFORM | Report the error to the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| EXPRESSION CANNOT BE GREATER THAN 50 | The computational expression given for the |
| CHARACTERS | new data name must be 50 characters or |
| | fewer. |
| | |
---------------------------------------------------------------------------------------------
| | |
| EXPRESSION ERROR | The computational expression contains an |
| | error, such as a missing arithmetic |
| | operator. |
| | |
---------------------------------------------------------------------------------------------
| | |
| EXTENDED PRECISION DIVIDE BY ZERO | Processor has detected a divide by zero in |
| | a double-precision floating point |
| | computation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| EXTENDED PRECISION OVERFLOW | Processor has detected an overflow in a |
| | double-precision floating point |
| | computation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| EXTENDED PRECISION UNDERFLOW | Processor has detected an underflow in a |
| | double-precision floating point |
| | computation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| FATAL PROCESSING ERROR number | Refer to Table D-2. |
| | |
---------------------------------------------------------------------------------------------
| | |
| FLOATING POINT DIVIDE BY ZERO | Processor has detected a divide by zero in |
| | a single-precision floating point |
| | computation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| FLOATING POINT OVERFLOW | Processor has detected an overflow in a |
| | single-precision floating point operation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| FLOATING POINT UNDERFLOW | Processor has detected an underflow in a |
| | single-precision floating point operation. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| FOLLOWING DATA NAMES ARE NOT IN ANY DATA | INFORM/V is unable to make a link between |
| SET OR FILE: datanames | the first and second group of file names. |
| | Check with the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| FOLLOWING FILE(S) CANNOT BE RELATED: | The two specified groups of files have not |
| filename(s) TO FILES: filename(s) | been linked to each other in the data |
| | dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| GROUP DOES NOT EXIST IN DICTIONARY | The INFORM/V Group selected does not exist |
| | in the data dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| GROUP PASSWORD EXPECTED | A group password must be entered. |
| | |
---------------------------------------------------------------------------------------------
| | |
| IMAGE ERROR number ON DICTIONARY | An error occurred getting some security or |
| | file equate information from the data |
| | dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| IMAGE ERROR number ON FILE | An error occurred on an open. The file is |
| | the name of the file it tried to open. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INCOMPATIBLE REPORT FILE | Report was created by an earlier version of |
| | INFORM/V and, for internal reasons, can no |
| | longer operate with the current version of |
| | INFORM/V. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INPUT FIELD LONGER THAN n | Length of data entered exceeds n, the size |
| | defined for the data name. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INSUFFICIENT STACK FOR SYSTEM LOAD | Report the error to the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INSUFFICIENT STACK FOR WORKSPACE RELOAD | Report the error to the DBA. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| INTEGER DIVIDE BY ZERO | Processor has detected a divide by zero in |
| | an integer arithmetic computation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INTEGER OVERFLOW | Processor has detected an overflow in an |
| | integer arithmetic operation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INTERNAL FILE ERROR, PLEASE REPORT | An error occurred in creating the batch |
| | file. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID ACCOUNT, USER, OR GROUP PASSWORD | Password is not correct; batch job cannot |
| | be streamed. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID ARITHMETIC FIELD FOR ITEM: | The processor is attempting to execute an |
| item-name | arithmetic operation using a data name |
| | defined as character, zoned or packed |
| | decimal (type=X,U,Z or P), and has detected |
| | an invalid data storage format for the |
| | name. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID DATA NAME FORMAT | Format of data name not consistent with |
| | format defined in the data dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID DATA NUMBER | Number indicated does not appear on menu of |
| | data names. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID ENTRY IGNORED | Entry is either non-numeric or not within |
| | the range of available options. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID FILE NAME FORMAT | Name given to report does not conform to |
| | file naming conventions. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID ITEM TO ITEM COMPARISION | The syntax for the data-name to data-name |
| | comparison is not valid. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID LOCKWORD | The lockword entered was invalid. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID LOGICAL CONNECTOR | Connector must be AND or OR. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID MODE | The mode used in opening the database must |
| | be numeric and must be between 1 and 8 |
| | inclusively. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID MODE, RE-ENTER MODE > | Data base open mode specified was invalid. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID NUMBER: expression | Expression indicated is not a valid number. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID NUMBER, RANGE IS x - y | Number entered falls outside the given |
| | range. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID NUMERIC ENTRY | A numeric value was expected in response to |
| | the prompt. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID OPEN MODE. DATA BASE WILL BE | You can respond password,mode to any |
| OPENED IN MODE 5. | database password prompt, where mode is a |
| | number from 1 to 8, representing the access |
| | mode you want to open the database in. |
| | |
---------------------------------------------------------------------------------------------
| | |
| INVALID RELATIONAL OPERATOR | Operator must be EQ, GT, LE, GE, LT, or NE. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| ITEM SIZES IN COMPARISON EXPRESSION MUST BE | Data names used in comparison must be |
| EQUAL | defined with the same length. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ITEM TYPES IN COMPARISON EXPRESSION MUST BE | Data names used in comparison must be of |
| THE SAME | the same data types. |
| | |
---------------------------------------------------------------------------------------------
| | |
| LOCKWORD CANNOT CONTAIN SPECIAL CHARACTERS | MPE lockwords cannot contain special |
| | characters. |
| | |
---------------------------------------------------------------------------------------------
| | |
| LOCKWORD MUST NOT BE GREATER THAN EIGHT | MPE lockwords cannot contain more than |
| CHARACTERS | eight characters. |
| | |
---------------------------------------------------------------------------------------------
| | |
| MISMATCHED PARENTHESES: expression | The computational expression indicated did |
| | not contain a matching number of open and |
| | close parentheses. |
| | |
---------------------------------------------------------------------------------------------
| | |
| MPE COMMAND ERROR | An error occurred setting or resetting a |
| | file equation. |
| | |
---------------------------------------------------------------------------------------------
| | |
| MPE FILE SYSTEM number ON FILE filename | An error occurred on an open. The file is |
| | the name of the file it tried to open. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| NO DATA BASES ARE IN THE DICTIONARY | No databases are identified in the data |
| | dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| NO DATA NAMES ARE DEFINED IN THIS DATA SET | No data names have been assigned to this |
| | data set in the data dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| NO DATA NAMES ARE DEFINED IN THIS SUBGROUP | No data names have been assigned to this |
| | subgroup in the data dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| NO DATA SETS ARE IN THIS DATA BASE | The data dictionary shows no association |
| | between this database and its corresponding |
| | data sets. |
| | |
---------------------------------------------------------------------------------------------
| | |
| NO INFORM GROUPS ARE IN THE DICTIONARY | No INFORM/V Groups have been set up in the |
| | data dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| <NO RECORDS FOUND> | The report processor could not find any |
| | matching record in the file or database. |
| | |
---------------------------------------------------------------------------------------------
| | |
| NO REPORTS FOUND UNDER groupname | Within the specified computer group, no |
| | reports appear in the catalog. |
| | |
---------------------------------------------------------------------------------------------
| | |
| NO SUCH REPORT NAME | The report name specified is not listed in |
| | the report catalog. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| NUMERIC DECIMAL PART LONGER THAN n | Decimal part of a decimal number exceeds |
| | the length n defined for the associated |
| | data name. |
| | |
---------------------------------------------------------------------------------------------
| | |
| NUMERIC INTEGER PART LONGER THAN n | Integer part of a decimal number exceeds |
| | the length n defined for the associated |
| | data name. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ONLY ONE ENTRY EXPECTED - REMAINDER | Only one entry can be made. |
| IGNORED | |
| | |
---------------------------------------------------------------------------------------------
| | |
| ONLY number ENTRIES EXPECTED - REMAINDER | Only the specified number of entries can be |
| IGNORED | made. |
| | |
---------------------------------------------------------------------------------------------
| | |
| OUT OF RANGE PCODE ADDRESS | Report the error to the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| OUTPUT FILE ACCESS | The output device is unavailable. Check |
| | FILE statement or call system operator. |
| | |
---------------------------------------------------------------------------------------------
| | |
| PASSWORD CANNOT CONTAIN SPECIAL | Passwords cannot contain special |
| CHARACTERS | characters. |
| | |
---------------------------------------------------------------------------------------------
| | |
| PASSWORD MUST BE 8 CHARACTERS OR LESS | Password entered was longer than eight |
| | characters. |
| | |
---------------------------------------------------------------------------------------------
| | |
| PASSWORD MUST NOT BE GREATER THAN EIGHT | Password entered was longer than eight |
| CHARACTERS | characters. |
| | |
---------------------------------------------------------------------------------------------
| | |
| PRINT FILE ACCESS | The print device is unavailable. Check |
| | FILE statement or call system operator. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| RELATIONAL OPERATOR IN EXPRESSION INVALID | The operator entered is not compatible with |
| WITH ITEM TYPE | the type of these data types. |
| | |
---------------------------------------------------------------------------------------------
| | |
| REPORT FILE ALREADY EXISTS, PURGE OLD | The report file name already exists in the |
| FILE(N/Y)?> | report catalog. Should the existing report |
| | definition be replaced with the new one? |
| | |
---------------------------------------------------------------------------------------------
| | |
| REPORT FILE CLOSE FAILURE | The report cannot be added to the |
| | catalog-see the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| REPORT FILE ERROR | Report the error to the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| REPORT FILE RENAME FAILURE | Contact the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| SELECTED DATA IS NON-NUMERIC | Data name selected is not defined as |
| | numeric type in the data dictionary. |
| | |
---------------------------------------------------------------------------------------------
| | |
| SORT END | Error in MPE SORT Utility during exit |
| | procedures. If cause is not apparent to |
| | the resident system programmer, contact the |
| | DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| SORT FILE WRITE | Error on releasing record to the MPE SORT |
| | Utility. If cause is not apparent to the |
| | resident system programmer, then contact |
| | the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| SORT INITIALIZATION | Error in call to MPE SORT Utility. The |
| | probable cause is insufficient disc space |
| | for sorting. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| Message | Explanation and/or Action |
---------------------------------------------------------------------------------------------
| SORT OUTPUT | Error on requesting record from MPE SORT |
| | Utility. If cause is not apparent to the |
| | resident system programmer, then contact |
| | the DBA. |
---------------------------------------------------------------------------------------------
| THAT PASSWORD IS UNKNOWN | An invalid password (one that does not |
| | belong to any of the classes in DATA-CLASS |
| | that are of type INFO) has been entered. |
---------------------------------------------------------------------------------------------
| TITLE CANNOT BE LONGER | A report title longer than 79 characters |
| | was |
| THAN 79 CHARACTERS | entered. |
---------------------------------------------------------------------------------------------
| TOO MANY ______DEFINED | Blank spaces may contain any of the |
| | following |
| IN ______ | combinations: |
| DATA NAMES/GROUP | The limit of 255 data names per dataset or |
| | 128 |
| DATA NAMES/SET | data names per Group has been exceeded. |
| | After this message appears, the current |
| | Data Names Menu is redisplayed and will |
| | include all new data names up to but not |
| | including the name that caused the error. |
| DATA BASES/DICTIONARY | Report the error to the DBA. |
| DATA SETS/DATA BASE | |
| GROUPS/DICTIONARY | |
| SUBGROUPS/GROUP | |
---------------------------------------------------------------------------------------------
| TOO MANY FILES | The data names to be included in the report |
| | are listed in more than 255 files- -the |
| | maximum number files that can be accessed. |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| TOO MANY FILE ELEMENT RELATIONSHIPS | There are too many file-element |
| | relationships defined for the particular |
| | list of data names selected for the report. |
| | Report the error to the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| TOO MANY FILES EXIST; UNABLE TO CREATE A | INFORM/V job files and cataloged reports |
| UNIQUE FILE | must total fewer than 99. |
| | |
---------------------------------------------------------------------------------------------
| | |
| TOO MANY SUBDIVISIONS, SUBTOTALS, AND | The total number of data names selected to |
| TOTALS | be subdivided, subtotaled, and totaled |
| | exceeds the maximum of 255. |
| | |
---------------------------------------------------------------------------------------------
| | |
| TOO MANY VARIABLES IN REPORT TITLE | No more than six variables can be used in |
| | the report title. |
| | |
---------------------------------------------------------------------------------------------
| | |
| UNDELIMITED TEXT STRING | A string value must begin and end with |
| | quotes. |
| | |
---------------------------------------------------------------------------------------------
| | |
| UNEXPECTED EOF IN REPORT FILE | The processor encountered an unexpected |
| | end-of-file while reading the report file. |
| | Notify the DBA. |
| | |
---------------------------------------------------------------------------------------------
| | |
| USER OR ACCOUNT DOES NOT POSSESS THE | User or account does not have the authority |
| CAPABILITY TO STREAM A JOB | to stream a batch job. |
| | |
---------------------------------------------------------------------------------------------
| | |
| USER CAPABILITIES DO NOT ALLOW A JOB TO BE | The user does not have the authority to |
| STREAMED | stream a batch job. |
| | |
---------------------------------------------------------------------------------------------
Table D-1. User Error Messages (continued)
---------------------------------------------------------------------------------------------
| | |
| Message | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| WARNING: DATA IS TYPE X OR U | Data name used in the computational |
| | expression is of type X or U. Conversion |
| | error might occur if data is not numeric. |
| | |
---------------------------------------------------------------------------------------------
| | |
| WARNING: DATA NAME * IS OF TYPE X OR U, | Data name used at the SUMMARIZE FOR prompt |
| DATA MAY NOT BE NUMERIC | is type X or U. Conversion error might |
| | occur if data is not numeric. |
| | |
---------------------------------------------------------------------------------------------
| | |
| WARNING ** REPORT MAY CONTAIN A MAXIMUM OF | No more than 128 data names can be included |
| 128 ENTRIES | in the report. |
| | |
---------------------------------------------------------------------------------------------
| | |
| YOUR PASSWORD DOES NOT ALLOW YOU TO RUN | User is attempting to produce a report |
| THIS REPORT | created by another user having different |
| | access authority. |
| | |
---------------------------------------------------------------------------------------------
Table D-2. Fatal Processing Errors.
---------------------------------------------------------------------------------------------
| | |
| Number | Explanation and/or Action |
| | |
---------------------------------------------------------------------------------------------
| | |
| 2 | Too many file set links (file/element |
| | relationships); the limit is 255. |
| | |
| 3 | Exceeded allowable p-code instructions; the |
| | maximum is 255. |
| | |
| 6 | Overflowed internal registers. Over 255 |
| | entries or 1024 words data. |
| | |
| 7 | Too many data elements to fit into data |
| | register. Maximum is 1024 words. |
| | |
| 11 | Link table overflow; limit is 128 items. |
| | |
| 12 | Zsize error; ran out of stack. |
| | |
| 13 | Too many items selected; the maximum is |
| | 128. |
| | |
| 100 | Table holding files overflowed; the maximum |
| | is 32 files. |
| | |
| 101 | Too many databases to load; the limit is 16 |
| | databases. |
| | |
| 102 | Too many file/element relationships; the |
| | maximum is 255. |
| | |
| 112 | Table holding items overflowed; the maximum |
| | is 128 items. |
| | |
| 113 | Cannot find a starting file for the report; |
| | missing file/element relationship. |
| | |
---------------------------------------------------------------------------------------------