Recovery log manager messages (CSQJ...)

The value specified by STARTRBA is the RBA of the first byte of log data in the named data set. The value specified by ENDRBA is the RBA of the last possible byte in the data set.

None required. However, if recovery is required, information from this message might be required as input to the change log inventory utility (CSQJU003).

This message is sent when logging switches to a new empty data set. The message shows the name and log RBA range of the full data set.

None required. However, if recovery is required, information from this message might be required as input to the change log inventory utility (CSQJU003).

Offloading for the specified archive log data set was successfully completed for the given volume. If the data set spans multiple tape volumes, this message is generated for each tape volume.

This message is sent when the dual active logging option is selected and copy n becomes inactive. A log copy becomes inactive when the next active log data set is not ready when required. ENDRBA is the last byte of log data written on copy n. This is usually caused by a delay in offload.

The log is switched to single mode until the next data set for copy n is ready for logging.

Perform a display request to ensure that there are no outstanding requests that are related to the log offload process. Take the necessary action to satisfy any requests, and permit offload to continue.

If the switch to single mode was caused by the lack of a resource required for offload, the necessary resource should be made available to allow offload to complete and thus permit dual logging to proceed. If recovery is required, information from this message might be required as input to the change log inventory utility (CSQJU003).

This message is sent when copy n of the log becomes active after previously being flagged as inactive. STARTRBA is the RBA of the first byte of log data written on copy n after it was activated.

None required. However, if recovery is required, information from this message might be required as input to the change log inventory utility (CSQJU003).

This message is sent if the operator answers 'N' to message CSQJ008E.

If the allocation is for the first copy of the archive log data set, offload terminates processing until the next time it is activated. If the first copy has already been allocated and this request is for the second copy, offload switches to single offload mode for this data set only.

If the operator answers 'N' to message CSQJ009E, this message is issued. volser is the volume serial of an archive log volume required to satisfy the read request. The name of the archive data set is given by message CSQJ022I which follows.

The read request that needed the archive volume is unsuccessful. If the request was issued with the COND=YES parameter, the log manager returns to its invoker with return code 12 and reason code X'00D1032B'. Otherwise, the log manager's invoker ends abnormally with the same reason code.

MQ needs a scratch volume for offloading an active log data set. qmgr-name is the name of the queue manager. nn is the number of full active log data sets. mm is the total number of active log data sets.

The offload task issues message CSQJ021D and waits for the operator's reply.

MQ needs the specified archive volume for a read operation. qmgr-name is the name of the queue manager.

The archive log read service task issues message CSQJ021D and waits for the operator's reply. This wait affects the agent for which the log read was issued and any other agents that might be waiting on the log read service task queue.

During archive data set allocation, a reply message was issued. The user did not respond correctly to the reply message. Either 'Y' or 'N' must be entered.

The original message is repeated.

During queue manager initialization, a conditional restart control record was found in the BSDS data set. Both the record identifier (a 4-byte hexadecimal number) and the creation time stamp are displayed to help identify the conditional restart record which will be used. If you want a conditional restart using that record, reply 'Y' to the message. Otherwise, reply 'N'.

If 'Y' is the response, the queue manager is started conditionally, using the record found. If 'N' is the response, startup is terminated.

Respond as indicated.

If a normal restart has failed and you have created a conditional restart record with the change log inventory utility, check whether the time and date in the message agree with when you created that record. If they do, reply 'Y'. If they do not, reply 'N' and investigate the discrepancy.

While scanning log records read into a buffer, MQ detected a logical error with reason code ccc. rrr is the log RBA of the segment in the buffer at which the error was detected. dsname is the name of the active or archive log data set from which the record was read. If dsname is blank, the data was read from an active log output buffer.

The connection ID and thread-xref identify the user or application that encountered the problem. Messages that have the same connection ID and thread-xref relate to the same user.

The application program is terminated with reason code ccc. However, information in this message might be useful in diagnosing the abnormal termination that will follow.

See Active log problems for information about dealing with problems on the log.

A scan of the log output buffer, just prior to writing the buffer, detected an inconsistency in the log data. ccc is the reason code associated with the SDUMP that is produced. rrr is the log RBA at which the error was detected.

The queue manager will terminate with a dump, and will not write the damaged buffer to either COPY 1 or COPY 2 active log data set.

Restart the queue manager after it terminates.

Because the damaged buffer has not been written to a log data set, the queue manager can be restarted. No corrective action is required.

A scan of the log output buffer, after writing to the first copy of the active log data set and before writing to the second copy, detected an inconsistency in the log data. ccc is the reason code associated with the SDUMP that is produced. rrr is the log RBA at which the error was detected.

The queue manager terminates with a dump, and does not write the damaged buffer to the COPY 2 data set.

The block containing the indicated log RBA might be damaged. The buffer was found to be in error at the completion of the write to the COPY 1 data set of the active log.

If dual active logs are being used, use the print log map utility (CSQJU004) to list the active log data sets for both copies of the active log. Find the COPY 2 data set with the corresponding RBA, and copy that data set (using Access Method Services REPRO) to the COPY 1 data set. Start the queue manager.

If only a single active log is used, contact the IBM® support center for assistance. An attempt to start the queue manager might succeed if the damage to the buffer occurred after completion of the write to DASD.

The operator chose to terminate queue manager startup by answering 'N' to msg-num.

The queue manager will not restart.

An archive log data set needs allocating, as indicated in the preceding CSQJ008E or CSQJ009E message.

The log service task waits for the operator's reply.

dsname is the name of the archive data set to which the preceding message refers.

Previous errors have made the active log data sets (that contain the RBA range reported in the message) unavailable. The status of these logs is STOPPED in the BSDS.

The queue manager terminates with a dump.

If, during queue manager initialization, the current log RBA value is equal or higher than FF8000000000 (if 6-byte log RBAs are in use) or FFFFFC0000000000 (if 8-byte log RBAs are in use) this message is issued for the operator to confirm if the restart of the queue manager should continue.

If 'Y' is the response, the queue manager startup continues.

If 'N' is the response, the queue manager startup terminates.

Stop the queue manager and reset the logs as soon as possible. See RESETPAGE for information on how to reset the logs using the CSQUTIL utility program and resetting the queue manager's log.

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

The current log RBA is approaching the end of the log RBA range. current-rba is the current log RBA value. The current log RBA should not be allowed to advance to the maximum log RBA value of max-rba.

This message is issued during queue manager initialization, or after the active log dataset is full and the queue manager switches to the next available log dataset.

Processing continues, unless the RBA value reaches FFF800000000 (if 6-byte log RBAs are in use) or FFFFFFC000000000 (if 8-byte log RBAs are in use) when the queue manager terminates with reason code 00D10257.

Plan to stop the queue manager and reset the logs as soon as possible; see RESETPAGE for information on how to reset the logs using the CSQUTIL utility program and resetting the queue manager's log.

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

Offloading for the specified archive log data set was successfully completed for the given volume. If the data set spans multiple tape volumes, this message is generated for each tape volume.

This message is issued in place of CSQJ003I for queue-sharing groups.

This message is issued during queue manager startup, to indicate the end of the log RBA range that can be addressed using the current log RBA size.

A max-rba value of 0000FFFFFFFFFFFF indicates that the queue manager is configured to use 6 byte RBAs, while a value of FFFFFFFFFFFFFFFF indicates that the queue manager is configured to use 8 byte RBAs.

You must reset the queue manager's log before the highest used log RBA reaches the end of the log RBA range.

Processing continues

If max-rba is 0000FFFFFFFFFFFF, consider converting the queue manager to use an 8-byte log RBA, to maximize the period of time until a reset of the queue manager's log is required. See Planning to increase the maximum addressable log range for further information.

The format of the parameters set by parm-name in the system parameter load module is invalid, so they cannot be used.

The queue manager is terminated with abnormally with reason code X'00E80084'.

Ensure that the queue manager is started with a correct system parameter module, for example CSQZPARM. If necessary, reassemble the module that uses the indicated parameters, and relink-edit your system parameter load module.

The parameters set by parm-name in the system parameter load module use some values which are now obsolete.

Processing continues. The obsolete parameters are ignored, and default values are used for new parameters.

Review your system parameter settings. If necessary, reassemble the module that uses the indicated parameters, and relink-edit your system parameter load module.

The system parameters (set by CSQ6ARVP) specify that the date and time of creation of an archive log data set be included as part of the archive log data set name (DSN). To accomplish this, MQ requires that the length of the archive log data set name prefix is limited. If the prefix requirement is not met, this message is issued just prior to the allocation of the archive log data set specified in the message.

The archive log data set will be allocated using the archive log prefix. However, the archive log DSN will not contain the date and time as the user requested.

The system parameters for the log archive function must be changed. Specifically, the TSTAMP and ARCPFXn fields are not consistent with one another. For information about the actions required to eliminate this problem, see Using CSQ6ARVP.

The system parameters (set by CSQ6ARVP) specify that the date and time of creation of an archive log data set be included as part of the archive log data set name (DSN). However, an attempt to get the current date and time from the system was unsuccessful. This message is issued just prior to the allocation of the archive log data set specified in the message.

The archive log data set will be allocated using the archive log prefix. However, the archive log DSN will not contain the date and time as the user requested.

The system parameters (set by CSQ6ARVP) specify that all archive log data sets should be uncataloged (CATALOG=NO). However, MQ requires that all archive log data sets allocated to non-tape devices must be cataloged. The archive log data set specified by dsname has been allocated to a non-tape device, and has thus been cataloged. The user's system parameter CATALOG setting of NO has been overridden.

The archive log data set has been allocated to a nontape device, and has been cataloged. The system parameter CATALOG=NO setting has been overridden. The BSDS reflects that the data set has been cataloged.

The archive system parameters must be changed. Specifically, the CATALOG and UNIT parameters are not consistent with one another. For information about the actions required to eliminate this problem, see Using CSQ6ARVP.

This message identifies a queue manager with log data that cannot be accessed. The logs or BSDSs of other queue managers in a queue-sharing group might be accessed during a RECOVER CFSTRUCT operation or during the rebuild of peer administration structures that might occur on a queue manager in a queue-sharing group.

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

Look for earlier messages which might identify more specifically the data set being accessed and the problem.

A conditional restart control record requests truncation, but it cannot take place because the end LRSN was not in the range of LRSN values known to either the active or archive logs. rrr is the end LRSN specified in the active record. The end LRSN is either higher than the end LRSN of the most recent active log data set, or lower than the starting LRSN of the oldest archive log data set.

Queue manager startup is terminated.

Check the ENDLRSN value specified in the conditional restart control record. If it is not correct, run the change log inventory utility (CSQJU003) using CRESTART CANCEL cancel the conditional restart, and a new CRESTART specifying the correct ENDLRSN.

This message is generated during queue manager startup. The value specified by STARTRBA is the RBA of the next byte of log data to be recorded in the active log data sets.

This message is preceded by one (if single logging) or two (if dual logging) CSQJ001I messages.

None required. However, if recovery is required, information from this message might be required as input to the change log inventory utility (CSQJU003).

During startup, or while processing a RECOVER BSDS command, MQ could not open the specified BSDS. BSDSn matches the DDname in the queue manager started task JCL procedure (xxxxMSTR) of the data set that cannot be opened. The value of n is 1 or 2. The error status contains the VSAM open return code in ee, and the VSAM open reason code in ii.

When this error occurs at initialization time, startup must be terminated, because the log data sets cannot be determined and allocated without the BSDS. When this error occurs during RECOVER BSDS processing, the command is terminated, and the queue manager continues in single BSDS mode.

Recover the BSDS that cannot be opened. See Active log problems for information about dealing with problems on the BSDS or the log.

A conditional restart control record requests truncation, but it cannot take place because the end RBA was not in the range of RBA values known to either the active or archive logs. rrr is the end RBA specified in the active record. The end RBA is either higher than the end RBA of the most recent active log data set, or lower than the starting RBA of the oldest archive log data set.

Queue manager startup is terminated.

Check the ENDRBA value specified in the conditional restart control record. If it is not correct, run the change log inventory utility (CSQJU003) using CRESTART CANCEL cancel the conditional restart, and a new CRESTART specifying the correct ENDRBA.

Otherwise, then most likely, the archive log data set that contained the requested RBA has been deleted from the BSDS data set by the change log inventory utility. Locate the output from an old print log map utility and identify the data set that contains the missing RBA. If the data set has not been reused, run the change log inventory utility to add this data set back into the inventory of log data sets. Restart the queue manager.

The log RBA range shown in the BSDS for the specified data set does not agree with the content of the data set.

Startup processing is terminated.

Use the print log map and change log inventory utilities to make the BSDS consistent with the log data sets.

An error occurred while attempting to allocate the active or archive log data set indicated by DSNAME. STATUS indicates the error reason code returned by z/OS dynamic allocation (SVC99).

This message might be preceded by message CSQJ073E.

Subsequent actions depend on the type of data set involved.

For active log data sets, if the error is encountered during queue manager initialization, startup is terminated. If two copies of the active log data sets are defined, this message appears only once.

For archive log data sets, if two copies of the archive log data sets are defined, processing continues on the remaining archive log data set.

The error status portion of this message contains a 2-byte error code (eeee, S99ERROR) followed by the 2-byte information code (iiii, S99INFO) from the SVC99 request block. If the S99ERROR code indicates an SMS allocation error ('97xx'), then ssssssss contains additional SMS reason code information obtained from S99ERSN. See the MVS Authorized Assembler Services Guide manual for a description of these codes.

See Active log problems for information about dealing with problems on the log.

See Active log problems for information about dealing with problems on the log.

Subsequent actions depend on when the error occurred.

During queue manager initialization, startup is terminated.

When using the data set either for offload or for input operations, processing continues. If a second copy of the data is available, MQ attempts to allocate and open the second data set.

When using the data set as an active log data set, MQ attempts to retry the request. If the retry is unsuccessful, the queue manager is terminated.

During checkpoint processing, where MQ attempts to locate the oldest active or archive log data sets that are required for restart recovery of page sets and restart and media recovery of CF structures, processing continues. The message is a warning that either restart recovery would fail or media recovery of CF structures would fail. It is most likely to occur when all CF application structures are not being regularly backed up, thereby requiring excessively old log data sets for recovery.

If the error occurred during initialization, either correct the problem so that the data set is available or provide another copy of the data set and change the BSDSs to point to the new data set.

If the error occurred after startup, the return code should be reviewed and the appropriate action taken to correct the problem, so that the data set can be used at a later time, or the data set entry can be removed from the BSDS using the change log inventory utility.

If the error was received from PROTECT, there might be a problem with the PASSWORD data set. See the appropriate DADSM publication to determine the cause of the problem. When the problem has been corrected, ensure the archive log data sets receiving the error are added to the PASSWORD data set. If these archive log data sets are not added to the PASSWORD data set, archive read will not be able to OPEN these data sets. If you do not have information about the named macro, note the macro name and the return code and contact your IBM support center for help.

If the error occurred during checkpoint processing, issue the DISPLAY USAGE TYPE(DATASET) command to show which log data sets are currently required for page set and media recovery, and ensure that they are available. If applicable, use the BACKUP CFSTRUCT command for your CF structures, and institute a procedure to back up your CF structures frequently.

An error occurred while writing a log data set. If csect-name is CSQJW107, the error occurred writing the log buffers to an active log data set. If csect-name is CSQJW207, the error occurred while preformatting the next control area before writing log data into it.

Error status contains the error information returned by media manager in the form ccccffss, where cccc is a 2-byte return code that describes the error, ff is a 1-byte code that defines the functional routine that detected the error, and ss is the 1-byte status code that defines a general category of error.

If the dual active logging option is selected, the MQ switches to the next data set for this copy. If the next data set is not ready, MQ temporarily enters single logging mode and allocates a replacement data set for the one that encountered the error. Dual logging is resumed as soon as possible.

If single active logging option is selected and the next data set is not ready, MQ waits for that data set to be available. In this case, log writing is inhibited until the replacement is ready for output.

See the MVS/DFP Diagnosis Reference manual for information about return codes from the media manager. If you are unable to resolve the problem, note the return code, and contact your IBM support center.

An error occurred while reading an active log data set. The error status contains the error information returned by the media manager in the form ccccffss, where cccc is a 2-byte return code that describes the error, ff is a 1-byte code that defines the functional routine that detected the error, and ss is the 1-byte status code that defines a general category of error. (See the MVS/DFP Diagnosis Reference manual for information about return codes from the media manager.)

If another log data set contains the data, MQ attempts to read the data from the alternate source. If an alternate source is not available, a read error return code is sent to the program requesting the log data. Depending on the circumstances under which the failure occurred, the queue manager might continue with the alternate log data set if dual logging is used, or end abnormally.

If you are using dual logging, the requested RBA was probably retrieved from the corresponding dual active log data set, and no immediate response is necessary. However, if this error occurs frequently, or if you are using single logging, immediate attention might be required. If so, note the contents of the error status field, and contact your IBM support center for help.

It might be necessary to replace the data set in error with a new data set containing the log data, and to update the BSDSs to reflect the new data set using the change log inventory (CSQJU003) NEWLOG operation.

See Active log problems for information about dealing with problems on the log.

An error occurred while reading the specified BSDS. Error Status contains the VSAM return and feedback codes. It is a 2-byte field with the first byte containing the hexadecimal return code and the second containing the hexadecimal feedback code. See the DFSMS/MVS Macro Instructions for Data Sets manual for a description of VSAM return and reason codes.

See Active log problems for information about dealing with problems on the BSDS or the log.

If dual BSDSs are available, MQ attempts to read from the other BSDSs. If the read from the second BSDS fails or if there is only one BSDS, an error code is returned to the log request that caused access to the BSDS.

If the read error is detected during startup, the queue manager terminates.

It might be necessary to replace or repair the BSDS, depending on what conditions resulted from the read error. To replace a BSDS, first delete the BSDS in error, then define the new BSDS with the same name and attributes. If a new name is used for the new BSDS, change the queue manager started task JCL procedure (xxxxMSTR) to specify the new BSDS name.

An error occurred while writing to the specified BSDS. Error Status contains the VSAM return and feedback codes. It is a 2-byte field with the first containing the hexadecimal return code and the second containing the hexadecimal feedback code. See the DFSMS/MVS Macro Instructions for Data Sets manual for a description of VSAM return and reason codes.

If dual BSDSs are available, MQ enters single BSDS mode using the remaining good BSDS. Otherwise, an error code is returned to the log request that caused access to the BSDS.

If dual BSDS mode is being used, run an offline Access Method Services job to rename the error BSDS and define a new BSDS with the same name. Then enter the RECOVER BSDS command to reestablish dual BSDS mode.

If dual BSDS mode is not being used, the queue manager must be shut down, and the BSDS must be recovered from a backup copy. To recover the BSDS, use the change log inventory utility.

There is no more space in the specified BSDS. The operation that encountered the out-of-space condition did not complete properly.

If dual BSDSs are available, MQ enters single BSDS mode using the remaining good BSDS. Otherwise, an error code is returned to the log request that caused access to the BSDS.

If dual BSDS mode is being used, run an offline Access Method Services job to rename the full BSDS and define a new, larger BSDS with the same name. Enter the RECOVER BSDS command to reestablish dual BSDS mode.

If dual BSDS mode is not being used, the queue manager must be shut down and the BSDS recovered offline. In this case, run the same Access Method Services job mentioned above to rename the full data set and define a larger data set. Next, run an Access Method Services REPRO job to copy the full BSDS into the new BSDS.

This message is issued when the last available active log data set is 5% full, and is reissued after each additional 5% of the data set space is filled.

Each time the message is issued, the offload processing will be re-attempted. If the situation is not corrected, the active log data set will fill to capacity, message CSQJ111A will be issued, and MQ processing will stop.

To clear this condition, you must take steps to complete other waiting offload tasks. Once an active log data set is made available (reusable) by completing the offload process for it, the MQ logging activity can continue.

Perform a display request to determine the outstanding requests related to the log offload process. Take the necessary action to satisfy any requests, and permit offload to continue.

Consider whether there are sufficient active log data sets. If necessary, additional log data sets can be added dynamically using the DEFINE LOG command.

If offload does not complete normally or cannot be initiated, either correct the problem that is causing the offload process error, increase the size of the allocated data sets, or add more active log data sets. Note that the latter action requires the queue manager to be inactive and the change log inventory utility to be run.

Due to delays in offload processing, all available space in all active log data sets has been exhausted. Recovery logging cannot continue.

MQ waits for an available data set. Any tasks performing MQ API calls that require logging will wait.

Perform a display request to ensure that there are no outstanding requests that are related to the log offload process. Take the necessary action to satisfy any requests, and permit offload to continue.

Consider whether there are sufficient active log data sets. If necessary, additional log data sets can be added dynamically using the DEFINE LOG command.

If the delay was caused by the lack of a resource required for offload, the necessary resource must be made available to allow offload to complete and thus permit logging to proceed. For information about recovery from this condition, see Archive log problems.

If the problem occurred because archiving was set off, or because archive data sets could not be allocated, or for any other reason that requires the system parameters to be changed, the queue manager must be canceled as neither STOP MODE(QUIESCE) nor STOP MODE(FORCE) commands will work.

To free any tasks that are waiting because they were performing MQ API calls that require logging, you must solve the underlying problem, or cancel the queue manager.

If the offload process has stalled because some resource is not available or for some other reason, it may be possible to resolve the problem by canceling the currently executing offload task using the ARCHIVE LOG CANCEL OFFLOAD command, and then starting another. If there are hardware problems, it may be necessary to use z/OS commands to cancel the devices with problems.

Startup is terminated.

Use the change log inventory utility to make the number of active log data sets defined in the BSDS consistent with the system parameters specified in CSQ6LOGP, or to add further active log data sets so that there are two or more active log data sets available for use in each active log copy. Restart the queue manager.

There was a request to read the log record starting at this RBA. However, this log record cannot be found in any active or archive log data set. The connection ID and thread-xref identify the user or application that encountered the problem (this could be an internal IBM MQ task). See Active log problems for information about dealing with problems on the log.

Depending upon what log record is being read and why, the requestor might end abnormally with a reason code of X'00D1032A'.

Probable user error. Most likely, the archive log data set that contained the requested RBA has been deleted from the BSDS by the change log inventory utility. Locate the output from an old print log map run, and identify the data set that contains the missing RBA. If the data set has not been reused, run the change log inventory utility to add this data set back into the inventory of log data sets. Restart the queue manager.

An error occurred while accessing one of the archive data sets being created by offload. Because the dual archive option is specified, offload is continuing with the other archive data set. For the RBA range being offloaded, there is only one copy of archive instead of the usual two copies.

Offload produces a single archive data set.

A second copy of this archive log data set can be made, and the BSDSs can be updated with the change log inventory utility.

Offload could not allocate an archive log data set. The offload was not performed. This message is preceded by message CSQJ103E or CSQJ073E.

Offload will be tried at a later time.

Review the error status information of message CSQJ103E or CSQJ073E. Correct the condition that caused the data set allocation error so that, on retry, the offload can take place.

Offload could not add an archive entry to the BSDS. The offload is considered incomplete. The active log data set is not marked as reusable for new log data. This message is preceded by message CSQJ107E, CSQJ108E, or CSQJ109E.

Offload will be retried at a later time.

See the specific preceding message for action.

An error occurred during initialization reading from the specified BSDS. Error Status contains the VSAM return and feedback codes. It is a 2-byte field with the first containing the hexadecimal return code and the second byte containing the hexadecimal feedback code. See the DFSMS/MVS Macro Instructions for Data Sets manual for a description of VSAM return and reason codes.

Startup is terminated.

Determine the cause of the read error using the VSAM error status information provided. Restart the queue manager.

Log initialization received a return code from the named macro.

Startup is terminated.

Determine the problem from the documentation on the named macro and return code. Then take appropriate steps, and restart the queue manager. If you do not have information about the named macro, note the macro name and the return code and contact your IBM support center for help.

During queue manager initialization, the BSDS access function was unable to complete its initialization process. See Active log problems for information about dealing with problems on the BSDS or the log.

Startup is terminated.

One or more error messages describing the specific error have preceded this message. See the specific messages for error analysis and the appropriate action to take.

When the queue manager was initialized, the time stamps of the dual BSDS did not agree. The time stamps from the system and from the change log inventory utility are shown for each BSDS. The time stamps have the format date hh:mm:ss.th.

The queue manager attempts to re-synchronize the BSDS data sets to restore dual BSDS mode. If re-synchronization is successful, message CSQJ130I is issued and startup continues. Otherwise, startup is terminated.

If startup fails, run the print log map utility against each BSDS. From the output, determine which data set is obsolete, delete it, define a replacement for it, and copy the remaining BSDS to the replacement.

If output from the print log map utility for both data sets is similar, delete the data set with the oldest time stamp, and copy the data set with the most recent time stamp.

During queue manager initialization (if dual BSDS data sets are specified), the job file control block (JFCB) in z/OS is read to obtain the data set names associated with DDnames BSDS1 and BSDS2. This error is caused by a missing DD statement.

Startup is terminated.

Ensure that a DD statement exists in the queue manager started task JCL procedure xxxxMSTR for DDname BSDS1. If dual BSDS data sets are used, ensure that a DD statement also exists in the queue manager started task JCL procedure xxxxMSTR for DDname BSDS2.

During queue manager initialization, or when running a utility, the dual BSDSs were found to differ in content.

The program or queue manager startup is terminated.

If the error occurred during queue manager initialization, run the print log map utility against each BSDS to determine which data set was last used as the first copy. Delete the second copy data set, define a replacement for the deleted data set, and copy the remaining BSDS to the replacement.

If the error occurred when running the BSDS conversion utility after the queue manager terminated abnormally, first attempt to restart the queue manager and shut it down cleanly before attempting to run the BSDS conversion utility again. If this does not solve the problem, run the print log map utility against each BSDS to determine which data set was last used as the first copy. Change the JCL used to invoke the BSDS conversion utility to specify this BSDS in the SYSUT1 DD statement, and remove the SYSUT2 DD statement, before submitting the job again.

During queue manager initialization, the BSDSs was found to have been incompletely processed by the change log inventory utility.

Startup is terminated.

Run the print log map utility to determine what operation against the BSDS did not complete. Run the change log inventory utility against the BSDSs to allow any unfinished processing to be completed.

During offload, an unrecoverable input/output error was encountered on an active log data set. The data set experiencing the error is marked unusable, and no further logging is done to that data set.

Active log data sets continue to be offloaded as they become full.

Recover the data manually from the data set, copy it to an archive data set, run the change log inventory utility to make the new archive data set available to the queue manager, and remove the error-prone active log data set.

An error occurred while copying the BSDS data set during the offload process. The data set is not produced, and the volume containing the offloaded data set does not contain a BSDS for recovery use.

The queue manager continues the offload process without producing a copy of the BSDS.

When archiving occurs, both a copy of the active log data set, and the BSDS at that time, are dumped. The BSDS is not critical because it will be copied again with the next archive log (the missing one simply means an extended restart time). However, the underlying data management problem (for example, not enough space allocated) should be resolved for subsequent BSDS offloads to occur.

An input/output error or a VSAM logical error occurred on a BSDS. This message is preceded by message CSQJ107E or CSQJ108E.

IBM MQ enters single BSDS mode using the remaining BSDS.

Run an offline Access Method Services job to rename the error BSDS and define a new BSDS with the same name. Then enter the RECOVER BSDS command to reestablish dual BSDS mode.

When the queue manager is initialized, the system time stamp for the BSDS is displayed. The time stamp is of the format date hh:mm:ss.th. This time stamp should be close to the last time at which this queue manager was stopped. If not, it might indicate a restart is being attempted with the wrong BSDS.

The time stamp will show as '****' if the BSDS has not been used before.

Startup continues.

If the time displayed is not close to the time this queue manager was last stopped, and you cannot explain any time discrepancy, cancel the queue manager. From the queue manager started task JCL procedure xxxxMSTR, determine the data set names of the BSDSs and run the print log map utility. Check whether the active and archive log data sets all belong to this queue manager. If not, then change the started task JCL procedure xxxxMSTR for the queue manager to use the correct BSDSs.

The offload task ended abnormally while attempting to offload the RBA range in active log data set dsname.

The offload task terminates and the archive data sets allocated to the offload task are deallocated and deleted. The status of the active log data sets involved in the unsuccessful offload processing remains set to 'not reusable'.

This message is the result of an offload error, and will be preceded by one or more IBM MQ messages (for example, CSQJ073E) and z/OS messages (for example, IEC030I, IEC031I, IEC032I). If the queue manager is operating with restricted active log resources (see message CSQJ110E), quiesce the system to restrict logging activity until the abnormal termination or the CSQJ110E condition can be resolved.

Investigate and correct the cause of the abnormal termination before the offload is attempted again by the queue manager.

There was a request to find eol-rba, the log record that has been recorded in the BSDS as the highest RBA written. This RBA cannot be found in any active log data set. The highest RBA which could be found in any active data set was hi-rba.

Startup processing is terminated.

Most likely, the active log data set containing the requested RBA has been deleted from the BSDS by the change log inventory utility. If the data set has not been reused, run the change log inventory utility to add this data set back into the BSDS. Restart the queue manager.

If the data set is not available, contact your IBM support center.

Dual BSDS mode was restored using BSDS copy n. This is the BSDS data set with the most recent system time stamp.

Startup continues.

During command processing, a failure occurred attempting to write queue manager information to Db2.

Processing of the command is terminated.

Check the console for messages relating to the problem.

During command processing, a failure occurred attempting to read queue manager information from Db2.

Processing of the command is terminated.

Check the console for messages relating to the problem.

There was a request to read the log record starting at this LRSN for the indicated queue manager (which might not be the issuer of the message). However, this log record cannot be found in any active or archive log data set. The connection ID and thread-xref identify the user or application that encountered the problem (this could be an internal IBM MQ task). See Active log problems for information about dealing with problems on the log.

Depending upon what log record is being read and why, the requestor might end abnormally with a reason code of X'00D1032A'.

This is probably a user error. Most likely, the archive log data set that contained the requested RBA has been deleted from the BSDS by the change log inventory utility. Locate the output from an old print log map run, and identify the data set that contains the missing LRSN. If the data set has not been reused, run the change log inventory utility to add this data set back into the inventory of log data sets. Restart the queue manager.

There was a request to read the log record starting at this RBA for the indicated queue manager. However, this log record cannot be found in any active or archive log data set. The connection ID and thread-xref identify the user or application that encountered the problem (this could be an internal IBM MQ task). See Active log problems for information about dealing with problems on the log.

Depending upon what log record is being read and why, the requestor might end abnormally with a reason code of X'00D1032A'.

See BSDS problems for further information.

An attempt to allocate a tape unit for the indicated connection ID failed. The current maximum tape unit specified is n, but only m are physically available.

The process for the connection ID and correlation ID is held until either an allocated tape unit becomes free or more tape units are varied online and made available to the archive read task. This situation rectifies itself over time as currently allocated tape units become available.

Processing of the active log offload ended.

This message is written to the z/OS console.

A DEFINE LOG command has dynamically added a new log data set, dsn, and added it to either the LOGCOPY1 or LOGCOPY2 ring of active log data sets, as indicated by n.

The new active log data set is eligible to be used when the current active log data set fills and logging switches to the next active log data set in the ring.

Information about the data set is stored in the BSDS and will persist over a restart of the queue manager.

A DEFINE LOG command failed to add a new log data set. Further information about the failure is given in the preceding messages.

Investigate and correct the cause of the failure, then enter the command again.

IBM MQ checks that a data set being added by a DEFINE LOG command has not been previously used as a log data set, as this might be an indication of operator error. The requested data set dsname was found to have been previously so used.

The data set is closed and deallocated. Dynamic addition of a new active log data set fails.

Ensure that the data set being added as an active log data set is newly allocated, or has been formatted with the active log preformat utility, CSQJUFMT.

The maximum number of active log data sets is fixed. No further entries can be inserted in the BSDS after the maximum has been reached.

Dynamic addition of a new active log data set fails.

It was not possible for IBM MQ to dynamically allocate the requested data set (named in the following CSQJ141E message) for use as a new active log data set.

Dynamic addition of a new active log data set fails.

Ensure that the data set being added as a new active log data set is a VSAM linear data set with SHAREOPTIONS(2 3) and that it is not in use by any other jobs.

An abnormal program interrupt was detected while executing in the installation-supplied log capture exit code (that is entry point CSQJW117 in load module CSQJL004). As a result of this, the log capture exit will no longer be active; log data will no longer be available for exit capture/processing.

This message can only occur when an installation-supplied log capture exit (entry CSQJW117) is active for this queue manager.

The log capture exit (entry point CSQJW117) is terminated. No further calls will be attempted for this queue manager. A full dump is provided for diagnostic purposes.

Determine the cause of the CSQJL004 load module (CSQJW117 entry point) abend and take corrective action.

The queue manager could not successfully complete the read of the indicated RBA due to reason code ccc. The user or application that encountered the error is identified by the connection and correlation IDs. Messages that have the same connection ID and correlation ID relate to the same application. Correlation IDs beginning with '0nn', where nn is a number from 01 to 28, identify system agents.

The queue manager attempts to recover from the error.

If the queue manager was able to recover from the error and successfully complete the application, no further action is required. If the application abnormally terminated or the queue manager could not recover successfully, this message is followed by one or more messages. Refer to the information in this message and the subsequent messages to determine the appropriate corrective action. .

An error occurred while attempting to create the archive log volume report. An RBA range could not be successfully mapped into one or more archive data sets due to reason code ccc. The user or application that encountered the error is identified by the connection and correlation IDs. This message might be preceded by one or more related error messages. Messages that have the same connection ID and correlation ID relate to the same application. Correlation IDs beginning with '0nn', where nn is a number from 01 to 28, identify system agents.

This failure could be caused by one or more missing archive log data sets, or a system error (for example, an I/O error reading the BSDS).

The archive log volume report (see message CSQJ330I) is not produced. In addition, no premounting of tapes is possible.

The user or application continues processing. The physical read process for the user or application continues until the job completes normally or terminates abnormally. The job can terminate abnormally if the error is encountered again when the data set is physically required for the read process.

If the user or application completes successfully, no further action is necessary. If the user or application does not complete successfully, refer to the messages related to the actual failure to determine the appropriate corrective action.

The queue manager could not successfully complete the read of the indicated LRSN for the indicated queue manager (which might not be the issuer of the message) due to reason code ccc. The user or application that encountered the error is identified by the connection and correlation IDs. Messages that have the same connection ID and correlation ID relate to the same application. Correlation IDs beginning with '0nn', where nn is a number from 01 to 28, identify system agents.

The queue manager attempts to recover from the error.

If the queue manager was able to recover from the error and successfully complete the application, no further action is required. If the application abnormally terminated or the queue manager could not recover successfully, this message is followed by one or more messages. Refer to the information in this message and the subsequent messages to determine the appropriate corrective action..

The queue manager could not successfully complete the read of the indicated RBA for the indicated queue manager due to reason code ccc. The user or application that encountered the error is identified by the connection ID and correlation ID. Messages that have the same connection ID and correlation ID relate to the same application. Correlation IDs beginning with '0nn', where nn is a number from 01 to 28, identify system agents.

The queue manager attempts to recover from the error.

If the queue manager was able to recover from the error and successfully complete the application, no further action is required. If the application abnormally terminated or the queue manager could not recover successfully, this message is followed by one or more messages. Refer to the information in this message and the subsequent messages to determine the appropriate corrective action.

The queue manager has opened a LOG dataset that has space allocated that is larger than 4GB. The maximum LOG size supported is 4GB.

Processing continues. The LOG dataset continues to be used but the space used is smaller than the space allocated. The allocated highest RBA value overflows a 32bit word and it is truncated. The truncated highest RBA is used resulting in a smaller LOG dataset.

The LOG dataset should be allocated with space not exceeding 4GB. Use Access Method Services to define the data set with a maximum size of 4 GB. Refer to Log dataset definitions to determine the LOG dataset size.

During log switch processing an uncommitted unit of recovery, spanning more than two active log switches, has been encountered. The unit of recovery identifier urid together with the connection name name identify the associated thread.

Processing continues.

Consult with the application programmer to determine if there is a problem with the unit of recovery, and to ensure that the application commits work frequently enough. Uncommitted units of recovery can lead to difficulties later.

During log switch processing, an uncommitted unit of recovery was encountered that now has activity spanning several log data sets. The unit of recovery identifier urid together with the connection name name identify the associated thread.

Processing continues.

Consult with the application programmer to determine if there is a problem with the unit of recovery, and to ensure that the application commits work frequently enough. Uncommitted units of recovery can lead to difficulties later.

A DEFINE LOG command specified the COPY(2) parameter but the dual logging parameter (TWOACTV=YES) was not specified in CSQ6LOGP at queue manager startup.

Dynamic addition of the new active log data set fails.

Either specify COPY(1) on the DEFINE LOG command or configure the queue manager to use dual logging.

The offload of one or more active logs has been delayed because all available offload tasks are in use.

A maximum of 31 offload tasks can concurrently write new archive log data sets. The number of offload tasks can be tuned using the MAXCNOFF parameter, which is set using either CSQ6LOGP or the SET LOG command. MAXCNOFF is provided to tailor the offloading of IBM MQ logs to match system constraints, such as the number of available tape units.

Processing continues. The offload will complete when an offload task becomes available. Message CSQJ168I will be issued when the offload of active logs is no longer being delayed.

This is most likely a transient situation as a result of IBM MQ suddenly being able to archive a large number of full active logs, for example after problems with archiving have been resolved.

In other circumstances, review the MAXCNOFF parameter setting.

Consider increasing the active log capacity to match the active and archive log rates. The DEFINE LOG command can be used to provide additional active log capacity.

csect-name Log archiving is no longer delayed

The offload of active logs is no longer being delayed by a shortage of available offload tasks.

Processing continues.

The utility completed successfully.

The utility was unable to complete processing successfully.

The current utility is terminated.

Review other messages produced by the utility to determine the appropriate action to be taken.

A request for storage was unsuccessful because no more storage is available.

The current utility is terminated.

Rerun the utility after increasing the storage available.

The user entered a utility control statement operation (oper) that is invalid.

The current utility is terminated.

Correct the control statement, and rerun the utility.

The user specified a utility control statement parameter (xxxx) that is invalid.

The current utility is terminated.

Correct the control statement, and rerun the utility.

xxxx contains the name of a parameter that requires an argument.

The current utility is terminated.

Specify an argument for the identified parameter and then rerun the utility.

xxxx contains the name of the parameter that has been incorrectly followed by an = symbol.

The current utility is terminated.

Correct the control statement, and rerun the utility.

The user has specified utility control statement parameters that are inconsistent with the specified utility operation.

The current utility is terminated.

Correct the control statement, and rerun the utility.

Additional control statements were expected, but could not be found.

The current utility is terminated.

Correct the control statements, and rerun the utility.

A VSAM GET was issued that resulted in a nonzero return code. yy contains the error code returned by VSAM. ddd contains the DDname of the BSDS encountering the error.

The current utility is terminated.

The action taken is dictated by the reason code. See RPLERRCD for information about the reason code in RPLERRCD. The BSDS might have to be recovered by use of a backup copy.

A VSAM PUT was issued that resulted in a nonzero return code. yy contains the error code returned by VSAM. ddd contains the DDname of the BSDS encountering the error.

The current utility is terminated.

The action to be taken is dictated by the reason code. See RPLERRCD for information about the reason code in RPLERRCD. The BSDS might have to be recovered by use of a backup copy.

If this error occurs when running the BSDS conversion utility (CSQJUCNV), and RPLERRCD indicates that the reason was an attempt to store a record with a duplicate key, ensure that the output BSDS is empty before running the utility.

You attempted a NEWLOG operation with a data set name that already exists in the BSDS. An entry is never made in a BSDS if the specified DSNAME currently exists in either the active or archive records of that BSDS. ddd contains the DDname of the subject BSDS.

The current utility is terminated.

Either correct the control statement and rerun the utility, or delete the existing DSNAME from the BSDS and rerun the utility.

The parameter TIME(RAW) was specified on the invocation of utility modname. Where possible, timestamps formatted as date and time in the output will have no local timezone, or leapsecond adjustment performed so will be the UTC time of the event on the source system.

This mode of processing is most useful when the log, or BSDS being formatted has been produced on a remote system in a different timezone, or in a different daylight saving regime.

Processing continues.

Either correct the control statement and rerun the utility, or delete the existing DSNAME from the BSDS and rerun the utility.

The maximum number of active log data sets is fixed. No further entries can be inserted in the BSDS after the maximum has been reached. ddd contains the DDname of the subject BSDS.

The current utility is terminated.

Run the print log map utility to determine the current status of the BSDS. Subsequent actions can then be formulated, depending upon the status of the BSDS.

The DELETE operation specifies a DSNAME that cannot be found in the BSDS. ddd contains the DDname of the subject BSDS.

The current utility is terminated.

Correct the control statement, and rerun the utility.

The DELETE operation specifies a COPY1VOL or COPY2VOL argument that cannot be found in the BSDS. ddd contains the DDname of the subject BSDS.

The current utility is terminated.

Correct the control statement, and rerun the utility.

An error occurred when csect-name tried to open a data set named ddd.

The current utility is terminated.

A utility found the BSDS to be in create mode, so it cannot contain data to map. ddd contains the DDname of the data set.

The current utility is terminated.

Correct the JCL so that a non-null data set can be processed.

Errors were encountered errors during utility processing. These errors subsequently caused oper to be bypassed.

This message is a warning only and is displayed after messages that specify the error or errors that occurred. Note that the error or errors might not be associated with the current oper operation; rather, under log utility processing, a significant error in any operation causes the control statements for this and any subsequent operations to be checked for syntax only. BSDS updates do not occur for any operation specified in this message.

The log utility continues to process. However, for this and all subsequent operations, the BSDS is not updated and the utility only checks the syntax of the control statements.

Consult the previous messages and correct any errors that caused this message to be generated. Resubmit the log utility job for all operations that have been bypassed.

You specified the parameter xxxx. This parameter is not valid for the argument.

The current utility is terminated.

Correct the parameter argument on the control statement, and rerun the utility.

xxxx specifies the name of the parameter with an argument value that exceeded the maximum length allowed.

The current utility is terminated.

Correct the parameter argument on the control statement, and rerun the utility.

xxxx gives the name of the parameter that you have specified more than once on the same control statement.

The current utility is terminated.

Remove the redundant parameter, and rerun the utility.

The oper specified in the message identifies the name of the change log inventory utility operation that has been successfully completed.

The specified volume currently exists in the archive log records of the BSDS. ddd specifies the DDname of the subject BSDS.

The current utility is terminated.

Either correct the parameter argument on the control statement, or delete the specified volume and rerun the utility.

The maximum number of archive volumes has been exceeded, and no more space is available for volume entries in the copy specified.

The current utility is terminated.

Delete some of the archive entries in the specified copy number, and rerun the utility.

An error occurred when trying to dynamically deallocate the data set. Error status is the error reason code returned by z/OS dynamic allocation.

Processing continues.

The error status portion of this message contains a 2-byte error code (eeee, S99ERROR) followed by the 2-byte information code (iiii, S99INFO) from the SVC99 request block. If the S99ERROR code indicates an SMS allocation error ('97xx'), then ssssssss contains additional SMS reason code information obtained from S99ERSN. See the MVS Authorized Assembler Services Guide manual for a description of these codes.

During queue manager initialization, the offload function was unable to complete its initialization process.

Startup is terminated.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate actions to take.

During queue manager initialization, the command function was unable to complete its initialization process.

Startup is terminated.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During queue manager initialization, the output data set control function was unable to complete its initialization process.

Startup is terminated.

One or more error messages describing the specific error preceded this message. See the specific message for error analysis and the appropriate action to take.

During queue manager initialization, the archive log read function was unable to complete its initialization process.

Startup is terminated.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During queue manager initialization, the quiesce function which supports the ARCHIVE LOG MODE(QUIESCE) command processing was unable to complete its initialization process.

Startup is terminated.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During queue manager initialization, the output buffer writer function was unable to complete its initialization process.

Startup is terminated.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During queue manager termination, the BSDS access function was unable to complete its termination process.

Termination processing continues.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During queue manager termination, the offload function was unable to complete its termination process.

Termination processing continues.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During queue manager termination, the command function was unable to complete its termination process.

Termination processing continues.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During queue manager termination, the output data set control function was unable to complete its termination process.

Termination processing continues.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During queue manager termination, the archive log read function was unable to complete its termination process.

Termination processing continues.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During queue manager termination, the quiesce function which supports the ARCHIVE LOG MODE(QUIESCE) command processing was unable to complete its termination process.

Termination processing continues.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During queue manager termination, the output buffer writer function was unable to complete its termination process.

Termination processing continues.

One or more error messages describing the specific error preceded this message. See the specific messages for error analysis and the appropriate action to take.

During termination, there was a return code from the named macro that indicated an error.

Termination processing continues.

If the problem persists, contact your IBM support center for assistance.

The conditional restart control record in use indicates that the log should be truncated at the specified RBA.

If 'Y', queue manager startup continues. If 'N', startup is terminated.

Run the change log inventory utility (CSQJU003) to modify the conditional restart record.

The conditional restart control record in use indicates that the queue manager is to be restarted and that logging is to begin at the specified RBA.

If 'Y', queue manager startup continues. If 'N', startup is terminated.

Run the change log inventory utility (CSQJU003) to modify the conditional restart record.

An input/output error occurred while processing a BSDS record. rc indicates the return code received from the input/output operation. reason indicates the reason code received from the operation.

Return code 4 indicates that IBM MQ detected a problem. Return code 8 indicates a VSAM error.

Startup is terminated.

For a return code of 4, if the problem persists, contact your IBM support centre for assistance. For a return code of 8, run an offline Access Method Services job to determine the cause of the VSAM error.

An active log data set was detected with share options that do not permit CF structure recovery in a queue-sharing group environment. All active log data sets must be have SHAREOPTIONS(2 3) at least to allow CF structure recovery.

This can occur when the queue manager's own log data sets are checked during startup, or when a RECOVER CFSTRUCT command is issued that requires to access another queue manager's log data sets.

If this is a result of a RECOVER CFSTRUCT command, the command is terminated. Otherwise, startup continues, but CF structure recovery will not be possible.

The conditional restart control record in use indicates that the log should be truncated at the specified LRSN.

If 'Y', queue manager startup continues. If 'N', startup is terminated.

Run the change log inventory utility (CSQJU003) to modify the conditional restart record.

If this message was received during processing of the RECOVER BSDS command, then the queue manager will continue in single BSDS mode. If this message was received during processing of the ARCHIVE LOG command, the archive log history record in the BSDS will not be updated to reflect the occurrence of an ARCHIVE LOG command; logging and the offload processing will continue.

If this message was received during processing of the RECOVER BSDS command, recovery action must be performed on the BSDS before re-entering the command. If this message was received during processing of the ARCHIVE LOG command, no action is necessary.

The RECOVER BSDS command encountered an error while trying to allocate the specified data set dynamically. DSNAME is the data set name. Error Status is the error code and information code returned by z/OS dynamic allocation.

Processing of the command is terminated. The queue manager continues in single BSDS mode.

Determine the cause of the error from the error status contained in the message, and correct the condition. Then re-enter the RECOVER BSDS command.

Go to the z/OS MVS Authorized Assembler Services Guide and select the Interpreting DYNALLOC return codes topic for information about these codes .

The RECOVER BSDS command encountered an error while attempting to write to the specified BSDS. Error status contains the VSAM return and feedback codes. It is a 2-byte field with the first containing the hexadecimal return code and the second containing the hexadecimal feedback code.

Processing of the command is terminated. The queue manager continues in single BSDS mode.

Run an offline Access Method Services job to delete or rename the replacement BSDS and define a new BSDS with the same name. Re-enter the RECOVER BSDS command to reestablish dual BSDS mode.

The RECOVER BSDS command encountered an error while attempting to close the specified BSDS. Error Status contains the VSAM return and feedback codes. It is a 2-byte field with the first containing the hexadecimal return code and the second containing the hexadecimal feedback code.

Processing of the command is terminated. The queue manager continues in single BSDS mode.

Run an offline Access Method Services job to delete or rename the replacement BSDS and define a new BSDS with the same name. Re-enter the RECOVER BSDS command to reestablish dual BSDS mode.

The RECOVER BSDS command was issued, but the replacement BSDS was not empty; that is, it contained data.

Processing of the command is terminated. The queue manager continues in single BSDS mode.

Run an offline Access Method Services job to delete or rename the error BSDS and define a new BSDS with the same name. Re-enter the RECOVER BSDS command to reestablish dual BSDS mode.

The RECOVER BSDS command was issued, but the queue manager was already in dual BSDS mode.

The command is ignored.

The RECOVER BSDS command was issued, but the queue manager was initialized in single BSDS mode.

Processing of the command is terminated. The queue manager continues in single BSDS mode.

The ARCHIVE LOG command was issued, but archiving is off (that is, OFFLOAD is set to 'NO' in the CSQ6LOGP system parameters).

The current active log data set is not offloaded. However, it is truncated and logging continues using the next active log data set.

An ARCHIVE LOG command with the MODE(QUIESCE) and WAIT(YES) options has been accepted by the queue manager. The quiesce processing has commenced.

WAIT(YES) means that quiesce processing will be synchronous to the user; that is, the user can enter additional commands, but they will not be processed until the quiesce processing has ended.

The queue manager attempts to stop all updates to IBM MQ resources within the time period specified in the message. Users and jobs using the queue manager are allowed to reach a point of consistency (commit point) before being blocked from further update activity. Users and jobs are suspended until they are released by the queue manager following the initiation of the offload processing. If the queue manager can effectively block all users from performing updates before the maximum specified time, the offload is initiated immediately, and normal processing is resumed.

This message will be followed by message CSQJ311I or CSQJ317I.

An ARCHIVE LOG command with the MODE(QUIESCE) and WAIT(NO) by the queue manager. The quiesce processing has commenced.

WAIT(NO) means that quiesce processing will be asynchronous to the user; that is, control will be returned to the invoker as soon as the quiesce task has been started. Thus, the queue manager will accept, and process, any new commands while the quiesce task is running.

The queue manager attempts to stop all updates to IBM MQ resources within the time period specified in the message. Users and jobs using the queue manager are allowed to reach a point of consistency (commit point) before being blocked from further update activity. Users and jobs are suspended until they are released by the queue manager following the initiation of the offload processing. If the queue manager can effectively block all users from performing updates before the maximum specified time, the offload is initiated immediately, and normal processing is resumed.

This message will be followed by message CSQJ311I or CSQJ317I.

A user-initiated ARCHIVE LOG command has been accepted by the queue manager. A task to archive (offload) the active log data set has been started.

The current active log data sets will be truncated and switched to the next available active log data sets. The task has been started will archive the active log data sets asynchronously, allowing the queue manager to continue processing.

This message will be followed by the CSQJ312I message if the MODE(QUIESCE) option was used with the ARCHIVE LOG command.

An ARCHIVE LOG command with the MODE(QUIESCE) option was processed by the queue manager. As part of the MODE(QUIESCE) processing, an attempt was made to stop all new update activity against IBM MQ resources. This message signals the end of the quiesce processing, and the resumption of normal activity for all users and jobs which were blocked during the quiesce period.

This message will follow the CSQJ311I message or CSQJ317I message.

The queue manager has now resumed all normal activity for all users and jobs which were blocked during the quiesce period.

A command was entered that specified the kwd1 keyword. However, use of this keyword requires that the kwd2 keyword is also used.

Processing for the command is terminated.

An attempt was made to issue an ARCHIVE LOG command when a STOP QMGR MODE(FORCE) command was already in progress.

Command processing will terminate for the ARCHIVE LOG command. The STOP QMGR MODE(FORCE) processing will continue.

An ARCHIVE LOG command with the MODE(QUIESCE) option or a SUSPEND QMGR LOG command was issued when a system quiesce was already in progress. The system quiesce could be the result of processing by another ARCHIVE LOG MODE(QUIESCE) command, or by a STOP QMGR MODE(QUIESCE) command.

Command processing will terminate. The system quiesce currently in progress will continue.

An ARCHIVE LOG MODE(QUIESCE) command was processed by the queue manager. However, the queue manager was not able to quiesce all update activity in the user-specified quiesce time interval.

This message is for information only. The queue manager determined that nn units of recovery did not reach a point of consistency during the quiesce period, and therefore could not be stopped from continuing their associated update processing.

Consequently, the ARCHIVE LOG processing will be terminated. The current active log data sets will not be truncated, and will not be switched to the next available active log data sets. The log archive (offload) task will not be created. All jobs and users suspended during the quiesce will be resumed, and normal update activity against IBM MQ resources will be commenced.

This message will be followed by the CSQJ312I message.

You must decide whether the outstanding (non-quiesced) units of recovery represent significant work.

Each user on the system has a unit of recovery if they are modifying IBM MQ resources. Units of recovery are also created by the queue manager itself for internal processing. Because the purpose of the MODE(QUIESCE) option is to have all units of recovery reach a point of consistency (commit point) before the active log data set is truncated and offloaded, determine all outstanding non-queued jobs and users by using DISPLAY THREAD and the z/OS command DISPLAY ACTIVE,LIST.

Note that units of recovery might be outstanding due to lock contention between a user or job that holds a resource (and has reached a point of consistency), and a user or job that wants a lock (and therefore cannot reach a point of consistency).

If expiration of the quiesce period before all units of recovery reach a consistent point is a problem, you might have to adjust the QUIESCE value in the CSQ6ARVP system parameters. For more information, see Using CSQ6ARVP.

An attempt was made to issue an ARCHIVE LOG command when another ARCHIVE LOG command was already in progress.

Command processing will terminate. The ARCHIVE LOG command currently in progress will continue.

The ARCHIVE LOG command was rejected because the current active log is the last available active log data set. To process the command when these conditions exist would cause the queue manager to exhaust its available active log resources and immediately halt processing.

Processing for the command is terminated.

If the situation is not corrected, the queue manager will issue the CSQJ110E message (if it has not already done so) when the available active log data space reaches critically low levels. Ultimately, message CSQJ111A will be issued when the available active log data space is exhausted, and processing will stop until active log space is made available.

To clear this condition, steps must be taken to complete other waiting offload tasks. Once another active log is made available (re-usable) by completing the offload process for it, the command processing for the current active log can proceed.

Perform a display request to determine the outstanding requests related to the log offload process. Take the necessary action to satisfy any requests, and permit offload to continue.

If offload does not complete normally, or cannot be initiated, either correct the problem that is causing the offload problem, or consider whether there are sufficient active log data sets. If necessary, additional log data sets can be added dynamically using the DEFINE LOG command.

While processing an ARCHIVE LOG command, an internal request was made of the log buffer output routine to force-write the log buffers and to truncate and switch the active log to the next available active log data sets.

Processing for the command is terminated.

This is an internal error detected by the queue manager. The error might be caused by an unrelated error in the log buffer writer component (CSQJWxxx), by a STOP QMGR MODE(FORCE) command, or by abnormal termination. See any messages that precede this message.

An ARCHIVE LOG command with the MODE(QUIESCE) option was processed by the queue manager. As part of the MODE(QUIESCE) processing, an attempt was made to stop all new update activity against IBM MQ resources. During the processing, an internal error occurred.

The ARCHIVE LOG MODE(QUIESCE) processing is terminated. This message will be followed by message CSQJ312I after all users and jobs quiesced by the MODE(QUIESCE) processing are resumed.

This error is an internal error detected by the queue manager. Retry the ARCHIVE LOG MODE(QUIESCE) command. If the error persists, the active log data sets can be switched using the ARCHIVE LOG command without the MODE(QUIESCE) option.

Processing continues.

Processing continues.

This message lists the names of the archive log volumes needed by the indicated correlation ID for the given connection ID. The archive log volumes are listed with a maximum of six on each line. It is generated automatically by the archive read process at the first archive log tape mount for that correlation ID. The connection ID is an identifier representing the connection name used to establish the thread; the correlation ID is an identifier associated with a specified thread, such as a job name.

A volume name prefixed with an '*' signifies that the data on the archive log volume is also mapped by an active log data set. As such, the volume might not be required for the read process, because the data is read from the active log if possible.

CSQJ330I: ARCHIVE LOG VOLUMES required for connection-ID xxxx, 
 correlation-ID yyyyyy: volume1, volume2, volume3, volume4, volume5, volume6 End of ARCHIVE LOG VOLUMES report 

Processing continues.

The parameter value specified is not an acceptable value for the named keyword, or is incompatible with values set for other keywords.

Processing for the command is terminated.

No keywords or an unacceptable combination of keywords was specified on a command.

Processing for the command is terminated.

The SET command completed successfully, setting system parameter values for the indicated parm-type (SYSTEM, LOG, or ARCHIVE).

This is issued as part of the response to a DISPLAY SYSTEM command if the MQ-IMS Bridge facility to the partner IMS system identified by gname and mname is suspended.

Use the RESUME QMGR FACILITY(IMSBRIDGE) command when ready to resume the IBM MQ-IMS Bridge.

This is issued as part of the response to a DISPLAY SYSTEM command if the connection to Db2 is suspended.

Use the RESUME QMGR FACILITY(Db2) command when ready to resume the connection to Db2.

A SUSPEND QMGR LOG command was issued, but logging was already suspended by a previous command.

The command is ignored.

A SUSPEND QMGR LOG command was issued, but the queue manager is stopping.

The command is ignored.

A RESUME QMGR LOG command was issued, but logging was not suspended.

The command is ignored.

A SUSPEND QMGR LOG command was issued, but it terminated abnormally.

The command is ignored, and logging is not suspended.

Verify the command entry, and reissue the command. If it fails again, collect the items listed in the Problem Determination section, and contact your IBM support center.

Processing continues.

This is issued in response to a SUSPEND QMGR LOG command if it completed successfully.

It is also issued in response to other commands if logging is suspended, indicating that the command cannot be processed while logging is suspended.

All log update activity is suspended for the queue manager named. rrr is the RBA of the last log record written.

For commands other than SUSPEND QMGR LOG, the command is ignored.

Use the RESUME QMGR LOG command when ready to resume logging.

The RESUME QMGR LOG command completed successfully.

All log update activity is resumed for the queue manager named.

An attempt was made to read the rrrr record from the BSDS. In doing so, the read routine (CSQJU01B) could not find the record.

This is not necessarily an error; for example, if you have never used CSQJU003 CRESTART, there will not be any CRCR records, so you will get this message from CSQJU004 for the RESTART CONTROL records.

Utility processing continues.

An invalid keyword was used during the oper operation.

The current utility processing is terminated.

Keywords kwd1 and kwd2 cannot appear on the same control statement.

The current utility processing is terminated.

A required keyword was not used on the control statement. Use either kwd1 or kwd2 with that control statement type.

The current utility processing is terminated.

After completing its search through the resource manager status table and the checkpoint queue, no valid checkpoint RBA was found within the specified range.

The current utility processing is terminated.

The last 100 checkpoints are recorded in the BSDS, including the log STARTRBA and log ENDRBA of the checkpoint range. The utility attempts to locate a valid checkpoint in the range. In this case the utility was unsuccessful in finding a valid checkpoint.

Use the Print Log Map Utility (CSQJU004) to determine the valid RBA ranges, and rerun the job with a suitable RBA specification.

After completing its search through the resource manager status table and the checkpoint queue, rba was the most recent checkpoint RBA in the specified range, and date time was the time of the checkpoint.

Utility processing continues.

An input/output error occurred during a READ of a record. yyy specifies the record in question.

The current utility processing is terminated. This message is accompanied by message CSQJ212E.

Determine the cause of the error based on the error status information provided in message CSQJ212E.

An input/output error occurred during a WRITE of a record. yyy specifies the record in question.

The current utility processing is terminated. This message is accompanied by message CSQJ213E.

Determine the cause of the error based upon the error status information provided in message CSQJ213E.

A CRESTART CREATE request has just completed. yyyy is the restart control record hexadecimal identifier and ddd is the BSDS data set (SYSUT1 or SYSUT2) associated with the request.

Current® utility processing continues.

Note the record identifier for future reference.

A CRESTART CANCEL keyword was specified but the conditional restart control record does not exist in the BSDS data set.

Current utility processing is terminated.

None necessary, if CANCEL was the intended action. Otherwise, correct the control statement and rerun the utility.

The values specified through the STARTRBA and ENDRBA keywords are invalid.

Current utility processing is terminated.

Ensure that the log range values are correct and correspond to the other log range values either specified or defaulted. The STARTRBA must be less than or equal to the ENDRBA.

STARTRBA and ENDRBA are equal. A cold start will result if this restart control record is used during restart. No forward or backout processing will be performed.

CRESTART processing continues.

No additional actions are required if a cold start of the queue manager is desired. If a cold start is not desired, reissue the CRESTART and either CANCEL the current restart control record, or CREATE a new restart control record.

The specified ENDRBA at rba is not a multiple of 4K.

CRESTART processing is terminated.

Correct the ENDRBA value on the CRESTART statement and rerun the utility.

As a result of a change log inventory update, it was discovered that the SYSUT1 BSDS and SYSUT2 BSDS time stamps are unequal. Their inequality indicates the possibility of a BSDS mismatch.

Current utility processing continues.

Run the print log map utility against the SYSUT1 BSDS and SYSUT2 BSDS. Determine if each BSDS is current. If each BSDS is current, this warning can be ignored. If either BSDS is not current, delete the obsolete data set and define a replacement data set, then copy the current BSDS into the replacement data set.

Required parameter xxxx for a log utility operation was missing from the log utility control statement. The attempted operation is oper.

The log utility oper operation does not perform its function. All subsequent log utility control statements are processed. A nonzero return code is issued by the utility.

Add the missing parameter to the control statements associated with the specified operation and rerun the utility.

The data set name specified on the DSNAME parameter of the change log inventory utility DELETE statement was a NOTREUSABLE active log.

The change log inventory utility processing continues. It will terminate with a return code of 4.

No additional actions are required if you want to delete a NOTREUSABLE active log. If not, re-create the deleted log by using the NEWLOG statement with the RBA values specified in the warning message.

A CRESTART CANCEL request has just completed. yyyy is the restart control record hexadecimal identifier and ddd is the BSDS data set (SYSUT1 or SYSUT2) associated with the request.

Current utility processing continues.

Note the record identifier for future reference.

The xxxx parameter contains an incorrect value or incorrect format for the date and time.

The current utility is terminated.

Correct the control statement and rerun the utility.

The STARTIME and ENDTIME parameters specify a time range. Therefore, the ENDTIME value must be equal to or greater than STARTIME value.

The current utility is terminated.

Correct the control statement and rerun the utility.

The checkpoint record specified has been added to the checkpoint queue in the BSDS.

Processing continues.

The checkpoint record specified has been deleted from the checkpoint queue in the BSDS. sss and ttt was the RBA range indicated in the deleted checkpoint record.

Processing continues.

The specified RBA range for the new checkpoint record either exists, or overlaps an existing RBA range in the checkpoint queue in the BSDS.

The current utility is terminated.

Run the print log map utility against the SYSUT1 BSDS and SYSUT2 BSDS. Determine the correct RBA range, correct the STARTRBA and ENDRBA parameters, and rerun the utility.

The specified RBA range for the new checkpoint record is less than the lowest existing entry. The checkpoint queue in the BSDS is currently full and cannot add the new entry without overlaying the lowest entry.

The current utility is terminated.

Run the print log map utility against the SYSUT1 BSDS and SYSUT2 BSDS. Determine the lowest existing entry, either change the STARTRBA and ENDRBA parameters or delete the lowest existing entry and add a new low checkpoint entry, and rerun the utility.

The specified STARTRBA could not be located in the checkpoint queue in the BSDS.

The current utility is terminated.

Run the print log map utility against the SYSUT1 BSDS and SYSUT2 BSDS. Determine the correct STARTRBA value, correct the STARTRBA parameter, and rerun the utility.

The value specified for keyword kwd is not valid. It must end with 'xxx'.

The current utility is terminated.

Correct the control statement and rerun the utility.

This message is issued as part of the header to reports issued by the utility programs.

This message is issued as a header to the report issued by the utility program.

This message is issued as a header to the report issued by the utility program.

This message is issued as a header to the report issued by the utility program.

The BSDS conversion utility detected that at least one queue manager in the queue-sharing group does not support the version of BSDS that will be produced as a result of the conversion.

The current utility is terminated with no action taken.

Migrate all queue managers in the queue-sharing group to a level that supports the new BSDS version and change the setting of OPMODE if necessary, then run the conversion utility again.

A data set provided to the BSDS conversion utility is unusable because the CI size is not correct. The CI size of the BSDS must be 4096. The variable ddd contains the DD name of the data set..

The current utility is terminated with no action taken.

Ensure that the DD statement refers to a valid BSDS. If the DD name refers to an output data set, delete and redefine the output BSDS, then rerun the utility.

A mismatch was detected in the timestamps for the SYSUT1 and SYSUT2 BSDS copies during execution of the BSDS conversion utility. This mismatch indicates the possibility that the dual BSDSs are out of sync.

The current utility is terminated with no action taken.

Run the print log map utility (CSQJU004) against each BSDS. From the output, determine which data set is obsolete, delete it, and define a replacement for it. Then copy the remaining data set into the replacement and try the utility again.

If output from the print log map utility for both data sets is similar, delete the data set with the oldest timestamp, then copy the data set with the most recent timestamp into the replacement.

The BSDS conversion utility detected that the input BSDS was not in the correct format to be converted. The input BSDS must be in version 1 format. The variable ddd contains the DD name of the data set.

The current utility is terminated with no action taken.

Run the print log map utility (CSQJU004) against the BSDS to determine its version. Ensure that the DD statement refers to an input BSDS in version 1 format, then rerun the utility if necessary.

During conversion of the BSDS, a record was found that is not a known format. The key-value is the VSAM KSDS key of the BSDS record that was not recognized.

The current utility is terminated.

To determine the operation that inserted the record into the BSDS, use IDCAMS PRINT and specify this key value. If the record is not needed, delete it then rerun the BSDS conversion.

This message is issued when a utility, attempting to access the BSDS data set, encounters an invalid BSDS. An invalid BSDS is the result of a failure during a prior attempt to run the BSDS conversion utility.

The current utility is terminated with no action taken.

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.

The xxxx parameter specifies the name of the parameter with a value that exceeds the maximum that can be specified for a BSDS in version n format.

The current utility is terminated.

Correct the parameter argument on the control statement, then rerun the utility.

This message is issued as a header to the report issued by the utility program.

This identifies the name of the log data set to be preformatted.

The input log data set is not a VSAM data set.

Utility processing is terminated.

Check that the SYSUT1 DD statement and the data set name is specified correctly. Use Access Method Services to define the data set as a VSAM linear data set.

Opening the log data set failed with the indicated ACB error code.

Utility processing is terminated if the error code is 128 or more; otherwise processing continues.

See the DFSMS/MVS Macro Instructions for Data Sets for information about the VSAM error code.

Writing the log data set failed with the indicated RPL error code and reason code.

Utility processing is terminated.

See the DFSMS/MVS Macro Instructions for Data Sets for information about the VSAM error code and reason code.

The active log data set has been preformatted successfully.

Utility processing is complete.

Preformatting the active log data set did not complete successfully.

Utility processing is terminated.

See the preceding error messages for more information.

The input log data set is not an empty data set.

Utility processing is terminated.

Check that the SYSUT1 DD statement and the data set name is specified correctly. Use Access Method Services to define the data set as a VSAM linear data set.

Log data set is larger than 4GB

The log preformat utility, CSQJUFMT, detected that the VSAM data set to be formatted is greater than 4 GB in size.

Processing continues. The entire data set will be pre-formatted, but IBM MQ for z/OS log data sets are restricted to a maximum of 4 GB. Any additional space in the data set is not used to hold log data.

If an SMDS is being pre-formatted that is intended to be greater than 4 GB, if it is defined using an SMS data class which has the VSAM extended addressability attribute it will not be restricted to a maximum of 4 GB.

Check that the data set name is specified correctly. Use Access Method Services to define the data set with a maximum size of 4 GB.