Recovery log manager codes (X'D1')

If a recovery log manager reason code occurs that is not listed here, an internal error has occurred. Collect the following diagnostic items and contact the IBM support center.

Diagnostics

The console output for the period leading up to the error.
The system dump resulting from the error.
If we are using CICS, the CICS transaction dump output.
Appropriate IBM MQ, z/OS, Db2, CICS, and IMS service levels.
A printout of SYS1.LOGREC, if the reason code is issued by an active queue manager.
If the reason code is issued by an active queue manager, a CSQ1LOGP detail report containing the log records associated with the problem.
Contents of the BSDS. Obtain a listing by running the Print Log Map utility (CSQJU004).
The recovery log manager standard diagnostic information, which is provided in the SYS1.LOGREC variable recording area (VRA) of the system diagnostic work area (SDWA) for many of the reason codes:

00D10010

The end log range value specified on an invocation of the log print utility (CSQ1LOGP) is less than or equal to the start range value.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Correct the log range input control parameters specified in the invocation of the log print utility.

For more information about log services, refer to CSQ1LOGP.

00D10011

An invocation of the log print utility (CSQ1LOGP) was unable to obtain the storage required to perform the request.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

It is probable that the REGION parameter on the EXEC statement of the job control language (JCL) for this invocation is too small. Increase the REGION size, and resubmit the log print request.

For more information about log services, refer to Address space storage.

00D10012

An invocation of the log print utility (CSQ1LOGP) was unsuccessful because the job control language (JCL) for this invocation did not specify either the use of the bootstrap data set (BSDS) or, in the absence of the BSDS, the active or archive log data sets.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Correct the JCL and resubmit the log print request.

For more information about BSDS, refer to Manage the BSDS.

00D10013

An invocation of the log print utility (CSQ1LOGP) resulted in a VSAM error while attempting to open the bootstrap data set (BSDS).

This reason code, and the VSAM return code are issued with message CSQ1221E.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Refer to the DFSMS/MVS Macro Instructions for Data Sets to determine the meaning of the VSAM OPEN error. Take appropriate action, and resubmit the log print request.

00D10014

The job control language (JCL) for an invocation of the log print utility (CSQ1LOGP) specified the use of the bootstrap data set (BSDS), but the utility control statements did not specify values for RBASTART and RBAEND.

The RBASTART and RBAEND values must be specified when using the BSDS, although they are not required when using the active or archive logs.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Either:

Continue to use the BSDS, but change the utility control statements to specify values for RBASTART and RBAEND
Change the JCL to use the active and archive data sets instead

For more information, refer to CSQ1LOGP.

00D10015

An invocation of the log print utility (CSQ1LOGP) was unsuccessful because the record format of the bootstrap data set is incompatible with this release of the log print services.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Ensure that the correct release of the log print services are used with the appropriate BSDS record format.

For more information, refer to CSQ1LOGP.

00D10019

An invocation of the log print utility (CSQ1LOGP) resulted in a VSAM error while attempting to open the bootstrap data set (BSDS). The error was determined to be one which could be corrected by use of a VSAM access method services (AMS) VERIFY call, but the VERIFY call was also unsuccessful.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Collect the following items, and contact the IBM support center:

A copy of the user's job control language (JCL) that was used to invoke the log print utility (CSQ1LOGP)
The log data sets that the user was attempting to print

00D10020

The log print utility (CSQ1LOGP) issued this message because the end of data has been reached (that is, the end of the log, or the end of the user-specified data sets, or the user-specified RBAEND value has been reached).

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

This is not an error. This reason code denotes a normal end of data condition. No action is necessary.

For more information, refer to CSQ1LOGP.

00D10021

An invocation of the log print utility (CSQ1LOGP) encountered a gap in the log RBA range when switching log data sets. This indicates that log records might be missing.

Normally, a continuous set of log records is supplied as input by the ACTIVE and ARCHIVE DDnames (or the BSDS DDname if we are using the bootstrap data set (BSDS) to access the log data sets) in the job control language (JCL) used to invoke the utility. If a log data set was removed from the JCL, this condition will arise.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

If the log data set was not removed intentionally, check the JCL to ensure that the log data sets are specified in ascending RBA value order. If we are using the BSDS to access the log data sets, use the print log map utility (CSQJU004) to examine the RBA ranges as recorded in the BSDS, and note any RBA gaps that might have resulted from the deletion of an active or archive log data set.

If it appears that a log error might have occurred, see Active log problems for information about dealing with problems on the log.

00D10022

An invocation of the log print utility (CSQ1LOGP) encountered a gap in the log RBA range when switching log data sets. This indicates that log records might be missing. The log RBA of the next record following the gap is greater than the RBAEND value specified in the utility control statements.

Normally, a continuous set of log records is supplied as input by the ACTIVE and ARCHIVE DDnames (or the BSDS DDname if using the bootstrap data set (BSDS) to access the log data sets) in the job control language (JCL) used to invoke the utility. If a log data set was removed from the JCL, this condition will arise.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Check the JCL and the RBAEND value specified in the utility control statements.

If a log data set was not removed intentionally, check that the log data sets are specified in ascending RBA value order. If using the BSDS to access log data sets, use the print log map utility (CSQJU004) to examine the RBA ranges as recorded in the BSDS, and note any RBA gaps that might have resulted from the deletion of an active or archive log data set.

If it appears that a log error might have occurred, see Active log problems for information about dealing with problems on the log.

00D10024

An invocation of the log print utility (CSQ1LOGP) encountered a log RBA sequence error. The RBA of the previous log record is greater than the RBA of the current log record.

Normally, a continuous set of log records is supplied as input by the ACTIVE and ARCHIVE DDnames (or the BSDS DDname if using the bootstrap data set (BSDS) to access the log data sets) in the job control language (JCL) used to invoke the utility. If a log data set appears out of sequence, this condition will arise.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Check the JCL to ensure that the log data sets are specified in ascending RBA value order. If using the BSDS to access the log data sets, use the print log map utility (CSQJU004) to examine the RBA ranges associated with each archive and active log data set. If both archive and active log data sets are used, the first archive log data set must contain the lowest log RBA value. If necessary, adjust the concatenation of the archive and active log data sets in the JCL to ensure that log records are read in ascending RBA sequence, and resubmit the log print request.

If it appears that a log error might have occurred, see Active log problems for information about dealing with problems on the log.

00D10025

An invocation of the log print utility (CSQ1LOGP) resulted in a VSAM GET error while attempting to read the active log data set.

This reason code, and the VSAM return and reason codes are issued in message CSQ1221E.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Refer to the DFSMS/MVS Macro Instructions for Data Sets to determine the meaning of the VSAM GET error and the RPL error code. Take appropriate action to correct the error, and resubmit the log print request.

00D10026

An invocation of the log print utility (CSQ1LOGP) was unsuccessful because an RBA value within the range specified by RBASTART and RBAEND could not be located on a log data set.

This reason code, and the RBA value that could not be located are issued with message CSQ1216E

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Check the utility control statements to ensure that the RBASTART and RBAEND values have not exceeded the lower or upper bounds of the RBAs available on all the active or archive log data sets defined by DDnames in the JCL.

If we are using the BSDS to access the log data sets, use the print log map utility (CSQJU004) to examine the RBA ranges associated with each archive and active log data set.

Correct the JCL and utility control statements as necessary, and resubmit the log print request.

For more information, refer to CSQ1LOGP.

00D10027

An invocation of the log print utility (CSQ1LOGP) resulted in a VSAM GET error while attempting to read the bootstrap data set (BSDS).

This reason code, and the VSAM return and reason codes, are issued with message CSQ1221E.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Refer to the DFSMS/MVS Macro Instructions for Data Sets manual to determine the meaning of the VSAM GET error and the RPL error code. Take appropriate action to correct the error and resubmit the log print request.

00D1002A

This reason code, and the VSAM return and reason codes, are issued in message CSQ1221E.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Refer to the DFSMS/MVS Macro Instructions for Data Sets manual to determine the meaning of the VSAM OPEN error and the ACB error code. Take appropriate action to correct the error, and resubmit the log print request.

00D1002B

An invocation of the log print utility (CSQ1LOGP) was unsuccessful because an RBA value has been requested in an active log data set that has previously not been opened. A VSAM OPEN error occurred while attempting to open the active log data set. The VSAM OPEN error was determined to be one that could be corrected, however, a system error occurred while executing a z/OS TESTCB macro to determine whether the active log data set in question was a VSAM ESDS (entry-sequenced data set) or a VSAM LDS (linear data set).

This reason code, and the VSAM return and reason codes are issued in message CSQ1221E.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

If the problem persists, collect the following items, and contact the IBM support center:

A copy of the job control language (JCL) used to invoke the log print utility (CSQ1LOGP)
The log data sets that the user was attempting to print

00D1002C

An invocation of the log print utility (CSQ1LOGP) was unsuccessful because an RBA value has been requested in a active log data set that has previously not been opened. A VSAM OPEN error occurred while attempting to open the active log data set. The VSAM OPEN error was determined to be one which could be corrected by use of a VSAM access method services (AMS) VERIFY call, but the VERIFY call was unsuccessful.

This reason code, and the VSAM return and reason codes are issued with message CSQ1221E.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

00D1002D

An invocation of the log print utility (CSQ1LOGP) was unsuccessful because an RBA value has been requested in an active log data set that has previously not been opened. A VSAM OPEN error occurred while attempting to open the active log data set. The VSAM OPEN error was corrected by use of a VSAM access method services (AMS) VERIFY call, but a subsequent attempt to reposition the VSAM pointer back to the beginning of the active log data set (using the VSAM AMS POINT call) was unsuccessful.

This reason code and the VSAM return and reason codes are issued with message CSQ1221E.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Refer to the DFSMS/MVS Macro Instructions for Data Sets manual to determine the meaning of the VSAM OPEN error and the ACB error code. Take the appropriate action to correct the error, and resubmit the print log request.

00D10030

An invocation of the log print utility resulted in an internal error.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Collect the following items, and contact the IBM support center:

A copy of the job control language (JCL) used to invoke the log print utility
The log data sets that the user was attempting to print

00D10031

An invocation of the log print utility (CSQ1LOGP) was unsuccessful because an RBA value has been requested in a log data set that has previously not been opened. The job control language (JCL) has specified that the bootstrap data set (BSDS) be used as the guide to determine which data sets are required. An attempt to allocate the appropriate data set dynamically (using z/OS SVC 99) was unsuccessful.

This reason code, and the dynamic allocation information and error codes (S99INFO and S99ERROR) are issued with message CSQ1222E.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Go to the z/OS MVS™ documentation in Knowledge Center, and select the Interpreting DYNALLOC return codes topic of the MVS Authorized Assembler Services Guide for information about these codes. Take the appropriate action to correct the error, then resubmit the log print request.

00D10040

An invocation of the log print utility (CSQ1LOGP) was unsuccessful because an RBA value has been requested in an archive log data set (on tape) that has previously not been opened. An attempt was made to open the second file on the archive log tape (the first file normally contains the bootstrap data set) but this was unsuccessful because the archive log data set was not the second file on the archive log tape. The read job file control block (RDJFCB) macro was then invoked to attempt to change the data set sequence number from the default value of 2 to a value of 1, before attempting to open the second file again, but the macro invocation resulted in an error.

This reason code, and the RDJFCB return code are issued in message CSQ1223E.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Refer to the MVS/ESA DFP System Programming Reference manual to determine the meaning of the RDJFCB error code. Take the appropriate action to correct the error, and resubmit the log print request.

00D10044: An invocation of the log print utility (CSQ1LOGP) was unsuccessful because an RBA value has been requested in an archive log data set that has previously not been opened. An attempt to open the archive log data set resulted in a QSAM (queued sequential access method) error.
System action: No error is issued by log services, and no information is written to SYS1.LOGREC data set.
System programmer response: Check the console for messages indicating the cause of the QSAM error. Take the appropriate action to correct the error, and resubmit the log print request.

00D10048: An invocation of the log print utility (CSQ1LOGP) was unsuccessful because a QSAM (queued sequential access method) GET error occurred while reading an archive log data set.
System action: No error is issued by log services, and no information is written to SYS1.LOGREC data set.
System programmer response: Check the console for messages indicating the cause of the QSAM error. Take the appropriate action to correct the error, and resubmit the log print request.

00D10050

An invocation of the log print utility (CSQ1LOGP) was unsuccessful because the bootstrap data set (BSDS) was erroneously specified as one of the archive data sets in the job control language (JCL).

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set.

System programmer response

Examine the JCL, and remove the occurrence of the BSDS data set as one of the concatenated ARCHIVE data sets. Resubmit the log print request.

For more information, refer to Archive log problems.

00D10061

An invocation of the log print utility (CSQ1LOGP) succeeded, but an unexpected physical record length was encountered for the log record control interval (CI) for an active or archive log data set.

The data on the log data set might have been corrupted after it was written by IBM MQ. The data in the log data set might still be usable, but with caution.

The length of a log CI in an active log data set is expected to be 4096 bytes. The length of a log CI in an archive log data set is expected to be 4089 bytes.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set. The log print request has completed. This reason code is issued as a warning.

System programmer response

Ensure that the ACTIVE and ARCHIVE DDnames in the job control language (JCL) refer to active and archive logs correctly.

If the problem persists, collect the following items, and contact the IBM support center:

A copy of the job control language (JCL) used to invoke the log print utility (CSQ1LOGP)
The log data set that the user was trying to print

00D10062

An invocation of the log print utility (CSQ1LOGP) succeeded, but the first log record segment could not be found for a middle spanned log record segment.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set. The log print request has completed. This reason code is issued as a warning.

System programmer response

Several possibilities exist for the cause of this condition:

The recovery log manager component of IBM MQ did not originally construct the log record header (LRH) properly
The LRH for the log record segment was damaged after it was written by IBM MQ
The application program continued to process after being informed about a gap in the log RBA values (reason code X'00D10021')

Determine if the LRH of the log record segment is truly in error by looking at the record segments directly preceding and after the record segment in question. Take the appropriate action to correct the error, and resubmit the log print request. If the problem persists, collect the following items, and contact the IBM support center:

A copy of the job control language (JCL) used to invoke the lop print utility (CSQ1LOGP)
The log data set that the user was attempting to print

00D10063

An invocation of the log print utility (CSQ1LOGP) succeeded, but the first log record segment could not be found for a last spanned log record segment.

System action

No error is issued by log services, and no information is written to SYS1.LOGREC data set. The log print request has completed. This reason code is issued as a warning.

System programmer response

Several possibilities exist for the cause of this condition:

The recovery log manager component of IBM MQ did not originally construct the log record header (LRH) properly
The LRH for the log record segment was damaged after it was written by IBM MQ
The application program continued to process after being informed about a gap in the log RBA values (reason code X'00D10021')

Determine if the LRH of the log record segment is truly in error by looking at the record segments directly before and after the record segment in question. Take the appropriate action to correct the error, and resubmit the log print request. If the problem persists, collect the following items, and contact the IBM support center:

A copy of the job control language (JCL) used to invoke the lop print utility (CSQ1LOGP)
The log data set that the user was attempting to print

00D10114: IBM MQ failed to read or write member information in the queue sharing group table, CSQ.ADMIN_B_QSG.
System action: Queue manager initialization terminates.
System programmer response: Investigate Db2 SQL errors reported in the queue manager job log immediately preceding this error, to determine the cause. It is most likely due to incorrect table setup, plans not bound or insufficient authority to execute Db2 plans.

00D10121

The BSDS is not valid. A non-valid BSDS is the result of a failure during a previous attempt to run the BSDS conversion utility.

System action

Queue manager startup terminates.

System programmer response

The procedure for running the BSDS conversion utility involves renaming the original BSDS. Restore the BSDS to the original pre-conversion copy by renaming the data sets, then try the conversion again.

When the conversion is successful, try the program that issued the error message again.

00D10122: The BSDS version is not supported by this release of IBM MQ.
System action: Queue manager startup, or the process that was accessing the BSDS, terminates.
System programmer response: Start the queue manager at a version of IBM MQ that supports the BSDS version.
We can determine the version of a BSDS by running the print log map utility (CSQJU004)

00D10250

An unrecoverable error occurred while updating either the BSDS or the z/OS catalog to reflect changes in active log data sets.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The queue manager then terminates abnormally.

System programmer response

Obtain the SYS1.LOGREC and SVC dump. Correct the error, and restart the queue manager.

We might find the items listed in Diagnostics useful in resolving the problem. In addition, see the description of reason code X'00D10252' for details of the information recorded in the variable recording area (VRA) of the system diagnostic work area (SDWA).

Examine the console log for a CSQJxxxx message preceding this error to determine whether the error was a BSDS error or a z/OS catalog update error. If you cannot resolve the problem, contact your support center.

00D10251

An unrecoverable error occurred in the log buffer writer.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The queue manager then terminates abnormally.

System programmer response

Obtain the SYS1.LOGREC and the SVC dump. This error is usually caused by a previous error that was recorded on SYS1.LOGREC and produced an SVC dump. The SYS1.LOGREC entries and SVC dump should be examined to determine the primary error that occurred.

If we cannot resolve the problem, contact your support center.

00D10252

This reason code is used to define the format of the information recorded in the variable recording area (VRA) of the system diagnostic work area (SDWA).

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump.

System programmer response

Obtain the SYS1.LOGREC and SVC dump.

We might find the items listed in Diagnostics useful in resolving the problem. In addition, the following information is contained in the VRA of the SDWA:

Reason code X'00D10252' stored with VRA key 6.
The log buffer writer recovery tracking area is stored with VRA key 10.

00D10253

An application program check occurred in an MVCP instruction that attempted to move a parameter list or other data from the caller's address space to the queue manager address space.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump.

System programmer response

Obtain the SYS1.LOGREC and SVC dump. We might find the items listed in Diagnostics useful in resolving the problem.

Examine the area from which data was to be moved. It might be in the wrong key, or the address might be the cause of the problem. The incorrect instruction has a DA opcode and indicates the registers showing address and length to be moved.

00D10254

An application program check occurred in an MVCS instruction that attempted to move data from the queue manager address space to the caller's address space.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump.

System programmer response

Obtain the SYS1.LOGREC and SVC dump. We might find the items listed in Diagnostics useful in resolving the problem.

Examine the area to which data was to be moved. It might be in the wrong key, or the address might be the cause of the problem. The incorrect instruction has a DB opcode and indicates the registers showing address and length to be moved.

00D10257

The log RBA has reached or exceeded the value FFF800000000 (if 6-byte log RBAs are in use) or FFFFFFC000000000 (if 8-byte log RBAs are in use). The queue manager is terminated because the log RBA range has reached a CRITICAL level where the available range is too small for the queue manager to continue.

System action

The queue manager terminates with reason code 00D10257.

System programmer response

We need to reset the logs before the queue manager can be restarted. If we do not perform this action, the queue manager will abend once again after the next log data set switch.

For information on how to reset the logs using the CSQUTIL utility program, see RESETPAGE.

If your queue manager is using 6-byte log RBAs, consider converting the queue manager to use 8-byte log RBAs. See Plan to increase the maximum addressable log range for further information.

00D10261

While scanning the records and record segments in a log control interval (CI), it was discovered that the forward record chain was broken. This condition is the result of an incorrect record length in the log record header of some record in the log CI.

System action

This reason code can be issued by an active queue manager as the log buffers are scanned before they are written to the active log, or by the IBM MQ log services GET processor as a CI is retrieved from a user-specified active or archive log data set.

If the reason code is issued by an active queue manager, a diagnostic record is written to SYS1.LOGREC, and an SVC dump is requested.

If the error was detected by CSQJOFF1, the archiving of the active log data set is terminated and the faulty active log data set is marked 'stopped'
If the error was detected by CSQJR005, message CSQJ012E is issued and the calling agent is terminated
If the error was detected by CSQJW009, message CSQJ012E is issued and the queue manager is terminated
If the error was detected by CSQJW107, the queue manager is terminated

If this reason code is issued as the result of IBM MQ log services GET processing, no error is issued and no information is written to the SYS1.LOGREC data set.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem. If we are unable to solve the problem, contact the IBM support center.

00D10262

While scanning a log control interval (CI), the offset to the last record or record segment in the CI was found to be incorrect.

System action

If the reason code is issued by an active queue manager, a diagnostic record is written to SYS1.LOGREC, and an SVC dump is requested.

If the error was detected by CSQJOFF1, the archiving of the active log data set is terminated and the faulty active log data set is marked 'stopped'
If the error was detected by CSQJR005, message CSQJ012E is issued and the calling agent is terminated
If the error was detected by CSQJW009, message CSQJ012E is issued and the queue manager is terminated
If the error was detected by CSQJW107, the queue manager is terminated

If this reason code is issued as the result of IBM MQ log services GET processing, no error is issued, and no information is written to the SYS1.LOGREC data set.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem. If we are unable to solve the problem, contact the IBM support center.

00D10263

While scanning a log control interval (CI), the VSAM RDF/CIDF control information was found to be incorrect.

System action

If the reason code is issued by an active queue manager, a diagnostic record is written to SYS1.LOGREC, and an SVC dump is requested.

If the error was detected by CSQJOFF1, the archiving of the active log data set is terminated and the faulty active log data set is marked 'stopped'
If the error was detected by CSQJR005, message CSQJ012E is issued and the calling agent is terminated
If the error was detected by CSQJW009, message CSQJ012E is issued and the queue manager is terminated
If the error was detected by CSQJW107, the queue manager is terminated

If this reason code is issued as the result of IBM MQ log services GET processing, no error is issued, and no information is written to the SYS1.LOGREC data set.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem. If we are unable to solve the problem, contact the IBM support center.

00D10264

While scanning a log control interval (CI), the beginning log RBA of the CI was not the expected RBA.

System action

If the reason code is issued by an active queue manager, a diagnostic record is written to SYS1.LOGREC, and an SVC dump is requested.

If the error was detected by CSQJOFF1, the archiving of the active log data set is terminated and the faulty active log data set is marked 'stopped'
If the error was detected by CSQJR005, message CSQJ012E is issued and the calling agent is terminated
If the error was detected by CSQJW009, message CSQJ012E is issued and the queue manager is terminated
If the error was detected by CSQJW107, the queue manager is terminated

If this reason code is issued as the result of IBM MQ log services GET processing, no error is issued, and no information is written to the SYS1.LOGREC data set.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem. If we are unable to solve the problem, contact the IBM support center.

00D10265

While scanning the records and record segments in a log control interval (CI), it was discovered that the backward record chain was broken. This condition is the result of an incorrect record length in the log record header of some record in the log CI.

System action

If the reason code is issued by an active queue manager, a diagnostic record is written to SYS1.LOGREC, and an SVC dump is requested.

If the error was detected by CSQJOFF1, the archiving of the active log data set is terminated
If the error was detected by CSQJR005, message CSQJ012E is issued and the calling agent is terminated
If the error was detected by CSQJW009, message CSQJ012E is issued and the queue manager is terminated
If the error was detected by CSQJW107, the queue manager is terminated

If this reason code is issued as the result of IBM MQ log services GET processing, no error is issued, and no information is written to SYS1.LOGREC data set.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem. If we are unable to solve the problem, contact the IBM support center.

00D10266

While scanning a log control interval (CI), a unit of recovery ID or LINK RBA in some record was found to be inconsistent with the beginning log RBA of the CI.

System action

If the reason code is issued by an active queue manager, a diagnostic record is written to SYS1.LOGREC, and an SVC dump is requested.

If the error was detected by CSQJOFF1, the archiving of the active log data set is terminated and the faulty active log data set is marked 'stopped'
If the error was detected by CSQJR005, message CSQJ012E is issued and the calling agent is terminated
If the error was detected by CSQJW009, message CSQJ012E is issued and the queue manager is terminated
If the error was detected by CSQJW107, the queue manager is terminated

If this reason code is issued as the result of IBM MQ log services GET processing, no error is issued, and no information is written to SYS1.LOGREC data set.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem. If we are unable to solve the problem, contact the IBM support center.

00D10267

While scanning a log control interval (CI), a middle or last spanned record segment was not the first segment contained in the log CI.

System action

This reason code can be issued by an active queue manager because the log buffers are scanned before they are written to the active log, or by the IBM MQ log services GET processor because a CI is retrieved from a user-specified active or archive log data set.

If the reason code is issued by an active queue manager, a diagnostic record is written to SYS1.LOGREC, and an SVC dump is requested.

If the error was detected by CSQJOFF1, the archiving of the active log data set is terminated and the faulty active log data set is marked 'stopped'
If the error was detected by CSQJR005, message CSQJ012E is issued and the calling agent is terminated
If the error was detected by CSQJW009, message CSQJ012E is issued and the queue manager is terminated
If the error was detected by CSQJW107, the queue manager is terminated

If this reason code is issued as the result of IBM MQ log services GET processing, no error is issued, and no information is written to the SYS1.LOGREC data set.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem. If we are unable to solve the problem, contact the IBM support center.

00D10268

While scanning a log control interval (CI), a first or middle spanned record segment was not the last segment contained in the log CI.

System action

If the reason code is issued by an active queue manager, then a diagnostic record is written to SYS1.LOGREC, and an SVC dump is requested.

If the error was detected by CSQJOFF1, the archiving of the active log data set is terminated and the faulty active log data set is marked 'stopped'
If the error was detected by CSQJR005, message CSQJ012E is issued and the calling agent is terminated
If the error was detected by CSQJW009, message CSQJ012E is issued and the queue manager is terminated
If the error was detected by CSQJW107, the queue manager is terminated

If this reason code is issued as the result of IBM MQ log services GET processing, no error is issued, and no information is written to the SYS1.LOGREC data set.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem. If we are unable to solve the problem, contact the IBM support center.

00D10269: An unrecoverable error was found in one of the buffers, while moving the current log buffer to the static write buffer in preparation for the physical write to the active log.
System action: An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The queue manager then terminates.
System programmer response: We might find the items listed in Diagnostics useful in resolving the problem. If we are unable to solve the problem, contact the IBM support center.

00D10270

A LOG WRITE request completed unsuccessfully because the length of the log record header was not as expected. This is an internal error.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

Examine the SYS1.LOGREC, console log, and SVC dump for information about prior errors during LOG WRITE processing.

If we are unable to solve the problem, contact the IBM support center.

00D10327

A LOG READ completed unsuccessfully because of an invalid log LOGRBA. A log read, MODE(DIRECT) with a requested RBA does not match the start of a log record.

System action

An SVC dump is requested and the execution unit ends abnormally. If the log read error occurs during queue manager startup then the queue manager ends abnormally.

System programmer response

Log read with MODE(DIRECT) is most commonly used in the queue manager for verifying that the start RBA of a unit of work can be found on the log, before a sequential (maybe backward) read of the log data to recover locks on an in-doubt unit of work, or to back out a unit of work. It indicates that the queue manager is being started with incomplete log data available.

If you suspect an error in IBM MQ, collect the following data and contact IBM support:

The BSDS
All active and archive logs
The SVC dump created by this error

00D1032A: An unsuccessful completion of a LOG READ has occurred. BSDS does not map the specified RBA into a log data set. Either the BSDS is in error, or the log data set has been deleted.
System action: An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.
System programmer response: We might find the items listed in Diagnostics useful in resolving the problem.

00D1032B

Completion of a LOG READ was unsuccessful, because an error occurred while attempting to allocate a log data set.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

Examine LOGREC and SVC dump information. Also, examine any prior messages with a CSQJ prefix from recovery log manager allocation processing.

00D1032C

A LOG READ completed unsuccessfully, because an error occurred while opening or closing a log data set.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

Examine LOGREC and SVC dump information. Also, examine prior messages from recovery log manager open/close processing. These messages have a prefix of CSQJ.

00D1032E: A LOG READ completed unsuccessfully due to an internal error.
System action: An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.
System programmer response: We might find the items listed in Diagnostics useful in resolving the problem. Examine the SYS1.LOGREC and SVC dump information.

00D10340

An unsuccessful completion of a LOG READ has occurred. This reflects an internal recovery log manager (RLM) logic error.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

Examine the SYS1.LOGREC, console log and SVC dump for information about prior errors during LOG READ processing.

If we cannot solve the problem, contact the IBM support center.

00D10341

A LOG READ completed unsuccessfully because an error was detected during a Forward READ of the log record. This is an internal error.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

Examine the SYS1.LOGREC, console log and SVC dump for information about prior errors during LOG READ processing.

If we cannot solve the problem, contact the IBM support center.

00D10342

A LOG READ completed unsuccessfully because an error was detected during a backward READ of a log record. This is an internal error.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

Examine the SYS1.LOGREC, console log and SVC dump for information about prior errors during LOG READ processing.

If we cannot solve the problem, contact the IBM support center.

00D10343

A LOG READ completed unsuccessfully because an error was detected during a READ of a log record due to an invalid CI offset. This is an internal error.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

Examine the SYS1.LOGREC, console log and SVC dump for information about prior errors during LOG READ processing.

If we cannot solve the problem, contact the IBM support center.

00D10345: A LOG READ completed unsuccessfully because an error was received from a CATALOG LOCATE request for an archive log data set. The requested archive log data set might have been uncataloged or deleted.
System action: An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.
System programmer response: We might find the items listed in Diagnostics useful in resolving the problem. Examine the SYS1.LOGREC and SVC dump.

00D10348

The maximum retry count was exceeded while attempting to read a log RBA.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

Check the console log for related errors. This problem might occur if the user has specified an archive or active log data set to the BSDS with an incorrect RBA range.

If we cannot solve the problem, contact the IBM support center.

00D10354

A LOG READ request completed successfully but the length of the log record header was not as expected. This is an internal error.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

Examine the SYS1.LOGREC, console log, and SVC dump for information about prior errors during LOG READ processing.

If we are unable to solve the problem, contact the IBM support center.

00D10406: The bootstrap data set access service received a request with an invalid function code.
System action: An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.
System programmer response: We might find the items listed in Diagnostics useful in resolving the problem. If we cannot solve the problem, contact the IBM support center.

00D10410

An unsuccessful completion of a READ BSDS RECORD has occurred. An error has been returned from VSAM.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

Check the console log for return codes from VSAM.

If we are unable to resolve the problem, note these values, collect the items listed in Diagnostics, and contact the IBM support center.

00D10411

An unsuccessful completion of a WRITE UPDATE BSDS RECORD has occurred. An error has been returned from VSAM.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

Check the console log for return codes from VSAM.

If we are unable to resolve the problem, note these values, collect the items listed in Diagnostics, and contact the IBM support center.

00D10412

An unsuccessful completion of a WRITE INSERT BSDS RECORD has occurred. An error has been returned from VSAM.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

Check the console log for return codes from VSAM.

If we are unable to resolve the problem, note these values, collect the items listed in Diagnostics, and contact the IBM support center.

00D10413

An unsuccessful completion of a DELETE BSDS RECORD has occurred. An error has been returned from VSAM.

System action

An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.

System programmer response

Check the console log for return codes from VSAM.

If we are unable to resolve the problem, note these values, collect the items listed in Diagnostics, and contact the IBM support center.

00D10419: An error was returned from the z/OS GETDSAB service.
System action: The current utility terminates abnormally.
System programmer response: Contact the IBM support center.

00D1041A: An error was returned from the z/OS SWAREQ service.
System action: The current utility terminates abnormally.
System programmer response: Contact the IBM support center.

00D1041B

The Db2 subsystem that a utility has connected to does not meet the minimum system requirements for this version of IBM MQ for z/OS.

System action

The current utility terminates abnormally.

System programmer response

Ensure that the Db2 data-sharing group name, and subsystem ID provided in the parameters to the utility are correct, and that the Db2 subsystem meets the system requirements for this version of IBM MQ for z/OS.

See IBM MQ prerequisites for a link to the IBM MQ for z/OS requirements web page.

00D10700: An error completion code was returned by SETLOCK OBTAIN.
System action: An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.
System programmer response: We might find the items listed in Diagnostics useful in resolving the problem. In the dump, register 0 contains the return code from SETLOCK OBTAIN.

00D10701: An error completion code was returned by SETLOCK RELEASE.
System action: An execution unit writes a record to SYS1.LOGREC and requests an SVC dump. The execution unit then terminates abnormally.
System programmer response: We might find the items listed in Diagnostics useful in resolving the problem. In the dump, register 0 contains the return code from SETLOCK RELEASE.

00D10905

During recovery of a peer queue manager, a discrepancy has been detected between the peer queue manager's BSDS system timestamps. This can only occur if the peer queue manager was using dual BSDS.

System action

This typically results in recovery of the peer queue manager being unable to continue.

System programmer response

The print log map utility (CSQJU004) can be used to confirm the system timestamp discrepancy of the peer queue manager.

We can resolve the discrepancy by manually restarting the peer queue manager, which then attempts to resolve the problem.

Parent topic: IBM MQ for z/OS codes