Reason:
The PF3 Continue key was pressed on the variable definition panel for the last variable in the text, and the definition is complete.
Action:
Submit the PROC to test all variables.
Reason:
The DIALOG or PROC definition is not complete. You have pressed PF3 on the DIALOG variable definition panel for the last variable to continue, but the DIALOG or PROC has not been completely defined or saved. For example, a variable in the text may not have a Prompt or Type saved for it.
Action:
Use the SCROLL FORWARD and SCROLL BACKWARD PF keys to scroll through the variables. An error message will be displayed for any variable that is in error. Correct any errors. Save the corrected variables, and after the last variable is displayed, press the Continue PF key to return to Editor where the DIALOG may be validated.
Reason:
The condition named in the message has not been defined. Therefore, the Restriction member cannot be saved.
Action:
Use the CONDITIONS option from the Administrative Menu, or type CONDITION on the command line to activate the Condition Editor. Define the condition you want to include in your Restriction. Then you can return to the Restriction Editor and add the new Condition to your Restriction.
Reason:
The user you requested to be deleted has been removed.
Action:
None is required.
Reason:
You have attempted to save a PUBLIC DIALOG. Dataquery does not allow a public dialog to be saved. It must first be saved as PRIVATE, have the DIALOG variables completely defined, be validated, and then be UPDATED to PUBLIC.
Action:
Save the DIALOG as PRIVATE until all the DIALOG variables have been defined, and then UPDATE the status to PUBLIC.
Reason:
You have not saved (or updated) the JCL PROC TEXT on the library. This must be done before defining the PROC variables.
Action:
Save or update the JCL PROC TEXT. After that you may define the PROC variables.
Reason:
Your user name is too long to be substituted for the string, #DQOPERATORNAME, in the JCL member you are using.
Action:
Have your CA Dataquery Administrator modify your JCL so that your user name can be substituted in the JCL in place of #DQOPERATORNAME without causing the line to extend past column 71.
Reason:
Your save request for the variable you changed to a numeric type failed because the variable was previously defined with a list. The list definition must be deleted before this change can be made.
Action:
Either request the list definition panel for the variable you want to change, delete the list, and then save the variable, or, change the variable type back to what it was before.
Reason:
Your request to save or update a member on the library was not completed because the CA Dataquery Library (DQQ) is full.
Action:
Contact your CA Dataquery Administrator to see if the library can be enlarged, or if obsolete members can be deleted from the library.
Follow the directions below depending on your job responsibilities:
CA Dataquery Administrator
Look through the CA Dataquery Library (DQQ) for obsolete members that may be deleted. The Last Used Date may be helpful in identifying library members that might be obsolete. If you are unable to remove a sufficient number of members, you can contact your systems programmer and ask that the file be enlarged.
Systems Programmer
Enlarge the CA Dataquery Library (DQQ). See the CA Dataquery Administrator Guide for further information.
Reason:
Your request to display a condition name that appears on the restriction edit panel cannot be completed because CA Dataquery cannot find a condition with that name.
Since it is not possible to create a new restriction member containing condition names that do not exist, the condition name you requested has probably been deleted from the Directory of Conditions panel, and this restriction member was never updated to remove the reference to the deleted condition.
Action:
Either create a new condition using the name you originally selected or delete that condition name from the restriction member.
Reason:
Your request to save a new user on the user table was not completed because the CA Dataquery User Table (DQU) is full.
Action:
Contact your CA Dataquery Administrator to see if the table can be enlarged, or if obsolete members can be deleted from the table.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
If possible, delete obsolete users from the table. If this cannot be done, or if there is still insufficient space, contact your Database Administrator and request that the CA Dataquery User Table (DQU) be enlarged.
Database Administrator
Backup the CA Dataquery User Table (DQU) with "DBUTLTY," allocate a larger area for the table, initialize the expanded table with "DBUTLTY," and load the table using "DBUTLTY" and the backup you created before enlarging the table.
Reason:
You issued an EXTRACT command to save your found set. This has been done as requested. You can now find your extracted file listed on the directory of saved sets.
Action:
None is required. The EXTRACTED set can now be used by systems and programs outside CA Dataquery.
Reason:
The new user name contains characters that are not allowed by Datadictionary, and, therefore, are not allowed by CA Dataquery. Allowable characters are:
Action:
Remove the invalid special characters from your user name.
Reason:
One or more values entered in the list of valid values for a DIALOG variable begins with a blank or underscore.
Action:
Scroll the list of values, correct all values that begin with a blank or underscore, and save the list again.
Reason:
A CA Dataquery system administrator may change either the author or the status of a query library member, but both attributes may not be changed in the same transaction.
Action:
If both attributes are to be changed, it must be completed with two transactions. Restore the status to its original value, leave the author name changed, and press the Update PF key. Finally, change the status and press the Update PF key.
Reason:
The text for the member you requested is too long for the Active Query Area. The member was created when the "QPAGES" parameter in the System Option Table was larger than it is now. The member cannot be retrieved until the query area is large enough to hold it.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator and ask that the QPAGES parameter in the System Option Table be increased at least to its previous level, so that you can retrieve the member. This parameter determines the maximum size of any member.
Database Administrator
Increase the QPAGES parameter of the System Option Table. Its value can be from 1 to 4. The default is 1. Each page has 24 lines. If you are going to use the GUIDED QUERY CREATION Facility at your site, it is recommended that you specify QPAGES to be at least 2. This parameter does not affect what is stored in the Query Library. If the query uses only one page, only one page will be stored in the library. Once you have changed the value of this parameter, reassemble the System Option Table.
Reason:
You are requesting to USE a saved found set that was extracted. This type of Saved Set can be accessed only outside CA Dataquery. You may access Saved Sets that have been saved by the KEEP command.
Action:
If you are viewing the Directory of Sets, the TYPE column indicates whether the set was saved by using KEEP (K) or EXTRACT (E). If the original found set is still active, issue the KEEP command to save it so it can be accessed by CA Dataquery later. If the Saved Set is not active, you must execute the query again. Then issue the KEEP command to save it.
Reason:
A variable default value has a beginning quote but there is no corresponding ending quote. A variable can be only 77 characters long.
Action:
Supply a default value that has either a pair of quotation marks, one at the beginning and one at the end, or no quotation marks.
Reason:
You have returned to a previous process while using the Guided Query Creation Facility. Your previous work on the query will be displayed, but it will not be carried forward unless you look at every display that shows your previous selections. For example, if you were on the panel for selecting sort columns and had previously selected several columns from different pages of a column list, you must view each page containing a selection before continuing.
Action:
Review all selections you previously made so that they will be carried forward.
Reason:
You requested a list of available columns but no columns are available for your use.
Action:
Contact your CA Dataquery Administrator to determine if the table definition is correct in Datadictionary.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator to determine what has caused this situation.
Database Administrator
Determine whether the problem has been caused by faulty Datadictionary definitions or if the user was denied access to all columns in the table. If the latter is the case, user access to the table should be removed. Work with your Datadictionary Administrator and your Security Administrator to resolve the problem.
Security Administrator
Work with the Database Administrator to determine if there are problems with profile codes or if the user should have table accessibility.
Datadictionary Administrator
Work with your Database Administrator to determine if there are Datadictionary definition problems. Make any changes necessary to rectify the situation.
Reason:
You requested a list of available columns and keys but none are available for your use.
Action:
Contact your CA Dataquery Administrator to determine if the table definition is correct in Datadictionary.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator to determine what has caused this situation.
Database Administrator
Determine whether the problem has been caused by faulty Datadictionary definitions or if the user was denied access to all columns in the table. If the latter is the case, user access to the table should be removed. Work with your Datadictionary Administrator and your Security Administrator to resolve the problem.
Security Administrator
Work with the Database Administrator to determine if there are problems with profile codes or if the user should have table accessibility.
Datadictionary Administrator
Work with your Database Administrator to determine if there are Datadictionary definition problems. Make any changes necessary to rectify the situation.
Reason:
You requested a list of available keys but none are available for your use.
Action:
Contact your CA Dataquery Administrator to determine if the table definition is correct in Datadictionary.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator to determine what has caused this situation.
Database Administrator
Determine whether the problem has been caused by faulty Datadictionary definitions or if the user was denied access to all columns and keys in the table. If the latter is the case, user access to the table should be removed. Work with your Datadictionary Administrator and your Security Administrator to resolve the problem.
Security Administrator
Work with the Database Administrator to determine if there are problems with profile codes or if the user should have table accessibility.
Datadictionary Administrator
Work with your Database Administrator to determine if there are Datadictionary definition problems. Make any changes necessary to rectify the situation.
Reason:
You requested that dumps be turned on or off at this network printer or terminal ID, but the ID you supplied is unknown to CA Dataquery.
Action:
Check the spelling of your chosen Network Printer or terminal ID, and if incorrect, retype it. If the spelling is correct, check with your CA Dataquery Administrator for a list of network printer or terminal IDs that are available for a dump.
Reason:
The CBS Diagnostics Facility has been activated successfully. The diagnostic information will be written to the DB PXX area.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
When you deactivate the CBS Diagnostic Facility, request that your Database Administrator print the PXX where your diagnostic information will be stored.
Database Administrator
When requested, print the PXX using DBUTLTY and assist your CA Dataquery Administrator in interpreting the diagnostic information.
Reason:
Your request to deactivate the Diagnostics Facility has been processed successfully. Any diagnostics produced during the activation of the Diagnostics Facility were written to the DB PXX area.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Request that your Database Administrator print the PXX where your diagnostic information was stored.
Database Administrator
Print the PXX using DBUTLTY and assist your CA Dataquery Administrator in interpreting the diagnostic information.
Reason:
You previously defined one or more join conditions to establish the relationship between the two tables you selected. You are now creating the final WHERE clause for your query. The WHERE clause combines all join conditions and all search conditions. If two tables are selected, and no join condition is specified, each row in the first table will be returned to you once in combination with each row from the second table. For example: if table A has ten rows, and table B has ten rows, one hundred rows will be returned to you.
Action:
Use at least one join condition identifier (of the form "F01") in the statement you write. See panel help for more information.
Reason:
After successfully defining a join condition for the two tables you selected in Guided Query Creation, you depressed the <PF3> key while viewing the Join Condition: Define Relation panel. This is a request to define another join condition. You can define up to ten join conditions using Guided Query Creation.
Action:
You can use the displayed panel to define another join condition, or press <PF2> to review the join condition just completed.
Reason:
After successfully defining an expression to be included as a column in the output row, you depressed the <PF3> key while viewing the Define Expression: Write Statement panel. This is a request to define another expression. You can define up to ten expressions using Guided Query Creation.
Action:
You can use the displayed panel to define another expression, or press <PF2> to review the expression just completed.
Reason:
You selected a page break for a sort column without selecting a control break for the same column. Page breaks will not be processed unless both options are selected.
Action:
Use the displayed panel to select a control break and a page break for any columns you want to use for page breaks.
Reason:
You requested that the first table be related to the second table. You must choose a column from the first table and a column from the second table to relate rows from the two tables. Rows from the two tables are related when the value of a common column is the same in both rows.
Action:
Make a selection by typing any character over the underscore in the SELECT column next to the column name of your choice. You can then continue with Guided Query Creation. You can view the column definition by using the extended column key (PF5).
Reason:
You requested that the number of rows returned to you be limited by search conditions. You have selected a column to be used as the subject of a compare. A comparison operator (for example: equal, not equal, greater than, and so forth) and a search string are required in order to complete the search condition.
Action:
Make a selection by typing any character over the underscore next to the comparison operator that defines the relation between the column you selected and the search string that you key in at the bottom of the panel. You can then continue with Guided Query Creation by pressing <PF4>. You can view the extended column definition by pressing <PF5>.
Reason:
You requested that the number of rows returned to you be limited by search conditions. You selected a column to be used as the subject of the compare and a comparison operator to define the relationship. A search string or column name used as the object of the comparison is required to complete the search condition. A space is provided at the bottom of the panel for you to enter a comparison string or column. A character string must be enclosed in single quotes ('), but a numeric value may be entered without quotes. A column name is entered without quotes.
Action:
Enter a comparison string or a column name. You can then continue with Guided Query Creation by pressing <PF4>. If you wanth, you can view extended column definitions by pressing <PF5>.
Reason:
You typed a non-numeric value in a field that requires a number.
Action:
Type a number in the field indicated by the cursor. You may then continue with Guided Query Creation by pressing <PF4>.
Reason:
Due to the complexity of your query, you have reached the limits of internal storage available for use in processing your query. For this reason, as you continue to define your query using Guided Query Creation, you may not be able to make use of all documented features. The query you are defining will be a valid, executable query; you will, however, have fewer options available to you as you continue in its definition.
Action:
Press <PF4> to continue definition, or press <PF2> to back up and simplify your query definition by removing some of the options you selected previously.
Reason:
You have selected more than one table in Guided Query Creation for use as either your primary or your secondary table. Only one primary table can be joined, or related, to one secondary table when using Guided Mode. A secondary table selection is not required.
Action:
Make only one selection for primary table. If you want to select a secondary table, make only one selection. Press <PF4> to continue in Guided Query Creation.
Reason:
Your report output can be in either columnar format (one output row per line) or list format (one output row per page). You must select one, but not both, of these options.
Action:
Select either columnar format or list format by placing any non-blank character next to your selection. Press <PF4> to continue in Guided Query Creation.
Reason:
You have defined at least one column function for your output. In Guided Query creation, if any column functions are defined, you must define at least one column function for any expressions that you have defined. One or more expressions in your output do not have column functions defined.
Action:
Scroll through your output column definitions. Define a column function for each expression that is displayed by placing any non-blank character in one of the fields to the right of the expression. Press <PF4> to continue in Guided Query creation.
Reason:
More than one option under Preparation Time or Execution Time or Optimization Mode has been chosen.
Action:
Choose only one option under each group of options.
Reason:
The Plan Optimization Options have been updated to reflect the changes that were made. These Plan Optimization Options will be in effect for each SQL query executed during this session. These options are reset to their defaults when you sign on or may be reset during the session.
Action:
None is required. You can continue to update the Plan Optimization Options, or you can use the PF2 key to return to the previous panel.
Reason:
The Plan Optimization messages have been deleted.
Action:
None is required. You can continue to update the Plan Optimization Options, or you can use the PF2 key to return to the previous panel.
Reason:
To view Plan Optimization Messages for an SQL query, the query must be executed after one or more of the Plan Optimization Options have been set. The Plan Optimization Options are only active for the session in which they were set, they revert to their default values when the session is ended.
Action:
None is required. You can update the Plan Optimization Options from this panel, or you can use the PF2 key to return to the previous panel.
Reason:
The user for which you want to add database or table privileges cannot be found on the CA Dataquery User Table.
Action:
Check the spelling of the user name you entered. If you misspelled it, correct the name. If the user name is spelled correctly, contact your CA Dataquery Administrator. Describe the error message you have received, including the error number and text, and what you were attempting to do when this error occurred.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator for assistance. There may be a problem with the User Table.
Database Administrator
Research and correct the problem with the CA Dataquery User Table. Most likely the index has become corrupted.
Reason:
The value you entered for a privilege was not Y (YES) or N (NO). All privileges must have a value of either Y (YES) or N (NO). One of the privileges has an incorrect value.
Action:
Enter the value Y (YES) or N (NO) for each privilege.
Reason:
Your request to remove a profile code privilege for a specified user has completed successfully. The user will no longer be able to access or update the columns to which this profile code is attached.
Action:
None is required.
Reason:
The user you selected for processing cannot be found. This is a CA Dataquery system error.
Action:
Contact your CA Dataquery Administrator. Describe the error message you have received, including the error number and text, and what you were attempting to do when this error occurred.
Reason:
There is no internal space in the Datadictionary table (that holds CA Dataquery security information) available at this time. CA Dataquery security is unable to process your request at this time.
Action:
Contact your CA Dataquery Administrator and describe the error message, including the text and message number. Your CA Dataquery Administrator will have to determine the Datadictionary table that is full and enlarge it. Possibilities include REL, PER, or ATZ.
Reason:
Your request to change a user's profile code privileges has completed successfully. The user will now have only the designated access to the columns to which this profile code is attached.
Action:
None is required.
Reason:
Your request to assign a profile code privilege to a particular user has completed successfully. The user will now be able to access or update the columns to which this profile code is attached.
Action:
None is required.
Reason:
Your request that a user be given specific access privileges to an entire database or to only one table has completed successfully. The specified user will be able to access the particular database or single table only as you have specified.
Action:
None is required.
Reason:
Your request to modify a user's access privileges to an entire database or to only one table has completed successfully. The specified user will be able to access the particular database or single table only as you have specified.
Action:
None is required.
Reason:
The value you entered for the CA Datacom/DB database identifier is not numeric, or is all zeros. The value cannot be all zeros.
Action:
Enter a three-digit number greater than zero for the CA Datacom/DB database identifier.
Reason:
The value you entered for the CA Datacom/DB table name does not begin with an alphabetic character, or has a leading, embedded, or trailing blank, or the last two characters are XX.
Action:
Enter a three-character value for the CA Datacom/DB table name. It must begin with an alphabetic character. It must not have a leading, embedded, or trailing blank. The last two characters must not be XX.
Reason:
Your request to delete all security privileges including both database and table privileges as well as profile code privileges has completed successfully. Unless "DATA AUTHORIZED," this user will not be able to access any tables or columns using CA Dataquery.
Action:
None is required.
Reason:
You attempted to give a user access privileges for an entire database or for a single table but did not select at least one privilege to grant to the user. The user must be allowed to perform at least one function: find, update, insert, or delete.
Action:
Enter a "Y" to indicate that you want to grant a specific access privilege to this user. At least one of the privileges must be a "Y."
Reason:
You attempted to add a user, but did not select at least one security privilege (find or update). The user must have at least one privilege for this profile code.
Action:
Enter a "Y" to indicate that you want to assign the appropriate privileges for this user. At least one of the privileges must be a "Y."
Reason:
Your request to delete all table and database access privileges for the specified user has completed successfully. Unless "DATA AUTHORIZED," this user will not be able to access any tables using CA Dataquery. If profile code privileges were assigned, they will remain intact.
Action:
None is required.
Reason:
Your request that all table and database access privileges be copied from one user to another has completed successfully. The target user will now be able to access the same tables and databases as the source user. If the target user already had some table and database privileges, these are still intact. The copy request simply adds the additional privileges from the source user to the privileges the target user already has.
Action:
None is required.
Reason:
You requested that all the security profile code privileges for a user be deleted. This request has been completed successfully. The user will no longer have access to any columns to which these profile codes are attached.
Action:
None is required.
Reason:
You requested that all the security profile code privileges for a user be copied to another user. This request has been completed successfully. The target user will now have access to all columns to which the copied profile codes are attached.
Action:
None is required.
Reason:
Your request that all privileges including both database and table privileges as well as profile code privileges be copied from one user to another has been completed successfully. The target user will now be able to access the same tables, databases, and columns as the source user. If the target user already had assigned privileges, these are still intact. The copy request simply adds the additional privileges from the source user to the privileges the target user already has.
Action:
None is required.
Reason:
Privileges for the specified database or single table have been deleted for the user. The user will no longer be able to access the database or table.
Action:
None is required.
Reason:
Your request to delete all table and database privileges for the user has failed. The user does not have any privileges.
Action:
If you selected the wrong user, place the cursor on the desired user name, and press the appropriate PF key.
Reason:
Your request to copy all table and database privileges from one user to another has failed. The source user does not have any privileges.
Action:
If you have selected the wrong source user, return to the Security User Directory panel, select the desired user by placing the cursor on the user name and press the Copy Security PF key.
Reason:
Your request to delete all profile code privileges for the user has failed. This user does not have any assigned profile code privileges.
Action:
If you have selected the wrong user, place the cursor on the desired user name, and press the appropriate PF key.
Reason:
Your request to copy all profile code privileges from one user to another failed. The source user does not have any profile code privileges.
Action:
If you have selected the wrong source user, return to the Security User Directory panel, select the desired user by placing the cursor on the user name, and press the Copy Security PF key.
Reason:
The password was deleted as you requested. On subsequent signons to CA Dataquery., no password will be required.
Action:
None is required.
Reason:
The password was updated as you requested. On subsequent signons to CA Dataquery., the new password will be required.
Action:
None is required.
Reason:
The password was added as you requested. On subsequent signons to CA Dataquery., this password will be required.
Action:
None is required.
Reason:
The password cannot contain blanks.
Action:
Reenter the password without embedded blanks.
Reason:
You have attempted to blank out or erase the system or group level password. The purpose of this panel is to add or update the password.
Action:
If you want to delete the system or group level password, return to the Directory of Defined CA Dataquery Groups, place the cursor on SYSTEM or the desired group, and press <PF6> to delete the password for the system or groups.
Reason:
You attempted to add a profile code for a user, but the profile code is not in the correct format. It must be four characters long with no embedded blanks and begin with a letter or a number.
Action:
Enter a valid profile code and add the profile code again.
Reason:
You attempted to assign a decimal point character in your user profile with something other than a period "." or a comma ",". These are the only two values that may be entered here.
Action:
Enter either a period "." or a comma "," for the value of the decimal point character. You can also leave this field blank, and the default decimal point character for your site will be assigned.
Reason:
A system or group level password has been assigned by a site administrator. Therefore, you are not permitted to update your individual password until the system or group level password has been removed.
Action:
The system or group level password can be removed only by an administrator with the proper authorization. See your CA Dataquery Administrator for further information.
Reason:
You have included a variable in the text that is used more than once. This is permitted only if the default values are the same.
For example: find 1?100 company
with 2?company-name___ gt 3?'a'______
print 2?company-name___ company-number
Action:
Correct the format of the variable by either making the default value the same or by changing the variable ID of one of them. For more information, consult the USER GUIDE, USER REFERENCE, or HELP from the Main Menu.
Reason:
The cancel find function may not be used for an SQL query in the SELECT stage.
Action:
Contact your CA Dataquery Administrator for assistance in canceling the long running SQL query. If long running SQL queries appear to be a problem at your site, contact your CA Dataquery Administrator to see about changing the REQTHD parameter of the CICS Service Facility DBCVTPR macro.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator for assistance with canceling the long running SQL query or reducing the value of the REQTHD parameter of the CICS Service Facility DBCVTPR macro.
Database Administrator
You can cancel a long running SQL query in either of two ways:
You can limit the future occurrence of any long running queries (both SQL and DQL) by permanently reducing the size of the REQTHD parameter. This parameter limits the number of CA Datacom/DB requests that any logical unit of work can make. Any tasks exceeding this limitation will be abended. See your CICS Service Facility documentation for more information.
Reason:
After selection of graph type SCATTER or HISTOGRAM, the CHART OPTION PFkey was pressed from the GRAPH OPTION panel.
Action:
If you want to use CHART OPTIONS, you must select a different chart type to use in your graph.
|
Copyright © 2014 CA.
All rights reserved.
|
|