Reason:
You have requested a key or column display but you have not yet selected a table from which the keys or columns should be taken.
Action:
Either key in the table name in the CURRENT TABLE area at the top of the panel and press the desired PF key, or, use the List Tables function, select a table from the list by placing the cursor on its name, press PF2 to return to the Editor, and then, you may request a key or column display.
Reason:
You have requested a "return data" function and the cursor has not been placed on a location where the data can be returned. You have requested a List Tables, Display Columns, Display Keys, Display All, or a List Commands function. You might be in the wrong mode. <PF3> is DISPLAY in Create Mode and EXECUTE in Process Mode.
Action:
Make sure you are in Create Mode. To use one of these functions, place the cursor on a location in the text where names or commands can be returned, and press the desired PF key.
Reason:
The command you entered in the line command column is not valid or is not recognizable to CA Dataquery.
Valid line commands and their meanings are as follows:
|
Valid Line Command |
Meaning |
Valid Line Command |
Meaning |
|---|---|---|---|
|
B |
Bottom |
MB |
Move to the bottom |
|
C |
Copy |
MM |
Move a block of text |
|
Cn |
Copy n number of lines |
MT |
Move to the top |
|
CB |
Copy to the bottom |
R |
Repeat |
|
CC |
Copy column of text |
Rn |
Repeat n number of times |
|
CT |
Copy to the top |
* |
Scroll this line to the top |
|
D |
Delete |
T |
Top |
|
Dn |
Delete n number of lines |
<n |
Shift left n number of spaces |
|
I |
Insert |
>n |
Shift right n number of spaces |
|
In |
Insert n number of lines |
SP |
Split the line |
|
M |
Move |
X |
Cancel a pending command |
|
Mn |
Move n number of lines |
|
|
Other editing commands are:
Change string1 to string 2
Find the next occurrence of this string
Find the previous occurrence of this string
Action:
Select the line command you want to use and reenter your line command using the correct format.
Reason:
The line command that you used requires that you specify a numeric value defining the number of lines/columns affected by the command. Commands which may contain a numeric value in the second position are: Cn (Copy n Lines), Dn (Delete n lines), In (Insert n lines), Mn (Move n lines), Rn (Repeat n lines), <n (Shift left n columns), and >n (Shift right n columns).
Action:
Compare your line command with the commands listed above. If the command you want to use is one of these commands, enter a number in the second position of the sequence number.
Reason:
You have requested an INSERT, COPY, or REPEAT function that would have added too many lines to the query text. A query cannot exceed the number of lines indicated in the QPAGES parameter of the System Option Table.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
If there are any blank lines in the query text, delete them and try again. If not, try reformatting the query text. If these actions do not work, contact your Database Administrator about increasing the size of the "QPAGES" parameter in the System Option Table.
Database Administrator
Increase the size of the "QPAGES" parameter in the System Option Table and reassemble it. The maximum allowed is four and the default is one. Each page allows 24 lines. If you use the Guided Query Creation Facility at your site, it is recommended that you specify QPAGES to be at least two. This parameter does not affect what is stored in the query library. If the query uses one page, only one page will be stored in the library.
Reason:
You have requested a block command, but have not completed it properly before entering another command. The pending commands are displayed on their respective lines. Most likely you have not specified the end of the block or the destination for the copied or moved text lines. The block commands CC or MM must be entered on two different lines: one indicating the beginning of the block and one indicating the end of the block. After the block has been specified, you must indicate the destination for a copy or move command by entering an A (AFTER) or a B (BEFORE) over the sequence number of destination.
Other block commands (Cn, CB, CT, Dn, MB, Mn, MT) must be entered only one time. To cancel a block command, type X over the sequence number of any line.
Action:
Complete or cancel the pending block command.
Reason:
You have specified a block move or copy command, but the destination is invalid. To specify the destination for the moved or copied text lines, type an A over the sequence number of the line after which you want the text placed, or type a B over the sequence number of the line before which you want the text placed.
Action:
Type either an A or a B over the appropriate sequence number. If you want to cancel the block command, type XX over the sequence number of any line.
Reason:
You have indicated that a NExt, PRevious, or CHange command is to be performed but have not indicated what character string the Editor is to locate. A string consists of 1 to 32 characters. A NExt or PRevious command consists of two parts: NE or PR in the sequence number field and a character string, surrounded by a special character, in the text portion of the same line.
Example: NE /DATAQUERY/ PR $DONUT$
A CHange command consists of three parts: CH in the sequence number field and two character strings, each surrounded by a special character, in the text portion of the same line.
Example: CH /DATAQUERY/DQ/ CH $DONUT$COFFEE & DONUTS$
Action:
Add the string(s) to the text portion adjacent to the command, or remove the command from the sequence number area.
Reason:
The string you requested in the NExt, PRevious, or CHange Editor command could not be found in the text of the member you are currently editing.
Action:
None is required.
Reason:
You have indicated that a CHANGE command is to be performed but have not specified a valid replacement string. A CHange command consists of three parts: CH in the sequence number field and two character strings, each 1 to 32 characters in length, surrounded by a special character.
Example:
CH /DATAQUERY/DQ/
CH $DONUT$COFFEE & DONUTS$
Action:
Add the string to the text portion adjacent to the command, or remove the command from the sequence number area.
Reason:
You have requested a right or left shift which would result in non-blank characters being moved beyond column 1 or column 80.
Action:
If there are any embedded blanks in the line, remove them before requesting the shift. Otherwise, reduce the number of columns to shift before issuing the request again.
Reason:
You requested a block move or copy command but have not yet completed it. The pending commands are displayed on their respective lines. Most likely you have not specified the end of the block or the destination for the moved or copied text lines.
Action:
To indicate the end of a block move, type MM in the sequence number of the last line to be moved. To indicate the end of a block copy, type CC in the sequence number of the last line to be copied. To specify the location for the moved or copied text lines, type an A over the sequence number if the text is to be placed after this line, or type a B over the sequence number if the text is to be placed before this line. To cancel the block command, type XX over the sequence number of any text line.
Reason:
You requested that a particular member be saved in the CA Dataquery library. This request has been completed successfully. However, this does not imply that the member is free of errors. If the member is a query or a dialog, you must validate it to detect any edit errors.
Action:
None is required. However, if the member is a QUERY, you should validate it to find any edit errors. If the member is a dialog, it must be completely defined and then validated.
Reason:
You requested that a particular member be deleted from the CA Dataquery library. This request has been completed successfully. The member has been permanently removed.
Action:
None is required.
Reason:
Your query was validated. No errors were found in the displayed query.
Action:
None is required. You may execute this query.
Reason:
An internal CA Dataquery error has occurred. This is a CA Dataquery system problem.
If you are using CA Dataquery online, a SNAP dump is generated with the message. If you are using CA Dataquery batch, the message occurs but a SNAP dump is not generated.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Assuming you are using CA Dataquery online and a SNAP dump has been generated with this message, ask your system 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
When the dump has completed printing, contact Technical Support for CA Dataquery.
Reason:
The function key that you pressed is not active on this panel.
Action:
Review the panel and choose an appropriate function key. You can panel help for this panel or see the CA Dataquery Reference Guide for further information.
Reason:
You have not saved/updated the DIALOG or the JCL PROC Text since you changed the text. The text must be SAVED/UPDATED prior to defining the DIALOG variables.
Action:
SAVE or UPDATE the DIALOG or the JCL PROC Text. You may then proceed with defining or changing the DIALOG variables.
Reason:
The row you wanted to add with your INSERT query was successfully added. You can now retrieve it with CA Dataquery if desired.
Action:
None is required.
Reason:
You have specified a scroll command with + or - and did not follow the sign with the number of lines to be scrolled.
Action:
Type the number of lines you want to scroll forward or backward.
Reason:
The help panel you requested is not available.
Action:
Contact your CA Dataquery Administrator for assistance with any questions you have.
Reason:
Your PF key scroll command would cause you to scroll past the end or in front of the beginning of the HELP panels.
Action:
You may type TOP or BOTTOM on the command line to see the first or last HELP panel respectively.
Reason:
You have changed the name, status, or type of the member. These fields, or attributes, must remain unchanged on this panel or the member cannot be deleted.
Action:
Return to the appropriate directory and place the cursor on the desired member name. Request the DELETE function.
Reason:
You have requested query execution but have not specified with which phase CA Dataquery should begin execution.
Action:
Indicate whether the query execution should begin in the SELECTION, COMPUTATION, SORTING, or REPORTING phase.
Reason:
You have requested a query execution but have not indicated where your query output should be sent. You may select one or more destinations.
Action:
Specify the destination for your query output: VIDEO TERMINAL, NETWORK PRINTER, or SYSTEM PRINTER.
Reason:
You have requested totals in your query execution but have not indicated which totaling option you prefer.
Action:
Specify which totaling option you want performed during the execution of your query: DETAIL AND TOTALS, DETAIL ONLY, TOTALS ONLY, or TOTALS BY NAME.
Reason:
You must complete the DEFINITION function after the last change to the text. A DIALOG must also be validated before it can be executed. A definition is complete when the text and all variables have been defined and saved.
Action:
Save the text and use the Dialog Definition facility to define the variables. For a DIALOG, after the variables are defined, validate the query. If the validation is successful, the DIALOG may be executed. For a PROC, once all variables are defined, the PROC may be submitted.
Reason:
You selected either the WHEN/DO RESULTS ONLY option and your query does not contain any when/do column functions or you have selected the NO DETAIL option and your query does not contain any columns which are totaled or you have selected DETAIL ONLY and your print statement contains no columns to be printed.
Action:
If you still want to execute the query, you may change the totaling option and execute the query again. You may also edit the query and add when/do column functions or add totaling to one or more of the printed columns or add columns to be printed to your print statement.
Reason:
You specified a single control break column for your query execution that has not been specified as a control break column in the SORT statement. Columns are designated as control break columns by placing parentheses around them in the SORT statement of your query.
Example: SORT (state) (city) street-address
State and city are control break columns.
Action:
Either change the single control break column to a column that has been designated as a control break column in the SORT statement, or modify your query by adding this control break column to the SORT statement and try executing it again.
Reason:
You selected the TOTALS ONLY option, but the query does not contain any columns that are totaled. Column totaling is specified in the PRINT statement by enclosing the column name in parentheses. Only numeric columns can be totaled.
Example: PRINT FROM PAYROLL (WAGES)
WAGES is the column that will be totaled.
Action:
If you still want to execute the query, you may change the totaling option to DETAIL ONLY or DETAIL AND TOTALS and execute the query again. You may also edit the query and add totaling to one or more of the printed columns.
Reason:
You have selected more than one of the totaling options for your report. You may choose only one of them.
Action:
Select only one of the totaling options for your report. Erase the selection mark beside the options that you do not want.
Reason:
You must press the PF3 key when you want to execute the query.
Action:
Make your selections on the query execution panel, and press the PF3 key when you are ready to execute the query.
Reason:
The LIST command that you entered was incorrect. The LIST command requests a directory listing of a particular type. The type can be QUERIES, TERMS, DIALOGS, TABLES, SETS or ALL. If you are listing QUERIES, TERMS or DIALOGS you may request to see those that are PUBLIC, PRIVATE, or BOTH. If you did not choose the SETS directory type, you may also specify a string of up to 32 characters which will be used to determine where the listing should begin.
Action:
Enter your choices on the panel. Each part you enter has a number corresponding to a list of values below. Choose a value for each from the list. Default values are provided for you.
Reason:
There are no more entries in the list you are viewing. You may scroll the list backward by using the PF7 key.
Action:
None is required.
Reason:
CA Dataquery has encountered a problem. Your LIST request cannot continue. The information after RC= further identifies the particular problem.
Action:
Gather information from the user including the message number, the return code at the end of the text, and what was being attempted when the error was received. Then contact Technical Support for CA Dataquery.
Reason:
A CICS GETMAIN failed. CA Dataquery is unable to execute the VALIDATE function. This is a CICS system problem.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
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 group display option is on, and you have requested that a repeating compound field, subscripted with a value greater than 1, be printed on your report. The group display option will be ignored for this field only.
Action:
If you want to print the individual subfields that make up the compound field, reference the simple fields instead of the compound field in your print statement.
Reason:
The function that you requested with the PF key requires that the cursor be positioned on a line containing the object of the requested function. The cursor is currently on a line that does not contain an object that the function can use.
Action:
Position the cursor on the line containing the object of the function and press the appropriate PF key again. If requesting <PF3> DISPLAY in Create Mode, make sure the cursor is in the query creation area.
Reason:
The Datadictionary Service Facility interface received an error from Datadictionary while requesting a service. The Datadictionary Service Facility return code is displayed with the error message.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Call your Database Administrator and describe the error message, including the error number, the text, and the return code at the end of the text, and what you, or your user, were attempting to do when the error occurred.
Database Administrator
Use the return code at the end of the message text to look up the error in the CA Datacom/DB Message Reference Guide. Follow the suggestions given there to correct the problem.
Reason:
The line item has been successfully deleted.
Action:
None is required.
Reason:
The query you are attempting to use has an error. It cannot be executed.
Action:
Follow the directions according to your job responsibilities:
Associate User
You have attempted to execute a query that accesses a table you are not authorized to access or there is an error in the query. See your CA Dataquery Administrator if you need to use the query.
CA Dataquery Administrator
Edit the query your Associate User was attempting to use. Check to see whether the user is authorized for the table(s) it accesses. If the user is authorized, validate it to determine what errors it contains. Correct the errors and revalidate. If it passes validation, update the existing query and try executing it.
Reason:
You cannot execute a query until one has been activated.
Action:
Either return to the directory of queries, place the cursor on the query you want to execute, and press PF3, or, enter "EXECUTE queryname" on the command line. (queryname is the name of the query you want to execute.)
Reason:
The variable was defined and saved previously, but has since been removed from the text of the DIALOG or PROC. When you remove a variable from the DIALOG text, you must also delete its definition.
Action:
Either delete the definition of the variable, or add the variable to the DIALOG or PROC text. You may delete the variable through the DIALOG Definition panel. If you want to add the variable back into the text, edit the text and insert it at the desired location.
Reason:
You are attempting to delete a definition for a DIALOG variable for which no values are currently saved.
Action:
None is required.
Reason:
The definition of the DIALOG variable has been successfully deleted. It is no longer part of the DIALOG definition.
Action:
If the variable is still in the DIALOG text, you must either specify a new definition for it, or you must remove it from the text before the DIALOG can be validated or executed.
Reason:
The definition which you have given for this DIALOG variable has been saved. It is now available for use during validation and execution.
Action:
None is required.
Reason:
The range of values you defined for the DIALOG variable has been successfully saved. It is now available for use when the DIALOG is validated or executed.
Action:
None is required.
Reason:
The range that was defined for the DIALOG variable has been successfully deleted.
Action:
None is required.
Reason:
The list of values that you defined for the DIALOG variable has been successfully saved. It is now available for use during validation and execution.
Action:
None is required.
Reason:
The list that was defined for the DIALOG variable has been successfully deleted.
Action:
None is required.
Reason:
You attempted to define a range or list for the variable before saving it.
Action:
Use the SAVE PF key to save the variable definition. Then, you may use the RANGE/LIST PF key to define a range or list for the variable.
Reason:
The length of this variable has changed in the text.
Action:
If you want the new length to be used, delete the variable definition. This panel will be redisplayed for the entry of the new variable definition. Enter the new information and save the variable definition.
If the old length is correct, RETURN to the Editor panel and correct the variable in the text of the Dialog.
Reason:
You have changed the TYPE of this variable and one or more values in the LIST definition do not match this new TYPE. For example, you may have changed the TYPE to alphabetic and you may have an entry in the list that contains both letters and numbers.
Action:
Change the TYPE to be compatible with the LIST entries, modify the LIST entries to match the new TYPE before changing the variable type, or delete the LIST.
Reason:
Your save request for the variable you changed to a non-numeric type failed because the variable was previously defined with a range. The range definition must be deleted before this change can be made.
Action:
Either request the range definition panel for the variable you want to change, delete the range, and save the variable. Or, change the variable type back to numeric.
Reason:
No RANGE or LIST was defined for this DIALOG variable when the DIALOG was created. When a RANGE is specified for a numeric variable, a value that you give at execution time must fall within the defined range. When a list is specified for a character variable, a value that you give at execution time must appear in the defined list. Since no range or list was defined for this variable, you can enter any value of the proper type (that is, any number if the variable is numeric, or any character string if the variable is character).
Action:
Continue with your DIALOG or PROC execution process.
Reason:
The indicated number contains more digits tha CA Dataquery can accept. The maximum for CA Dataquery is 18 digits. The number you type, however, may contain a sign and/or a decimal point.
Action:
Correct the number you typed by reducing the number of digits in the number until the total number of digits does not exceed 18.
Reason:
You are attempting to enter a non-numeric value for a numeric variable.
Action:
Enter a number to be used as the value of the variable.
Reason:
You have entered a value for an alphabetic DIALOG variable that is not a string of letters. This DIALOG variable was defined as an alphabetic variable during DIALOG creation.
Action:
Enter a new value that contains only letters (A-Z).
Reason:
You have entered a value for a character DIALOG variable that contains some incorrect characters. The DIALOG variable was defined as a character variable during DIALOG creation.
Action:
Enter a new value that does not contain any illegal characters. Check with your CA Dataquery Administrator to determine which characters are illegal at your site.
Reason:
The specified literal contains more than one sign. A number can have only one plus (+) or minus (-) sign.
Action:
Remove the extra sign(s).
Reason:
The indicated literal contains more than one decimal point.
Action:
Remove the extra decimal point(s).
Reason:
You have requested the DIALOG variable definition function but there are no variables indicated in the member text. A DIALOG or PROC must contain at least one variable. A variable is indicated by a one or two digit number, between 1 and 25, followed by the dialog symbol (your symbol is shown at the end of the message line) and a default value. If your dialog symbol is a question mark (?), an example of a dialog variable definition would be:
FIND 2?100 PAYROLL ROWS
Action:
Edit the member text and add at least one DIALOG variable. Then, you may proceed with the define DIALOG variable function (PF 5).
Reason:
You have included a variable in the text that is not formatted correctly or you have more than 25 variable substitutions in the text. With multiple variables, you must place a comma immediately after each variable except the last one. The required format is:
NN?DDDDD
Where:
NN = the variable identification which is a number between 1 and 25.
? = the dialog symbol. Your symbol may be different.
DDDDD = the default value for the variable.
No blanks are allowed between the ID, the Dialog Symbol, and the default value. The default value, depending on the context of the statement, may be:
100
'DALLAS'
<, >, =, LT,
A company name
+,-,\,*
Examples:
Action:
Correct the format of the variable. For more information, consult the USER GUIDE, USER REFERENCE, or HELP from the Main Menu.
Reason:
You have included a variable ID in the text that is not in the required format. The required format is:
NN?DDDDD
where:
NN = the variable identification which is a number between 1 and 25
? = the dialog symbol. Your symbol may be different.
DDDDD = the default value for the variable.
No blanks are allowed between the ID, the Dialog Symbol, and the default value.
Examples:
FIND 12?300 COMPANY
PRINT 22?ZIP-CODE
Action:
Correct the format of the variable ID.
Note: For more information, consult your CA Dataquery Reference Guide.
Reason:
A variable has been located in the member text but the default value cannot be found. An example is "2?100": the question mark is the dialog symbol (yours may be different since this is a site-defined option) and the 100 is the default value for the variable identified as 2. The default may be smaller than the maximum variable length. If this is the case, you use fill characters, which are also site-defined, to indicate the maximum size for the variable. For example, 5?'Dallas'_________ would indicate that "Dallas" is the default for a 15 character variable (where, in this case, _ is the site-defined dialog fill character).
Action:
Supply a default value for the variable, or, remove the variable from the text.
Reason:
The value indicated by the cursor cannot be interpreted by the DIALOG variable parser. It is either an invalid literal or an invalid DIALOG variable. Some examples of DIALOG variables with apostrophes are:
12?'TEXAS'
22?'11/12/87'
25?'AB0017'
Action:
Correct the DIALOG variable or literal in error. Either remove the extraneous apostrophe, or add one in the appropriate place.
Reason:
An internal error has occurred during VPE initialization. The processing of your request could not continue.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact the systems programmer to report the error. Include the CA Dataquery error number and the VPE error number displayed at the end of the error message.
Systems Programmer
Use the VPE error code displayed at the end of the CA Dataquery error message to look up the error in the CA IPC Message Guide. The CA IPC Message Guide will contain information about the precise error and the appropriate action to take.
Reason:
A Datadictionary Service Facility error was detected during initialization.
Action:
Follow the directions for your job responsibilities.
CA Dataquery Administrator
Contact the Database Administrator to report the error. Describe the error number and the DSF error code or CA Datacom/DB return code displayed at the end of this message.
Database Administrator
For instructions on how to respond, see the CA Datacom/DB Message Reference Guide for the DSF error code or CA Datacom/DB return code displayed at the end of this message.
Reason:
You pressed the Enter or PF4 key on the Guided Primary Table Selection panel without selecting a primary table. A primary table selection is required.
Action:
Choose a primary table and then continue.
Reason:
A CICS GETMAIN failed. CA Dataquery is unable to execute the requested function. This is a CICS system problem.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
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:
No rows match your selection criteria. Therefore, no rows can be updated or erased.
Action:
Review your selection criteria (the WITH statement) to see if it is accurate. Make any corrections necessary and try again. For further assistance, see your CA Dataquery Administrator.
CA Dataquery Administrator
Assist your users by reviewing their selection criteria (the WITH statement) to see if it is accurate. Assist in making any necessary corrections.
Reason:
You have specified that a row, or rows, be updated or erased. This request has been completed successfully. If the row was updated, you can now retrieve the updated row with CA Dataquery.
Action:
None is required.
Reason:
You have selected more than one beginning point for your query execution. You may choose only one. Your choice determines the statement in your query where processing will begin. You must specify Selection (the FIND statement) unless you have just run or rerun the current Active Query. All other beginning points use the records in the Active Found Set for processing.
Action:
Select only one beginning point for your query execution. Erase the selection mark beside the ones you do not want.
Reason:
You specified that you wanted a report containing totals only, but the query does not contain any columns to be totaled. A column is totaled if it is enclosed in parentheses in the PRINT statement. A detail report was produced instead.
Action:
None is required. You may view the report that was produced at your terminal. If you want the query to produce totals, use the Editor to add parentheses around the columns in the PRINT statement, and after saving and validating the query, execute the query again, beginning with the reporting step.
Reason:
You specified that you wanted a report containing totals only, but the query does not contain any columns to be totaled. A column is totaled if it is enclosed in parentheses in the PRINT statement. The report was not produced.
Action:
If you want to see the report without totals, change your totaling option to Detail Only. If you want to add totals to the query, use the Editor to place parentheses around the columns in the PRINT statement. After saving and validating the query, execute it again, beginning with the reporting step.
Reason:
You are viewing the end of the report.
Action:
None is required.
Reason:
The user requested that the system flush the output report. The report will not be produced.
Action:
None is required.
Reason:
You have entered a command on the command line of the Print Output panel that is not recognizable to CA Dataquery. The valid commands are: T, TOTALS, TOTALS-ONLY, N, NOT, NO-TOTALS, D, DET, DETAIL, +nnn, -nnn, nnn, TOP, and BOTTOM.
Action:
Either use a valid command on the command line, or use one of the active PF keys displayed on the bottom of the panel.
Reason:
There are not any previous entries in the list you are viewing. You may scroll the list forward using the PF8 key.
Action:
None is required.
Reason:
You specifed that you wanted a report containing no totals, but the query does not contain any columns to be printed on a detail line, only totals and/or WHEN/DO column functions are produced instead.
Action:
None is required. You may view the report that was produced at your terminal. If you want the query to produce detail lines, use the Editor to add column names to be printed in the PRINT statement, and after saving and validating the query, execute the query again, beginning with the reporting step.
Reason:
No join is possible using the key or column selected for your Primary Table. The key or column you selected does not match any keys in the Secondary Table.
Action:
Return to the Key and Column Display panel for your Primary Table and select another key or column to use to join the two tables.
Reason:
You requested that the primary table be related to the secondary table. You must choose a key or column from the first table which is common to a key in the second table. Rows from the two tables are related when they have a common value for the key or column which you select.
Action:
Make a selection by typing any character over the underscore in the SELECT column next to the column or key name of your choice before continuing with the Guided Query Creation. If you no longer want to use both tables, use the PF2 key to return to the appropriate panel and cancel the selection.
Reason:
You requested that the first table be related to the second table. Now you must choose a key from the second table that will be used to relate the column or key from the first table to the second table. Rows from the two tables are related when the value for 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 key name of your choice. You may then continue with Guided Query Creation. You may view the key definition by using the extended column key (PF5).
Reason:
The DIALOG definition must be completed before validation is attempted. A definition is complete when the text and all variables have been defined and saved.
Action:
Save the text, and use the Dialog Definition facility to define the variables. After the DIALOG definition is completed and saved, you may validate the DIALOG.
Reason:
The size or precision you specified for the result field is not correct. The correct format of a precision specification is N.D, where N and D must be numeric, containing the digits 0 through 9. The sum of N and D cannot exceed 18. The default is 13.2.
Action:
Reenter the precision of the result field, or type spaces over your precision specification if you want to use the default.
Reason:
You have defined more than 10 temporary result fields in your query. The maximum allowed in GUIDE mode is 10.
Action:
Remove temporary result fields until there are ten or less.
Reason:
You wanted to view the stored text for a table, column or key but no text exists for it.
Action:
Contact your CA Dataquery Administrator if you want text to be added.
Follow the directions for your job responsibilities:
CA Dataquery Administrator
If you want text to be added for the entity, contact your Data Base Administrator and request that text be added.
Database Administrator
Work with the CA Dataquery Administrator to determine what should be included in the text description of the entity. Your Datadictionary Administrator will enter the text you want added into Datadictionary.
Datadictionary Administrator
Enter the text for the entity into Datadictionary as requested by the Database Administrator.
Reason:
You must choose YES or NO but not both for your response to "Retrieve the first related row (bypass other occurrences)?" You have marked neither selection or both selections.
Action:
Mark ONE selection for YES or NO and proceed with guided query creation.
Reason:
The table name you entered on the command line cannot be displayed because either you are in Process Mode, it does not exist in Datadictionary, and, hence is not known to CA Dataquery, or, you may not be authorized to use this table. You may, however, have misspelled the table name.
Action:
Make sure you are in Create Mode. Check the spelling of the table name by viewing the Directory of Tables. When you find the one you want to display, you may place the cursor on the name of the table and press PF5, or you may type "DISPLAY tablename" on the command line.
If you cannot find the table on your Directory of Tables, you may not be authorized to use this table. Contact your CA Dataquery Administrator for further information.
|
Copyright © 2014 CA.
All rights reserved.
|
|