Service facilities messages (CSQ1...)
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.
Log services return codes
- 0
- Successful completion
- 4
- Exception condition (for example, end of file), not an error.
- 8
- Unsuccessful completion due to parameter errors.
- 12
- Unsuccessful completion. Error encountered during processing of a valid request.
- CSQ1000I
csect-name IBM® WebSphere® MQ for z/OS® Vn
- Severity
- 0
- Explanation
This message is issued as the first part of the header to the report issued by the log print utility program.
- CSQ1100I
csect-name LOG PRINT UTILITY - date time
- Severity
- 0
- Explanation
This message is issued as the second part of the header to the report issued by the log print utility program.
- CSQ1101I
csect-name UTILITY PROCESSING COMPLETED, RETURN CODE=rc
- Severity
- 0
- Explanation
The log print utility completed with the return code rc indicated. 0 indicates successful completion.
- CSQ1102I
SEARCH CRITERIA
- Severity
- 0
- Explanation
The search criteria specified for printing the log follow.
- CSQ1105I
LOG PRINT UTILITY SUMMARY - date time
- Severity
- 0
- Explanation
This is issued as a header to the summary data set written by the log print utility.
- CSQ1106I
END OF SUMMARY
- Severity
- 0
- Explanation
This marks the end of the summary data set written by the log print utility.
- CSQ1110E
LIMIT OF 50 STATEMENTS EXCEEDED
- Severity
- 8
- Explanation
The limit of 50 input statements allowed by CSQ1LOGP has been exceeded.
- System action
Processing is terminated.
- System programmer response
Resubmit the job using no more than 50 statements.
- CSQ1111E
LIMIT OF 80 TOKENS EXCEEDED
- Severity
- 8
- Explanation
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.
- System action
Processing is terminated.
- System programmer response
Resubmit the job using no more than 80 tokens.
- CSQ1112E
TOKEN xxx... EXCEEDS 48 CHARACTERS
- Severity
- 8
- Explanation
An input statement contains the character string beginning xxx. This string is not valid because it exceeds 48 characters in length.
- System action
Processing is terminated.
- System programmer response
Resubmit the job with a valid token.
- CSQ1113E
INVALID SYNTAX FOR KEYWORD kwd
- Severity
- 8
- Explanation
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).
- System action
Processing is terminated.
- System programmer response
Resubmit the job with the correct form of the keyword.
- CSQ1127E
KEYWORD kwd UNKNOWN
- Severity
- 8
- Explanation
CSQ1LOGP does not recognize the keyword kwd.
- System action
Processing is terminated.
- System programmer response
Check to make sure all keywords are valid and resubmit the job.
- CSQ1128E
END OF LOG RANGE SPECIFIED WITHOUT START
- Severity
- 8
- Explanation
You cannot specify the end of a search range (RBAEND or LRSNEND) without specifying a beginning of the search range (RBASTART or LRSNSTART).
- System action
Processing is terminated.
- System programmer response
Resubmit the job providing an RBASTART or LRSNSTART value to correspond to the RBAEND or LRSNEND value given to specify a valid search range.
- CSQ1129E
LIMIT OF 10 kwd KEYWORDS EXCEEDED
- Severity
- 8
- Explanation
The kwd keyword appears too many times in the control statements. The limit is 10.
- System action
Processing is terminated.
- System programmer response
Resubmit the job providing no more than 10 of these keywords.
- CSQ1130E
INVALID VALUE FOR KEYWORD kwd NUMBER n
- Severity
- 8
- Explanation
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.
- System action
Processing is terminated.
- System programmer response
Resubmit the job providing a correct value specification.
- CSQ1131E
INVALID VALUE FOR KEYWORD kwd
- Severity
- 8
- Explanation
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.
- System action
Processing is terminated.
- System programmer response
Resubmit the job providing a correct value specification.
- CSQ1132E
NO VALUE FOR KEYWORD kwd NUMBER n
- Severity
- 8
- Explanation
The nth occurrence of keyword kwd is not followed by a value.
- System action
Processing is terminated.
- System programmer response
Resubmit the job providing a correct value specification.
- CSQ1133E
NO VALUE FOR KEYWORD kwd
- Severity
- 8
- Explanation
The keyword kwd is not followed by a value.
- System action
Processing is terminated.
- System programmer response
Resubmit the job providing a correct value specification.
- CSQ1134E
KEYWORD EXTRACT REQUIRES AT LEAST ONE OUTPUT DDNAME
- Severity
- 4
- Explanation
The keyword extract requires at least one output DDNAME for log records to be extracted.
- System action
Processing continues, however, no log records are extracted .
- System programmer response
Remove EXTRACT(YES), or alternatively add a DDNAME from the following list: CSQBACK, CSQCMT, CSQBOTH, CSQINFLT, CSQOBJS. Resubmit the job. For more information see, The log print utility (CSQ1LOGP).
- CSQ1135E
KEYWORD kwd SPECIFIED MORE THAN ONCE
- Severity
- 8
- Explanation
The keyword kwd can only be specified once.
- System action
Processing is terminated.
- System programmer response
Resubmit the job providing only one of these keywords.
- CSQ1137I
FIRST PAGE SET CONTROL RECORD AFTER RESTART = r-rba
- Severity
- 0
- Explanation
r-rba is the log RBA of a record that serves as an implicit indication that a restart occurred just prior to this point.
- System action
Processing continues.
- CSQ1138E
- kwd1 AND kwd2 CANNOT BOTH BE SPECIFIED
- Explanation
kwd1 and kwd2 cannot both appear in the control statements.
- System action
Processing is terminated.
- System programmer response
Correct the control statements and rerun the job.
- CSQ1139E
SYSSUMRY DD STATEMENT MISSING
- Severity
- 8
- Explanation
You requested the SUMMARY option, but did not include the SYSSUMRY DD statement in your JCL.
- System action
Processing terminates.
- System programmer response
Resubmit the job with a SYSSUMRY DD statement included in the JCL.
- CSQ1145E
CURRENT RESTART TIME STAMP OUT OF SEQUENCE - TIME=date time LOG RBA=t-rba
- Severity
- 4
- Explanation
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.
- System action
Processing continues.
- System programmer response
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.
- CSQ1146E
CURRENT END CHECKPOINT TIME STAMP OUT OF SEQUENCE - TIME=date time LOG RBA=t-rba
- Severity
- 4
- Explanation
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.
- System action
Processing continues.
- System programmer response
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.
- CSQ1147I
LATEST TIME STAMP SEEN SO FAR - TIME=date time LOG RBA=t-rba
- Severity
- 4
- Explanation
This message follows message CSQ1145I or CSQ1146I and gives the latest time stamp seen.
- CSQ1148I
MULTIPLE QUEUE MANAGERS MAY BE WRITING TO THE SAME LOG
- Severity
- 4
- Explanation
This message follows message CSQ1145I or CSQ1146I to indicate a possible cause of the time stamp problem.
- CSQ1150I
SUMMARY OF COMPLETED EVENTS
- Severity
- 0
- Explanation
This message heads the summary of completed units of recovery (URs) and checkpoints.
- System action
Processing continues.
- CSQ1151I
UR CONNID=cc THREAD-XREF=bb USERID=aa TIME=date time START=s-rba END=e-rba DISP=xx INFO=ii
- Severity
- 0
- Explanation
- This message describes a unit of recovery that terminated.
- cc
- Connection id (for example, BATCH)
- bb
- Thread cross-reference id (for example, JOB xxx)
- aa
- User id executing the UR
- date time
- Starting time of the UR
- s-rba
- Log RBA of the first log record associated with the UR (that is, the URID)
- e-rba
- Log RBA of the last log record associated with the UR If the UR is not complete, e-rba is shown as '***'
- xx
- Disposition of the UR, values include:
- INFLIGHT
- IN BACKOUT
- IN COMMIT
- INDOUBT
- COMMITTED
- BACKED OUT
- ii
- Status of the data, one of the following:
- COMPLETE, indicating that all page sets modified by this UR have been identified
- PARTIAL, indicating that the list of page sets modified by this UR is incomplete (this is shown if all records associated with a UR are not available, and no checkpoint is found prior to the UR's completion)
- System action
Processing continues.
- CSQ1153I
CHECKPOINT START=s-rba END=e-rba TIME=date time
- Severity
- 0
- Explanation
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.
- System action
Processing continues.
- CSQ1154I
RESTART AT r-rba TIME=date time
- Severity
- 0
- Explanation
A normal restart occurred at log RBA r-rba. CSQ1LOGP also returns the date and time of that restart.
- System action
Processing continues.
- CSQ1155I
CONDITIONAL RESTART AT r-rba TIME=date time
- Severity
- 0
- Explanation
A conditional restart occurred at log RBA r-rba. CSQ1LOGP also returns the date and time of that restart.
- System action
Processing continues.
- CSQ1156I
ALL URS COMPLETE
- Severity
- 0
- Explanation
There are no URs outstanding for restart.
- System action
Processing continues.
- CSQ1157I
RESTART SUMMARY
- Severity
- 0
- Explanation
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 Problem determination on z/OS for information about identifying and reporting the problem.
- System action
Processing continues.
- CSQ1158I
NO CHECKPOINT AVAILABLE - RESTART SUMMARY INCOMPLETE
- Severity
- 0
- Explanation
- No checkpoint is available within the scope of the log scanned. The information following this message includes:
- URs that have not completed
- Page sets modified by these URs
- Page sets with writes pending
- System action
Processing continues.
- CSQ1161E
INVALID URE FOUND AT x-rba
- Severity
- 4
- Explanation
While processing the SUMMARY option, an invalid URE checkpoint record was encountered in the log.
- System action
Processing continues.
- System programmer response
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.
- CSQ1162E
INVALID RURE FOUND AT x-rba
- Severity
- 4
- Explanation
While processing the SUMMARY option, an invalid RURE checkpoint record was encountered in the log.
- System action
Processing continues.
- System programmer response
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.
- CSQ1163E
NO CHECKPOINT AVAILABLE DUE TO LOG ERROR - RESTART SUMMARY INCOMPLETE
- Severity
- 4
- Explanation
- 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:
- URs that have not completed
- Page set modified by these URs
- Page sets with writes pending
- System action
Processing continues.
- CSQ1165E
UR REQUIRES LOG WHICH IS IN ERROR
- Severity
- 0
- Explanation
While processing a UR, information was required from the log, but the log was in error, as indicated by previous messages.
- System action
Processing continues.
- CSQ1166I
INFORMATION INCOMPLETE FOR UR - LOG TRUNCATED AT xx
- Severity
- 0
- Explanation
Complete information for the UR is not available within the scope of the log scanned.
- System action
Processing continues.
- CSQ1209E
END OF LOG RANGE IS LESS THAN START
- Severity
- 8
- Explanation
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).
- System action
Processing is terminated.
- System programmer response
Resubmit the job providing an RBASTART or LRSNSTART value and a corresponding RBAEND or LRSNEND value to specify a valid search range.
- CSQ1210E
LOG READ ERROR RETCODE=rc REASON CODE=reason
- Severity
- 8
- Explanation
An error was detected while attempting to read the log.
- System action
Processing is terminated.
- CSQ1211E
BAD LOG RBA RETURNED
- Severity
- 8
- Explanation
- One of the three problems listed in this topic exists:
- The recovery log data set is damaged
- You identified a data set that is not a recovery log data set
- There is a problem with the log print utility
- System action
Processing terminates, and a dump is produced.
- System programmer response
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.
- CSQ1212I
FIRST LOG RBA ENCOUNTERED = s-rba
- Severity
- 0
- Explanation
This identifies the RBA of the first log record read.
- System action
Processing continues.
- CSQ1213I
LAST LOG RBA ENCOUNTERED = e-rba
- Severity
- 0
- Explanation
This identifies the RBA of the last log record read.
- System action
Processing continues.
- CSQ1214I
nn LOG RECORDS READ
- Severity
- 0
- Explanation
This identifies the number (in decimal) of logical log records read during CSQ1LOGP processing.
- System action
Processing continues.
- CSQ1215I
NO LOG RECORDS READ
- Severity
- 0
- Explanation
CSQ1LOGP read no log records.
Possible explanations are:- An error has prevented CSQ1LOGP from continuing, therefore no log records have yet been processed (if this is so, an error message should precede this message)
- You specified the active log data sets or archive log data sets out of RBA sequence
- You specified an RBASTART or LRSNSTART value that is greater than any RBA or LRSN in the active and archive data sets available
- You specified a log range using LRSNs, but the queue manager is not in a queue-sharing group.
- System action
Processing continues.
- CSQ1216E
LOG READ ERROR, RETCODE=rc, REASON CODE=reason, RBA=x-rba
- Severity
- 4
- Explanation
- 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:
- The start of the CI if there is a problem with the log control interval definition (LCID), or with any of the general control information within a CI
- The log record in the CI if there is a problem with a log record header (LRH)
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.
- System action
Processing continues.
- CSQ1217E
RBA RANGE WARNING, RETCODE=rc, REASON CODE=reason, PRIOR RBA=p-rba, CURRENT RBA=c-rba
- Severity
- 4
- Explanation
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.
- System action
Processing continues.
- CSQ1218I
nn LOG ERROR MESSAGES
- Severity
- 0
- Explanation
- CSQ1LOGP distinguishes three classes of errors:
- Code problems existing in the MQ or system code used for CSQ1LOGP. In such cases, abnormal termination with a user completion code of U0153 occurs.
- Incorrect invocation of CSQ1LOGP caused, perhaps, by your having used an incorrect keyword or missed a DD statement. Under these circumstances, CSQ1LOGP issues appropriate error messages, and the program is terminated.
- An error in a particular log CI under the scrutiny of CSQ1LOGP.
Such scrutiny is performed before any of the records within the CI
are processed. This is an indication of logical damage, and error
messages are issued by the utility. The CI or log record in error
is printed, and CSQ1LOGP continues to the next CI or log record.
The count nn provided summarizes the number (in decimal) of errors CSQ1LOGP detected while accessing the log.
- System action
Processing continues.
- CSQ1219I
-
LOG RECORDS CONTAIN n BYTE RBA - QSG(in-qsg)
- Severity
- 0
- Explanation
-
This message is issued by CSQ1LOGP to indicate the format of the log records being processed, and whether the queue manager was a member of a queue-sharing group (QSG). The message is issued before any log records are printed, and whenever the format of the log records change.
The value of n identifies the log RBA format of the log records being processed, and can be either 6 or 8.
The value of in-qsg identifies whether the log records were written by a queue manager that was a member of a QSG, and can be one of the following values:- YES
- The log records were written by a queue manager that was a member of a QSG
- NO
- The log records were written by a queue manager that was not a member of a QSG
- System action
- Processing continues
- CSQ1220E
ARCHIVE LOG TRUNCATED AT xxxx - INVALID LOG RECORDS READ
- Severity
- 4
- Explanation
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.
- System action
Processing continues.
- System programmer response
To avoid this condition, use the BSDS DD statement instead of the ARCHIVE DD statement.
- CSQ1221E
VSAM ERROR, RETCODE=rc, REASON CODE=reason,VSAM RETURN CODE=aaaa, ERROR CODE=bbbb
- Severity
- 8
- Explanation
A VSAM error was encountered while attempting to read the log.
- System action
Processing continues.
- CSQ1222E
LOG ALLOCATION ERROR, RETCODE=rc, REASON CODE=reason, DYNALLOC INFO CODE=aaaa, ERROR CODE=bbbb
- Severity
- 8
- Explanation
An error occurred while dynamically allocating a log data set.
- System action
Processing terminates.
- CSQ1223E
JFCB READ ERROR, RETCODE=rc, REASON CODE=reason, RDJFCB RETURN CODE=aaaa
- Severity
- 8
- Explanation
An error occurred while trying to read the job file control block.
- System action
Processing continues.
- CSQ1224I
INFORMATION INCOMPLETE FOR LOG RECORD, CURRENT RBA=c-rba, CURRENT URID=c-urid
- Severity
- 0
- Explanation
Incomplete information for the log record was found within the scope of the logs scanned. An end of log condition was encountered before all segments of a spanned record could be found. CURRENT RBA c-rba indicates the log RBA of the record in question. CURRENT URID c-urid indicates the UR to which the spanned log record is related. If there is no URID associated with the log record (for instance, a checkpoint record), then this will show zeros.
- System action
Processing continues.
- System programmer response
If complete information for the identified log record is required, extend the RBA range to be processed until the required log data is available.
- CSQ1271I
START OF LOG RANGE SET TO LRSN=s-lrsn
- Severity
- 0
- Explanation
The LRSN value you specified for the start of the log range is less than the lowest possible LRSN value, which is s-lrsn.
- System action
Processing continues, using an LRSNSTART value of s-lrsn.
- CSQ1272I
FIRST LOG LRSN ENCOUNTERED = s-lrsn
- Severity
- 0
- Explanation
This identifies the LRSN of the first log record read.
- System action
Processing continues.
- CSQ1273I
LAST LOG LRSN ENCOUNTERED = e-lrsn
- Severity
- 0
- Explanation
This identifies the LRSN of the last log record read.
- System action
Processing continues.
- CSQ1275I
LRSN RANGE CAN BE USED ONLY WITH A QUEUE-SHARING GROUP
- Severity
- 0
- Explanation
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.
- System action
Processing continues.
- System programmer response
If the queue manager is not in a queue-sharing group, rerun the job using RBA specifications for the log range.
- CSQ1276E
LOG READ ERROR, RETCODE=rc, REASON CODE=reason, LRSN=x-lrsn
- Severity
- 4
- Explanation
- 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:
- The start of the CI if there is a problem with the log control interval definition (LCID), or with any of the general control information within a CI
- The log record in the CI if there is a problem with a log record header (LRH)
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.
- System action
Processing continues.
- CSQ1277E
LRSN RANGE WARNING, RETCODE=rc, REASON CODE=reason, PRIOR LRSN=p-lrsn, CURRENT LRSN=c-lrsn
- Severity
- 4
- Explanation
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.
- System action
Processing continues.