The following messages are from the IDMS macros. These messages can be identified by APS-IDB at the beginning of the message code in the message report. The messages are in numerical sequence.
The $DB-BIND macro call did not include a record name as an argument.
When MANUAL is coded for the $DB-PROTOCOL, $DB-BIND expects a record name as an argument. Either replace MANUAL for $DB-PROTOCOL with an alternate argument, or supply a record for $DB-BIND.
$IDM-BIND call specifies a record name as an argument although $IDM-PROTOCOL does not specify MANUAL.
Change $IDM-PROTOCOL so that MANUAL is specified, or remove the record name as an argument for $DB-BIND.
$DB-SUBSCHEMA macro call is missing, or the subschema name was not supplied as an argument, therefore, records cannot be bound.
Ensure that the $DB-SUBSCHEMA macro was generated or coded properly, refer to documentation for $DB-SUBSCHEMA.
The keyword 'REC' is expected prior to specifying the record name parameter.
Correct the call by specifying the keyword REC immediately followed by the record name.
The keyword 'REC' was coded but no additional parameters were supplied.
Correct the call by supplying the record name immediately after the keyword 'REC'.
An unknown or invalid parameter was coded for the $DB-ERASE macro.
Check the documentation for $DB-ERASE and change the unknown or invalid parameter.
A database macro call was invoked but no parameters were passed.
Correct the call by specifying the appropriate parameters.
The keyword 'TO' should precede the set name for the $IDM-CONNECT macro call.
Correct the call by coding the keyword 'TO' immediately followed by the set name parameter.
The keyword 'TO' was specified but no set name was coded.
Correct the call by supplying the set name parameter immediately after the 'TO' keyword.
The keyword 'FROM' should precede the set name for the $IDM-DISCONNECT macro call.
Correct the call by coding the keyword 'FROM' immediately followed by the set name parameter.
The keyword 'FROM' was specified but no set name was coded.
Correct the call by supplying the set name parameter immediately after the 'FROM' keyword.
The keywords REF and REC were specified in the wrong order.
Correct the CALL by specifying the parameters in the proper order. (See APS/IDMS Generator Reference Manual on $DB-OBTAIN or $DB-PROCESS.).
When referencing a qualified data name, the group level name was not specified.
Correct the CALL by supplying the group level name immediately after the 'OF' keyword.
The parameter is invalid or it is misplaced in the command syntax.
Check the spelling and/or placement of the parameter.
An unrecognizable combination of parameters was specified for a $DB-OBTAIN macro.
Correct the CALL by specifying a valid combination of parameters. (See APS/IDMS Generator Reference Manual for information on $DB-OBTAIN).
They keyword 'WHERE' was coded, but no additional parameters were specified.
Correct the CALL by supplying the parameters desired. (See APS/IDMS Generator Reference Manual for information on $DB-OBTAIN).
This parameter is invalid or it is misplaced in the command.
Check the spelling and/or placement of the parameter.
A database macro was invoked but not enough parameters were passed.
Correct the CALL by specifying the appropriate parameters.
When coding $DB-OBTAIN or $DB-PROCESS, either the keyword 'IDMSREC' or a valid record name must be coded following the 'REC' or 'REF' keywords.
Correct the CALL by specifying the keyword 'REC' or 'REF' as first parameter, followed by the record name.
When coding $DB-OBTAIN or $DB-PROCESS, either the keyword 'IDMSREC' or a valid record name must be coded following the 'REC' or 'REF' keywords.
Correct the CALL by specifying 'IDMSREC' or a valid record name.
When using format 5 of $DB-OBTAIN (obtains the owner of a set when the record name is unknown), set name must be specified. must be specified.
Correct the CALL by specifying the 'SET' keyword followed by a valid set name.
The $DB-OBTAIN format specified requires a set or an area name.
Correct the CALL by specifying the 'SET' keyword followed by a valid set name, or the 'AREA' keyword followed by a valid area name.
The keyword 'WHERE' with a key name and a relational operator were specified, but no value was found to complete the qualification.
Correct the CALL by supplying the area name immediately after the 'AREA' keyword.
The keyword 'AREA' was specified, but no area name was coded.
Correct the CALL by supplying the area name immediately after the 'AREA' keyword.
The keyword 'SET' was specified, but no set name was coded.
Correct the CALL by supplying the set name immediately after the 'SET' keyword.
A relational operator was expected to complete the qualification.
Complete the qualification by specifying a relational operator followed by a data name or literal.
The DB-PROCESS-ID specified is longer than 18 characters.
Correct the DB-PROCESS-ID name so that it is 18 characters or less.
Duplicate DB-PROCESS-ID names were found.
Provide a unique DB-PROCESS-ID name.
A positional argument passed in the macro call is invalid.
Check the spelling of the argument and/or the macro documentation for the list of valid arguments.
When using format 1 (retrieves records based on a CALC key or an indexed or sorted set), of the $DB-OBTAIN MACRO, the relational operator must be '=' 'EQ' or 'EQUAL'.
Correct the area name.
Performing a FIND or OBTAIN against the OWNER of an AREA is invalid.
Correct the call by specifying the keyword 'SET' and the set name rather than keyword 'AREA' and area name.
An invalid combination of keywords was specified in a $DB-OBTAIN call.
Correct the CALL by specifying a valid combinations of parameters; refer to $DB-OBTAIN documentation.
The keyword 'REC' or 'REF' was specified, followed by an invalid record name or a record name not found in the subschema.
Correct the record name.
The keyword 'MODE' is specified twice for the $DB-OPEN macro.
Remove the second keyword 'MODE' and/or the second usage mode from the argument macro call.
The keyword 'AREA' is specified twice for the $DB-OPEN macro.
Remove the second keyword 'AREA' and/or the second usage mode from the argument macro call.
When using format 4 (obtains a record based on its database address) of $DB-OBTAIN, extraneous keywords were specified.
Correct the CALL by removing unnecessary parameters.
When using format 4 (obtains a record based on its database address) of $DB-OBTAIN, the relational operator must be '=', 'EQ', or 'EQUAL'.
Correct the relational operator.
When keywords 'WHERE SEQUENCE' are specified, the relational operator must be '=', 'EQ,' or 'EQUAL'.
Correct the relational operator.
The keywords specified may not be used together.
Correct the CALL by removing the unnecessary keyword. See APS/IDMS Generator Reference Manual for further information on $DB-OBTAIN or $DB-PROCESS.
The 'WHERE' keyword was followed by an invalid key name or a keyname not found in the subschema.
Correct the keyname.
The 'SET' keyword was followed by an invalid set name or a set name not found in the subschema.
Correct the set name.
The keywords 'REC' and 'REF' were coded, followed by valid record names, but no set was found in the subschema that connects those records.
Correct the record name(s) specified.
When coding $DB-OBTAIN the 'WHERE' clause may not be used for VIA keys.
Correct the key specified in the CALL.
The key specified is not found in the named set; either the key is no longer in the set, or it was incorrectly specified.
Check the spelling on the specified key.
The specified record exists, but the key entered is not recognized as being part of that record.
Ensure that the correct key and record are referenced, and that they are spelled correctly.
More than one set contains the key name that was specified.
Include the set name in your key name specifications.
The protocol mode was set to the value of the FMP variable APS-MDC as the default value.
Information item: protocol mode can be overridden, if desired, by supplying the appropriate value on the macro call.
The protocol mode was set to the value of IDMS-DC as the default.
Information item: protocol mode can be overridden, if desired, by supplying the appropriate value on the macro call.
The IDMS records will be put in working storage as the default.
Information item: Protocol mode can be overridden, if desired, by supplying the appropriate value on the macro call.
The $IDMS-PROTOCOL macro was not coded.
Information item: Code the $IDMS-PROTOCOL macro if not using the IDCS painter keyword.
The $DB-SUBSCHEMA macro was not coded.
Information item: Code the $DB-SUBSCHEMA macro if the program needs database access and the IDSS painter keyword is not used.
The $DB-OPEN macro was not coded.
Information item: Code $DB-OPEN if necessary.
The $DB-CLOSE macro was not coded.
Information item: code $DB-CLOSE if necessary.
More than one $IDM-PROTOCOL macro was coded.
Remove all but one $IDM-PROTOCOL macro call.
More than one $DB-SUBSCHEMA macro was coded.
Remove all but one $DB-SUBSCHEMA macro call.
The FMP variable containing the name of the schema for the application is not defined.
Contact your APS Administrator and/or the DBA for the project so the variable can be defined and included from the proper library of symbols. Otherwise, code the $DB-SUBSCHEMA macro, supplying all required arguments.
The format of the FMP variable containing the schema name indicates that a version number will be specified. The version number is missing.
The APS Administrator or the project DBA should supply the missing version number or correct the FMP format. Otherwise, code the $DB-SUBSCHEMA macro, supplying all required arguments.
The DDISYMB generation failed to create the AREA NAME SYMBOL.
Check to see if the area name exists in the specified subschema.
The DDISYMB generation failed to create the key name symbol.
Check to see if the key exists in the specified subschema.
DDISYMB has been corrupted.
Regenerate the DDISYMB and re-try.
DDISYMB has been corrupted.
Regenerate the DDISYMB and retry.
Copyright © 2002 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.