Reason:
A request has been made in CA Dataquery for an unknown error message whose number appears at the end of this message. This is a CA Dataquery system problem.
Action:
Gather together all the end-user information you have received. This information includes the error message, including the error number and the text, and what the user was attempting to do when the error occurred. Then contact contact Technical Support for CA Dataquery.
Reason:
CA Dataquery has detected an internal processing problem. This is a DATAQUERY system error. A snap dump was taken. If this error appears in CA Dataquery security for module DQAUUPR, it is probably because the PER record for the user ID was deleted.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Ask your systems programmer to print the snap dump. Explain what error message was received, including the error number and the text, and what you, or the user, were attempting to do when the error occurred.
Systems Programmer
After printing the dump, contact Technical Support for CA Dataquery.
Reason:
You have attempted to change a master key or to insert a new row with a master key that already exists.
Action:
Review your set statements with your CA Dataquery Administrator to determine which key is the "master key." Ask about the rules that have been defined for the specific master key you have attempted to use.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Review the set statements with your user and determine which key is a "master key." If you do not know what rules have been defined for the specific master key the user has attempted to change or duplicate, contact your Database Administrator. If the needs of your organization have changed, the database definition may require changing and your Database Administrator must assist you in accomplishing this.
Database Administrator
Assist your CA Dataquery Administrator in determining the proper action to take. Since database requirements may have changed, you may need to make changes to the master key structure. If changes are needed, advise your CA Dataquery Administrator when they have been completed.
Reason:
You have typed in a member name that is either unrecognizable to CA Dataquery or requires special authorization that you have not been assigned. You may have misspelled the name.
Action:
Check the appropriate directory listing for the member to verify the spelling. Either place the cursor on the desired query name and press the appropriate PF key, or, type the member name with the correct spelling. If the member name does not appear in your directory list, check with your CA Dataquery Administrator to see if you have been authorized to access that particular member.
Reason:
The command you typed on the command line is either not a CA Dataquery command or requires special authorization that you have not been assigned. The standard CA Dataquery commands are: +nnnn, -nnnn, ADmin, BOttom, CReate, DIRectory, DISplay, EDit, EXEcute, EXTract, GUide, Help, Keep, LIst, MEnu, MSg, OFF, PFn, PRofile, STats, SUbmit, TIme, and TOp. Refer to your CA Dataquery Reference Guide or to the other CA Dataquery commands that require special authorization. Commands may be abbreviated.
Action:
Check the spelling of the command you want to use and retype it. If the spelling is correct, check with your CA Dataquery Administrator to see if you have been authorized to perform the requested function.
Reason:
A serious internal storage error has occurred during CA Dataquery processing. This error occurs when the defined record/field sizes for Datadictionary are not the same as the record/field sizes in the CA Datacom/DB CXX. During query validation, the size of the file defined to Datadictionary is checked against the BUFSIZE parameter in the System Option Table and is rejected if the file size exceeds this parameter. However, if it passes this validation and the query is subsequently executed, if the actual file size in the CXX exceeds the BUFSIZE parameter, the file will fill the buffer and could actually overlay data and/or instructions, causing a storage violation.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator and ask that the Datadictionary and CXX definitions be synchronized.
Database Administrator
Synchronize the Datadictionary and CXX definitions by running the "DDCFBLD" Utility. See your CA Datacom Datadictionary Batch Reference Guide for further information.
Reason:
The query name you entered is not correct. Query names cannot be longer than 15 characters, and cannot contain embedded blanks.
Action:
Verify that the query name is not longer than 15 characters and contains no embedded blanks. Look at the Directory of Queries to check the spelling. Then, either place the cursor on the desired query name and press the appropriate PF key, or reenter the command using the correct spelling for the query name.
Reason:
There is another member in the library with the same name. There cannot be two members in the library with the same name.
Action:
If you want to update the existing member, use the UPDATE PF key. Otherwise, change the name of the member in the Active Area and SAVE it.
Reason:
Your site has elected to obtain user IDs from an external security package. Your user ID obtained from external security is unknown to CA Dataquery.
Action:
Contact your CA Dataquery Administrator to have your user ID validated for CA Dataquery.
Reason:
You cannot delete or replace a PUBLIC member, or one that belongs to another user.
Action:
If the member has been saved in the public library, only your CA Dataquery Administrator can delete or replace it if the libraries have been partitioned at your site.
If you want to save the member in the Active Area, change the member name and SAVE it.
If you want to delete the member and it has been saved in a private library, contact the owner of the member and have that user delete it. If you do not know who owns the member, see your CA Dataquery Administrator.
Reason:
CA Dataquery has recognized the use of a dialog symbol in the text of this member and the member type is not DIALOG or PROC. The use of a dialog symbol in the text of CA Dataquery members is reserved for identifying variables in DIALOGS or PROCS.
Action:
Remove the dialog symbols or change the member type to be compatible with the presence of variables.
Reason:
You have attempted to use a saved set or to edit, execute, or submit an Active Query when there is no query in the Active Query Area. Or, you have issued an EXTRACT command and there is no PRINT or DISPLAY statement in the Active Query Area.
Action:
Activate a query by using the Directory of Queries panel: place the cursor on the desired query name and press an appropriate PF key. You may also type "EDIT queryname," "EXEC queryname," or "SUBMIT queryname" on the command line. Queryname is the name of the desired query. Another alternative is to use the EXECUTE or SUBMIT panel for online or batch execution.
If you want to use a Saved Set for the selected query, the query must be validated prior to selecting the Saved Set to USE.
Reason:
You have attempted to print the request table before it is available.
Action:
Move your request below the EXEC statement. DIAGNOSTICS=RQT is only valid in SIGN/ON mode for DQBATCH.
Reason:
Your site has elected to use external security for CA Dataquery. You have requested a function for which you have not been authorized by external security. The function is displayed in the error message.
Action:
Contact your CA Dataquery Administrator to have your user ID validated for the function you have requested.
Reason:
You named a table in a SORT, PRINT, or DISPLAY statement that did not appear in your FIND statement. Therefore, information from that table was not retrieved and cannot be used in the SORT, PRINT, or DISPLAY statement as requested.
Action:
Include the table named in the SORT, PRINT, or DISPLAY statement in your FIND statement and execute the query again.
Reason:
No internal space in the CA Dataquery work table is available. CA Dataquery is unable to process your request at this time. There are currently too many active CA Dataquery requests.
Action:
Try your request again later when the system is not as busy. If this is a frequent occurrence on your system, contact your CA Dataquery Administrator and describe the error message, including the text and message number. Your CA Dataquery Administrator can increase the size of the work table.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator. If the error occurred online, ask that the CA Dataquery Found Table (DQF) be enlarged. If the error occurred in batch, ask that the CA Dataquery Work Table (DQW) be enlarged.
Database Administrator
Enlarge the CA Dataquery Found Table (DQF) or the CA Dataquery Work Table (DQW) by enlarging the area using the standard CA Datacom/DB method and then null loading and initializing the table with DQWFINIT. If you have enlarged the CA Dataquery Found Table (DQF), you must also null load the CA Dataquery Spool Table (DQS) also.
Reason:
CA Datacom/DB has encountered a problem. Your request could not be completed. The information, following the words "DB RETURN" relates to the CA Datacom/DB error. The format is:
DB RETURN XX YYY CCCCCFFFKKKKK
where XX is the DB return code, YYY is the Subcode, and CCCCCFFFKKKKK is the DB Request Area.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator and describe the error, including the error message number and text and the "DB RETURN" information provided at the end of the error message.
Database Administrator
Determine the table on which the error occurred by extracting the value for FFF in the DB Request Area shown at the end of the error message. Look up the error in the CA Datacom/DB Message Reference Guide by using the return code and subcode presented at the end of the error message. Take the appropriate action, as specified, for the CA Datacom/DB error.
Reason:
No internal space in the CA Dataquery DQE work table is available. CA Dataquery is unable to process your request at this time. There are currently too many active CA Dataquery requests.
Action:
Try your request again later when the system is not as busy. If this is a frequent occurrence on your system, contact your CA Dataquery Administrator and describe the error message, including the text and message number. Your CA Dataquery Administrator can increase the size of the work table.
Reason:
You have attempted to execute a SET, SORT, DISPLAY, or PRINT statement and there is no active found set. You must execute either a FIND statement or a USE command prior to issuing one of the above statements.
Action:
Either issue a query with a FIND statement, or look at the Directory of Saved Sets, place your cursor on the desired set, and press PF4.
Note: This message is also displayed for a batch export in which no rows were found.
Reason:
No internal space in the CA Dataquery work table is available. CA Dataquery is unable to process your request at this time. There are currently too many active CA Dataquery requests.
Action:
Try your request later when the system is not as busy. If this error occurs frequently on your system, contact your CA Dataquery Administrator and describe the error message, including the text and message number. Your CA Dataquery Administrator can consider increasing the size of the work table.
Reason:
Your report has terminated because it exceeds the maximum number of pages allowable at your site. The limit was set at CA Dataquery installation by the PRTCTL parameter in the System Option table.
Action:
If possible, shorten the size of your report by suppressing the detail print, or by reducing the number of found rows. If neither of these alternatives is satisfactory, see your CA Dataquery Administrator about increasing the size of the PRTCTL parameter.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator and ask that the PRTCTL parameter be increased.
Database Administrator
Increase the PRTCTL parameter contained in the System Option Table and reassemble it. The PRTCTL parameter specifies the maximum number of pages a user may print on a system printer. It can be any amount from 1 to 999. The default is 10. See the CA Dataquery Administrator Guide for further information.
Reason:
A request for a LIST format display continues for more than one panel. The order in which the columns have been requested cause one of the columns to be split between panels. This is not allowed.
Action:
Change the order of the columns that have been requested in the display command and try executing the query again.
Reason:
The total length of all sort columns exceeds the maximum allowable length of 100 characters.
Action:
Remove sort columns until the combined length of the requested sort columns no longer exceeds 100 characters.
Reason:
There is an invalid or missing word in the EXECUTE statement.
Action:
Check the syntax of the EXECUTE statement, make the appropriate corrections, and retry the command.
Valid execute statements are:
where:
Reason:
You requested that the output report from your query be sent to a printer that is not in service.
Action:
Either wait until the printer is back in service or direct your output to another printer.
Reason:
There is no active found set, or the query in the active query area does not contain a DQL FIND statement, so a table cannot be created.
Action:
Execute a DQL query which finds some rows and prints the result. Then, retry the STORE command.
Reason:
You have named a key in the PRINT/DISPLAY statement, or you have named a column with an invalid type or length, which cannot be used by the STORE command. Valid types are character, binary halfword, binary fullword, long floating point. Packed and zoned decimal types with no more than 15 digits are also valid. No key names may be used.
Action:
Correct the PRINT/DISPLAY statement in your query, naming only valid columns, then retry the STORE command.
Reason:
You requested CA Dataquery to STORE data on a new table, but the active query did not contain a PRINT or DISPLAY statement. The rows for the new table are determined by the columns listed in the PRINT or DISPLAY statement of the active query.
Action:
Add a PRINT or DISPLAY statement to the query and execute it again. Then, you can perform the STORE, using the Active Found Set.
Reason:
Your query cannot be validated because the user validation exit at your site has rejected it. The return code issued by the user validation exit is shown in the message.
Action:
Contact your CA Dataquery Administrator with a copy of your query and the return code to obtain an explanation for the query error.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator to obtain information about the validation exits being used at your site.
Database Administrator
Provide your CA Dataquery Administrator with the necessary information about your site's validation exits and the return codes generated. Your systems programmer should be able to provide any specific details you require.
Systems Programmer
Provide information to your Database Administrator about the VALEXIT System Option Table Parameter and the module being used for the exit. Include specific information about the return codes being generated and the additional validations being made.
Reason:
You have not executed either a FIND in a query, or requested that a previously saved found set be activated by executing the USE function.
Action:
Execute a query with a FIND verb or activate the desired saved set, after selecting the SETS function from the Administrative Menu, by pressing PF4 while the cursor is on the desired saved set name.
Reason:
You are attempting to save a found set but the name you assigned it is not unique. There is another saved set on the Found Table (DQF) with the same name.
Action:
Change the name for the new saved set. Or, delete the existing saved set and then save the new set.
Reason:
Your found set cannot be saved because you have exceeded the maximum number of saved sets you are allowed. This limit is set by the MXSETS parameter in the CA Dataquery System Option Table. (The default is 5 sets.)
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator about increasing the MXSETS parameter in the System Option Table.
Database Administrator
Increase the MXSETS parameter and reassemble the System Option Table. MXSETS may be a value from 1 to 999 with a default of 5. Consider increasing the size of the Found File (DQF) to accommodate the higher MXSETS value.
Reason:
The Saved Set you selected for deletion was not found, so your request could not be processed.
Action:
Check the directory of saved sets to see if this member appears on the list. If it does, contact your CA Dataquery Administrator to report the problem. Include information such as the error number, the error message and the name of the saved set you are trying to delete.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Check the Directory of Saved Sets to verify that the Set is listed in the directory but not contained on the DQF. If this is the case, an internal inconsistency has occurred. Contact your systems programmer to reinitialize the Found Table (DQF) and the Spool Table (DQS).
Systems Programmer
Reinitialize the Found Table (DQF) and the Spool Table (DQS) using the DQWFINIT Utility. If this particular problem occurs frequently, call CA Technical Support for CA Dataquery to report the problem.
Reason:
The person entity for the selected user was not found on the Datadictionary. The person entity is required for Dataquery security functions, and must be in either PROD or TEST status with version number 001. It may have been deleted or may be present with the wrong status and version.
Action:
Contact the CA Dataquery Administrator to see if the person entity has been deleted from the Datadictionary or is not in PROD or TEST status, version 001. The person entity must be returned to the Datadictionary with the proper status and version before Dataquery security maintenance can be performed.
Reason:
Database ID nnn was not found on the Datadictionary.
Action:
Contact the Datadictionary Database Administrator to make certain that the database ID has been defined to Datadictionary.
Reason:
You requested that your query output be printed at a network printer, but the network printer ID you supplied is unknown to CA Dataquery.
Action:
Check the spelling of the Network Printer ID you want to use, and if incorrect, retype it. If the spelling is correct, check with your CA Dataquery Administrator for a list of network printer IDs that you can use to print your query results.
Reason:
The output data you have requested to be extracted will not fit in the CA Dataquery Found Table (DQF).
Action:
Reduce the size of your output by further qualifying your FIND statement. If this is not a practical solution, contact your CA Dataquery Administrator about the system option table parameter (XTRBLKS) which determines the maximum size of your extract output. (The default is 20 blocks.)
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator about increasing the XTRBLKS parameter in the System Option Table.
Database Administrator
Increase the XTRBLKS parameter in the System Option Table. This parameter determines the number of physical blocks that a single EXTRACT request can allocate at one time on the Found Table (DQF). This parameter can be a value from 1 to 9999 and the default is 20. After you change the value of this parameter, reassemble the System Option Table.
Reason:
An internal error occurred while CA Dataquery was processing your SUBMIT or PRINT OFFLINE request. This is a system error.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your systems programmer and describe the error you or your user received. Make sure you provide the return code that appears at the end of the message list. No SUBMIT or PRINT OFFLINE requests can be honored until the situation is resolved.
Systems Programmer
A SUBMIT or PRINT OFFLINE command cannot be used at this time.
If the return code is 36, either the Internal Reader data set has not been opened, or it is not defined in the appropriate control table. The control table to use depends on which monitor is being used. Refer to your VPE documentation for information about the internal reader.
If the return code is 40, a permanent I/O error has occurred while writing to the internal reader data set. Retry the SUBMIT or PRINT OFFLINE command. If the problem persists, contact Technical Support for CA Dataquery after gathering all information.
If the return code is 44, a return code which cannot be recognized has been received from your monitor while it was attempting to write to the internal reader data set. Gather all information and contact Technical Support for CA Dataquery.
Reason:
CA Dataquery has encountered errors during the execution of your request for update. The request has been canceled.
Action:
Review your SET statements. The columns you used in your calculations may contain non-numeric data. You may have attempted to divide by zero. The calculation may be too large for CA Dataquery to process, that is, a calculation cannot exceed a total of 18 digits. Correct the SET statement and try to execute the query again.
Reason:
The update/erase you requested has completed. One or more of the records in the found set could not be updated because of bad data in the record retrieved. This is probably due to invalid data in a numeric field.
Action:
None is required. To determine which records were not updated, you should execute a FIND query with the same selection criteria as the update/erase query and display the data rows retrieved. The rows with invalid data cannot be updated using CA Dataquery.
Reason:
The system does not have enough storage at this time to produce your report.
Action:
Follow the directions for your job responsibilities.
CA Dataquery Administrator
Contact your systems programmer and describe the error you received that indicates that CICS needs more storage.
Systems Programmer
Increase the storage for the region, or partition, in which CICS is running.
DB Return Code = SQL Return Code = Command =
Error Program = Error Diagnostic =
Reason:
CA Dataquery has encountered an unexpected error when processing an SQL statement. The return codes and diagnostic information supplied by the database are displayed after you press PF1.
Action:
Contact your CA Dataquery Administrator and describe the error message, including the text, message number and diagnostic information displayed above, and what you were doing when the error occurred.
CA Dataquery Administrator
See the CA Datacom/DB Message Reference Guide for an explanation of the return codes.
Reason:
One or more input fields has been determined to contain an error. The fields are highlighted. Column names must begin with a letter, followed by zero or more letters, digits, or underscores. Valid data types are DECIMAL, NUMERIC, INTEGER, SMALLINT, FLOAT, and CHARACTER. If the data type is SMALLINT, the range is -32767 to 32767. The range for INTEGER IS -2147483648 to 2147483647. The range for FLOAT is 5.4E-79 to 7.2E+75. Maximum precision for a decimal or numeric column is 15 digits, and its scale must be less than or equal to its precision. Values must correspond to type and length of column. For row maintenance, both a comparison operator and a value must be entered to use a column in selection criteria.
Action:
Correct the highlighted entries and try the function again.
Reason:
The table you defined with the Personal Database Create Table Panel has been added to your personal database. You may now use the data entry feature to add data items to this table.
Action:
None is required.
Reason:
You must supply a correct name for the new table you want to add to your personal database. The name must be a letter followed by zero or more characters, each of which may be a letter, a digit, or the underscore character.
Action:
Correct the table name and add the table again.
Reason:
You have not been authorized by your CA Dataquery Administrator to use the SQL Data Definition Commands: CREATE, COMMENT, or DROP.
Action:
See your CA Dataquery Administrator to obtain proper authorization if you must use one or more of these commands.
Reason:
You have not been authorized by your CA Dataquery Administrator to use the SQL Data Maintenance commands: UPDATE, INSERT, or DELETE.
Action:
See your CA Dataquery Administrator to obtain proper authorization if you must use one or more of these commands.
Reason:
The first word in your SQL query is not a valid SQL command you can use in CA Dataquery. The valid SQL commands are: COMMENT, CREATE, DELETE, DROP, INSERT, SELECT, UPDATE.
Action:
Correct your query and retry query validation.
|
Copyright © 2014 CA.
All rights reserved.
|
|