MPE/iX Error Messages Manual Vol 3 (32650-90880)

Chapter 6 245
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
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