Schema Processor Error Messages

The Schema Processor accesses three files:

The text file (DBSTEXT) containing the schema records and Schema Processor commands for processing.
The list file (DBSLIST) containing the schema listing, if requested, and error messages, if any.
The root file, if requested, created as a result of an error-free schema.

Any file error which occurs while accessing any of these files causes the Schema Processor to terminate execution. A message indicating the nature of the error is sent to $STDLIST (and to the list file, if the list file is different from $STDLIST).

Schema Processor command errors may occur. They neither cause termination nor do they prohibit the creation of a root file. In some cases, however, the resultant root file will differ from what might have occurred had the commands been error free. Command errors are added to an error count which, if it exceeds a limit, will cause the Schema Processor to terminate execution.

Note that if the LIST option is active, error messages for command errors and syntax errors appear in the list file following the offending statement. If the NOLIST option is active, only the offending statement, followed by the error message, is listed.

Schema Processor File Errors

Various file error messages are listed in this section. Each such message is preceded by the character string:

		****** FILE ERROR ******

Additionally, the Schema Processor prints a standard MPE/iX file information display on the $STDLIST file.

MESSAGE: READ ERROR ON file name
CAUSE: FREAD error occurred on the specified file.
ACTION: Check text file or :FILE command.

MESSAGE: FILE ALREADY EXISTS; UNABLE TO CLOSE file name
CAUSE: FCLOSE error occurred on specified file. May be caused by duplicate file in group with same name as root file.
ACTION: Change database name or purge file of same name. Or, be sure correct file and file name used. Check :FILE commands used. If other cause, consult MPE/iX Intrinsics Manual (32650-90028) for similar message.

MESSAGE: UNABLE TO USE file name
CAUSE: Specified file cannot be FOPENed or its characteristics make it unsuitable for its intended use.
ACTION: Change database name or purge file of same name. Or, be sure correct file and file name used. Check :FILE commands used. If other cause, consult MPE/iX Intrinsics Manual (32650-90028) for similar message.

MESSAGE: UNABLE TO WRITE LABEL OF file name
CAUSE: FWRITELABEL error occurred on specified file.
ACTION: Change database name or purge file of same name. Or, be sure correct file and file name used. Check :FILE commands used. If other cause, consult MPE/iX Intrinsics Manual (32650-90028) for similar message.

MESSAGE: UNEXPECTED END-OF-FILE ON file name
CAUSE: Call to FREAD or FWRITE on specified file has yielded unexpected end of file condition.
ACTION: Change database name or purge file of same name. Or, be sure correct file and file name used. Check :FILE commands used. If other cause, consult MPE/iX Intrinsics Manual (32650-90028) for similar message.

MESSAGE: WRITE ERROR ON file name
CAUSE: FWRITE error occurred on the specified file.
ACTION: Change database name or purge file of same name. Or, be sure correct file and file name used. Check :FILE commands used. If other cause, consult MPE/iX Intrinsics Manual (32650-90028) for similar message.

Schema Processor Command Errors

Various Schema Processor command error messages are listed in this section. Each such message is preceded by the character string:

		***** ERROR ******

MESSAGE: COMMAND CONTINUATION NOT FOUND
CAUSE: If the schema processor command is continued to the next record, the last non-blank character of the preceding line must be an ampersand (&) and the continuation record must start with a dollar sign ($).
ACTION: Examine the schema text file to find any incorrect commands. Edit the text file and run the Schema Processor again.

MESSAGE: COUNT HAS BAD FORMAT
CAUSE: The numbers in ERRORS, LINES, or BLOCKMAX parameters of the $CONTROL command are not properly formatted integer values.
ACTION: Examine the schema text file to find any incorrect commands. Edit the text file and run the Schema Processor again.

MESSAGE: ILLEGAL COMMAND
CAUSE: The Schema Processor does not recognize the command. Valid commands are $PAGE, $TITLE, and $CONTROL.
ACTION: Examine the schema text file to find any incorrect commands. Edit the text file and run the Schema Processor again.

MESSAGE: IMPROPER COMMAND PARAMETER
CAUSE: One of the commands in the parameter is not valid.
ACTION: Examine the schema text file to find any incorrect commands. Edit the text file and run the Schema Processor again.

MESSAGE: MISSING QUOTATION MARK
CAUSE: Character string specified in $PAGE or $TITLE command must be bracketed by quotation marks (").
ACTION: Examine the schema text file to find any incorrect commands. Edit the text file and run the Schema Processor again.

MESSAGE: SPECIFIED TITLE IS TOO LONG
CAUSE: Character string in $TITLE or $PAGE command exceeds 104 characters.
ACTION: Examine the schema text file to find any incorrect commands. Edit the text file and run the Schema Processor again.

Schema Syntax Errors

Database definition syntax errors may be detected by the Schema Processor. Their existence does not cause termination but does prohibit root file creation. Discovery of one may trigger others which disappear after the first is corrected. Also, detection of one may preclude detection of others which appear after the first is corrected. Syntax errors are also added to an error count which, if excessive, will cause Schema Processor termination.

Various syntax error messages are listed in this section. As with command errors, each syntax error is preceded by the character string:

		***** ERROR ******

MESSAGE: AUTOMATIC MASTER DATA SET MUST HAVE SEARCH ITEM ONLY
CAUSE: Automatic master data sets must contain entries with only one data item. The data item must be a key item.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD CAPACITY OR TERMINATOR
CAUSE: Either the number in the CAPACITY: statement is not an integer between 1 and 2 -1, or a semicolon is missing.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD CHARACTER IN USER CLASS NUMBER
CAUSE: User class number in password is not an integer from 1 to 63.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD DATA BASE NAME OR TERMINATOR
CAUSE: Database name in BEGIN DATA BASE statement is not a valid database name beginning with an alphabetic character and having up to 6 alphanumeric characters. Or, the name is not followed by a semicolon (;).
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD DATA SET TYPE
CAUSE: The data set type designator is not AUTOMATIC (or A), MANUAL (or M), or DETAIL (or D).
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD DEVICE CLASS NAME
CAUSE: The device class name specified contains an invalid character. The name must be less than eight characters and begin with a letter.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD DEVICE CLASS NAME OR TERMINATOR
CAUSE: The device class name specified contains an invalid character or was not ended with a semicolon ";".
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD LANGUAGE
CAUSE: Language name contains invalid characters, or the language number is not a valid integer.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD PATH CONTROL PART DELIMITER
CAUSE: Data item defined as sort item in detail data set is not properly delimited with parentheses ().
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD PATH COUNT OR TERMINATOR
CAUSE: The path count in the master data set definition is not an integer from 1 to 16 (for an automatic master), or 0 to 16 (for a manual master). This message may also mean the path count is not followed by a quotation mark (").
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD PATH SPECIFICATION DELIMITER
CAUSE: Name of master data set following search item name in detail data set definition is not followed by a right parenthesis ")", or by a sort item name in parentheses.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD READ CLASS OR TERMINATOR
CAUSE: Read user class number defined for either a data set or data item is not an integer from 0 to 63, or it is not terminated by a comma (,) or slash (/).
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD SET NAME OR TERMINATOR
CAUSE: The data set name does not conform to naming rules. (Names must start with a letter and may have up to 16 alphanumeric characters including + - * / ? ' # % & @.) Or the data set name is not terminated by the correct character for the context in which it appears.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD SUBITEM COUNT OR TERMINATOR
CAUSE: Subitem count for a data item defined in schema item part is not an integer from 1 to 255.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD SUBITEM LENGTH OR TERMINATOR
CAUSE: Subitem length for data item defined in schema item is not an integer from 1 to 255.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD TERMINATOR-';' EXPECTED
CAUSE: Password or capacity was not followed by a semicolon.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD TERMINATOR- ';' OR ',' EXPECTED
CAUSE: Items within an entry definition must be separated from each other with commas and terminated with a semicolon.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD TYPE DESIGNATOR
CAUSE: Data item defined in schema item part is not defined as type I, J, K, R, U, X, Z, or P.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: BAD WRITE CLASS OR TERMINATOR
CAUSE: Write user class number shown for the data set or data item is not an integer from 0 to 63, or it is not terminated by a right parenthesis ")" or comma.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: 'CAPACITY:' EXPECTED
CAUSE: CAPACITY statement must follow entry definition in the definition of data sets in the set part of schema.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: DATA BASE HAS NO DATA SETS
CAUSE: No data sets were defined in the set part of schema. The database must contain at least one data set.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: DATA BASE NAME TOO LONG
CAUSE: Database name has more than six characters.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: DUPLICATE ITEM SPECIFIED
CAUSE: The same data item name was used more than once in the entry definition of data sets.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: DUPLICATE SET NAME
CAUSE: The same data set name was used to define more than one data set in the set part of schema.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: 'ENTRY:' EXPECTED
CAUSE: Each set defined in the set part of schema must contain ENTRY: statement followed by the data item names of the data items in entry.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: ENTRY TOO BIG
CAUSE: The number and size of the data items defined for an entry makes an entry too big for maximum block size. The block size is specified by $CONTROL, or BLOCKMAX= command, or default.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: ENTRY TOO SMALL
CAUSE: A detail data set that is not linked to any master data set must have a data entry length of two or more halfwords. This length is determined by adding the size in halfwords of each data item defined in the data entry.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: ILLEGAL ITEM NAME OR TERMINATOR
CAUSE: The data item name does not conform to naming rules. (Names must start with a letter and may have up to 16 alphanumeric characters including + - ? / # $ & * @ ). Or if in the item part, it is not followed by a comma.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: ILLEGAL USER CLASS NUMBER
CAUSE: User class number defined in schema password part is not an integer between 1 and 63.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: ITEM TOO LONG
CAUSE: The length of a single data item may not exceed 2047 halfwords.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: 'LANGUAGE:' EXPECTED
CAUSE: The Schema Processor expected to find a LANGUAGE statement after the comma following the BEGIN DATA BASE name statement.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: LANGUAGE NOT SUPPORTED
CAUSE: Language specified is not supported on your system, or is not a valid language.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: MASTER DATA SET LACKS EXPECTED DETAIL(S)
CAUSE: Master data set was defined with a non-zero data count, but the number of detail search items which back-referenced the master is less than the value of the path count.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: MASTER DATA SET LACKS KEY ITEM
CAUSE: A master data set was defined without defining one of the data items in the set as a key item.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: MORE THAN ONE KEY ITEM
CAUSE: A master data set cannot be defined with more than one key item.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: MORE THAN ONE PRIMARY MASTER
CAUSE: User has defined more than one primary path for a detail data set.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: 'NAME:' OR 'END.' EXPECTED
CAUSE: Schema Processor expected, at this point, to find the beginning of another data set definition, or the end of schema.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: NATIVE LANGUAGE SUPPORT ERROR
CAUSE: NLS/3000 returned an error.
ACTION: Notify the system manager

MESSAGE: 'PASSWORDS:' NOT FOUND
CAUSE: 'PASSWORDS:' statement must immediately follow the BEGIN DATA BASE statement in schema. If it does not, DBSCHEMA terminates execution.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: PASSWORD TOO LONG
CAUSE: A password defined in data schema cannot exceed eight characters.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: REFERENCED SET NOT MASTER
CAUSE: The data set referenced by the detail data set search item is another detail data set instead of a master data set.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: SCHEMA PROCESSOR LACKS NEEDED TABLE SPACE
CAUSE: Schema Processor is unable to expand its data stack to accommodate all of the translated information which will make up the root file. It continues to scan the schema for the proper form, but will not perform all of the checks for correctness nor will it create a root file. To process the schema correctly, the operating system must be configured with a larger maximum stack size.
ACTION: Ask system manager to increase maximum stack size.

MESSAGE: SEARCH OR KEY ITEM NOT SIMPLE
CAUSE: All data items defined in data schema as key or search items must be simple items.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: SEARCH AND KEY ITEMS NOT OF SAME LENGTH
CAUSE: Master key item must be the same length as any related detail data set search item.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: SEARCH AND KEY ITEMS NOT OF SAME TYPE
CAUSE: Master key item must be of the same type as any related detail data set search item.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: SET HAS NO PATHS AVAILABLE
CAUSE: More detail data set search items have specified a relationship with a master data set than the number specified in the master set's path count.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: SORT ITEM OF BAD TYPE
CAUSE: Data item defined as sort item must be of type U, K, or X.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: SORT ITEM NOT IN DATA SET
CAUSE: Detail data set's entry definition does not include an item which is specified as a sort item for another item in the entry.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: SORT ITEM SAME AS SEARCH ITEM
CAUSE: The same item cannot be both a search and a sort item for the same path.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: TOO MANY DATA ITEMS
CAUSE: The item part of schema cannot have more than 1023 data item names
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: TOO MANY DATA SETS
CAUSE: The database cannot have more than 199 data sets.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: TOO MANY ERRORS
CAUSE: The specified or default number of errors has been exceeded. Processing is terminated.
ACTION: Correct the errors, or increase the ERROR parameter value.

MESSAGE: TOO MANY ITEMS SPECIFIED
CAUSE: The data set entry cannot have more than 255 data items.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: TOO MANY PATHS IN DATA SET
CAUSE: Detail data set entries cannot have more than 16 search items.
ACTION: Examine the schema text file to find the error and edit the file. Run the Schema Processor again.

MESSAGE: UNDEFINED ITEM REFERENCED
CAUSE: A data item appearing in the data set definition was not previously defined in the item part of schema.
ACTION: Examine the schema text file and find the incorrect statement. Edit it and run the Schema Processor again.

MESSAGE: UNDEFINED SET REFERENCED
CAUSE: Master data set referenced by detail search item was not previously defined in the set part of schema.
ACTION: Examine the schema text file and find the incorrect statement. Edit it and run the Schema Processor again.

Schema Processor Error Messages

Technical documentation

» Table of Contents

Schema Processor File Errors

Schema Processor Command Errors

Schema Syntax Errors