Reason:
The batch output file could not be opened for batch processing. Either the DD statement was missing, the file was not available, or the file is not in the system or you have already written to DQFIXD this run.
Action:
Determine the reason for the file error and make the appropriate correction. Retry the batch job.
Reason:
An I/O error was encountered when writing to the export batch output file (DQFIXD).
Action:
Verify that the RECORD SIZE and BLOCK SIZE are not in your JCL. If this problem continues, contact your CA Dataquery Administrator.
Reason:
The function you requested failed because there is insufficient CICS Temporary Storage. This is a system problem.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your systems programmer and ask that the temporary storage pool be increased.
Systems Programmer
Increase the temporary storage pool, if possible.
Reason:
The function you requested failed because of a Temporary Storage failure. This is a system problem.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
If this is a persistent problem, collect the information from your user about the sequence of events that lead up to the error. Contact your systems programmer about the problem.
Systems Programmer
Using the CA Dataquery Planning Guide, determine the CICS Temporary Storage requirements for your site and ensure that these are met. Increase temporary storage as required.
Reason:
You are attempting to add an input vocabulary term that already exists for this language. Duplicate terms are not permitted.
Action:
Edit the existing vocabulary term or change the one you are adding.
Reason:
You are attempting to save a query but the name you have given it is not unique. There is another query in the query library (DQQ) with the same name.
Action:
Change the name for the new query and save it. Or, use the Update PF key (PF 9).
Reason:
A query cannot be submitted for batch execution without a JCL member. You did not specify a JCL member name, and a default JCL member was not found for you.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Establish a default JCL member for the user or provide a list of JCL members to use to submit a batch CA Dataquery job. If there are no JCL members established, contact your systems programmer to help you create the necessary JCL members.
Systems Programmer
Assist the CA Dataquery Administrator in creating the necessary JCL members to submit batch CA Dataquery jobs.
Reason:
The JCL member name you typed is either not found in the CA Dataquery JCL Library, or its use requires special authorization that you have not been assigned.
Action:
Check the spelling of the JCL member name and then retype it. If the spelling is correct, check with your CA Dataquery Administrator to see if you are authorized to use it. To use a default member, leave the name blank.
Reason:
You have asked for a variable comma separated file to be created by EXPORT and you have not provided the name of the export file.
Action:
Provide a name for the export file or change to a fixed-length export file which does not require a file name.
Reason:
Your job was submitted for execution as you requested. For your information, the time it was submitted is displayed.
Action:
None is required.
Reason:
Your job has been scheduled for deferred execution as you requested. It will be scheduled to run at the time you requested. The job will not execute before the time you specified.
Action:
None is required.
Reason:
You have submitted a query for offline print. The time that the query was submitted appears at the end of the message.
Action:
None is required.
Reason:
An unrecoverable error has been detected while accessing the CA Dataquery Found Table (DQF) or, in batch, the DQW. A return code is shown at the end of the message text.
Action:
Contact your CA Dataquery Administrator and describe the error you have received, including the message number, text, and the return code that appears at the end of the text, and what you were attempting to do when you received the error.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Null load the DQF/DQS and format the DQF with DQWFINIT.
Null load the DQW and format the DQW with DQWFINIT.
If problems persist, contact Technical Support for CA Dataquery and describe the error message, the return code at the end of the message, and what was being attempted when the error occurred.
Reason:
You have attempted to execute a DIALOG which has not been successfully validated.
Action:
Edit the DIALOG with the CA Dataquery Text Editor and perform the validation.
Reason:
You have attempted to perform a maintenance function on a public query or term. Your CA Dataquery Administrator has not authorized you to do so.
Action:
To obtain maintenance authorization, contact your CA Dataquery Administrator.
Reason:
You have not entered a new value for the vocabulary term. The value must contain at least one non-blank character.
Action:
Enter a non-blank value for the vocabulary term.
Reason:
The value you entered for the vocabulary term contains blanks. This value must consist of a single, contiguous string of non-blank characters.
Action:
Enter a value for the vocabulary term that does not contain blanks. You can substitute hyphens for blanks. For example, use "ACTIVE-QUERY" instead of "ACTIVE QUERY."
Reason:
You have not entered a description for the panel. The description is displayed as part of a panel listing. It helps to identify the panel.
Action:
Enter a description of the panel in the space provided.
Reason:
You have not entered a value for the literal. The value for a literal cannot be blank.
Action:
Enter a non-blank value for the literal.
Reason:
The DIALOG being used has an error. This error is not related to the information typed in response to the variable prompts.
Action:
Edit the DIALOG and fix the problem. Save and validate the corrected DIALOG.
Reason:
You have attempted to submit a query for batch execution, but your CA Dataquery Administrator has not authorized you to do so.
Action:
You can execute the query online. Contact your CA Dataquery Administrator if you want to obtain authorization to submit queries for batch execution.
Reason:
The selected Directory does not contain any members; no directory list can be displayed.
Action:
Verify START WITH is blank and the DQ MODE is set appropriately. Try displaying a different directory set. If you know that you should have members on a particular directory, contact your CA Dataquery Administrator with the directory name and the names of the members that should be there.
Reason:
You are in the process of adding a new restriction. The panel you are viewing contains prompted fields which will be used to create the restriction.
Action:
Enter the appropriate data in the fields and press the PF4 key to save the new restriction. Use the PF1 key for panel help.
Reason:
CA Dataquery was unable to access the query request table because there is no active query that has been validated.
Action:
Validate a query first, and then you can access the request table. If the table is still unavailable, report it to your CA Dataquery Administrator.
Reason:
The dump option you entered was not 1 or 2. The dump option specifies whether you want the Transaction (1) or Module (2) Dump Facility.
Action:
In the space provided, enter either a 1 for transaction dump or a 2 for module dump.
Reason:
You did not specify which dump option you wanted when you made the request for the dump facility to be turned on or off.
Action:
Enter either a 1 for a transaction dump or a 2 for a module dump in the space provided.
Reason:
You have attempted to turn on or turn off a dump facility, but you have not specified the terminal ID. A storage dump is taken on a specific terminal, which is determined by the ID you enter.
Action:
Enter the four-character terminal ID in the appropriate space, depending on whether you are turning the Facility on or off.
Reason:
You are attempting to add a new user, but the user name entered already exists. A user name must be unique.
Action:
Choose another name for the new user. If you were intending to update an existing user's profile or authorizations, return to the Directory of Users panel, locate the user name in the listing, and choose PROFILE or UPDATE instead of ADD.
Reason:
You attempted to activate the Transaction Dump Facility, but it is already active. The dumps are written to the CICS dump data set.
Action:
None is required. Turn off the Transaction Dump Facility as soon as you are ready since dumps consume a large amount of computer resources. Contact your systems programmer to have the dumps printed.
Reason:
CA Dataquery cannot activate the Transaction Dump Facility as you requested because the Module Dump Facility is currently activated. Only one dump facility can be active at a time.
Action:
Turn off the Module Dump Facility first, then activate the Transaction Dump Facility.
Reason:
You attempted to activate the Module Dump Facility, but it is already active. The dumps are being written to the CICS dump data set.
Action:
None is required. Turn off the Module Dump Facility as soon as you are ready since dumps consume a large amount of computer resources. Contact your systems programmer to have the dumps printed.
Reason:
You have attempted to activate the Module Dump Facility, but the Transaction Dump Facility is currently active. Only one dump facility can be active at one time.
Action:
Turn off the Transaction Dump Facility first, and then activate the Module Dump Facility. Dumps are written to the CICS data set. Contact your systems programmer to have the dumps printed.
Reason:
The Transaction Dump Facility has been activated successfully. A dump will be written to the CICS dump data set at the end of each CA Dataquery transaction.
Action:
Turn off the Transaction Dump Facility as soon as possible since dumps consume a large amount of computer resources. Contact your systems programmer to have the dumps printed.
Reason:
The Module Dump Facility has been activated successfully. Dumps for the module will be written to the CICS dump data set.
Action:
Turn off the Module Dump Facility as soon as you are ready since dumps consume a large amount of computer resources. Contact your systems programmer to have the dumps printed.
Reason:
Your request to deactivate the dump facility has been processed successfully. Any dumps produced during the activation of the Dump Facility were written to the CICS Dump Data Set.
Action:
None is required. See your system programmer about getting the dumps printed.
Reason:
The value you entered for the DIALOG variable is not within the range specified when the DIALOG was defined. When a range is defined, the value for the DIALOG variable must fall within that range.
Action:
Change the value that you entered. To view the range that has been defined for the variable, place the cursor on the value and press the LIST/RANGE PF key.
Reason:
The value you entered for the DIALOG variable does not appear in the list of values specified when the DIALOG was defined. When a list is specified, a value given for the DIALOG variable must be in that list.
Action:
Change the value that you entered. To view the list that has been defined for the variable, place the cursor on the value and press the LIST/RANGE PF key. You can return a value of your choice by placing the cursor on it and pressing PF2.
Reason:
You are attempting to delete your own user definition which is not allowed. Your user definition identifies you to CA Dataquery and contains your authorizations and profile options.
Action:
Contact your CA Dataquery Administrator to delete your user definition.
Reason:
You are attempting to save a JCL member, but you are not authorized to do so. The ability to save a JCL member requires special authorization from your CA Dataquery Administrator.
Action:
If you want to submit a query for batch execution, use a JCL member that already exists. A default JCL member should be available for you, and it will be displayed on the batch query execution panel. Contact your CA Dataquery Administrator to obtain authorization to save JCL members.
Reason:
You requested query statistics with a PF key or the STATS command, but there are no query statistics available. Query statistics are available only after the execution of the Active Query.
Action:
Execute the query, and then use the STATS PF key or command.
Reason:
Your message has been saved. You can now select the users to whom you want to send this message.
Action:
Type any character over the underscore in the SELECT column next to the names of the users to whom you want to send the message. Press the PF5 key to send the message.
Reason:
Your message has been sent as you requested.
Action:
None is required.
Reason:
CA Dataquery has encountered an error while attempting to read the CA Dataquery Found Table (DQF). This is a system problem.
Action:
Contact your CA Dataquery Administrator and describe the error, including both the error number and text, and what you were attempting to do when the error occurred.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your systems programmer and ask that the Found Table (DQF) be reinitialized.
Systems Programmer
Reinitialize the CA Dataquery Found Table (DQF). Directions for this process can be found in the CA Dataquery Administrator Guide.
Reason:
Your query output cannot be written to your terminal because wrapping has been specified, and there is not enough space on your screen to display an entire row.
Action:
Contact your CA Dataquery Administrator for assistance. Ask how to specify windowing, instead of wrapping, for your report. Windowing will allow you to scroll through a long output row.
Reason:
The user to whom you attempted to send a message is not currently signed on to CA Dataquery.
Action:
You must wait until the user has signed on to CA Dataquery before you send the message.
Reason:
The name you entered is not correct. All names in CA Dataquery must begin with an alphabetic character including names of queries, terms, dialogs, conditions, restrictions, and user identifications.
Action:
If you are entering the name of a new user or a new query library member, enter a name with a letter in the first position. If you want to refer to an existing user or query library member, you can find the correct spelling by searching the appropriate directory.
Reason:
CA Dataquery could not locate a particular panel that was to be displayed on your terminal. This is a CA Dataquery system problem.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your systems programmer and describe the error message, including the panel number at the end.
Systems Programmer
Check the Panel Table (DQP) in the DQM area for the specified panel number with the language "AE." If it is not there, reload the DQM area from an installation or backup tape.
If the panel is still missing after reloading the DQM area, contact Technical Support CA Dataquery.
Reason:
After applying all the logical conditions in your query's COUNT statement, CA Dataquery could count no rows that satisfied the conditions you specified.
Action:
If this is not the result you expected, examine your query for errors in your WITH or RELATED clauses or for statements that would always evaluate false. An example of this latter type of statement would be:
WITH Field-A > 10 and Field-A < 10
Make any necessary corrections, revalidate your query, and try executing it again. See your CA Dataquery Administrator if you require further assistance.
Reason:
Your query's COUNT statement has terminated because one of the system limitations, set at CA Dataquery installation in the System Option Table or in your user definition, has been exceeded. No rows were counted before the limit was exceeded.
This message is also displayed when a FIND statement value exceeds the MAXIO limit.
Action:
Contact your CA Dataquery Administrator for assistance. Ask about your SRCHLIM, MFTIME, MAXIO, and FNDBLKS parameters. Your CA Dataquery Administrator may be able to increase these parameters for you.
Reason:
You issued a KEEP command to save the found set, but you did not specify a name for it. The name can contain up to eight characters and must begin with a letter (A-Z). The description is optional.
Action:
Enter a name for the found set in the space provided.
Reason:
Your found set cannot be saved because the Found Table (DQF) is full.
Action:
Remove any saved sets or extract files you do not need. This will make free space in the Found Table. Try saving the found set again. If this does not work, try making your FIND statement more restrictive so the number of found records is reduced, hence, reducing the space requirement of your found set. If neither of these actions is successful, contact your CA Dataquery Administrator and describe the error you received, including the message number and text, and what you were attempting to do when the error was received.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Remove any obsolete saved sets or extract files. If this does not free up enough space in the Found Table (DQF), the Found Table should be enlarged. Contact your Database Administrator and ask that the Found Table be enlarged.
Database Administrator
Allocate a larger area for the table, null load the table with "DBUTLTY," and then initialize (format) the Found Table (DQF) and Spool Table (DQS) with "DQWFINIT."
Note: Everything saved on the Found Table will be lost including Saved Sets, Active Query Area, Active Found Set, and so forth.
Reason:
You issued a KEEP command so that CA Dataquery would save your Found Set. Your Found Set has been saved as requested. You can now find it listed on the Directory of Saved Sets.
Action:
None is required.
Reason:
The literal you are translating already exists in the language you specified. You are not allowed to add a new translation for a literal that already exists. You can edit the existing literal, however.
Action:
If you want to edit the literal, return to the Directory of Literals panel, and use the EDIT PF key instead of the TRANSLATE key.
Reason:
You have entered a value for EXPORT ALLOWED that is not a Y (YES) or an N (NO). This authorization allows a user to export found sets into a comma separated format so that the data can be accessed outside CA Dataquery.
Action:
Enter either a Y (YES) or an N (NO) for EXPORT ALLOWED.
Reason:
Your request to delete the restricted condition has been successfully executed. The restricted condition has been permanently removed from the system.
Action:
None is required.
Reason:
The delete restriction request failed because of an internal error. This is most likely a system problem.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
The return code value determines the type of error that occurred.
Database Error: The 01 is followed by a DB Return Code. Contact your Database Administrator and describe the error and the DB return code that appears after the 01 return code.
User is not authorized: If desired, give the user the necessary authorization, and let the user try again.
No record found: Try again later. If the problem is not resolved, contact Technical Support CA Dataquery and describe the error, the return code, and what was being attempted when the error occurred.
GETMAIN Failed: Try again later. If this problem continues to occur, notify your systems programmer. Explain the error that was received and what was being attempted when it occurred.
Database Administrator
Using the DB return code at the end of the message, look up the error in the CA Datacom/DB Message Reference Guide and follow the instructions found there.
Systems Programmer
If requested, increase the region, or partition, size for CICS.
Reason:
You are executing a query online and the execution of your FIND statement is in progress. This step searches the tables for rows that satisfy your query.
Action:
None is required.
Reason:
A FIND statement using more than 17 tables cannot be processed. The number of tables, however, is based upon these considerations:
Complex WITH statement example:
Action:
Reduce the complexity of your FIND statement and try again.
Reason:
The system does not have enough storage to execute your FIND statement.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
If this is a persistent error, notify your systems programmer that this problem has occurred. Explain the error that was received and what was being attempted when it occurred.
Systems Programmer
Increase the region, or partition, size for CICS.
Reason:
The total number of rows found to satisfy your FIND request appears above.
Action:
None is required.
Reason:
Online: Your query's FIND statement has terminated because one of the system limitations, set at CA Dataquery installation in the System Option Table or in your User definition, has been exceeded.
Batch: The DQW space has been exceeded.
Action:
Contact your CA Dataquery Administrator for assistance. If this is an online problem, ask about your SRCHLIM, MFTIME, and FNDBLKS parameters. Your CA Dataquery Administrator may be able to increase these parameters for you. If it is a batch problem, your CA Dataquery Administrator needs to determine the appropriate resolution.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Online: Look at the Query Statistics panel to determine the parameter that was exceeded (SRCHLIM, MFTIME, or FNDBLKS). Based on this, help the user to make their selection criteria more selective. If this is not satisfactory, either increase the FNDBLKS parameter in the User record, or contact your Database Administrator to see about increasing the FNDBLKS, MFTIME, or SRCHLIM parameters.
Batch: See the person responsible for maintaining the CA Dataquery. system about enlarging the size of the DQW.
Database Administrator
Online: If requested and if system resources allow it, increase the FNDBLKS parameter in the System Option Table. This parameter determines how many logical blocks can be allocated in the work table during FIND execution. The maximum value for the FNDBLKS parameter is 9999999, the minimum is 1, and the default is 10. If MFTIME is to be increased, the maximum value is 9999999 and zero indicates that there is no time limit. MFTIME limits the number of seconds during which a single FIND statement may execute. If SRCHLIM is increased, the maximum is 99999999, the default. The SRCHLIM parameter limits the number of CA Datacom/DB I/Os that can occur during the execution of a FIND statement. After you have made the necessary parameter changes, reassemble the System Option Table.
Batch: If the error occurs in batch, increase the size of the DQW or reduce the number of DQW partitions specified in the DQWFINIT. See the CA Dataquery Administrator Guide for details.
Reason:
CA Dataquery. cannot locate a PERSON entity in Datadictionary for your signon. A PERSON entity entry in Datadictionary is automatically generated when a user is given a CA Dataquery signon. However, if changes are made to your Datadictionary PERSON entity independent of CA Dataquery., CA Dataquery does not necessarily know about these changes.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator and request that the PERSON entity in Datadictionary for the user be synchronized with the user information in CA Dataquery.
Database Administrator
Work with your Datadictionary Administrator to synchronize the Datadictionary PERSON entity and the CA Dataquery User Information. Find out why the Datadictionary PERSON entity was deleted while the CA Dataquery User record remains in place and decide whether the user should be deleted from CA Dataquery., or the PERSON entity for the user should be added to Datadictionary.
Datadictionary Administrator
Help the Database Administrator to synchonize the Datadictionary PERSON entity and the CA Dataquery User Information. If requested, add the Datadictionary PERSON entity for the user to Datadictionary.
Reason:
The PF key you pressed is not used with this member type. The key either does not have a function assigned to it, or its function is not applicable to this type of member. Member type is one of the following: QUERY, DIALOG, TERM.
Action:
None is required.
Reason:
The Descriptive TEXT definition has been deleted from the DIALOG or PROC per your request. It must be redefined and saved before validation or execution is allowed.
Action:
None is required.
Reason:
This Descriptive text definition has been saved and is now part of the DIALOG or PROC for use during validation and execution.
Action:
To complete the definition, use the PF7 and PF8 keys to scroll through the variables. When each variable has a prompt and type defined and saved, then the variable STATUS will change from "INCOMPLETE" to "COMPLETE." If the member is a DIALOG, it should be validated at that time.
Reason:
After applying all the logical conditions in your query's FIND statement, CA Dataquery could find no rows that satisfied the conditions you specified.
Action:
If this is not the results you expected, examine your query for errors in your WITH or RELATED clauses or for statements that would always evaluate false. An example of this latter type of statement would be:
WITH Field-A > 10 and Field-A < 10
Make any necessary corrections, revalidate your query, and try executing it again. See your CA Dataquery Administrator if you require further assistance.
Reason:
Your query's FIND statement has terminated because one of the system limitations, set at CA Dataquery installation in the System Option Table or in your User definition, has been exceeded. No rows were found before the limit was exceeded.
Action:
Contact your CA Dataquery Administrator for assistance. Ask about your SRCHLIM, MFTIME, and FNDBLKS parameters. Your CA Dataquery Administrator may be able to increase these parameters for you.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Look at the Query Statistics panel to determine the parameter that was exceeded (SRCHLIM, MFTIME, or FNDBLKS). Based on this, help the user to make their selection criteria more restrictive. If this is not satisfactory, either increase the FNDBLKS parameter in the user row, or contact your Database Administrator to see about increasing the FNDBLKS, MFTIME, or SRCHLIM parameters.
Database Administrator
If requested and if system resources allow it, increase the FNDBLKS parameter in the System Option Table. This parameter determines how many logical blocks can be allocated in the work table during FIND execution. The maximum value for the FNDBLKS parameter is 9999999, the minimum is 1, and the default is 10. If MFTIME is to be increased, the maximum value is 9999999, and zero indicates that there is no time limit. MFTIME limits the number of seconds during which a single FIND statement may execute. If SRCHLIM is to be increased, the maximum is 99999999, the default. The SRCHLIM parameter limits the number of CA Datacom/DB I/Os that can occur during the execution of a FIND statement. After you have made the necessary parameter changes, reassemble the System Option Table.
Reason:
The total number of rows found to satisfy your COUNT request appears above.
Action:
None is required.
Reason:
Your query's COUNT statement has terminated because one of the system limitations, set at CA Dataquery installation in the System Option Table or in your user definition, has been exceeded.
Action:
Contact your CA Dataquery Administrator for assistance. Ask about your SRCHLIM, MFTIME, and FNDBLKS parameters. Your CA Dataquery Administrator may be able to increase these parameters for you.
Reason:
The CA Dataquery signon exit has determined that you may not continue.
Action:
Contact your CA Dataquery Administrator to determine your correct signon procedure.
Reason:
You have previously saved this Found Set. You cannot perform another KEEP command without rerunning the active query or executing a different query. Only one KEEP may be done per query execution. The FIND must be reexecuted before another KEEP command can be executed.
Action:
Execute a query. Then you may perform the KEEP function.
Reason:
You have returned from DIALOG execution by pressing the Return PF key. The dialog will not be executed.
Action:
None is required.
Reason:
You have returned from the execute status panel by pressing the Return PF key. The query will not be executed.
Action:
If desired, rerun the query starting at the FIND statement.
Reason:
You requested that query execution begin at the Selection step, but the query does not contain a FIND statement.
Action:
Either make a different selection for the beginning step of the query execution, or edit the query and add a FIND statement.
Reason:
The PF10 key for validation was pressed on an editor panel, but the text of this DIALOG has not been saved/updated since the last change to the text.
Action:
Save or update the DIALOG, and then use the PF5 (Define Dialog) key to make sure the dialog definition is complete. Then use the PF10 key to validate the DIALOG.
Reason:
You requested that CA Dataquery produce your report using a saved set. The data in the saved set that you specified has been altered since the found set was saved.
Action:
You will need to rerun the query from the selection step to generate a current found set that may be used by the report step. The altered saved set should be deleted.
Reason:
A command "EDIT membername member-type" was entered but you are not authorized to access that member-type.
Action:
See your CA Dataquery Administrator to obtain the proper authorization.
Reason:
The EXTRACT function was initiated for a large found set, and it is progressing normally.
Action:
None is required.
Reason:
The NUMBER OF COLUMNS option must be a number in the range of 80 to 255. The number of columns indicates how many columns (characters) appear across the page on a printed report.
Action:
Enter a number greater than 79 and less than 256.
Reason:
All rows that were to be updated/erased have been processed successfully.
Action:
None is required.
Reason:
An internal system error has occurred. Your update/erase request could not be processed.
Action:
Contact your CA Dataquery Administrator and describe the error you received, including the error text, number, and the error code displayed at the end of the text. Also describe the tables, columns, and selection criteria you were using for the update/erase.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact the systems programmer and request that the dump that was taken be printed. Give your systems programmer all pertinent information.
Systems Programmer
After printing the dump, contact Technical Support CA Dataquery.
Reason:
The member has been updated although this should not imply that it is free of errors.
Action:
If the member is a query or a DIALOG, you must validate it to detect any syntax errors.
Reason:
You requested that an existing condition be updated. The update was not completed because the existing condition applies to a different table than the condition you are attempting to update.
Action:
To change the table to which the condition applies, an existing condition must be deleted, and a new condition must be entered and saved.
Reason:
The PF3 Continue or the PF4 Save key was pressed on the Descriptive Text Dialog/Proc Definition panel, but no text was entered.
Action:
Enter text to be used as a title during execution/validation of a DIALOG or during submission of a PROC.
Reason:
The PF3 Submit key was used on the submit panel, but the named or default PROC is not completely defined.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Edit the PROC, and use the PF5 Def Proc key to complete the definition. For further assistance with JCL, contact your systems programmer.
Systems Programmer
Assist your CA Dataquery Administrator in completing the PROC.
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:
You must validate the DIALOG successfully at least once before you may execute it.
|
Copyright © 2014 CA.
All rights reserved.
|
|