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.

CSQ1000I

csect-name IBM WebSphere MQ for z/OS version

Explanation:

This message is issued as the first part of the header to the report issued by the log print utility program.

Severity:

CSQ1100I

csect-name LOG PRINT UTILITY - date time

Explanation:

This message is issued as the second part of the header to the report issued by the log print utility program.

Severity:

CSQ1101I

csect-name UTILITY PROCESSING COMPLETED, RETURN CODE=rc

Explanation:

The log print utility completed with the return code rc indicated. 0 indicates successful completion.

Severity:

CSQ1102I

SEARCH CRITERIA

Explanation:

The search criteria specified for printing the log follow.

Severity:

CSQ1105I

LOG PRINT UTILITY SUMMARY - date time

Explanation:

This is issued as a header to the summary data set written by the log print utility.

Severity:

CSQ1106I

END OF SUMMARY

Explanation:

This marks the end of the summary data set written by the log print utility.

Severity:

CSQ1110E

LIMIT OF 50 STATEMENTS EXCEEDED

Explanation:

The limit of 50 input statements allowed by CSQ1LOGP has been exceeded.

Severity:

System Action:

Processing is terminated.

System Programmer Response:

Resubmit the job using no more than 50 statements.

CSQ1111E

LIMIT OF 80 TOKENS EXCEEDED

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.

Severity:

System Action:

Processing is terminated.

System Programmer Response:

Resubmit the job using no more than 80 tokens.

CSQ1112E

TOKEN xxx... EXCEEDS 48 CHARACTERS

Explanation:

An input statement contains the character string beginning xxx. This string is not valid because it exceeds 48 characters in length.

Severity:

System Action:

Processing is terminated.

System Programmer Response:

Resubmit the job with a valid token.

CSQ1113E

INVALID SYNTAX FOR KEYWORD kwd

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).

Severity:

System Action:

Processing is terminated.

System Programmer Response:

Resubmit the job with the correct form of the keyword.

CSQ1127E

KEYWORD kwd UNKNOWN

Explanation:

CSQ1LOGP does not recognize the keyword kwd.

Severity:

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

Explanation:

We cannot specify the end of a search range (RBAEND or LRSNEND) without specifying a beginning of the search range (RBASTART or LRSNSTART respectively).

Severity:

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

Explanation:

The kwd keyword appears too many times in the control statements. The limit is 10.

Severity:

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

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.

Severity:

System Action:

Processing is terminated.

System Programmer Response:

Resubmit the job providing a correct value specification.

CSQ1131E

INVALID VALUE FOR KEYWORD kwd

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.

Severity:

System Action:

Processing is terminated.

System Programmer Response:

Resubmit the job providing a correct value specification.

CSQ1132E

NO VALUE FOR KEYWORD kwd NUMBER n

Explanation:

The nth occurrence of keyword kwd is not followed by a value.

Severity:

System Action:

Processing is terminated.

System Programmer Response:

Resubmit the job providing a correct value specification.

CSQ1133E

NO VALUE FOR KEYWORD kwd

Explanation:

The keyword kwd is not followed by a value.

Severity:

System Action:

Processing is terminated.

System Programmer Response:

Resubmit the job providing a correct value specification.

CSQ1135E

KEYWORD kwd SPECIFIED MORE THAN ONCE

Explanation:

The keyword kwd can only be specified once.

Severity:

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

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.

Severity:

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

Explanation:

You requested the SUMMARY option, but did not include the SYSSUMRY DD statement in your JCL.

Severity:

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

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.

Severity:

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

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.

Severity:

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

Explanation:

This message follows message CSQ1145I or CSQ1146I and gives the latest time stamp seen.

Severity:

CSQ1148I

MULTIPLE QUEUE MANAGERS MAY BE WRITING TO THE SAME LOG

Explanation:

This message follows message CSQ1145I or CSQ1146I to indicate a possible cause of the time stamp problem.

Severity:

CSQ1150I

SUMMARY OF COMPLETED EVENTS

Explanation:

This message heads the summary of completed units of recovery (URs) and checkpoints.

Severity:

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

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)

If the UR identifying information is not available, it will be shown as '***'.

Severity:

System Action:

Processing continues.

CSQ1153I

CHECKPOINT START=s-rba END=e-rba TIME=date time

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.

Severity:

System Action:

Processing continues.

CSQ1154I

RESTART AT r-rba TIME=date time

Explanation:

A normal restart occurred at log RBA r-rba. CSQ1LOGP also returns the date and time of that restart.

Severity:

System Action:

Processing continues.

CSQ1155I

CONDITIONAL RESTART AT r-rba TIME=date time

Explanation:

A conditional restart occurred at log RBA r-rba. CSQ1LOGP also returns the date and time of that restart.

Severity:

System Action:

Processing continues.

CSQ1156I

ALL URS COMPLETE

Explanation:

There are no URs outstanding for restart.

Severity:

System Action:

Processing continues.

CSQ1157I

RESTART SUMMARY

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 the WebSphere MQ for z/OS Problem Determination Guide for information about identifying and reporting the problem.

Severity:

System Action:

Processing continues.

CSQ1158I

NO CHECKPOINT AVAILABLE - RESTART SUMMARY INCOMPLETE

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

The information cannot be considered complete.

Severity:

System Action:

Processing continues.

CSQ1161E

INVALID URE FOUND AT x-rba

Explanation:

While processing the SUMMARY option, an invalid URE checkpoint record was encountered in the log.

Severity:

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

Explanation:

While processing the SUMMARY option, an invalid RURE checkpoint record was encountered in the log.

Severity:

System Action:

Processing continues.

System Programmer Response:

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

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

This information cannot be considered complete.

Severity:

System Action:

Processing continues.

CSQ1165E

UR REQUIRES LOG WHICH IS IN ERROR

Explanation:

While processing a UR, information was required from the log, but the log was in error, as indicated by previous messages.

Severity:

System Action:

Processing continues.

CSQ1166I

INFORMATION INCOMPLETE FOR UR - LOG TRUNCATED AT xx

Explanation:

Complete information for the UR is not available within the scope of the log scanned.

Severity:

System Action:

Processing continues.

CSQ1209E

END OF LOG RANGE IS LESS THAN START

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 respectively).

Severity:

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

Explanation:

An error was detected while attempting to read the log.

Severity:

System Action:

Processing is terminated.

Problem Determination:

Refer to Log services return codes for information about the return code included in the message, and Codes for information about the reason code.

CSQ1211E

BAD LOG RBA RETURNED

Explanation:

One of the three problems listed below 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

Severity:

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

Explanation:

This identifies the RBA of the first log record read.

Severity:

System Action:

Processing continues.

CSQ1213I

LAST LOG RBA ENCOUNTERED = e-rba

Explanation:

This identifies the RBA of the last log record read.

Severity:

System Action:

Processing continues.

CSQ1214I

nn LOG RECORDS READ

Explanation:

This identifies the number (in decimal) of logical log records read during CSQ1LOGP processing.

Severity:

System Action:

Processing continues.

CSQ1215I

NO LOG RECORDS READ

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.

Severity:

System Action:

Processing continues.

CSQ1216E

LOG READ ERROR, RETCODE=rc, REASON CODE=reason, RBA=x-rba

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.

Severity:

System Action:

Processing continues.

Problem Determination:

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.

CSQ1217E

RBA RANGE WARNING, RETCODE=rc, REASON CODE=reason, PRIOR RBA=p-rba, CURRENT RBA=c-rba

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.

Severity:

System Action:

Processing continues.

Problem Determination:

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.

CSQ1218I

nn LOG ERROR MESSAGES

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 will occur.
Incorrect invocation of CSQ1LOGP caused, perhaps, by your having used an incorrect keyword or missed a DD statement. Under these circumstances, CSQ1LOGP will issue appropriate error messages, and the program will be terminated.
An error in a given 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.

Severity:

System Action:

Processing continues.

CSQ1220E

ARCHIVE LOG TRUNCATED AT xxxx - INVALID LOG RECORDS READ

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.

Severity:

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

Explanation:

A VSAM error was encountered while attempting to read the log.

Severity:

System Action:

Processing continues.

Problem Determination:

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.

CSQ1222E

LOG ALLOCATION ERROR, RETCODE=rc, REASON CODE=reason, DYNALLOC INFO CODE=aaaa, ERROR CODE=bbbb

Explanation:

An error occurred while dynamically allocating a log data set.

Severity:

System Action:

Processing terminates.

Problem Determination:

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.

CSQ1223E

JFCB READ ERROR, RETCODE=rc, REASON CODE=reason, RDJFCB RETURN CODE=aaaa

Explanation:

An error occurred while trying to read the job file control block.

Severity:

System Action:

Processing continues.

Problem Determination:

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.

CSQ1271I

START OF LOG RANGE SET TO LRSN=s-lrsn

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.

Severity:

System Action:

Processing continues, using an LRSNSTART value of s-lrsn.

CSQ1272I

FIRST LOG LRSN ENCOUNTERED = s-lrsn

Explanation:

This identifies the LRSN of the first log record read.

Severity:

System Action:

Processing continues.

CSQ1273I

LAST LOG LRSN ENCOUNTERED = e-lrsn

Explanation:

This identifies the LRSN of the last log record read.

Severity:

System Action:

Processing continues.

CSQ1275I

LRSN RANGE CAN BE USED ONLY WITH A QUEUE-SHARING GROUP

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 we cannot use LRSN specifications.

Severity:

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

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.

Severity:

System Action:

Processing continues.

Problem Determination:

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.

CSQ1277E

LRSN RANGE WARNING, RETCODE=rc, REASON CODE=reason, PRIOR LRSN=p-lrsn, CURRENT LRSN=c-lrsn