Solving User Problems

As the CA Dataquery Administrator, you need to know what to do when user problems occur, both for online and batch CA Dataquery.

It is your responsibility to:

Identify the source of the user's problem. For example, did the user specify the correct JCL member when he executed the batch job?
Help the user to resolve his problem wherever possible. For example, direct the user to the proper section in the CA Dataquery end-user documentation.
Be aware of your site standards and their impact on the user. For example, if your site uses CA Top Secret, CA ACF2, or another security package, it can impact your site's CA Dataquery signon procedures.
Interface with the Security Administrator, Systems Programmer, and Database Administrator when appropriate. For example, a user cannot save his found sets because there is insufficient storage available in the Found Table and he cannot delete any saved found sets, so you need to request more blocks of storage.
Interface with CA Support whenever a user encounters an internal error, or you are unable to resolve the user's problem.

User Exits

There are user exits that your site can elect to use.

Batch Line Printer Exit
Batch Submit Exit
Network Printer Exit
Query Validation Exit
Database ID Exit
Signon/off Exit Batch
Signon/off Exit Online
User-Defined Functions Exit
Output Exit - Online
Output Exit - Batch

If your site has made use of any of these exits, make sure that you are familiar with them and that they are executing properly and issuing the expected return codes to CA Dataquery. Your Systems Programmer can provide you with more information about the user exits in use at your site.

The CA Dataquery HELP function <PF1> can assist users in answering many problems that they encounter while using CA Dataquery. However, there can be problems that arise that only the CA Dataquery Administrator has the authority or access to the particular functions to solve.