Solving User Problems › Encountering Other CA Dataquery Errors

Encountering Other CA Dataquery Errors

Initial Action

Whenever a user encounters an error that is not a transaction abend, or an internal error message, attempt to determine the cause of the error with careful analysis. Collect the following information to help you with your analysis:

• Name and number of the CA Dataquery panel that was displayed with the error message.
• Name and number of the CA Dataquery panel that was displayed prior to the panel with the error message.
• Sequence of events that led up to the error message.

Query Problems

If a query or dialog was being validated, executed or submitted, collect the following information:

• Text of the query that was being validated, executed or submitted.
• User name of the user who received the error, and a list of any groups to which he is assigned.
• Any restricted conditions assigned to this user or to the user's assigned groups.
• Any defined terms or user-defined functions within the query.

With this information, you and the user should be able to solve the problems.

Items that frequently cause problems include:

• Incorrect TABLE, KEY, or FIELD entity-occurrence definitions in CA Datacom Datadictionary.
• TABLE, KEY, and FIELD entity-occurrences named the same.
• TABLE, KEY, and FIELD entity-occurrences named the same as CA Dataquery keywords.
• CA Datacom/DB tables closed and not accessible to CA Dataquery.
• Terms named the same as CA Dataquery keywords or TABLE, KEY, and FIELD entity-occurrences.