The following is a listing of the unnumbered CA Dataquery batch messages. Each message is documented with the message text, the program name from which the message originates, the reason the message was generated, and the suggested action you should take. The messages are listed in alphabetical order based on the text of the message.
Reason:
You coded values for the GROUPS= keyword that are not compatible with the groups assigned to you.
Action:
Code only groups that are named in your profile, and in the same order as they appear in your profile. If you have no group assignment (that is, blanks) in any of the three group assignment positions, you can name a group for that position.
For example, your group assignment is:
group1=DALLAS, group2=DATACOM, group3=
You can code, on one of your control cards:
GROUPS=DALLAS,DATACOM,GROUPX
because you have no group assignment for group3. You cannot code:
GROUPS=DALLAS,GROUPX
because the second group you coded does not match the second group in your profile.
Reason:
You coded values for the GROUPS= keyword that are not compatible with the groups assigned to you.
Action:
Code only groups that are named in your profile, and in the same order as they appear in your profile. If you have no group assignment (that is, blanks) in any of the three group assignment positions, you can name a group for that position.
For example, your group assignment is:
group1=DALLAS, group2=DATACOM, group3=
You can code, on one of your control cards:
GROUPS=DALLAS,DATACOM,GROUPX
because you have no group assignment for group3. You cannot code:
GROUPS=DALLAS,GROUPX
because the second group you coded does not match the second group in your profile.
Reason:
The function named was not authorized for the user by the external security package.
Action:
Make sure the necessary authorization is in place in the external security package and resubmit.
Reason:
The function named was not authorized for the user by the external security package.
Action:
Make sure the necessary authorization is in place in the external security package and resubmit.
Reason:
The requested add of a user to CA Dataquery was successful.
Action:
None. This message is informational only.
Reason:
The requested add of a user to CA Dataquery was not successful. Another message will specify the cause.
Action:
See the message with the input card which was being processed to determine the error.
Reason:
Every input card had at least one error.
Action:
Correct all cards and rerun the job.
Reason:
No processing was done because all input cards contained an error.
Action:
Correct the cards from the messages given for each and resubmit the job.
Reason:
All input cards have been processed.
Action:
Review program output to ascertain if execution was successful or unsuccessful.
Reason:
All of your input cards were processed by CA Dataquery. Other messages indicate the disposition of each input card.
Action:
None. This message is informational only.
Reason:
Partitioning the Work File (DQW) as specified on the "DQW xx" card results in fewer than 10 logical blocks per partition which is too small.
Action:
Either increase the Work File (DQW) size, or decrease the number of partitions (xx) requested.
Reason:
The function named was not authorized for the user by the external security package.
Action:
Make sure the necessary authorization is in place in the external security package and resubmit.
Reason:
The file type for a z/VSE execution was not TAPE or DISK.
Action:
Correct the DOSFILE= card to use a value of TAPE or DISK, and rerun the job.
Reason:
A record on the input file for a RUNTYPE=LOAD was not a valid type. The record was skipped and not loaded.
Action:
Follow the directions for your job responsibilities:
End User
Contact your CA Dataquery Administrator with information about the error and the tape you were using.
CA Dataquery Administrator
You can dump the tape with a tape dump utility to see if the record is valid or not. See your systems programmer for assistance. The type appears as the first byte of the record: 1 indicates a panel, L indicates a literal, and V indicates a vocabulary term. After you have dumped the tape, contact Technical Support for CA Dataquery.
Systems Programmer
Dump the tape so that you and your CA Dataquery Administrator can look at the record in error.
Reason:
You have coded RUNTYPE=LOAD and RUNTYPE=UNLOAD in one input card stream.
Action:
DQLANGMT will process the first RUNTYPE= card that has no errors. If a subsequent input card contains the opposite RUNTYPE from the above card, this message appears. Split the LOAD and UNLOAD into separate jobs and rerun the ones not successfully run.
Reason:
An update was requested which would remove user maintenance authorization from the user who is currently signed on. This is not allowed by DQUSERMT.
Action:
Correct the update card and resubmit.
Reason:
There is an internal error in DQLANGMT.
Action:
Save all job output, including this message and contact Technical Support for CA Dataquery.
Reason:
A continuation character was found in column 72 but the next input card was not a continuation.
Action:
Correct the input and resubmit the job.
Reason:
One (or more) of the errors listed on your error report (probably the last one), was so serious that processing has been halted.
Action:
Correct the error conditions listed on your error report and rerun the job.
Reason:
One (or more) of the errors listed on your error report (probably the last one), was so serious that processing has been halted.
Action:
Correct the error conditions listed on your error report and rerun the job.
Reason:
CA Dataquery could not find data in the online Found File (DQF) to complete the print request to the system printer probably because the Found File (DQF) was reinitialized after the print was requested and before the batch job ran.
Action:
Reexecute the query online, specifying the system printer as your output destination.
Reason:
A database error was encountered when accessing the Work File (DQW) to begin CA Dataquery batch processing. The CA Datacom/DB return code is displayed in the message.
Action:
Follow the directions for your job responsibilities:
End User
Contact your CA Dataquery Administrator for assistance. Describe the error you received and the CA Datacom/DB return code that appears in the message.
CA Dataquery Administrator
Contact your Database Administrator and describe the error and the return code that appears in the message.
Database Administrator
Using the database return code displayed in the message, look up the error in the CA Datacom/DB Message Reference Guide. Follow the instructions found there to correct the problem. It can be necessary to run DQWFINIT to reinitialize the batch Work File (DQW).
Reason:
CA Dataquery batch could not find an available batch work file partition and could not execute at this time.
Action:
Follow the directions for your job responsibilities:
End User
Wait until all other CA Dataquery batch jobs have terminated normally and try running the job again. If this problem occurs frequently, contact your CA Dataquery Administrator.
CA Dataquery Administrator
If this problem occurs frequently, contact your systems programmer and ask that the number of work file partitions be increased.
Systems Programmer
If requested, reinitialize the Work File (DQW) and increase the number of partitions.
Reason:
CA Dataquery batch has terminated abnormally. The ABEND code is displayed as part of the error message.
Action:
Follow the directions for your job responsibilities:
End User
Contact your CA Dataquery Administrator for assistance. Describe the error and what you were attempting when the error occurred.
CA Dataquery Administrator
Contact your systems programmer and describe the error that was received and the ABEND code that appears in the message.
Systems Programmer
See the IBM documentation for the meaning of the ABEND code and follow the instructions found there. If necessary, collect the dumps produced by the ABEND and contact Technical Support for CA Dataquery.
Reason:
CA Dataquery batch has terminated abnormally. The IBM CANCEL code is displayed as part of the error message.
Action:
Follow the directions for your job responsibilities:
End User
Contact your CA Dataquery Administrator for assistance. Describe the error and what you were attempting when the error occurred.
CA-DATAQUERY Administrator
Contact your systems programmer and describe the error that was received and the IBM CANCEL code that appears in the message.
Systems Programmer
See the VSE/Advanced Functions Cancel Codes section of the IBM z/VSE Messages and Codes manual for the meaning of the IBM CANCEL code and follow the instructions found there. If necessary, collect the dumps produced by the IBM CANCEL code and contact Technical Support.
Reason:
All partitions on the batch Work File (DQW) are being used. CA Dataquery batch will wait 30 secords and try again for a partition. CA Dataquery will try to obtain a partition up to five times before giving up.
Action:
No action is required. This is an informative message. You can try running your job again later.
Reason:
The value you coded after the DATE= keyword did not follow the date format that is used in DQLIBRMT. The first two positions are a numeric month code, with a value from 01 through 12. A slash follows. The fourth and fifth positions represent a numeric day code, with a value from 01 through 31. A slash follows. The seventh and eighth positions represent the last two digits of the year.
Action:
Rewrite the DATE= value using the format described above.
Reason:
You coded the DATE= keyword along with the TYPE=JCL or the TYPE=PROC keywords. You cannot select JCL records by date.
Action:
Remove the DATE= keyword if you want to access only JCL.
Reason:
A database error has occurred.
Action:
Determine the cause of the error from the accompanying return code.
Reason:
An error was encountered on the database file.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator and describe the error, including the return code at the end of the message.
Database Administrator
Look up the message number in the CA Datacom/DB Message Reference Guide manual using the code displayed at the end of the message. If the file is closed, take the appropriate measures to rectify the situation. If it is a more serious condition, collect all job output, including the dump, and contact Technical Support for CA Dataquery.
Reason:
An error was encountered on the database file. The CA Datacom/DB return code was xxx.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator and describe the error you received including the CA Datacom/DB error code displayed in the message.
Database Administrator
Look up the message number in the CA Datacom/DB Message Reference Guide manual. If the file (table) is closed or if it is full, take the appropriate action to correct the condition. If it is a more serious condition, save all job output, including the dump, and contact Technical Support for CA Dataquery.
Reason:
An error was encountered on the database file. The CA Datacom/DB return code was xxx.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator and describe the error you received including the CA Datacom/DB error code displayed in the message.
Database Administrator
Look up the message number in the CA Datacom/DB Message Reference Guide manual. If the file (table) is closed or if it is full, take the appropriate action to correct the condition. If it is a more serious condition, save all job output, including the dump, and contact Technical Support for CA Dataquery.
Reason:
An index entry was found for a record, but the record was not found in the indicated location. This means that the index for your database does not reflect the physical location of the records. There are many possible causes for this situation, although most are rare occurrences.
Action:
Follow the directions for your job responsibilities:
End User
Contact your CA Dataquery Administrator for assistance. Describe the error and what you were attempting when the error occurred.
CA Dataquery Administrator
Gather all output data from the job, including the JCL output messages. Look in the JCL output message log to see if any Multi-User Facility error messages were displayed. If Multi-User Facility error messages were displayed, contact your database Administrator for assistance. If no Multi-User Facility error messages were received, try to rerun the job. If you still receive the same error, contact your systems programmer for further assistance.
Database Administrator
If Multi-User Facility error messages were displayed in the JCL output, determine the cause by referring to the CA Datacom/DB Message Reference Guide. Follow the instructions you find there.
Systems Programmer
Using the program output, assist your CA Dataquery Administrator in determining the cause and the resolution of the error.
Reason:
An index entry was found for a record, but the record was not found in the indicated location. This means that the index for your database does not reflect the physical location of the records. There are many possible causes for this situation, although most are rare occurrences.
Action:
Follow the directions for your job responsibilities:
End User
Contact your CA Dataquery Administrator for assistance. Describe the error and what you were attempting when the error occurred.
CA Dataquery Administrator
Gather all output data from the job, including the JCL output messages. Look in the JCL output message log to see if any Multi-User Facility error messages were displayed. If Multi-User Facility error messages were displayed, contact your database Administrator for assistance. If no Multi-User Facility error messages were received, try to rerun the job. If you still receive the same error, contact your systems programmer for further assistance.
Database Administrator
If Multi-User Facility error messages were displayed in the JCL output, determine the cause by referring to the CA Datacom/DB Message Reference Guide. Follow the instructions you find there.
Systems Programmer
Using the program output, assist your CA Dataquery Administrator in determining the cause and the resolution of the error.
Reason:
An error was encountered on the database file. The file name was fff, and the database return code was 99-99.
Action:
Follow the directions for your job responsibilities:
CA Dataquery Administrator
Contact your Database Administrator and describe the error you received including the CA Datacom/DB error code and the file displayed in the error message.
Database Administrator
Look up the message number in the CA Datacom/DB Message Reference Guide. If the file (table) is closed or if it is full, take the appropriate action to correct the condition. If it is a more serious condition, save all job output, including the dump, and contact Technical Support for CA Dataquery.
Reason:
The requested delete of a CA Dataquery user ID was not successful. Other messages will specify the cause of the error.
Action:
Determine the cause of the error from the other messages.
Reason:
The requested delete of a CA Dataquery user ID was successful.
Action:
None. This message is informational only.
Reason:
A CA Datacom/DB return code has been detected. The "variable text" gives a brief explanation of the return code. The CA Datacom/DB return code replaces nn in the error message.
Action:
See the CA Datacom/DB Message Reference Guide for the reason and action.
Reason:
The Spool File (DQS) is not empty (some network print requests are pending).
Action:
Either null load the Spool File (DQS) with DBUTLTY, or allow all pending print requests to complete, and then rerun the job.
Reason:
This message can be received on a BACKUP or a REMOVE request when the user ID entered as the value in the NAME= keyword cannot be found on the User File (DQU).
Action:
Review the spelling you used on your NAME= keyword to verify that is it spelled correctly. For further assistance, contact your CA Dataquery Administrator.
Reason:
This message can be received on a BACKUP or a REMOVE request when the user ID entered as the value in the NAME= keyword cannot be found on the User File (DQU).
Action:
Review the spelling you used on your NAME= keyword to verify that is it spelled correctly. For further assistance, contact your CA Dataquery Administrator.
Reason:
The blocks in a partition of the Work File (DQW) required rechaining. One possible cause is that a previous execution of CA Dataquery batch terminated abnormally.
Action:
None is required. This message is informational only. CA Dataquery batch will execute normally after rechaining completes.
Reason:
You have used the same keyword more than once on a single input card.
Action:
Remove the duplicate keyword and rerun the job.
Reason:
You have used the same keyword more than once on a single input card.
Action:
Remove the duplicate keyword and rerun the job.
Reason:
A keyword has been used more than once on a control card. DQLIBRMT cannot accept a keyword more than once for each FUNCTION REQUEST.
Action:
Use a keyword only once on a control card. Some control cards can be used more than one time (BACKUP, REMOVE, REPORT, USER). If, for example, you want to back up queries for more than one user, you can write multiple BACKUP cards, naming a different user on each card. You cannot name more than one user on any one BACKUP card. Correct the cards in error.
Reason:
The same keyword option was specified two or more times in the input.
Action:
Remove the duplication and resubmit the job.
Reason:
This can occur on a RESTORE request, when you have attempted to restore any query library member to the Query Library (DQQ) with the same member type, name, and group assignments as one that currently exists in the online file.
If using the RESTORE function to reassign queries to a new user, it can be that the new user has the same group assignments as the previous user and the old member has not been removed from the library, or that someone with the same group assignments as the new user owns a member of the same type and name.
Action:
Access the online member to determine if it should be REMOVED, or if a member should have its name changed before the restore takes place.
Reason:
Your input contained more than one sign/on card. The duplicate card was ignored.
Action:
None. This message is informational only.
Reason:
There are no input cards for CA Dataquery batch.
Action:
The first input card must be SIGN/ON in order to execute CA Dataquery batch in sign/on mode, or DEFER in order to execute deferred batch queries.
Reason:
The current run was aborted because an error was detected in the external security package.
Action:
Determine the cause of the error, possibly from other messages, change the external security package appropriately, and retry the job.
Reason:
The requested report can be incomplete. Other messages will specify the cause of the error.
Action:
Determine the cause of the error from the other messages.
Reason:
A comma was detected in columns 11 through 72, and no keyword followed it.
Action:
Either remove the comma from the control card, or code an appropriate keyword following the comma.
Reason:
A comma was detected in columns 11 through 72, and no keyword followed it.
Action:
Either remove the comma from the control card, or code an appropriate keyword following the comma.
Reason:
You have used a comma in the statement, but the comma is not followed by a keyword.
Action:
Either remove the comma from the statement or add an appropriate keyword after it, and rerun the job.
Reason:
A comma was found on the input card, but no keyword was following.
Action:
Correct the input card and resubmit the job.
Reason:
The current run was terminated because an error was detected in the external security package.
Action:
Determine the cause of the error, possibly from other messages, perform the appropriate changes, and retry the job.
Reason:
The file being intialized has not been null loaded with DBUTLTY.
Action:
Null load the file in question with DBUTLTY and rerun DQWFINIT. If the DQWFINIT fails again, do the following:
Reason:
Initialization of the Work File (DQW) has been successfully completed. xxxxx is the number of logical blocks in the file.
Action:
None is required. This message is informational only.
Reason:
Your batch query required more find blocks than allowed by the current DQW file allocation.
Action:
Increase the size of the DQW table or decrease the number of partitions in the current DQW table allocation.
Reason:
Your batch query required more time during the FIND processing than is allowed by the current DQ system table setting.
Action:
Increase the MFTIME parameter time allocation in the DQ System Table.
Reason:
Your batch query required more CA Datacom/DB physical I/O events than is allowed by the current DQ system table setting.
Action:
Increase the SRCHLIM parameter allocation in the DQ System Option Table.
Reason:
The sign/on could not be completed because the password is in error.
Action:
Correct the password and resubmit the job.
Reason:
Your input card contained no errors and was processed successfully.
Action:
None is required.
Reason:
More than 60 control cards were encountered in the input data stream within one job step. Only 60 cards can be processed in any one execution of DQLIBRMT.
Action:
Read the Query Utility report to determine which control statements were processed successfully. Rerun DQLIBRMT using the control statements that were not processed in the first run. If it is ever necessary to process more than 60 control statements in one job, DQLIBRMT can be executed multiple times, in more than one job step, within the same job, as long as 60 or fewer control statements are executed in any one job step.
Reason:
More than 60 control cards were encountered in the input data stream within one job step. Only 60 cards can be processed in any one execution of DQLIBRMT.
Action:
Read the Query Utility report to determine which control statements were processed successfully. Rerun DQLIBRMT using the control statements that were not processed in the first run. If it is ever necessary to process more than 60 control statements in one job, DQLIBRMT can be executed multiple times, in more than one job step, within the same job, as long as 60 or fewer control statements are executed in any one job step.
Reason:
All input control cards have been processed.
Action:
None is required. This message is informational only.
Reason:
All input control cards have been processed.
Action:
None is required. This message is informational only.
Reason:
DQLIBRMT was not able to honor the request on the control card that follows this message because the operating system was not able to provide the required amount of storage. This situation can occur on a BACKUP or a REMOVE request when the GROUPS= option is used in combination with the STATUS= option.
Action:
Follow the directions for your job responsibilities:
End User
Notify your CA Dataquery Administrator of the error.
CA Dataquery Administrator
Contact your systems programmer and describe the error that was received. Find out if a larger region, or partition, can be used to run the job or if the region, or partition, size can be increased.
Systems Programmer
If there is a larger region, or partition, that can be used, advise your CA Dataquery Administrator of it and any other needed information such as job class, and so forth. If there is no larger partition, increase the region or partition size so that DQLIBRMT can execute successfully.
Reason:
An invalid batch function was specified on an input card to CA Dataquery batch. Valid functions are: SIGN/ON and DEFER.
Action:
Correct the error and retry.
Reason:
An invalid CA Dataquery command was specified on an input statement to CA Dataquery batch. If the command is not recognized as one of the valid commands, you can get this error message. The only valid commands in batch are: FIND, EXECUTE, and EXPORT. If there is no continuation character when the command spans lines, CA Dataquery does not recognize the command.
Action:
Correct the error and retry.
Reason:
An invalid CA Dataquery command was specified on an input card to CA Dataquery batch. The only valid commands in batch are: FIND, EXECUTE, and EXPORT.
Action:
Correct the error and retry.
Reason:
Some keywords allow you a choice of acceptable values and others have a standard format. For example, STATUS= keyword can have a value of PUBLIC, PRIVATE or ALL, and the DATE= keyword must follow the format MM/DD/YY. One or more of your keyword values are incorrect.
Action:
See the CA Dataquery Administrator Guide for a list or a description of acceptable values for each keyword, and select an appropriate one for the function.
Reason:
Some keywords allow you a choice of acceptable values and others have a standard format. For example, STATUS= keyword can have a value of PUBLIC, PRIVATE or ALL, and the DATE= keyword must follow the format MM/DD/YY. One or more of your keyword values are incorrect.
Action:
See the CA Dataquery Administrator Guide for a list or a description of acceptable values for each keyword, and select an appropriate one for the function.
Reason:
The input card contained a parameter other than req, name, suffix and lang.
Action:
Correct the input card and resubmit.
Reason:
The value assigned to the TITLE= keyword on the REPORT control card was not DIRECTORY or QUERYTEXT.
Action:
Use either DIRECTORY or QUERYTEXT for the value assigned to the TITLE= keyword on the REPORT control card.
Reason:
The value assigned to the TITLE= keyword on the REPORT control card was not DIRECTORY or QUERYTEXT.
Action:
Use either DIRECTORY or QUERYTEXT for the value assigned to the TITLE= keyword on the REPORT control card.
Reason:
The report card that precedes a list of USER cards is invalid. Any USER cards that refer to that report will be ignored for the specified USERs.
Action:
See the CA Dataquery Administrator Guide for the correct format of the REPORT card. Type the card correctly and resubmit the job. When the REPORT card is correct, the USER cards will be honored.
Reason:
The report card that precedes a list of USER cards is invalid. Any USER cards that refer to that report will be ignored for the specified USERs.
Action:
See the CA Dataquery Administrator Guide for the correct format of the REPORT card. Type the card correctly and resubmit the job. When the REPORT card is correct, the USER cards will be honored.
Reason:
The first parameter on the input card must be "REQ=PRINT."
Action:
Correct the input card and resubmit.
Reason:
The SIGN/ON card was not in the proper format. The proper format is:
SIGN/ON userid PASSWORD password
Action:
Correct the SIGN/ON card and resubmit the job.
Reason:
The keyword you entered does not appear in the list of valid keyword entries. You can have misspelled it.
Action:
Use a keyword from the following list, making sure that the spelling is exactly the same, and rerun the job.
KEY WORDS:
Reason:
A keyword was used as an option on an add or update card which was not known to CA Dataquery.
Action:
See the list of valid keywords in the DQ ADMINISTRATION GUIDE and correct the input. Resubmit the job.
Reason:
You have specified the LANGUAGE= keyword in a statement along with the RUNTYPE= keyword, but the RUNTYPE value is not UNLOAD.
Action:
Remove the LANGUAGE= keyword if the RUNTYPE is not UNLOAD, and rerun the job.
Reason:
The language name must be a two-character language name, such as "LANG=AE".
Action:
Correct the input card and resubmit.
Reason:
The language code you specified is not two characters.
Action:
Specify a two-character language code and rerun the job.
Reason:
The number of partitions requested on the "DQW xx" card is not numeric or it exceeds 47.
Action:
Correct the card so that the xx value is less than or equal to 47. xx stands for the number of partitions to be allocated on the CA Dataquery Work File (DQW).
Reason:
You coded a user ID on a NAME= keyword for a user whose group assignments are not compatible with yours. You cannot have access to this user's queries.
Action:
Review the spelling you used on your NAME= keyword to verify that you have entered the user ID you intended to enter. For further assistance, see your CA Dataquery Administrator.
Reason:
You coded a user ID on a NAME= keyword for a user whose group assignments are not compatible with yours. You cannot have access to this user's queries.
Action:
Review the spelling you used on your NAME= keyword to verify that you have entered the user ID you intended to enter. For further assistance, see your CA Dataquery Administrator.
Reason:
You coded the MEMBER= keyword along with the TYPE=JCL or TYPE=PROC keyword. The MEMBER option has no meaning for JCL or PROC members, because of the manner in which these members are stored on the query library.
Action:
If you want to access JCL or PROCs on the query library, remove the MEMBER= keyword. You can use the GROUPS= keyword in its place, because JCL is stored by groups in the library. If you want to use the MEMBER= keyword, remove the TYPE=JCL or the TYPE=PROC keyword.
Reason:
More than one RESTORE card was encountered in your input control cards. Only one RESTORE request is permitted per job step.
Action:
You can pass your input backup file through multiple job steps. DQLIBRMT can be executed multiple times, in more than one job step, within the same job. Each job step can contain only one RESTORE request. Either break up your RESTORE requests into multiple job steps, or run the job multiple times using a single RESTORE request in each one.
Reason:
The NAME= keyword is required for the USER card and for the RESTORE card. NAME= was not found on the card that is displayed beside this error message.
Action:
Use the NAME= keyword, followed by a user ID, on all USER and all RESTORE cards.
Reason:
The NAME= keyword is required for the USER card and for the RESTORE card. NAME= was not found on the card that is displayed beside this error message.
Action:
Use the NAME= keyword, followed by a user ID, on all USER and all RESTORE cards.
Reason:
The first input card when running on z/VSE must contain DOSFILE=TAPE/DISK.
Action:
Add this card as the first card in the input card stream and rerun the job.
Reason:
DQLIBRMT detected data on the control card in columns 11 through 72 that follows a blank. No embedded blanks are permitted within the bounds of these columns. A keyword is separated from its first value by an equal sign (=), multiple keyword values are separated by commas, and any keywords that follow the first keyword are separated from the previous keyword's values by a comma.
Action:
Replace any embedded blanks by an equal sign (=) or commas, and remove any extraneous data from the end of the control card.
Reason:
DQLIBRMT detected data on the control card in columns 11 through 72 that follows a blank. No embedded blanks are permitted within the bounds of these columns. A keyword is separated from its first value by an equal sign (=), multiple keyword values are separated by commas, and any keywords that follow the first keyword are separated from the previous keyword's values by a comma.
Action:
Replace any embedded blanks by an equal sign (=) or commas, and remove any extraneous data from the end of the control card.
Reason:
There were no control statements in the input job stream. No processing occurred because no requests were made.
Action:
Include control statements in your job stream as a SYSIN data set for z/OS, or as a SYSIPT data set for z/VSE.
Reason:
There were no control statements in the input job stream. No processing occurred because no requests were made.
Action:
Include control statements in your job stream as a SYSIN data set for z/OS, or as a SYSIPT data set for z/VSE.
Reason:
Each control function requires entry of at least one keyword. No keyword was found on the control card that follows this message.
Action:
Use the list in the CA Dataquery Administrator Guide to determine which keywords are required for the function requested on the control card. Type the keyword and its values on the control card and resubmit the job.
Reason:
No keyword was found on the control card that follows this message.
Action:
Use the list in the CA Dataquery Administrator Guide to determine the keywords required for the function requested on the control card. Type the keyword and its values on the control card and resubmit the job.
Reason:
This message can be received for any control card to indicate that no records on the Query Library meet the selection criteria indicated on the control card. For example, a request to remove any library members that have not been used since 12/31/80 can yield no output because the product was not purchased until 1982.
Action:
Review the parameters entered on the control card to verify accuracy. Transposed numbers or misspelled names could cause a fruitless search.
Reason:
This message can be received for any control card to indicate that no records on the Query Library meet the selection criteria indicated on the control card. For example, a request to remove any library members that have not been used since 12/31/80 can yield no output because the product was not purchased until 1982.
Action:
Review the parameters entered on the control card to verify accuracy. Transposed numbers or misspelled names could cause a fruitless search.
Reason:
You specified that a language was to be unloaded, but no items for the specified language were found.
Action:
Verify that the language code you entered is valid and actually contains translated items.
Reason:
A REPORT card must immediately precede the first (or only) USER card in a group of USER cards. The USER cards specify that the named report be produced only for the users listed. A USER card was not preceded by a REPORT card in your input stream.
Action:
Code a REPORT card as the card immediately preceding the first USER card that refers to that report. Code any remaining USER cards that refer to that report immediately following the first USER card.
Reason:
A REPORT card must immediately precede the first (or only) USER card in a group of USER cards. The USER cards specify that the named report be produced only for the users listed. A USER card was not preceded by a REPORT card in your input stream.
Action:
Code a REPORT card as the card immediately preceding the first USER card that refers to that report. Code any remaining USER cards that refer to that report immediately following the first USER card.
Reason:
No RUNTYPE= keyword was found on the input card.
Action:
You must have a RUNTYPE=L/LOAD/U/UNLOAD on each input card. Correct the card, and rerun the job.
Reason:
No card was found specifying the type of maintenance desired. Valid types are ADD, UPDATE, DELETE, and REPORT.
Action:
Correct the input and resubmit the job.
Reason:
The function requested was not authorized by external security.
Action:
Make sure the necessary authorization is in place in the external security package and resubmit the job.
Reason:
The function requested was not authorized by external security.
Action:
Make sure the necessary authorization is in place in the external security package and resubmit the job.
Reason:
Your input card had no syntax errors, or, DQLIBRMT successfully processed the input control card that follows this message.
Action:
None is required. This message is informational only.
Reason:
Your input card had no syntax errors, or, DQLIBRMT successfully processed the input control card that follows this message.
Action:
None is required. This message is informational only.
Reason:
Your input card had no syntax errors.
Action:
None. This message is informational only.
Reason:
At least one input card contained an error. Messages with cards in error indicate what the errors were.
Action:
Fix the cards in error and resubmit those cards to process.
Reason:
An error was encountered while executing an IBM macro, LINK. Other error messages were written to the JES (Job Entry System) Log.
Action:
Follow the directions for your job responsibilities:
End User
Contact your CA Dataquery Administrator for assistance. Describe the error and what you were attempting when the error occurred.
CA Dataquery Administrator
Contact your systems programmer and describe the error that was received.
Systems Programmer
Check the JES (Job Entry System) Log for other error messages. See the IBM documentation for the meaning of these errors and follow the instructions found there.
Reason:
A program module in CA Dataquery batch received a nonzero return code from z/OS after execution of the STAE macro. The return code is included in this message.
Action:
Follow the directions for your job responsibilities:
End User
Contact your CA Dataquery Administrator for assistance. Describe the error and the return code displayed in the message.
CA Dataquery Administrator
Contact your systems programmer and describe the error and the return code displayed in the message.
Systems Programmer
See IBM documentation for the meaning of the return code. Follow the instructions found there to correct the condition; CA Dataquery batch cannot execute until the error has been resolved.
Reason:
An error condition has caused abnormal termination of CA Dataquery batch, and a data set, required to produce a snap dump of program storage (DDNAME=SNAPER), could not be opened for ABEND processing. As a result, no snap dump of the abnormal termination will be produced.
Action:
Follow the directions for your job responsibilities:
End User
Contact your CA Dataquery Administrator for assistance. Describe the error you received and what you were attempting to do when you received the error.
CA Dataquery Administrator
Check the JCL member that was used for the CA Dataquery batch job; there should be a DD statement for SNAPER. For further assistance, contact your systems programmer and describe the error.
Systems Programmer
Make sure that the JCL used for CA Dataquery batch contains a DD statement for SNAPER. This should be a SYSOUT data set.
Reason:
The panel name must be a three-character panel name, such as "NAME=D10".
Action:
Correct the input card and resubmit.
Reason:
The function named was not authorized for the user by the external security package.
Action:
Make sure the necessary authorization is in place in the external security package and resubmit.
Reason:
Processing is complete for the requested report.
Action:
None is required. This mesage is infomational only.
Reason:
This message specifies the end of a requested report.
Action:
None. This message is informational only.
Reason:
The function requested was not authorized by external security.
Action:
Make sure the necessary authorization is in place in the external security package and resubmit the job.
Reason:
The function requested was not authorized by external security.
Action:
Make sure the necessary authorization is in place in the external security package and resubmit the job.
Reason:
Each control card has at least one required keyword. The control card that is displayed beside this message on the error report is lacking a required keyword.
Action:
See the CA Dataquery Administrator Guide for a list of required keywords, and select an appropriate one for the function. Note that the BACKUP and the REMOVE cards each have three keywords that are mutually exclusive. Either NAME or GROUP or DATE is required, but only one can be used on the control card.
Reason:
Each control card has at least one required keyword. The control card that is displayed beside this message on the error report is lacking a required keyword.
Action:
See the CA Dataquery Administrator Guide for a list of required keywords, and select an appropriate one for the function. Note that the BACKUP and the REMOVE cards each have three keywords that are mutually exclusive. Either NAME or GROUP or DATE is required, but only one can be used on the control card.
Reason:
The function named was not authorized for the user by the external security package.
Action:
Make sure the necessary authorization is in place in the external security package and resubmit.
Reason:
This message will be accompanied by the DB ERROR 99-99 on fff FILE error message. This message displays the contents of the CA Datacom/DB request area that was being used at the time the error occurred.
Action:
Include the contents of this message with the other information you present your CA Dataquery Administrator when you report the DB ERROR. It will provide valuable information.
Reason:
An error was encountered either in the input cards or during execution.
Action:
See the other messages displayed during the job execution and take any appropriate action to correct the problem.
Reason:
An error was determined to be serious enough to cause the execution of DQUSERMT to be terminated.
Action:
See the message with the input card which was being processed to determine the error which caused the termination.
Reason:
The value after the RUNTYPE= keyword is not L, LOAD, U, or UNLOAD.
Action:
Type L, LOAD, U, or UNLOAD for the RUNTYPE value, and rerun the job.
Reason:
If DQ is externally secured, the signon retrieved from the external security package was not authorized to signon to CA Dataquery. If only the user ID is to be retrieved from the external security, the name was not a valid CA Dataquery user ID.
Action:
Make sure that the necessary authorizations are present and retry the job.
Reason:
If DQ is externally secured, the signon retrieved from the external security package was not authorized to signon to CA Dataquery. If only the user ID is to be retrieved from the external security, the name was not a valid CA Dataquery user ID.
Action:
Make sure that the necessary authorizations are present and retry the job.
Reason:
If DQ is externally secured, the signon retrieved from the external security package was not authorized to signon to CA Dataquery. If only the user ID is to be retrieved from the external security, the name was not a valid CA Dataquery user ID.
Action:
Make sure that the necessary authorizations are present and retry the job.
Reason:
If DQ is externally secured, the signon retrieved from the external security package was not authorized to signon to CA Dataquery. If only the user ID is to be retrieved from the external security, the name was not a valid CA Dataquery user ID.
Action:
Make sure that the necessary authorizations are present and retry the job.
Reason:
The signon retrieved from the external security package is not authorized to signon to CA Dataquery.
Action:
Make sure the necessary authorizations are present and retry the job.
Reason:
The CA Dataquery user ID was retrieved from external security and CA Dataquery has ignored the SIGN/ON card in the input.
Action:
None. This message is informational only.
Reason:
The CA Dataquery user ID was retrieved from external security and CA Dataquery has ignored the SIGN/ON card in the input.
Action:
None. This message is informational only.
Reason:
An error occurred trying to access the database to determine if CA Dataquery is externally secured, or an error occurred trying to access external security.
Action:
Make sure that the database Multi-User Facility is active and, if DQ is externally secured, make sure that the external security is functioning.
Reason:
An error occurred trying to access the database to determine if CA Dataquery is externally secured, or an error occurred trying to access external security.
Action:
Make sure that the database Multi-User Facility is active and, if DQ is externally secured, make sure that the external security is functioning.
Reason:
The BACKUP and REMOVE cards require entry of one, but not more than one, of the following keywords: GROUPS=, NAME=, or DATE=. You will receive this message if you do not use any of these keywords, or if you use more than one of these keywords on a BACKUP or a REMOVE card.
Action:
If you did not code one of these options on the card in question, enter one of them on your BACKUP or REMOVE card. If you want to back up or remove all library members that you can access, you can code GROUPS=ALL.
If you coded more than one of these keyword options on a single card, choose the most important one and code only that keyword.
Reason:
The current run has been terminated by a severe error detected in the external security package interface.
Action:
Determine the cause of the error, possibly from other messages, perform the appropriate changes, and retry the job.
Reason:
A sign/on card must precede all other input cards.
Action:
Include a sign/on card as the first card in your input and resubmit the job.
Reason:
The sign/on card was successfully processed.
Action:
None. This message is informational only.
Reason:
You did not use the proper format on your SIGN/ON card. The proper format is:
SIGN/ON userid PASSWORD password
The SIGN/ON card must be the first one in the set of control cards, and can appear only once in any execution of the DQLIBRMT utility.
Action:
Rewrite your SIGN/ON card to conform to the format described above and resubmit the job.
Reason:
You did not use the proper format on your SIGN/ON card. The proper format is:
SIGN/ON userid PASSWORD password
The SIGN/ON card must be the first one in the set of control cards, and can appear only once in any execution of the DQLIBRMT utility.
Action:
Rewrite your SIGN/ON card to conform to the format described above and resubmit the job.
Reason:
The password you coded on the SIGN/ON card does not match the password found in your user profile.
Action:
Review the spelling you used on your SIGN/ON card to verify that it is spelled correctly. If you cannot remember your password, contact your CA Dataquery Administrator for assistance.
Reason:
The password you coded on the SIGN/ON card does not match the password found in your user profile.
Action:
Review the spelling you used on your SIGN/ON card to verify that it is spelled correctly. If you cannot remember your password, contact your CA Dataquery Administrator for assistance.
Reason:
There is an error in your input card. It must be coded DQF or "DQW xx", where xx is the number of DQW partitions wanted.
Action:
Correct the card to match the format described above.
Reason:
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.
Reason:
The suffix name must be a three-character panel name, such as "NAME=D10."
Action:
Correct the input card and resubmit.
Reason:
You did not code the TITLE= keyword on the REPORT card. This is a required keyword.
Action:
Code TITLE=DIRECTORY or TITLE=QUERYTEXT on the REPORT cards in your set of input control cards.
Reason:
You did not code the TITLE= keyword on the REPORT card. This is a required keyword.
Action:
Code TITLE=DIRECTORY or TITLE=QUERYTEXT on the REPORT cards in your set of input control cards.
Reason:
Up to 20 continuation cards can be used. Your input contained more than this number.
Action:
Correct the input and resubmit the job.
Reason:
DQLIBRMT expects to find keywords and keyword values in columns 11 through 72, separated by commas. A complete list of keywords that are valid for each control function can be found in the CA Dataquery Administrator Guide. DQLIBRMT expected to find a keyword, but the word found is not on the list of valid keywords.
Action:
Place all keywords and the values assigned to those keywords in columns 11 through 72. Eliminate any spaces between keywords or values in columns 11 through 72. For each function, use only keywords that are valid for that function. Use an equal sign (=) to separate a keyword and its first value.
Reason:
DQLIBRMT expects to find keywords and keyword values in columns 11 through 72, separated by commas. A complete list of keywords that are valid for each control function can be found in the CA Dataquery Administrator Guide. DQLIBRMT expected to find a keyword, but the word found is not on the list of valid keywords.
Action:
Place all keywords and the values assigned to those keywords in columns 11 through 72. Eliminate any spaces between keywords or values in columns 11 through 72. For each function, use only keywords that are valid for that function. Use an equal sign (=) to separate a keyword and its first value.
Reason:
One of the input control cards does not contain a valid function in columns 1 through 10. Valid functions are: SIGN/ON, BACKUP, REMOVE, RESTORE, REPORT, and USER. Blanks must follow the function through column 10, and the keywords must begin in column 11.
Action:
Rewrite the input control card to conform to the format described above. Functions must be spelled exactly as shown, or the program will not recognize the function.
Reason:
One of the input control cards does not contain a valid function in columns 1 through 10. Valid functions are: SIGN/ON, BACKUP, REMOVE, RESTORE, REPORT, and USER. Blanks must follow the function through column 10, and the keywords must begin in column 11.
Action:
Rewrite the input control card to conform to the format described above. Functions must be spelled exactly as shown, or the program will not recognize the function.
Reason:
The requested update of a user was successful.
Action:
None. This message is informational only.
Reason:
The FT OPEN failed because of DB return code "nn."
Action:
See the CA Datacom/DB Message Guide (Part 1) and address the cause of the DB return code.
Reason:
You coded both the GROUPS= and the STATUS= keywords on a RESTORE card but these options are mutually exclusive on a RESTORE card. Neither is required.
Action:
Select and code only one of these keywords or remove both keywords from your RESTORE card.
Reason:
The user ID could not be added to CA Dataquery because the name is already a valid DQ user ID.
Action:
Determine if this should be an update instead of an add.
Reason:
The user ID you entered on the SIGN/ON card cannot be found on the user file.
Action:
Review the spelling you used on your SIGN/ON card to verify that it is spelled correctly. For further assistance, contact your CA Dataquery Administrator.
Reason:
The user ID you entered on the SIGN/ON card cannot be found on the user file.
Action:
Review the spelling you used on your SIGN/ON card to verify that it is spelled correctly. For further assistance, contact your CA Dataquery Administrator.
Reason:
The NAME= keyword was used on a control card, and either no keyword value was assigned, or the value was longer than the 32 character limit.
Action:
Assign a value to the NAME= keyword that is from 1 to 32 characters in length.
Reason:
The NAME= keyword was used on a control card, and either no keyword value was assigned, or the value was longer than the 32 character limit.
Action:
Assign a value to the NAME= keyword that is from 1 to 32 characters in length.
Reason:
The user is not authorized to perform this utility function.
Action:
Secure the necessary authorization and resubmit the job.
Reason:
The user signing on is not authorized to perform user maintenance activities.
Action:
Secure the necessary authorization and resubmit the job.
Reason:
The requested update of a user could not be performed because the name was not a valid DQ user ID.
Action:
Determine if this should be an add instead of an update.
Reason:
The sign/on could not be completed because the user ID given is not a valid CA Dataquery user ID.
Action:
Correct the sign/on card and resubmit.
Reason:
The name or password entered on the SIGN/ON card is invalid.
Action:
Correct the name or password and rerun the job.
|
Copyright © 2014 CA.
All rights reserved.
|
|