The diagnostic messages produced by the DML precompilers, along with their associated error numbers and severity-level designations, are listed below in numerical order by message ID. For those messages that are language specific, the appropriate languages are noted. Each message is followed by an explanation.
Reason:
The statement coded does not conform to a recognized syntax. Under the error message is a marker pointing to the keyword, identifier, number, string, or delimiter being scanned when the error condition was raised.
Severity:
E
Reason:
An internal error has occurred. See the accompanying text for details. Contact Technical Support for assistance.
Severity:
E
Reason:
An "END-EXEC" keyword is missing for COBOL or a semicolon is missing for non-COBOL programs. An SQL terminator is needed for an SQL statement.
Severity:
E
Reason:
The number of columns in the column list does not match the number of column aliases specified for the EXEC SQL INCLUDE TABLE.
Severity:
E
Reason:
The table name specified for the EXEC SQL INCLUDE TABLE could not be found in the SQL catalog. Recheck the spelling and if the table has been created, check with the DBA.
Severity:
E
Reason:
The named column exceeded the COBOL maximum of 18 digits for a decimal (COMP-3) or zoned decimal field, or a PL/I maximum of 15 for a fixed decimal or zoned decimal field. Appropriate compiler options must be specified to change the maximum precision to 31, else compiler errors will occur.
Severity:
W
Reason:
The length of a data identifier exceeds the legal limitation. Data identifiers are limited to a maximum of eight characters.
Severity:
E
Reason:
The length of a data identifier exceeds the legal limitation. Data identifiers are limited to a maximum of 32 characters.
Severity:
E
Reason:
The value specified for length must not be subscripted. This message applies only to DC programs only.
Severity:
E
Reason:
The named map is incompatible with the release level of the software. Using the proper release level of the software, recompile the map. This message applies only to DC programs.
Severity:
F
Reason:
The number of fields in the field list exceeds the size specified in the MAP SECTION. The field list size must be at least one greater than the largest field list in the program. Change the MAP FIELD LIST specification in the MAP SECTION to a larger value. This message applies only to DC programs.
Severity:
F
Reason:
Insufficient memory is available to accommodate requirements. Specify a larger region/partition size.
Severity:
T
Reason:
Probable causes for the return of this message are as follows:
Contact the DBA.
Severity:
E
Reason:
An error has occurred in accessing the data dictionary. This message is followed by a listing of the subschema control statistics current when the DML precompiler encountered the problem. This may be a system internal error.
Severity:
T
For more information about this error, see Precompilers.
Reason:
Probable causes for the return of this message are as follows:
Severity:
E
Reason:
The subschema named has not been defined in the data dictionary. Contact the DBA.
Severity:
E
Reason:
The schema named has not been defined in the data dictionary. Contact the DBA.
Severity:
E
Reason:
The subschema named has not been defined in the data dictionary under the schema specified. This message is also issued if the dictionary option 'AUTHORIZATION IS ON' is in effect and the program is not known to the dictionary. Contact the DBA.
Severity:
E
Reason:
The DML precompiler has encountered an ON clause, but AUTOSTATUS is not active. Check the MODE statement for the specification of an auto status protocol. (COBOL only)
Severity:
E
Reason:
The execution mode specified in the MODE statement has not been defined in the data dictionary. Contact the DBA.
Severity:
E
Reason:
The source program has not been registered for use with the named subschema, and program registration is in effect. Contact the DBA.
Severity:
E
Reason:
The IDMS communications block (subschema-control) specified has not been defined in the data dictionary. Contact the DBA.
Severity:
E
Reason:
The record SUBSCHEMA-LR-CTRL, which can be specified in a COPY IDMS or INCLUDE IDMS statement, has not been defined in the data dictionary. Contact the DBA.
Severity:
E
Reason:
Probable causes for the return of this message are as follows:
Reason:
Contact the DBA.
Severity:
E
Reason:
The logical record specified has not been defined in the data dictionary. Contact the DBA.
Severity:
E
Reason:
The record name is missing or misspelled.
Severity:
E
Reason:
The set name is missing or misspelled.
Severity:
E
Reason:
The record name, set name, or area name is missing or misspelled.
Severity:
E
Reason:
An integer is missing or specified incorrectly. Check the appropriate syntax.
Severity:
E
Reason:
An alphanumeric literal enclosed in quotes is missing or specified incorrectly. Check the appropriate syntax.
Severity:
E
Reason:
A user-supplied value is specified as a quoted literal, but the value should be a variable field name.
Severity:
E
Reason:
A duplicate control statement has been entered. The precompiler has ignored the duplicate control statement and has continued processing.
Severity:
W
Reason:
The statement contains a DC verb that is not allowed under mode DC-BATCH. Change the PROTOCOL statement to specify the appropriate mode.
Severity:
E
Reason:
The statement must be terminated by a period or a semicolon.
Severity:
E
Reason:
The qualifying record name specified for group-id-a is not valid for the variable field name specified. The named field is not contained in the named record.
Severity:
E
Reason:
The right parenthesis for subscript termination is missing.
Severity:
E
Reason:
A number, data name, or nested expression is not included after a unary plus or minus.
Severity:
E
Reason:
An invalid subscript is associated with a data name.
Severity:
E
Reason:
The right parenthesis for an expression is missing.
Severity:
E
Reason:
An invalid expression is contained within parentheses.
Severity:
E
Reason:
The second operand following a plus or minus operator is missing from an expression.
Severity:
E
Reason:
The second operand following a multiplication or division operator is missing from an expression.
Severity:
E
Reason:
The program variable field specified for variable-field-name does not exist in the data dictionary. All variable fields used in WHERE clauses must be defined in the dictionary.
Severity:
E
Reason:
The element named does not exist in the subschema or in the map.
Severity:
E
Reason:
Too many levels of subscripting are specified. See the DBA to determine the attributes of the variable in question.
Severity:
E
Reason:
Too few levels of subscripting are specified. See the DBA to determine the attributes of the variable in question.
Severity:
E
Reason:
The element named is not unique in the subschema or in the map. Record qualification is needed.
Severity:
E
Reason:
Subscripts are not legal for the indicated field.
Severity:
E
Reason:
A data type of group, floating point, or bit is not allowed with an arithmetic operation.
Severity:
E
Reason:
An operand of a logical conjunction (that is, AND, OR, or NOT)is invalid. To be valid, these operands must resolve to a condition of true or false. For example, the following expression is valid: WHERE AMT>0 AND SALES<10; both operands of the operator AND resolve to either a true or false condition. In contrast, the following expression is not valid: WHERE AMT AND SALES<10; the first operand, AMT, does not resolve to a true or false condition.
Severity:
E
Reason:
An operand of MATCHES or CONTAINS does not have a valid data type or length. The mask specified as an operand of MATCHES or CONTAINS must be equal to or shorter than the field specified as the other operand. Both operands of MATCHES or CONTAINS must be alphanumeric.
Severity:
E
Reason:
A subscript is expected for the indicated field.
Severity:
E
Reason:
The length of the divisor exceeds the maximum of 8 bytes (internal).
Severity:
E
Reason:
The OCCURS DEPENDING ON control field associated with the field name flagged is not a halfword or a full word. See the DBA.
Severity:
E
Reason:
A keyword is used in an arithmetic expression; keywords must not be used in arithmetic expressions.
Severity:
E
Reason:
An operand for a boolean AND, OR, or NOT operator is invalid or missing.
Severity:
E
Reason:
An invalid nested condition has been detected.
Severity:
E
Reason:
The right parenthesis for a nested condition is missing.
Severity:
E
Reason:
The operand for a relational operator is missing or invalid.
Severity:
E
Reason:
This message indicates that the SIZE IS specification in the COPY/INCLUDE SUBSCHEMA-LR-CTRL statement is not large enough to hold the variables and literals specified in the WHERE clause. Calculate the proper size specification according to the formula in the appropriate CA IDMS DML Reference Guide. (The default size is 512 bytes if no SIZE IS clause is specified.)
Severity:
E
Reason:
An ACCEPT OWNER DBKEY request has been made and the set has no owner pointer. Check the subschema definitions.
Severity:
I
Reason:
An attempt has been made to CONNECT a member record defined as mandatory automatic. CONNECT cannot be issued for a mandatory automatic member. Check the subschema definitions.
Severity:
E
Reason:
An attempt has been made to DISCONNECT a member record defined as mandatory. DISCONNECT cannot be issued for a mandatory member. Check the subschema definitions.
Severity:
E
Reason:
A FIND/OBTAIN CALC/DUPLICATE statement has specified a record not defined as CALC in the schema description. Check the subschema definitions.
Severity:
E
Reason:
A FIND/OBTAIN DUPLICATE statement has specified a record that has not been defined with DUPLICATES ALLOWED in the schema description.
Severity:
W
Reason:
The schema set description does not specify owner pointers for this set. Note that this message is informational only; no action is required. However, the lack of owner pointers may degrade processing efficiency when the program is executed.
Severity:
I
Reason:
A FIND/OBTAIN statement has named a record within a sorted set, but the set specified is not sorted. Check the subschema definitions.
Severity:
E
Reason:
A FIND/OBTAIN PRIOR WITHIN SET has been issued, but the named set has not been defined with prior pointers. Check the subschema definitions.
Severity:
E
Reason:
A tacit access restriction for ERASE, STORE, or MODIFY has been established for this member record type; this record cannot be updated. Check the subschema definitions.
Severity:
E
Reason:
The record named has been defined with an access restriction that does not allow the DML function requested. Check the subschema definitions.
Severity:
E
Reason:
A tacit restriction for CONNECT, DISCONNECT, FIND or KEEP has been established for this set; the requested function cannot be performed. Check the subschema definitions.
Severity:
E
Reason:
A DML statement has named a record as existing within a set, but the record does not participate in the set. Check the subschema definitions.
Severity:
E
Reason:
A DML statement has named a record as existing within an area, but the record does not occur within the area. Check the subschema definitions.
Severity:
E
Reason:
A tacit access restriction for RETRIEVAL or UPDATE has been established for this area; it cannot be readied in the requested mode. Check subschema definitions.
Severity:
E
Reason:
The BIND RUN-UNIT statement either has not been coded or has been coded incorrectly. Check the BIND RUN-UNIT statement for proper syntax. Note that programming logic for subprograms or for non-IDMS programs may generate this warning automatically; in this case, corrective action is unnecessary.
Severity:
W
Reason:
A BIND RECORD statement either has not been coded or has been coded incorrectly. Check the BIND RECORD statement for proper syntax. Note that programming logic for subprograms or for non-IDMS programs may generate this warning automatically; in this case, corrective action is unnecessary.
Severity:
W
Reason:
A subschema record has been copied into program variable storage more than once. For this record, the precompiler does not issue a BIND when it processes the COPY IDMS SUBSCHEMA-BINDS statement. The programmer must include a BIND RECORD statement to bind the record to the correct location.
Severity:
W
Reason:
The READY statement either has not been coded or has been coded incorrectly. Check the READY statement for proper syntax. Note that programming logic for subprograms or for non-IDMS programs may generate this warning automatically; in this case, corrective action is unnecessary.
Severity:
W
Reason:
The READY UPDATE statement either has not been coded or has-been coded incorrectly. Check the READY UPDATE statement for proper syntax. Note that programming logic for subprograms or for non-IDMS programs may generate this warning automatically; in this case, corrective action is unnecessary.
Severity:
W
Reason:
The FINISH statement either has not been coded or has been coded incorrectly. Check the FINISH statement for proper syntax. Note that programming logic for subprograms or for non-IDMS programs may generate this warning automatically; in this case, corrective action is unnecessary.
Severity:
W
Reason:
An ERASE statement specifies a logical record for which no ERASE path group has been defined. Check the subschema definitions.
Severity:
E
Reason:
An OBTAIN statement specifies a logical record for which no OBTAIN path group has been defined. Check the subschema definitions.
Severity:
E
Reason:
This message indicates one of the following error conditions:
Check the subschema definitions.
Severity:
E
Reason:
This message indicates one of the following error conditions:
Check the subschema definitions.
Severity:
E
Reason:
The file name specified for a COPY IDMS statement is missing or misspelled.
Severity:
E
|
Copyright © 2014 CA.
All rights reserved.
|
|