Previous Topic: Messages 800 - 899Next Topic: Unnumbered Messages

Numbered Messages and Codes › Messages 900 - 999

Messages 900 - 999

DQ900E

YOUR QUERY CANNOT BE VALIDATED OR EXECUTED - CONTACT YOUR DQA

Reason:

A restricted condition contains a word, file name, field name, and so forth, which causes a validation error.

Action:

Review all restrictions applied to this user. One of the conditions imposed by a restriction causes a validation error. Correct the erroneous condition.

DQ901E

AN ATTEMPT WAS MADE TO USE A KEY GREATER THAN 180 BYTES

Reason:

During the processing of a request, an attempt was made to use a key defined as greater than 180 bytes. CA Dataquery for CA Datacom only supports keys of 80 bytes or less.

Action:

Select a different key.

DQ904E

THE KEYWORD "FROM" WAS NOT FOUND IN YOUR QUERY

Reason:

Your query cannot be validated because the keyword "FROM" was not found in a "SELECT" or "DELETE" SQL statement. The correct formats for these SQL statements are:

SELECT column-names FROM table-names WHERE ...
DELETE FROM table-name WHERE ...

Action:

Correct your query statement and validate your query.

DQ905E

AN OBJECT NAME WAS NOT FOUND IN YOUR QUERY

Reason:

Your query cannot be validated because a valid object name was not found in the SQL statement in the expected location. Examples of the correct formats for SQL statements with object names indicated in lowercase are:

Action:

Correct and validate your SQL statement.

DQ906E

THE KEYWORD "INTO" WAS NOT FOUND IN YOUR INSERT STATEMENT

Reason:

Your query cannot be validated because the keyword "INTO" was not found following "INSERT" in the query statement. The correct format for this SQL statement is

INSERT INTO table-name (column-name,...) VALUES (...)

Action:

Correct your query statement and validate your query.

DQ907E

AN INCORRECT WORD FOLLOWS THE FUNCTION IN YOUR SQL STATMENT

Reason:

Your SQL statement cannot be validated because the word following the function (such as CREATE) is missing or incorrect. Examples of correct formats for some (but not all) SQL statements follow:

Note: For more information, see the CA Dataquery Reference Guide.

Action:

Correct and validate your SQL statement.

DQ908E

A SYNONYM NAME WAS NOT FOUND IN THE "CREATE SYNONYM" STATEMENT

Reason:

Your query cannot be validated because the name for a synonym was not found after the keywords "CREATE SYNONYM." The correct format for this SQL statement is:

CREATE SYNONYM synonym-name FOR table-name

Action:

Correct your query statement and validate your query.

DQ909E

THE KEYWORK "FOR" WAS NOT FOUND IN YOUR CREATE SYNONYM STATEMENT

Reason:

Your query cannot be validated because the keyword "FOR" was not found following the synonym name. The correct format for this SQL statement is:

CREATE SYNONYM synonym-name FOR table-name

Action:

Correct your query statement and validate your query.

DQ910E

THE KEYWORD "ON" WAS NOT FOUND IN YOUR COMMENT STATEMENT

Reason:

Your query cannot be validated because the keyword "ON" was not found following the word "COMMENT." The correct formats for the SQL statements are:

COMMENT ON TABLE table-name IS ...
COMMENT ON COLUMN table-name.column-name IS ...
COMMENT ON table-name (column-name IS ...)

Action:

Correct your query statement and validate your query.

DQ911E

YOUR "COMMENT ON" STATEMENT IS INCOMPLETE

Reason:

Your query cannot be validated because the keyword "TABLE" or the keyword "COLUMN," or a table name was not found following the keywords "COMMENT ON." The correct formats for these SQL statements are:

COMMENT ON TABLE table-name IS ...
COMMENT ON COLUMN table-name.column-name IS ...
COMMENT ON table-name (column-name IS ...)

Action:

Correct your query statement and validate your query.

DQ912E

A COLUMN NAME WAS NOT FOUND IN YOUR COMMENT STATEMENT

Reason:

Your query cannot be validated because a column-name was not found following the keywords "COMMENT ON COLUMN." The correct format for this SQL statement is:

COMMENT ON COLUMN table-name.column-name IS ...

Action:

Correct your query statement and validate your query.

DQ913E

A TABLE NAME QUALIFIER WAS NOT FOUND IN YOUR COMMENT STATEMENT

Reason:

Your query cannot be validated because a table-name qualifier was not found preceding the column-name in your query statement. The correct format for this SQL statement is:

COMMENT ON COLUMN table-name.column-name IS ...

Action:

Correct your query statement and validate your query.

DQ914E

YOUR SQL AUTHORIZATION ID IS TOO LONG

Reason:

Your query cannot be validated because you have used an SQL Authorization ID which is too long for CA Dataquery to process. An SQL Authorization ID for CA Dataquery cannot exceed 18 characters.

Action:

Shorten your SQL Authorization ID and validate your query.

DQ915E

THE SQL AUTHORIZATION ID YOU ENTERED IS NOT VALID

Reason:

You have entered an SQL Authorization ID which is not a valid SQL Authorization ID. Perhaps it is misspelled.

Action:

Correct the SQL Authorization ID you entered. You can use your own SQL Authorization ID or another to which you have been given access. Contact your CA Dataquery Administrator for a valid SQL Authorization ID to use.

DQ916E

THE KEYWORD "ON" WAS NOT FOUND IN YOUR GRANT OR REVOKE STATEMENT

Reason:

Your query cannot be validated because the keyword "ON" was not found in a "GRANT" or "REVOKE" SQL statement. The correct formats for these SQL statements are:

GRANT privileges ON TABLE table-name TO ...
REVOKE privileges ON TABLE table-name TO ...

Action:

Correct your query statement and validate your query.

DQ917I

RESOLVE DUPLICATE COLUMN NAMES IN ORDER BY WITH INTEGER DESIGNATIONS

Reason:

During query validation or execution, CA Dataquery detected an ORDER BY clause with duplicate field names. Field names are considered duplicates if they are the same, even though the table names are different.

Action:

This is an informational message. You can continue execution by pressing PF3 from the panel that received the message.

DQ980E

SUPPORT FOR CA-DATAQUERY NOT REQUESTED IN MULTI-USER STARTUP

Reason:

CA Dataquery cannot be used until the CA Datacom/DB Multi-User Facility has been initialized with DQ specified for the DATACOM MUF startup option. See the CA Datacom/DB Database and System Administration Guide for information on specifying the DATACOM MUF startup option.

Action:

Restart the CA Datacom/DB Multi-User Facility with DQ specified for the DATACOM MUF startup option, then rerun the CA Dataquery facility that received this message.

DQ990E through DQ999E xxxxxxxxxx

Reason:

These numbers are reserved for site-specific user-defined messages.

Action:

Contact your CA Dataquery Administrator for assistance.