The value shown for severity in the service facility messages that follow is the value returned as the job-step condition code from the job-step during which the message is issued. If additional messages having higher severity values are issued during the same job-step, the higher value is reflected as the job-step condition code.
This message is issued as the first part of the header to the report issued by the log print utility program.
0
This message is issued as the second part of the header to the report issued by the log print utility program.
0
The log print utility completed with the return code rc indicated. 0 indicates successful completion.
0
The search criteria specified for printing the log follow.
0
This is issued as a header to the summary data set written by the log print utility.
0
This marks the end of the summary data set written by the log print utility.
0
The limit of 50 input statements allowed by CSQ1LOGP has been exceeded.
8
Processing is terminated.
Resubmit the job using no more than 50 statements.
The limit of 80 keywords and corresponding value specifications allowed by CSQ1LOGP has been exceeded. A keyword with its value is considered as two tokens.
8
Processing is terminated.
Resubmit the job using no more than 80 tokens.
An input statement contains the character string beginning xxx. This string is not valid because it exceeds 48 characters in length.
8
Processing is terminated.
Resubmit the job with a valid token.
An input statement contains the keyword kwd. The value specified for this keyword is not valid, because it is not of the form kwd(value).
8
Processing is terminated.
Resubmit the job with the correct form of the keyword.
CSQ1LOGP does not recognize the keyword kwd.
8
Processing is terminated.
Check to make sure all keywords are valid and resubmit the job.
You cannot specify the end of a search range (RBAEND or LRSNEND) without specifying a beginning of the search range (RBASTART or LRSNSTART respectively).
8
Processing is terminated.
Resubmit the job providing an RBASTART or LRSNSTART value to correspond to the RBAEND or LRSNEND value given to specify a valid search range.
The kwd keyword appears too many times in the control statements. The limit is 10.
8
Processing is terminated.
Resubmit the job providing no more than 10 of these keywords.
The value for the nth occurrence of keyword kwd is invalid because it has invalid characters, it is not one of a list of permitted values, or it is too long.
8
Processing is terminated.
Resubmit the job providing a correct value specification.
The value for the keyword kwd is invalid because it has invalid characters, it is not one of a list of permitted values, or it is too long.
8
Processing is terminated.
Resubmit the job providing a correct value specification.
The nth occurrence of keyword kwd is not followed by a value.
8
Processing is terminated.
Resubmit the job providing a correct value specification.
The keyword kwd is not followed by a value.
8
Processing is terminated.
Resubmit the job providing a correct value specification.
The keyword kwd can only be specified once.
8
Processing is terminated.
Resubmit the job providing only one of these keywords.
r-rba is the log RBA of a record that serves as an implicit indication that a restart occurred just prior to this point.
0
Processing continues.
kwd1 and kwd2 cannot both appear in the control statements.
Processing is terminated.
Correct the control statements and rerun the job.
You requested the SUMMARY option, but did not include the SYSSUMRY DD statement in your JCL.
8
Processing terminates.
Resubmit the job with a SYSSUMRY DD statement included in the JCL.
This message indicates that the current log record has a time stamp that is less than the greatest time stamp processed so far. This might be a potential problem.
This message is followed by messages CSQ1147I and CSQ1148I which give the latest time stamp seen.
4
Processing continues.
Examine the current log to determine whether multiple queue managers are writing to the same log. (Data might be being overwritten.) This might lead to data inconsistencies.
This message indicates that the current log record has a time stamp that is less than the previous time stamp processed. This might be a potential problem.
This message is followed by messages CSQ1147I and CSQ1148I which give the latest time stamp seen.
4
Processing continues.
Examine the current log to determine whether multiple queue managers are writing to the same log. (Data might be being overwritten.) This might lead to data inconsistencies.
This message follows message CSQ1145I or CSQ1146I and gives the latest time stamp seen.
4
This message follows message CSQ1145I or CSQ1146I to indicate a possible cause of the time stamp problem.
4
This message heads the summary of completed units of recovery (URs) and checkpoints.
0
Processing continues.
This message describes a unit of recovery that terminated.
If the UR identifying information is not available, it will be shown as '***'.
0
Processing continues.
This message describes a complete checkpoint on the log starting at RBA s-rba and ending at RBA e-rba. If the information is available, CSQ1LOGP also returns the date and time that the checkpoint was completed.
When this message follows message CSQ1157I, it identifies the checkpoint that would be used at restart. If no checkpoint is available, message CSQ1158I is printed instead.
0
Processing continues.
A normal restart occurred at log RBA r-rba. CSQ1LOGP also returns the date and time of that restart.
0
Processing continues.
A conditional restart occurred at log RBA r-rba. CSQ1LOGP also returns the date and time of that restart.
0
Processing continues.
There are no URs outstanding for restart.
0
Processing continues.
This message heads the summary of the description of work to be performed at restart. Restart information that follows is based on the scope of the log scanned. If you suspect an error in MQ, see the WebSphere MQ for z/OS Problem Determination Guide for information about identifying and reporting the problem.
0
Processing continues.
No checkpoint is available within the scope of the log scanned. The information following this message includes:
The information cannot be considered complete.
0
Processing continues.
While processing the SUMMARY option, an invalid URE checkpoint record was encountered in the log.
4
Processing continues.
If the checkpoint record identified in the message is used to restart the queue manager, the restart will be unsuccessful because it will not be able to process the unit of recovery presented by the invalid URE.
Look for other messages that indicate the cause of the problem. If you are unable to resolve the problem, contact your IBM support center.
While processing the SUMMARY option, an invalid RURE checkpoint record was encountered in the log.
4
Processing continues.
If the checkpoint record identified in the message is used to restart the queue manager, the restart will be unsuccessful because it will not be able to process the unit of recovery presented by the invalid RURE.
Look for other messages that indicate the cause of the problem. If you are unable to resolve the problem, contact your IBM support center.
A log error was encountered. CSQ1LOGP marked any checkpoints encountered before the log error as invalid. There were no complete checkpoints following the log error in the specified log range. The information following this message includes:
This information cannot be considered complete.
4
Processing continues.
While processing a UR, information was required from the log, but the log was in error, as indicated by previous messages.
0
Processing continues.
Complete information for the UR is not available within the scope of the log scanned.
0
Processing continues.
The end log range value (specified by RBAEND or LRSNEND) is less than or equal to the start range value (specified by RBASTART or LRSNSTART respectively).
8
Processing is terminated.
Resubmit the job providing an RBASTART or LRSNSTART value and a corresponding RBAEND or LRSNEND value to specify a valid search range.
An error was detected while attempting to read the log.
8
Processing is terminated.
Refer to Log services return codes for information about the return code included in the message, and Codes for information about the reason code.
One of the three problems listed below exists:
8
Processing terminates, and a dump is produced.
A common error is to specify the first data set on an archive tape (the Bxxxxxxx data set) as a log data set; it is actually a bootstrap data set (BSDS).
Determine if the problem is your error by dumping the data set and determining if it is a log data set.
This identifies the RBA of the first log record read.
0
Processing continues.
This identifies the RBA of the last log record read.
0
Processing continues.
This identifies the number (in decimal) of logical log records read during CSQ1LOGP processing.
0
Processing continues.
CSQ1LOGP read no log records.
Possible explanations are:
0
Processing continues.
An error was encountered while attempting to read the log, indicating that either the log has an error in one of the control intervals (CI), or a data set containing the requested RBA cannot be located. The RBA specification in the message indicates where the error was detected and gives the requested RBA. It will point to:
If this is the first log record read during this execution of the Log Extractor, and if there is a problem with the LCID, the RBA specification will be all zeros.
Before returning any records, the utility checks the control information (LCID) at the end of a CI, and analyzes the LRH to ensure that all records are properly chained together within the CI. If an error is detected while performing this process, CSQ1LOGP will issue this message, before dumping the entire CI. It will not format individual records within the CI, but will, if possible, continue processing by reading the next CI.
4
Processing continues.
The reason code identifies the nature of the error. The return code included in the message is explained in Log services return codes, and the reason code is explained in Codes.
A gap in the log RBA range has been encountered. PRIOR RBA p-rba indicates the last good log RBA prior to the gap. CURRENT RBA c-rba indicates the log record following the gap, and will be formatted following this message.
4
Processing continues.
The reason code identifies the nature of the error. The return code included in the message is explained in Log services return codes, and the reason code is explained in Codes.
CSQ1LOGP distinguishes three classes of errors:
The count nn provided summarizes the number (in decimal) of errors CSQ1LOGP detected while accessing the log.
0
Processing continues.
At a restart of the queue manager, an archive log was truncated. This archive log data set could not be physically altered to reflect this truncation, and invalid log records therefore still exist. CSQ1LOGP has already reported this information in the summary report, and cannot retract it. Nor can it disregard the invalid log information already read in order adequately to summarize what has occurred. Therefore, all information up to this point in the log will be summarized, and a new summary report initiated. Consequently, the same UR might be reported twice with different dispositions and different page sets modified.
4
Processing continues.
To avoid this condition, use the BSDS DD statement instead of the ARCHIVE DD statement.
A VSAM error was encountered while attempting to read the log.
8
Processing continues.
The return code included in the message is explained in Log services return codes, and the reason code in Codes. The VSAM return code (aaaa), and error code (bbbb), identify the nature of the VSAM error. See the DFSMS/MVS Macro Instructions for Data Sets manual for an explanation of these codes.
An error occurred while dynamically allocating a log data set.
8
Processing terminates.
The return code indicated in the message is explained in Log services return codes, and the reason code is explained in Codes. Information code aaaa and error code bbbb were returned by the dynamic allocation SVC and identify the nature of the error. See the MVS Authorized Assembler Services Guide manual for an explanation of these codes.
An error occurred while trying to read the job file control block.
8
Processing continues.
The return code included in the message is explained in Log services return codes, and the reason code is explained in Codes. The RDJFCB return code (aaaa), identifies the nature of the error. See the MVS/ESA DFP System Programming Reference manual for an explanation of these codes.
The LRSN value you specified for the start of the log range is less than the lowest possible LRSN value, which is s-lrsn.
0
Processing continues, using an LRSNSTART value of s-lrsn.
This identifies the LRSN of the first log record read.
0
Processing continues.
This identifies the LRSN of the last log record read.
0
Processing continues.
You specified a log range using LRSNs, but CSQ1LOGP read no log records. This could be because the queue manager is not in a queue-sharing group, in which case you cannot use LRSN specifications.
0
Processing continues.
If the queue manager is not in a queue-sharing group, rerun the job using RBA specifications for the log range.
An error was encountered while attempting to read the log, indicating that either the log has an error in one of the control intervals (CI), or a data set containing the requested LRSN cannot be located. The LRSN specification in the message indicates where the error was detected and gives the requested LRSN. It will point to:
If this is the first log record read during this execution of the Log Extractor, and if there is a problem with the LCID, the LRSN specification will be all zeros.
Before returning any records, the utility checks the control information (LCID) at the end of a CI, and analyzes the LRH to ensure that all records are properly chained together within the CI. If an error is detected while performing this process, CSQ1LOGP will issue this message, before dumping the entire CI. It will not format individual records within the CI, but will, if possible, continue processing by reading the next CI.
4
Processing continues.
The reason code identifies the nature of the error. The return code included in the message is explained in Log services return codes, and the reason code is explained in Codes.
A gap in the log LRSN range has been encountered. The PRIOR LRSN specification indicates the last good log LRSN prior to the gap. The CURRENT LRSN specification indicates the log record following the gap, and will be formatted following this message.
4
Processing continues.
The reason code identifies the nature of the error. The return code included in the message is explained in Log services return codes, and the reason code is explained in Codes.
The return codes set by log services are:
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0422 |