TurboIMAGE/XL Database Management System Reference Manual MPE/iX V6.5 (30391-90011)

Appendix A 517
Error Messages
Schema Processor Error Messages
Schema Syntax Errors
Database definition syntax errors can be detected by the Schema Processor. Their
existence does not cause termination but does prohibit root file creation. Discovery of one
can trigger others which disappear after the first is corrected. Also, detection of one can
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 MUST HAVE SEARCH ITEM ONLY
MEANING 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. Edit the text file, and run
the Schema Processor again.
MESSAGE BAD BLOCKING FACTOR OR TERMINATOR
MEANING A bad blocking factor or terminator was specified.
ACTION Examine the schema text file to find any incorrect commands. Edit the text
file, and run the Schema Processor again.
MESSAGE BAD CAPACITY (MAX, INIT, INCREMENT) OR TERMINATOR
MEANING One of the capacity parameters (maximum, initial, or increment) is
incorrect, or the terminator is not ";".
ACTION Change the maximum, initial, or increment capacity parameter, and use
";" as the terminator. See "Set Part" in chapter 3 for correct values for the
parameters.
MESSAGE BAD CHARACTER IN USER CLASS NUMBER
MEANING User class number in password is not an integer from 1 to 63.
ACTION Examine the schema text file to find the error. Edit the text file, and run
the Schema Processor again.
MESSAGE BAD DATABASE NAME OR TERMINATOR
MEANING Database name in BEGIN DATABASE 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. Edit the text file, and run
the Schema Processor again.