Recovery log manager messages (CSQJ...)

CSQJ001I

CURRENT COPY n ACTIVE LOG DATA SET IS DSNAME=dsname, STARTRBA=sss ENDRBA=ttt

Explanation

This message is generated for one of two reasons:

When the queue manager starts, this information message is sent to identify the current active log data sets (copy 1 and, if dual logging is used, copy 2).
When the current active log data set is full (or when an ARCHIVE LOG command is issued), MQ will switch to the next available active log data set. This message identifies the next available active log data set that will be used for logging.

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.

System programmer response

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

CSQJ002I: END OF ACTIVE LOG DATA SET DSNAME=dsname, STARTRBA=sss ENDRBA=ttt
Explanation: 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.
System programmer response: None required. However, if recovery is required, information from this message might be required as input to the change log inventory utility (CSQJU003).

CSQJ003I

FULL ARCHIVE LOG VOLUME DSNAME=dsname, STARTRBA=sss ENDRBA=ttt, STARTTIME=ppp ENDTIME=qqq, UNIT=unitname, COPYnVOL=vvv VOLSPAN=xxx CATLG=yyy

Explanation

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.

System action

An archive log data set has been created, and the archive log data set inventory in the BSDS has been updated with the information in the message:

DSNAME

The name of the archive log data set

STARTRBA

The starting RBA contained in the volume

ENDRBA

The ending RBA contained in the volume

STARTTIME

The starting store-clock value of the log records in the volume

ENDTIME

The ending store-clock value of the log records in the volume

UNIT

The device unit to which the data set was allocated

COPYnVOL

The name of the volume; this is displayed as COPY1VOL if this is the copy-1 archive log data set, and as COPY2VOL if this is the copy-2 archive log data set

VOLSPAN

An indicator to denote one of four conditions:

NO: The data set is entirely contained on the volume specified by COPYnVOL
FIRST: This is the first entry of a multivolume data set
MIDDLE: This is the middle entry of a multivolume data set
LAST: This is the last entry of a multivolume data set

CATLG

An indicator to denote one of two conditions:

NO: The archive log data set is uncataloged
YES: The archive log data set is cataloged

The BSDS is automatically updated with the information contained in this message; however, if recovery is required, information from this message might be required as input to the change log inventory utility (CSQJU003).

CSQJ004I

ACTIVE LOG COPY n INACTIVE, LOG IN SINGLE MODE, ENDRBA=ttt

Explanation

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.

System action

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

If the queue manager is shut down or terminates abnormally while in single mode with the system parameter option still set for dual active data sets, the previous state of the active log data sets determines what happens when the queue manager is started, as follows:

If fewer than two data sets are available (not flagged as STOPPED) for each set of active logs, queue manager startup terminates and message CSQJ112E is issued.
If an active log data set is in NOTREUSABLE state, the queue manager can be started in single logging mode, but dual mode takes effect when the other active log data set becomes available after offloading.

System programmer response

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

CSQJ005I: ACTIVE LOG COPY n IS ACTIVE, LOG IN DUAL MODE, STARTRBA=sss
Explanation: 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.
System programmer response: None required. However, if recovery is required, information from this message might be required as input to the change log inventory utility (CSQJU003).

CSQJ006I: ALLOCATION FOR NEW ARCHIVE LOG DATA SET HAS BEEN CANCELED BY OPERATOR
Explanation: This message is sent if the operator answers 'N' to message CSQJ008E.
System action: 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.

CSQJ007I: ALLOCATION FOR ARCHIVE VOL SER=volser HAS BEEN CANCELED BY OPERATOR
Explanation: 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.
System action: 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.

CSQJ008E: nn OF mm ACTIVE LOGS ARE FULL, qmgr-name NEEDS ARCHIVE SCRATCH
Explanation: IBM 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.
System action: The offload task issues message CSQJ021D and waits for the operator's reply.

CSQJ009E: qmgr-name NEEDS VOL SER= nnnnnn
Explanation: MQ needs the specified archive volume for a read operation. qmgr-name is the name of the queue manager.
System action: 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.

CSQJ010I: INVALID RESPONSE - NOT Y OR N
Explanation: 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.
System action: The original message is repeated.

CSQJ011D

RESTART CONTROL rrr CREATED AT date time FOUND. REPLY Y TO USE, N TO CANCEL

Explanation

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 we want a conditional restart using that record, reply 'Y' to the message. Otherwise, reply 'N'.

System action

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

System programmer response

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.

CSQJ012E

ERROR ccc READING RBA rrr IN DATA SET dsname, CONNECTION-ID=xxxx THREAD-XREF=yyyyyy

Explanation

While scanning log records read into a buffer, IBM 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.

System action

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.

System programmer response

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

CSQJ013E

TERMINAL ERROR ccc IN BUFFER rrr BEFORE ACTIVE LOG WRITE

Explanation

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.

System action

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.

System programmer response

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.

CSQJ014E

TERMINAL ERROR ccc IN BUFFER rrr AFTER ACTIVE LOG WRITE

Explanation

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.

System action

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

System programmer response

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.

CSQJ020I: csect-name RECEIVED REPLY OF N TO msg-num. QUEUE MANAGER STARTUP IS TERMINATED
Explanation: The operator chose to terminate queue manager startup by answering 'N' to msg-num.
System action: The queue manager will not restart.

CSQJ021D: REPLY Y WHEN DEVICE READY OR N TO CANCEL
Explanation: An archive log data set needs allocating, as indicated in the preceding CSQJ008E or CSQJ009E message.
System action: The log service task waits for the operator's reply.

CSQJ022I: DSNAME=dsname
Explanation: dsname is the name of the archive data set to which the preceding message refers.

CSQJ030E

RBA RANGE startrba TO endrba NOT AVAILABLE IN ACTIVE LOG DATA SETS

Explanation

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.

System action

The queue manager terminates with a dump.

System programmer response

The log RBA range must be available for the queue manager to be recoverable. Correct the previous errors and restore the active log data sets that contain the RBA range reported in the message.

If the log data sets are recoverable, the active log data set inventory in the BSDS must be modified to reset the STOPPED status. Use the print log map utility (CSQJU004) to obtain a copy of the BSDS log inventory. Next, use the change log inventory utility (CSQJU003) to delete the active log data sets marked STOPPED (use the DELETE statement), then add them again (use the NEWLOG statement). The starting and ending RBA for each active log data set must be specified on the NEWLOG statement when the logs are added back to the BSDS using the change log inventory utility.
If the log data sets are not recoverable, see Active log problems for information about dealing with problems on the log.

CSQJ031D

csect-name, THE LOG RBA RANGE MUST BE RESET. REPLY 'Y' TO CONTINUE STARTUP OR 'N' TO SHUTDOWN.

Explanation

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.

System action

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

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

System programmer response

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 Plan to increase the maximum addressable log range for further information.

CSQJ032E

csect-name alert-lvl - APPROACHING END OF THE LOG RBA RANGE OF max-rba. CURRENT LOG RBA IS current-rba.

Explanation

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 data set is full and the queue manager switches to the next available log data set.

alert-lvl indicates one of the following:

WARNING: Issued when the current log RBA reaches the F80000000000 value (if 6-byte log RBAs are in use) or FFFFC00000000000 (if 8-byte log RBAs are in use).
CRITICAL: Issued after the log RBA value reaches FF8000000000 (if 6-byte log RBAs are in use) or FFFFFC0000000000 (if 8-byte log RBAs are in use).

System action

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.

System programmer response

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 Plan to increase the maximum addressable log range for further information.

CSQJ033I

FULL ARCHIVE LOG VOLUME DSNAME=dsname, STARTRBA= sss ENDRBA=ttt, STARTLRSN=ppp ENDLRSN=qqq, UNIT=unitname, COPYnVOL=vvv VOLSPAN=xxx CATLG=yyy

Explanation

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.

System action

See message CSQJ003I. STARTTIME and ENDTIME are replaced by the following:

STARTLRSN: The starting LRSN contained in the volume for queue sharing groups.
ENDLRSN: The ending LRSN contained in the volume for queue sharing groups.

CSQJ034I

csect-name END OF LOG RBA RANGE IS max-rba

Explanation

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.

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

System action

Processing continues

System programmer response

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 Plan to increase the maximum addressable log range for further information.

CSQJ060E: parm-name system parameters are unusable
Explanation: The format of the parameters set by parm-name in the system parameter load module is invalid, so they cannot be used.
System action: The queue manager is terminated with abnormally with reason code X'00E80084'.
System programmer response: 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 the system parameter load module.

CSQJ061I: parm-name system parameters are obsolete
Explanation: The parameters set by parm-name in the system parameter load module use some values which are now obsolete.
System action: Processing continues. The obsolete parameters are ignored, and default values are used for new parameters.
System programmer response: Review the system parameter settings. If necessary, reassemble the module that uses the indicated parameters, and relink-edit the system parameter load module.

CSQJ070E: csect-name ARCHIVE LOG DSN PREFIX NOT IN PROPER FORMAT TO RECEIVE TIME STAMP DATA. TIME STAMPING OF dsname BYPASSED
Explanation: 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, IBM 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.
System action: 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.
System programmer response: 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.

CSQJ071E: csect-name TIMER FAILURE CAUSED TIME STAMPING OF ARCHIVE dsname TO BE BYPASSED
Explanation: 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.
System action: 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.

CSQJ072E: ARCHIVE LOG DATA SET dsname HAS BEEN ALLOCATED TO NON-TAPE DEVICE AND CATALOGED, OVERRIDING CATALOG PARAMETER
Explanation: 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.
System action: 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.
System programmer response: 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.

CSQJ073E

LOG ARCHIVE UNIT ALLOCATION FAILED, REASON CODE= ccc. ALLOCATION OR OFFLOAD OF ARCHIVE LOG DATA SET MAY FAIL

Explanation

While building the SVC99 text entries to allocate a new archive log data set dynamically, a unit allocation error was detected. The reason code, indicated by ccc in the message, further clarifies the problem as follows:

4-28 (X'4'-X'1C')

Return code from z/OS IEFGB4UV macro. Common values are:

4 (X'04'): Invalid unit name
8 (X'08'): Unit name has incorrect units assigned
16 (X'10'): No storage available
20 (X'14'): Device numbers not valid

32 (X'20')

MQ was able to obtain a list of devices corresponding to the device type (unit name) specified in the system parameters. However, it was determined that this list contained a mixture of tape and nontape devices.

36 (X'24')

Nonfetch-protected storage could not be obtained to build a parameter list for a z/OS service.

40 (X'28')

The device type (unit name) specified by the user in the system parameters is valid. However, no devices are currently associated with the given device type (unit name).

44 (X'2C')

The device type (unit name) specified by the user in the system parameters is valid. However, no DASD volumes are available with a volume use attribute of storage.

System action

This message is issued after the SVC99 text entries are built, but prior to the allocation of the new archive log data set. As a result of the error, the dynamic allocation of the archive log data set will be attempted using standard default values. The standard default values are generally acceptable; however, the allocation might be unsuccessful or the subsequent offload might produce undesirable processing results. For example:

A reason code of 4 or 44 (X'2C') indicates an allocation error (CSQJ103E) when the SVC99 is issued for the archive data set.
Offload processing to tape might be unsuccessful. IBM MQ uses a volume count of 20 when allocating to tape, and uses the standard z/OS volume count default of 5 volumes when writing to non-tape devices. In the case of most of the above errors, it would be impossible for IBM MQ to determine the device type on which the data set is to be allocated. Therefore, the standard z/OS default is assumed for the volume count. If the data set is successfully allocated to a tape device, and the volume of data is such that more than five volumes will be used for the archive data set, the offload processing will receive a z/OS completion code X'837-08' with message IEC028I when attempting to write to the sixth tape volume.
Offload processing to a direct access device might be unsuccessful. When allocating a new archive log data set on a direct access device, IBM MQ will use a unit count to facilitate multivolume archive data sets. With most of the above errors, it might be impossible for IBM MQ to correctly determine the type of device on which the data set is to be allocated. Therefore, the standard default (1) is assumed for the unit count. If the data set is successfully allocated to a direct access device, and during the offload processing it becomes necessary to extend the data set to another device, the offload processing will receive a z/OS X'B37' (out of space) completion code, and the archive log data set will be deallocated.

System programmer response

The required action is based on the reason code indicated in the message:

4-28 (X'4'-X'1C')

See the MVS™ Authorized Assembler Services Guide for more info about the return code from the z/OS IEFGB4UV macro. The most likely causes for the common values are:

4 (X'04'): Incorrect specification in the archive system parameters. Correct the UNIT parameter. If the UNIT parameter from the archive system parameters appears to be correct, check the EDT to ensure that the esoteric or generic unit name specified in the parameters is actually in the EDT. Subsequent offload processing will archive the log data which could not be previously archived due to the allocation error (CSQJ103E).
8 (X'08'): Incorrect specification in archive system parameters, incorrect operational setup.
16 (X'10'): This is usually a temporary problem. If the allocation of the archive log data set is successful, no action is required to correct this situation. If this is a recurring problem, sufficient page space is not available, and the region size for the queue manager address space might have to be increased, or standard z/OS diagnostic procedures might have to be used to correct the problem.
20 (X'14'): Incorrect specification in archive system parameters, incorrect operational

32 (X'20') or 40 (X'28')

To correct this situation, change the archive system parameter UNIT to use a device type (unit name) that contains homogenous devices, or modify the device list associated with the device type (unit name) using a system generation to supply a list of homogenous devices.

44 (X'2C')

To correct this situation, issue the z/OS command MOUNT to change the volume use attribute of a mounted private volume to storage. If this is a recurring problem, you might have to do one of the following:

Perform a system generation to add permanently resident volumes with a volume use attribute of storage to the esoteric or generic unit
Change the archive system parameters to use a different esoteric or generic unit name for the UNIT

CSQJ077E

LOG OR BSDS READ ERROR FOR QMGR qmgr-name, REASON CODE=ccc

Explanation

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.

System action

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

System programmer response

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

For reason code 00D10905, which indicates that there is a mismatch between the two BSDS timestamps of the peer queue manager, we can resolve the problem by restarting the peer queue manager.

If we are unable to solve the problem, note the reason code, collect the following items, and contact the IBM support center:

System dump
Console output for the issuing queue manager
Console output for the other queue manager
Printout of SYS1.LOGREC

CSQJ098E: csect-name RESTART CONTROL ENDLRSN rrr IS NOT IN KNOWN LRSN RANGE. QUEUE MANAGER STARTUP IS TERMINATED
Explanation: 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.
System action: Queue manager startup is terminated.
System programmer response: 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.

CSQJ099I

LOG RECORDING TO COMMENCE WITH STARTRBA= sss

Explanation

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.

System programmer response

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

CSQJ100E: csect-name ERROR OPENING BSDSn DSNAME= dsname, ERROR STATUS=ee,ii
Explanation: 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.
System action: 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.
System programmer response: Recover the BSDS that cannot be opened. See Active log problems for information about dealing with problems on the BSDS or the log.

CSQJ101E

csect-name RESTART CONTROL ENDRBA rrr IS NOT IN KNOWN RBA RANGE. QUEUE MANAGER STARTUP IS TERMINATED

Explanation

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.

System action

Queue manager startup is terminated.

System programmer response

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.

CSQJ102E: LOG RBA CONTENT OF LOG DATA SET DSNAME= dsname, STARTRBA= sss ENDRBA=ttt, DOES NOT AGREE WITH BSDS INFORMATION
Explanation: The log RBA range shown in the BSDS for the specified data set does not agree with the content of the data set.
System action: Startup processing is terminated.
System programmer response: Use the print log map and change log inventory utilities to make the BSDS consistent with the log data sets.

CSQJ103E

csect-name LOG ALLOCATION ERROR DSNAME=dsname, ERROR STATUS=eeeeiiii, SMS REASON CODE=ssssssss

Explanation

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.

System action

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.

System programmer response

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.

Go to the z/OS MVS documentation in IBM Knowledge Center, and select the Interpreting DYNALLOC return codes topic of the MVS Authorized Assembler Services Guide for information about these codes .

For active log data sets, if the problem occurred during queue manager initialization, we can resolve the problem by doing one of the following:

Resolve the error associated with the active log data set as indicated by STATUS
Provide another copy of the active log data set, using Access Method Services
Update the BSDS with the change log inventory utility (CSQJU003)
Restart the queue manager

For archive log data sets:

If the problem occurred during allocation with the intent to write the data set, no immediate action is required. However, if we do not resolve the SVC99 error (indicated by the STATUS value in the message), the available space in the active log could eventually be exhausted (CSQJ111A) because all future offloads might be unsuccessful because of the same error.
If the problem occurred during allocation with the intent to read the data set, determine the problem, and use the change log inventory utility (CSQJU003) DELETE function to delete the archive log data set from the BSDS archive log inventory. Then use the NEWLOG function to add the data set back into the archive log inventory, pointing to the correct volume and device.

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

This message might also be issued as the result of a user error. If STATUS displays a value of '17080000', you might have one or more active log data sets defined in the BSDS, but not allocated on DASD. To correct the situation, print the contents of the current active log data set inventory using the print log map utility (CSQJU004), then either:

Use Access Method Services to allocate the active log data set for each active log data set listed in the BSDS, but not actually allocated on DASD. We can find the Access Method Services command syntax for active log data sets in the CSQ4BSDS sample JCL.
Use the change log inventory utility (CSQJU003) DELETE statement to delete the errant active log data set name, and the NEWLOG statement to add the correct name to the active log data set inventory. The name specified on the NEWLOG statement must be the same as the name of the actual active log data set allocated on DASD.

CSQJ104E

csect-name RECEIVED ERROR STATUS nnn FROM macro-name FOR DSNAME dsname

Explanation

An error ocurred while issuing macro macro-name. Error status is the return code from the specified macro:

For an OPEN of a VSAM data set, the return code in the error field of the Access Method Services control block is included in this message as the error status value. See the DFSMS/MVS Macro Instructions for Data Sets manual for a description of these values.
If the OPEN was for a non-VSAM data set, the error status is zero.
For MMSRV errors, error status contains the error information returned by media manager services. If an MMSRV CATUPDT error occurs attempting to truncate an active log data set, the log data set will be unavailable and the status of the log data set will be flagged as STOPPED in the BSDS.
For VSAM OPEN and MMSRV errors, this message is preceded by an IEC161I message that defines the error that occurred.
For a PROTECT of an archive log data set, the return code is from DADSM PROTECT. See the MVS/ESA System - Data Administration manual for details of the return code.

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

System action

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, IBM MQ attempts to allocate and open the second data set.

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

During checkpoint processing, where IBM 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.

System programmer response

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 we do not have information about the named macro, note the macro name and the return code and contact the 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 the CF structures, and institute a procedure to back up your CF structures frequently.

CSQJ105E

csect-name LOG WRITE ERROR DSNAME= dsname, LOGRBA=rrr, ERROR STATUS=ccccffss

Explanation

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.

System action

If the dual active logging option is selected, then IBM MQ switches to the next data set for this copy. If the next data set is not ready, IBM 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, IBM MQ waits for that data set to be available. In this case, log writing is inhibited until the replacement is ready for output.

System programmer response

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

CSQJ106E

LOG READ ERROR DSNAME=dsname, LOGRBA=rrr, ERROR STATUS=ccccffss

Explanation

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

System action

If another log data set contains the data, IBM 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.

System programmer response

If we 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 we are using single logging, immediate attention might be required. If so, note the contents of the error status field, and contact the 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.

This message might also be issued as the result of a user error. If the data set name specified by DSNAME is missing, and STATUS displays a value of '00180408' or '00100408', we are using dual logging, but only one set of active log data sets is defined in the BSDS. To resolve this condition, do either of the following:

Define a second set of active log data sets using Access Method Services (if they are not defined already), and update the BSDS log inventory, using the change log inventory (CSQJU003) NEWLOG operation.
Reset the log system parameters to indicate single logging. We can do this by setting TWOACTV to 'NO' in the CSQ6LOGP system parameters.

CSQJ107E

READ ERROR ON BSDS DSNAME=dsname ERROR STATUS=eee

Explanation

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.

System action

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.

System programmer response

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.

CSQJ108E

WRITE ERROR ON BSDS DSNAME=dsname ERROR STATUS=eee

Explanation

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.

System action

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.

System programmer response

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.

CSQJ109E

OUT OF SPACE IN BSDS DSNAME=dsname

Explanation

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

System action

If dual BSDSs are available, IBM 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.

System programmer response

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.

CSQJ110E

LAST COPYn ACTIVE LOG DATA SET IS nnn PERCENT FULL

Explanation

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.

System action

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 IBM MQ processing will stop.

System programmer response

To clear this condition, we 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 IBM 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.

Possible causes for the shortage of active log data space are:

Excessive logging. For example, there is a lot of persistent message activity.
Delayed or slow offloading. For example, failure to mount archive volumes, incorrect replies to offload messages, or slow device speeds.
Excessive use of the ARCHIVE LOG command. Each invocation of this command causes IBM MQ to switch to a new active log data set and to initiate an offload of the active log. Although the command will not be processed when only one active log data set remains in a copy of the active log (see CSQJ319I), excessive use of the command could have consumed all space in the active log except the current active log data sets.
Offloads were unsuccessful.
Insufficient active log space.

CSQJ111A

OUT OF SPACE IN ACTIVE LOG DATA SETS

Explanation

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

System action

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

System programmer response

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, we 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.

CSQJ112E

csect-name INSUFFICIENT ACTIVE LOG DATA SETS DEFINED IN BSDS

Explanation

There are not enough active log data sets defined in the BSDS to start the queue manager. This condition usually exists for one of the following reasons:

Fewer than two data sets are defined for one of the active log copy sets.
The CSQ6LOGP system parameters specified TWOACTV=YES but data sets for two copies of active log are not defined in BSDS.
Fewer than two data sets are available (not flagged as STOPPED) for one of the active log copy sets.

System action

Startup is terminated.

System programmer response

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.

Note: Log data sets that are flagged as STOPPED will not be reused by IBM MQ. Once the queue manager has been restarted you might need to recover STOPPED log data sets. To clear the STOPPED status:

Stop the queue manager
Recover the log data set (either redefined or recovered from the other copy of the log)
Delete and re-add to the BSDS (using the change log inventory utility) with the appropriate RBAs

CSQJ113E: RBA log-rba NOT IN ANY ACTIVE OR ARCHIVE LOG DATA SET, CONNECTION-ID=xxxx THREAD-XREF=yyyyyy
Explanation: 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.
System action: Depending upon what log record is being read and why, the requestor might end abnormally with a reason code of X'00D1032A'.
System programmer response: 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.

CSQJ114I: ERROR ON ARCHIVE DATA SET, OFFLOAD CONTINUING WITH ONLY ONE ARCHIVE DATA SET BEING GENERATED
Explanation: 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.
System action: Offload produces a single archive data set.
System programmer response: A second copy of this archive log data set can be made, and the BSDSs can be updated with the change log inventory utility.

CSQJ115E: OFFLOAD FAILED, COULD NOT ALLOCATE AN ARCHIVE DATA SET
Explanation: Offload could not allocate an archive log data set. The offload was not performed. This message is preceded by message CSQJ103E or `CSQJ073E.
Note: If we are using the dual archiving option, neither copy is made.
System action: Offload will be tried at a later time.
System programmer response: 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.

CSQJ116E: ERROR ADDING ARCHIVE ENTRY TO BSDS
Explanation: 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.
System action: Offload will be retried at a later time.
System programmer response: See the specific preceding message for action.

CSQJ117E: INITIALIZATION ERROR READING BSDS DSNAME= dsname, ERROR STATUS=eee
Explanation: 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.
System action: Startup is terminated.
System programmer response: Determine the cause of the read error using the VSAM error status information provided. Restart the queue manager.

CSQJ118E: MACRO xxx FAILED IN LOG INITIALIZATION, RC=ccc
Explanation: Log initialization received a return code from the named macro.
System action: Startup is terminated.
System programmer response: Determine the problem from the documentation on the named macro and return code. Then take appropriate steps, and restart the queue manager. If we do not have information about the named macro, note the macro name and the return code and contact the IBM support center for help.

CSQJ119E: BOOTSTRAP ACCESS INITIALIZATION PROCESSING FAILED
Explanation: 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.
System action: Startup is terminated.
System programmer response: 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.

CSQJ120E

DUAL BSDS DATA SETS HAVE UNEQUAL TIME STAMPS, SYSTEM BSDS1=sys-bsds1, BSDS2=sys-bsds2, UTILITY BSDS1=uty-bsds1, BSDS2=uty-bsds2

Explanation

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.

System action

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.

System programmer response

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.

CSQJ121E: INITIALIZATION ERROR READING JFCB, DDNAME=ddd
Explanation: 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.
System action: Startup is terminated.
System programmer response: 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.

CSQJ122E

DUAL BSDS DATA SETS ARE OUT OF SYNCHRONIZATION

Explanation

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

System action

The program or queue manager startup is terminated.

System programmer response

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.

CSQJ123E: CHANGE LOG INVENTORY FAILURE DETECTED
Explanation: During queue manager initialization, the BSDSs was found to have been incompletely processed by the change log inventory utility.
System action: Startup is terminated.
System programmer response: 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.

CSQJ124E: OFFLOAD OF ACTIVE LOG SUSPENDED FROM RBA xxxxxx TO RBA xxxxxx DUE TO I/O ERROR
Explanation: 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.
System action: Active log data sets continue to be offloaded as they become full.
System programmer response: 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.

CSQJ125E: ERROR COPYING BSDS, OFFLOAD CONTINUING WITHOUT THE BSDS COPY
Explanation: 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.
System action: The queue manager continues the offload process without producing a copy of the BSDS.
System programmer response: 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.

CSQJ126E: BSDS ERROR FORCED SINGLE BSDS MODE
Explanation: An input/output error or a VSAM logical error occurred on a BSDS. This message is preceded by message CSQJ107E or CSQJ108E.
System action: IBM MQ enters single BSDS mode using the remaining BSDS.
System programmer response: 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.

CSQJ127I

SYSTEM TIME STAMP FOR BSDS=date time

Explanation

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.

System action

Startup continues.

System programmer response

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.

CSQJ128E

LOG OFFLOAD TASK FAILED FOR ACTIVE LOG dsname

Explanation

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

System action

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

The log offload task will be reinitiated by one of several events. The most common are:

All the available space in the current active log data set has been used (normal case)
A CSQJ110E message is issued
The queue manager address space is started, but data in the active log has not been archived
An I/O error occurs on the active log, which will force the queue manager to truncate and offload the active log data set, and switch to a new active log data set

System programmer response

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.

CSQJ129E

END OF LOG RBA eol-rba COULD NOT BE FOUND IN ANY ACTIVE LOG DATA SET, HIGHEST RBA FOUND WAS hi-rba

Explanation

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.

System action

Startup processing is terminated.

System programmer response

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 the IBM support center.

CSQJ130I: DUAL BSDS MODE RESTORED FROM BSDSn
Explanation: Dual BSDS mode was restored using BSDS copy n. This is the BSDS data set with the most recent system time stamp.
System action: Startup continues.

CSQJ131E: csect-name ERROR WRITING QUEUE MANAGER INFORMATION TO Db2
Explanation: During command processing, a failure occurred attempting to write queue manager information to Db2.
System action: Processing of the command is terminated.
System programmer response: Check the console for messages relating to the problem.

CSQJ132E: csect-name ERROR READING QUEUE MANAGER INFORMATION FROM Db2
Explanation: During command processing, a failure occurred attempting to read queue manager information from Db2.
System action: Processing of the command is terminated.
System programmer response: Check the console for messages relating to the problem.

CSQJ133E: LRSN rrr NOT IN ANY ACTIVE OR ARCHIVE LOG DATA SET, CONNECTION-ID=xxxx THREAD-XREF= yyyyyy, QMGR=qmgr-name
Explanation: 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.
System action: Depending upon what log record is being read and why, the requestor might end abnormally with a reason code of X'00D1032A'.
System programmer response: 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.

CSQJ134E

RBA log-rba NOT IN ANY ACTIVE OR ARCHIVE LOG DATA SET, CONNECTION-ID=xxxx THREAD-XREF=yyyyyy, QMGR=qmgr-name

Explanation

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.

System action

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

System programmer response

This problem can occur for the following reasons:

The entry with the log range in the BSDS has been deleted from the BSDS
The entry with the log range is in BSDS, but the archive log data set has been deleted. When an archive log is created, the CSQ6ARVP parameter ARCRETN is used to specify when the data set can be deleted. When this date has passed MVS deletes the data set, so if we are trying to use this data set after this date, the data set cannot be found.

See BSDS problems for further information.

CSQJ136I: UNABLE TO ALLOCATE TAPE UNIT FOR CONNECTION-ID=xxxx CORRELATION-ID= yyyyyy, m ALLOCATED n ALLOWED
Explanation: 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.
System action: 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.

CSQJ139I: LOG OFFLOAD TASK ENDED
Explanation: Processing of the active log offload ended.
System action: This message is written to the z/OS console.

CSQJ140I

Data set dsname successfully added to active log copy n

Explanation

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.

CSQJ141E: Error adding new active log data set dsname
Explanation: A DEFINE LOG command failed to add a new log data set. Further information about the failure is given in the preceding messages.
System programmer response: Investigate and correct the cause of the failure, then enter the command again.

CSQJ142I: Data set dsname has been used previously
Explanation: 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.
System action: The data set is closed and deallocated. Dynamic addition of a new active log data set fails.
System programmer response: 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.

CSQJ143I: BSDS active log data set record is full
Explanation: 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.
System action: Dynamic addition of a new active log data set fails.

CSQJ144I: Active log data set allocation error
Explanation: 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.
System action: Dynamic addition of a new active log data set fails.
System programmer response: 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.

CSQJ150E

LOG CAPTURE EXIT ABEND, EXIT DEACTIVATED

Explanation

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.

System action

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.

System programmer response

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

Note: A correctly-functioning copy of load module CSQJL004/entry CSQJW117 must be available to start the queue manager. If the problem that caused this error cannot be corrected, ensure that the default CSQJW117 entry (load module CSQJL004 - supplied with IBM MQ) is available during the next queue manager start.

CSQJ151I: csect-name ERROR READING RBA rrr, CONNECTION-ID=xxxx CORRELATION-ID=yyyyyy REASON CODE=ccc
Explanation: 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.
System action: The queue manager attempts to recover from the error.
System programmer response: 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. .

CSQJ152I

csect-name ERROR BUILDING ARCHIVE LOG VOLUME REPORT, CONNECTION-ID=xxxx CORRELATION-ID=yyyyyy REASON CODE=ccc

Explanation

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

System action

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.

System programmer response

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.

CSQJ153I: csect-name ERROR READING LRSN rrr, CONNECTION-ID=xxxx CORRELATION-ID=yyyyyy REASON CODE=ccc, QMGR=qmgr-name
Explanation: 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.
System action: The queue manager attempts to recover from the error.
System programmer response: 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..

CSQJ154I: csect-name ERROR READING RBA rrr, CONNECTION-ID=xxxx CORRELATION-ID=yyyyyy REASON CODE=ccc, QMGR=qmgr-name
Explanation: 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.
System action: The queue manager attempts to recover from the error.
System programmer response: 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.

CSQJ155E

csect-name ACTIVE LOG DSNAME=xxxxx IS LARGER THAN 4GB

Explanation

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

System action

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.

System programmer response

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.

To reallocate LOG datasets with space smaller or equal to 4GB, carry out these steps:

Allocate and format new COPY1, and COPY2 if used, active log datasets with a maximum size of 4GB, and run CSQJUFMT if required.
Dynamically add the new logs to the queue manager with command DEFINE LOG.
Use command ARCHIVE LOG to roll into the new logs.
Shut down the queue-manager when one of the new logs is the current active log dataset.
Use the CSQJU003 utility to remove the active logs which are too small. First run CSQJU004 to display the log status in BSDS to make sure the ones to be removed are 'REUSABLE', that is they have been successfully archived.
Restart the queue manager. There should not be any CSQJ115E messages issued.

CSQJ160I

LONG-RUNNING UOW FOUND, URID=urid CONNECTION NAME=name

Explanation

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.

System action

Processing continues.

System programmer response

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.

If required, issue the command DISPLAY CONN(*) WHERE(QMURID EQ urid) ALL to display more information about the unit of recovery, including the channel name for remote connections.

CSQJ161I

UOW UNRESOLVED AFTER n OFFLOADS, URID=urid CONNECTION NAME=name

Explanation

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.

System action

Processing continues.

System programmer response

If required, issue the command DISPLAY CONN(*) WHERE(QMURID EQ urid) ALL to display more information about the unit of recovery, including the channel name for remote connections.

CSQJ163E: COPY(2) specified but TWOACTV(NO)
Explanation: 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.
System action: Dynamic addition of the new active log data set fails.
System programmer response: Either specify COPY(1) on the DEFINE LOG command or configure the queue manager to use dual logging.

CSQJ164I

csect-name Log archiving delayed, all available offload tasks in use

Explanation

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.

System action

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.

System programmer response

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.

CSQJ165I

zHyperWrite bypassed for active log data set dsname

Explanation

The system parameter ZHYWRITE has been enabled, but zHyperWrite has not been used for some write requests to the active log data set identified by dsname.

System action

Processing continues. If Basic Metro Mirror (PPRC) has been configured for the active log volumes then traditional PPRC is used.

Use traditional PPRC means that the queue manager does not benefit from performance gains that are available when using zHyperWrite.

System programmer response

Review the configuration for the active log volumes and the zHyperWrite feature. The most likely reason for bypassing zHyperWrite is that the HyperSwap relationships have not been set up correctly.

CSQJ166E

PPRC configuration is inconsistent for active log copy n

Explanation

The data sets for each copy of the active log should be consistently configured for Basic Metro Mirror (PPRC).

This means that, either all of the data sets that comprise an active log copy should be configured on PPRC-enabled volumes, or none of the data sets should be configured on PPRC-enabled volumes.

The queue manager has detected an inconsistency in the PPRC configuration for the data sets that comprise log copy n.

System action

Processing continues, but an inconsistent logging rate might be observed due to the inconsistent configuration of the active log volumes. There is also a risk of losing data on the remote site, because not all of the active log volumes have a remote copy.

System programmer response

Review the configuration for the active log volumes.

CSQJ166E

zHyperWrite configuration is inconsistent for active log copy n

Explanation

The data sets for each copy of the active log should be consistently configured so that they are capable of being used with zHyperWrite.

This means that, either all of the data sets that comprise an active log copy should be on zHyperWrite capable volumes, or none of the data sets should be on zHyperWrite capable volumes.

The queue manager has detected an inconsistency in the zHyperWrite configuration for the data sets that comprise log copy n.

System action

Processing continues, but an inconsistent logging rate might be observed due to the inconsistent configuration of the active log volumes.

System programmer response

Review the configuration for the active log volumes.

CSQJ167E: ZHYWRITE(YES) specified but no active logs are zHyperWrite capable
Explanation: The system parameter ZHYWRITE has been set to YES, but the queue manager cannot exploit zHyperWrite because none of the active log copies are on zHyperWrite capable volumes.
System action: Processing continues without zHyperWrite being enabled for log writes.
System programmer response: Review the configuration for the active log volumes and the zHyperWrite feature.

CSQJ168I: csect-name Log archiving is no longer delayed
Explanation: The offload of active logs is no longer being delayed by a shortage of available offload tasks.
System action: Processing continues.

CSQJ200I: csect-name UTILITY PROCESSING COMPLETED SUCCESSFULLY
Explanation: The utility completed successfully.

CSQJ201I: csect-name UTILITY PROCESSING WAS UNSUCCESSFUL
Explanation: The utility was unable to complete processing successfully.
System action: The current utility is terminated.
System programmer response: Review other messages produced by the utility to determine the appropriate action to be taken.

CSQJ202E: INSUFFICIENT STORAGE AVAILABLE TO CONTINUE
Explanation: A request for storage was unsuccessful because no more storage is available.
System action: The current utility is terminated.
System programmer response: Rerun the utility after increasing the storage available.

CSQJ203E: oper OPERATION IS INVALID
Explanation: The user entered a utility control statement operation (oper) that is invalid.
System action: The current utility is terminated.
System programmer response: Correct the control statement, and rerun the utility.

CSQJ204E: xxxx PARAMETER IS INVALID
Explanation: The user specified a utility control statement parameter (xxxx) that is invalid.
System action: The current utility is terminated.
System programmer response: Correct the control statement, and rerun the utility.

CSQJ205E: xxxx PARAMETER HAS NO ARGUMENT
Explanation: xxxx contains the name of a parameter that requires an argument.
System action: The current utility is terminated.
System programmer response: Specify an argument for the identified parameter and then rerun the utility.

CSQJ206E: xxxx PARAMETER REQUIRES NO ARGUMENT
Explanation: xxxx contains the name of the parameter that has been incorrectly followed by an = symbol.
System action: The current utility is terminated.
System programmer response: Correct the control statement, and rerun the utility.

CSQJ207E: PARAMETERS INCONSISTENT WITH SPECIFIED OPERATION
Explanation: The user has specified utility control statement parameters that are inconsistent with the specified utility operation.
System action: The current utility is terminated.
System programmer response: Correct the control statement, and rerun the utility.

CSQJ211E: UNEXPECTED END OF DATA ON SYSIN DATA SET
Explanation: Additional control statements were expected, but could not be found.
System action: The current utility is terminated.
System programmer response: Correct the control statements, and rerun the utility.

CSQJ212E: ERROR RETURNED FROM BSDS READ, RPLERRCD= yy, DDNAME=ddd
Explanation: 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.
System action: The current utility is terminated.
System programmer response: 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.

CSQJ213E

ERROR RETURNED FROM BSDS WRITE, RPLERRCD= yy, DDNAME=ddd

Explanation

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.

System action

The current utility is terminated.

System programmer response

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.

CSQJ214E: SPECIFIED DSNAME ALREADY EXISTS IN BSDS, DDNAME=ddd
Explanation: 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.
System action: The current utility is terminated.
System programmer response: Either correct the control statement and rerun the utility, or delete the existing DSNAME from the BSDS and rerun the utility.

CSQJ215I

modname timestamps formatted with no local correction

Explanation

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.

System action

Processing continues.

System programmer response

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

CSQJ216E: BSDS ACTIVE LOG DATA SET RECORD IS FULL, DDNAME=ddd
Explanation: 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.
System action: The current utility is terminated.
System programmer response: 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.

CSQJ217E: SPECIFIED DSNAME DOES NOT EXIST IN BSDS, DDNAME=ddd
Explanation: The DELETE operation specifies a DSNAME that cannot be found in the BSDS. ddd contains the DDname of the subject BSDS.
System action: The current utility is terminated.
System programmer response: Correct the control statement, and rerun the utility.

CSQJ218E: SPECIFIED VOLUME DOES NOT EXIST IN BSDS, DDNAME=ddd
Explanation: The DELETE operation specifies a COPY1VOL or COPY2VOL argument that cannot be found in the BSDS. ddd contains the DDname of the subject BSDS.
System action: The current utility is terminated.
System programmer response: Correct the control statement, and rerun the utility.

CSQJ219E

OPEN ERROR, DDNAME=ddd

Explanation

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

This error can be caused by a number of different conditions. The most probable conditions are:

The DDname of the SYSPRINT, SYSIN, or SYSUT1 data set was not specified in the user's job control language (JCL)
The queue manager is currently active
The BSDS has been allocated by another job with a disposition (DISP) that conflicts with the DISP specified in the user's JCL
The data set associated with ddd is already open, possibly due to an earlier error
The user is not authorized to access the data set associated with ddd
Insufficient storage is available to perform the OPEN operation
The catalog indicates that the data set associated with ddd has an invalid physical record size

System action

The current utility is terminated.

System programmer response

The user's action depends on the condition that caused the OPEN error. The following is a list of appropriate actions corresponding to the conditions listed in the explanation:

Provide the missing data definition (DD) statements, and then rerun the utility. See the section Preparing your program to run for further information.
Wait until the queue manager is inactive before running the utility again because the log utility cannot run while it is active.
Correct the disposition conflict and then rerun the utility.
Submit an Access Method Services (IDCAMS) VERIFY job against the data set associated with ddd. Rerun the log utility job.
In the case of an authorization problem, a separate message is usually generated from the authorization facility (RACF, for example). Investigate the authorization messages and obtain the proper authorization before running the utility again.
Insufficient storage is usually accompanied by a separate error from z/OS. Increase the storage available and rerun the utility.
Reallocate the data set with a suitable physical record size.

CSQJ220E: BSDS IN CREATE MODE. NO DATA TO MAP, DDNAME=ddd
Explanation: 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.
System action: The current utility is terminated.
System programmer response: Correct the JCL so that a non-null data set can be processed.

CSQJ221I

PREVIOUS ERROR CAUSED oper OPERATION TO BE BYPASSED

Explanation

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.

System action

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.

System programmer response

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.

CSQJ222E: INVALID SPECIFICATION OF xxxx PARAMETER ARGUMENT
Explanation: You specified the parameter xxxx. This parameter is not valid for the argument.
System action: The current utility is terminated.
System programmer response: Correct the parameter argument on the control statement, and rerun the utility.

CSQJ223E: xxxx PARAMETER ARGUMENT EXCEEDS MAXIMUM ALLOWABLE LENGTH
Explanation: xxxx specifies the name of the parameter with an argument value that exceeded the maximum length allowed.
System action: The current utility is terminated.
System programmer response: Correct the parameter argument on the control statement, and rerun the utility.

CSQJ224E: xxxx PARAMETER APPEARS TOO OFTEN
Explanation: xxxx gives the name of the parameter that we have specified more than once on the same control statement.
System action: The current utility is terminated.
System programmer response: Remove the redundant parameter, and rerun the utility.

CSQJ225I: oper OPERATION SUCCESSFULLY COMPLETED
Explanation: The oper specified in the message identifies the name of the change log inventory utility operation that has been successfully completed.

CSQJ226E: SPECIFIED VOLUME ALREADY EXISTS IN BSDS, DDNAME=ddd
Explanation: The specified volume currently exists in the archive log records of the BSDS. ddd specifies the DDname of the subject BSDS.
System action: The current utility is terminated.
System programmer response: Either correct the parameter argument on the control statement, or delete the specified volume and rerun the utility.

CSQJ227E: NO SPACE IN BSDS FOR ADDITIONAL ARCHIVE ENTRIES, DDNAME=ddd
Explanation: The maximum number of archive volumes has been exceeded, and no more space is available for volume entries in the copy specified.
System action: The current utility is terminated.
System programmer response: Delete some of the archive entries in the specified copy number, and rerun the utility.

CSQJ228E

csect-name LOG DEALLOCATION ERROR DSNAME=dsname, ERROR STATUS=eeeeiiii, SMS REASON CODE=ssssssss

Explanation

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

System action

Processing continues.

System programmer response

Go to the z/OS MVS documentation in IBM Knowledge Center, and select the Interpreting DYNALLOC return codes topic of the MVS Authorized Assembler Services Guide for information about these codes .

CSQJ230E: LOG OFFLOAD INITIALIZATION PROCESSING FAILED
Explanation: During queue manager initialization, the offload function was unable to complete its initialization process.
System action: Startup is terminated.
System programmer response: 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.

CSQJ231E: LOG COMMAND INITIALIZATION PROCESSING FAILED
Explanation: During queue manager initialization, the command function was unable to complete its initialization process.
System action: Startup is terminated.
System programmer response: 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.

CSQJ232E: OUTPUT DATA SET CONTROL INITIALIZATION PROCESSING FAILED
Explanation: During queue manager initialization, the output data set control function was unable to complete its initialization process.
System action: Startup is terminated.
System programmer response: 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.

CSQJ233E: ARCHIVE LOG READ INITIALIZATION PROCESSING FAILED
Explanation: During queue manager initialization, the archive log read function was unable to complete its initialization process.
System action: Startup is terminated.
System programmer response: 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.

CSQJ234E: ARCHIVE LOG COMMAND QUIESCE INITIALIZATION PROCESSING FAILED
Explanation: During queue manager initialization, the quiesce function which supports the ARCHIVE LOG MODE(QUIESCE) command processing was unable to complete its initialization process.
System action: Startup is terminated.
System programmer response: 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.

CSQJ235E: OUTPUT BUFFER WRITER INITIALIZATION PROCESSING FAILED
Explanation: During queue manager initialization, the output buffer writer function was unable to complete its initialization process.
System action: Startup is terminated.
System programmer response: 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.

CSQJ236E: BOOTSTRAP ACCESS TERMINATION PROCESSING FAILED
Explanation: During queue manager termination, the BSDS access function was unable to complete its termination process.
System action: Termination processing continues.
System programmer response: 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.

CSQJ238E: LOG OFFLOAD TERMINATION PROCESSING FAILED
Explanation: During queue manager termination, the offload function was unable to complete its termination process.
System action: Termination processing continues.
System programmer response: 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.

CSQJ239E: LOG COMMAND TERMINATION PROCESSING FAILED
Explanation: During queue manager termination, the command function was unable to complete its termination process.
System action: Termination processing continues.
System programmer response: 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.

CSQJ240E: OUTPUT DATA SET CONTROL TERMINATION PROCESSING FAILED
Explanation: During queue manager termination, the output data set control function was unable to complete its termination process.
System action: Termination processing continues.
System programmer response: 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.

CSQJ241E: ARCHIVE LOG READ TERMINATION PROCESSING FAILED
Explanation: During queue manager termination, the archive log read function was unable to complete its termination process.
System action: Termination processing continues.
System programmer response: 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.

CSQJ242E: ARCHIVE LOG COMMAND QUIESCE TERMINATION PROCESSING FAILED
Explanation: During queue manager termination, the quiesce function which supports the ARCHIVE LOG MODE(QUIESCE) command processing was unable to complete its termination process.
System action: Termination processing continues.
System programmer response: 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.

CSQJ243E: OUTPUT BUFFER WRITER TERMINATION PROCESSING FAILED
Explanation: During queue manager termination, the output buffer writer function was unable to complete its termination process.
System action: Termination processing continues.
System programmer response: 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.

CSQJ244E: MACRO xxx FAILED IN LOG TERMINATION, RC=ccc
Explanation: During termination, there was a return code from the named macro that indicated an error.
System action: Termination processing continues.
System programmer response: If the problem persists, contact the IBM support center for assistance.

CSQJ245D: RESTART CONTROL INDICATES TRUNCATION AT RBA rrr. REPLY Y TO CONTINUE, N TO CANCEL
Explanation: The conditional restart control record in use indicates that the log should be truncated at the specified RBA.
System action: If 'Y', queue manager startup continues. If 'N', startup is terminated.
System programmer response: Run the change log inventory utility (CSQJU003) to modify the conditional restart record.

CSQJ246D: RESTART CONTROL INDICATES COLD START AT RBA rrr. REPLY Y TO CONTINUE, N TO CANCEL
Explanation: 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.
System action: If 'Y', queue manager startup continues. If 'N', startup is terminated.
System programmer response: Run the change log inventory utility (CSQJU003) to modify the conditional restart record.

CSQJ247E

csect-name I/O ERROR PROCESSING BSDS ARCHIVE LOG RECORD, RC=rc REASON=reason

Explanation

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.

System action

Startup is terminated.

System programmer response

For a return code of 4, if the problem persists, contact the 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.

CSQJ250I

csect-name DATA SET dsname HAS SHAREOPTIONS LESS THAN (2 3) - CF STRUCTURE RECOVERY NOT POSSIBLE

Explanation

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.

System action

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.

System programmer response

If we want CF structure recovery, use the Access Method Services ALTER function to correct the SHAREOPTIONS for the data set; for example

  ALTER dsname.DATA SHAREOPTIONS(2 3)

Then restart the queue manager that owns the data set.

CSQJ295D: RESTART CONTROL INDICATES TRUNCATION AT LRSN rrr. REPLY Y TO CONTINUE, N TO CANCEL
Explanation: The conditional restart control record in use indicates that the log should be truncated at the specified LRSN.
System action: If 'Y', queue manager startup continues. If 'N', startup is terminated.
System programmer response: Run the change log inventory utility (CSQJU003) to modify the conditional restart record.

CSQJ301E

csect-name ERROR USING ONLINE BOOTSTRAP DATA SET (ACTION CODE a)

Explanation

During command processing for the RECOVER BSDS command or the ARCHIVE LOG command, an error occurred while performing an operation on the BSDS. The type of operation is specified by the code a:

1: Unable to OPEN the BSDS
2: Unable to read a required record from the BSDS
3: Unable to write a required record to the BSDS
4: The contents of the stable BSDS was successfully copied to the replacement BSDS; however, the queue manager was unable to successfully restore dual BSDS operation

System action

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.

System programmer response

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.

CSQJ302E

ALLOCATION ERROR ON REPLACEMENT BSDS DSNAME=dsname ERROR STATUS=eee

Explanation

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.

System action

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

System programmer response

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.

The error status portion of this message contains the 2-byte error code (S99ERROR) followed by the 2-byte information code (S99INFO) from the SVC request block.

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

CSQJ303E: WRITE ERROR ON REPLACEMENT BSDS DSNAME=dsname ERROR STATUS=eee
Explanation: 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.
System action: Processing of the command is terminated. The queue manager continues in single BSDS mode.
System programmer response: 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.

CSQJ304E: ERROR CLOSING REPLACEMENT BSDS DSNAME=dsname ERROR STATUS=eee
Explanation: 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.
System action: Processing of the command is terminated. The queue manager continues in single BSDS mode.
System programmer response: 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.

CSQJ305E: REPLACEMENT BSDS NOT EMPTY DSNAME=dsname
Explanation: The RECOVER BSDS command was issued, but the replacement BSDS was not empty; that is, it contained data.
System action: Processing of the command is terminated. The queue manager continues in single BSDS mode.
System programmer response: 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.

CSQJ306I: DUAL BSDS MODE ALREADY ESTABLISHED
Explanation: The RECOVER BSDS command was issued, but the queue manager was already in dual BSDS mode.
System action: The command is ignored.

CSQJ307I: LOG INITIALIZED IN SINGLE BSDS MODE
Explanation: The RECOVER BSDS command was issued, but the queue manager was initialized in single BSDS mode.
System action: Processing of the command is terminated. The queue manager continues in single BSDS mode.

CSQJ308I: LOG NOT OFFLOADED FOR ARCHIVE LOG COMMAND, ARCHIVING IS OFF
Explanation: The ARCHIVE LOG command was issued, but archiving is off (that is, OFFLOAD is set to 'NO' in the CSQ6LOGP system parameters).
System action: The current active log data set is not offloaded. However, it is truncated and logging continues using the next active log data set.

CSQJ309I

QUIESCING FOR ARCHIVE LOG COMMAND WITH WAIT(YES) STARTED FOR MAXIMUM OF xxx SECONDS

Explanation

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.

System action

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.

CSQJ310I

QUIESCING FOR ARCHIVE LOG COMMAND WITH WAIT(NO) STARTED FOR MAXIMUM OF xxx SECONDS

Explanation

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.

System action

This message will be followed by message CSQJ311I or CSQJ317I.

CSQJ311I

csect-name LOG ARCHIVE (OFFLOAD) TASK INITIATED

Explanation

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.

System action

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.

CSQJ312I

ARCHIVE LOG QUIESCE ENDED. UPDATE ACTIVITY IS NOW RESUMED

Explanation

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.

System action

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

CSQJ314E: 'kwd1' requires 'kwd2' to be specified too
Explanation: A command was entered that specified the kwd1 keyword. However, use of this keyword requires that the kwd2 keyword is also used.
System action: Processing for the command is terminated.

CSQJ315I: STOP QMGR MODE(FORCE) IN PROGRESS
Explanation: An attempt was made to issue an ARCHIVE LOG command when a STOP QMGR MODE(FORCE) command was already in progress.
System action: Command processing will terminate for the ARCHIVE LOG command. The STOP QMGR MODE(FORCE) processing will continue.

CSQJ316I: SYSTEM QUIESCE ALREADY IN PROGRESS
Explanation: 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.
System action: Command processing will terminate. The system quiesce currently in progress will continue.

CSQJ317I

QUIESCE PERIOD EXPIRED WITH nn OUTSTANDING URS AT time. ARCHIVE LOG PROCESSING TERMINATED

Explanation

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.

System action

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.

System programmer response

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

Before resubmitting the ARCHIVE LOG command with the MODE(QUIESCE) option, either:

Wait until the threads have been deallocated
Wait until the queue manager is less busy
Force the offending threads to terminate
Use the TIME option to override and extend the maximum quiesce time period specified in the system parameters
If having all units of recovery reach a point of consistency in the active log is no longer critical, issue the ARCHIVE LOG command without the MODE(QUIESCE) option

Note: If you decide to use the ARCHIVE LOG command without the MODE(QUIESCE) option, the active log data sets will be truncated without regard to quiescing activity on the queue manager. If the resulting archive log data set is used for recovery, it is possible that some units of recovery might be found to be in-flight, in-backout, in-commit, or in-doubt during queue manager initialization.

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.

CSQJ318I: ARCHIVE LOG COMMAND ALREADY IN PROGRESS
Explanation: An attempt was made to issue an ARCHIVE LOG command when another ARCHIVE LOG command was already in progress.
System action: Command processing will terminate. The ARCHIVE LOG command currently in progress will continue.

CSQJ319I

csect-name CURRENT ACTIVE LOG DATA SET IS THE LAST AVAILABLE ACTIVE LOG DATA SET. ARCHIVE LOG PROCESSING WILL BE TERMINATED

Explanation

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.

System action

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.

System programmer response

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.

Possible causes for the shortage of active log data space are:

Excessive logging. For example, there is a lot of persistent message activity.
Delayed or slow offloading. For example, failure to mount archive volumes, incorrect replies to offload messages, or slow device speeds.
Excessive use of the ARCHIVE LOG command. Each invocation of the command causes the queue manager to switch to a new active log data set. Excessive use could consume the available active log data space if the resulting offloads were not processed in a timely manner.
Offloads unsuccessful.
Insufficient active log space.

CSQJ320E: csect-name UNABLE TO PROCESS LOG TRUNCATION REQUEST DUE TO INTERNAL ERROR. (ERROR DATA=ddd)
Explanation: 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.
System action: Processing for the command is terminated.
System programmer response: 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.

CSQJ321E: UNABLE TO CONTINUE ARCHIVE LOG QUIESCE DUE TO INTERNAL ERROR. ARCHIVE LOG PROCESSING TERMINATED
Explanation: 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.
System action: 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.
System programmer response: 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.

CSQJ322I

DISPLAY parm-type report ...

Explanation

This message is part of the response to the DISPLAY and SET parm-type commands (where parm-type is SYSTEM, LOG, or ARCHIVE). It provides information about the corresponding system parameters. For example:

  Parameter  Initial value  SET value
  LOGLOAD      500000       400000 
  CMDUSER      CSQOPR 
  EXCLMSG      X500,X501,X528,X208, 
               X519,X599      
  End of parm-type report

where:

LOGLOAD: was set in CSQ6SYSP and changed using the SET SYSTEM LOGLOAD command.
CMDUSER: was set in CSQ6SYSP and has not been changed.
EXCLMSG: was set to the default in CSQ6SYSP, and has been changed using the SET SYSTEM EXCMSG command.

System action

Processing continues.

CSQJ325I

ARCHIVE tape unit report ...

Explanation

This message is part of the response to the DISPLAY and SET ARCHIVE commands. It provides information about tape units used for archive logging, as follows:

  Addr St CorrelID VolSer DSName  addr st correlid volser dsname|  End of tape unit report

where:

addr

The physical address of a tape unit allocated to read the archive log.

st

The status of the tape unit:

B: Busy, actively processing an archive log data set.
P: Premount, active and allocated for premounting.
A: Available, inactive and waiting for work.
*: Unknown.

correlid

The correlation ID associated with the user of the tape being processed; '*****' if there is no current user.

volser

The volume serial number of the tape that is mounted.

dsname

The data set name on the tape volume that is being processed or was last processed.

If no tape units are allocated, the list is replaced by:

  No tape archive reading activity

System action

Processing continues.

CSQJ330I

ARCHIVE LOG VOLUMES required for connection-ID xxxx, correlation-ID yyyyyy:

Explanation

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.

The following is an example of the output produced by message CSJ330I::

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

System action

Processing continues.

CSQJ334E: Parameter value is unacceptable for ' kwd'
Explanation: The parameter value specified is not an acceptable value for the named keyword, or is incompatible with values set for other keywords.
System action: Processing for the command is terminated.

CSQJ335E: Invalid command syntax
Explanation: No keywords or an unacceptable combination of keywords was specified on a command.
System action: Processing for the command is terminated.

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

CSQJ364I: IMS Bridge facility suspended for XCFGNAME=gname XCFMNAME=mname
Explanation: This is issued as part of the response to a DISPLAY SYSTEM command if the IBM MQ-IMS Bridge facility to the partner IMS system identified by gname and mname is suspended.
System programmer response: Use the RESUME QMGR FACILITY(IMSBRIDGE) command when ready to resume the IBM MQ-IMS Bridge.

CSQJ365I: Db2 connection suspended
Explanation: This is issued as part of the response to a DISPLAY SYSTEM command if the connection to Db2 is suspended.
System programmer response: Use the RESUME QMGR FACILITY(Db2) command when ready to resume the connection to Db2.

CSQJ366I: Logging already suspended
Explanation: A SUSPEND QMGR LOG command was issued, but logging was already suspended by a previous command.
System action: The command is ignored.

CSQJ367I: Queue manager stopping
Explanation: A SUSPEND QMGR LOG command was issued, but the queue manager is stopping.
System action: The command is ignored.

CSQJ368I: Logging not suspended
Explanation: A RESUME QMGR LOG command was issued, but logging was not suspended.
System action: The command is ignored.

CSQJ369E: csect-name Failure while suspending logging
Explanation: A SUSPEND QMGR LOG command was issued, but it terminated abnormally.
System action: The command is ignored, and logging is not suspended.
System programmer response: Verify the command entry, and reissue the command. If it fails again, collect the items listed in the Problem Determination section, and contact the IBM support center.

CSQJ370I

LOG status report ...

Explanation

This message is part of the response to the DISPLAY and SET LOG commands. It provides information about the status of the log data sets, as follows:

Copy %Full zHyperWrite DSName 
1    k     p       dsname  
2    k     p       dsname  
Restarted at date time using RBA=sss  
Latest RBA=rrr  
Offload task is xxx  
Full logs to offload - m of n

Copy %Full zHyperWrite Encrypted DSName 
1    k     p           e         dsname  
2    k     p           e         dsname  
Restarted at date time using RBA=sss  
Latest RBA=rrr  
Offload task is xxx  
Full logs to offload - m of n

where:

1, 2

Information for the current active log copy 1 and copy 2 data sets.

k

The percentage of the active log data set that has been used.

p

Indicates whether this data set is zHyperWrite capable or not.

NO: This log data set is not zHyperWrite capable.
CAPABLE: This log data set is zHyperWrite capable. If the ZHYWRITE system parameter has been set to YES, then log writes will be made with zHyperWrite enabled.

e

Indicates whether the data set is encrypted or not.

NO: This data set is not encrypted.
YES: This data set is encrypted.

dsname

The data set name of the active log data set. If the copy is not currently active, this is shown as Inactive.

date time

The time that the queue manager was started.

sss

The RBA from which logging began when the queue manager was started.

rrr

The RBA of the most recently written log record. If logging is suspended, this line is replaced by

  Logging suspended at RBA=rrr

xxx

The status of the offload task, which can be:

BUSY, allocating archive data set: This could indicate that a tape mount request is pending.
BUSY, copying BSDS: Copy the BSDS data set.
BUSY, copying active log: Copy the active log data set.
BUSY: Other processing.
AVAILABLE: Waiting for work.

m, n

The number of full active log data sets that have not yet been archived, and the total number of active log data sets.

System action

Processing continues.

CSQJ372I

Logging suspended for qmgr-name at RBA=rrr

Explanation

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.

System action

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.

System programmer response

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

CSQJ373I: Logging resumed for qmgr-name
Explanation: The RESUME QMGR LOG command completed successfully.
System action: All log update activity is resumed for the queue manager named.

CSQJ401E

RECORD NOT FOUND - rrr

Explanation

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 we will get this message from CSQJU004 for the RESTART CONTROL records.

System action

Utility processing continues.

CSQJ404E: kwd NOT ALLOWED FOR oper OPERATION
Explanation: An invalid keyword was used during the oper operation.
System action: The current utility processing is terminated.

CSQJ405E: KEYWORDS kwd1 AND kwd2 CANNOT BOTH BE SPECIFIED
Explanation: Keywords kwd1 and kwd2 cannot appear on the same control statement.
System action: The current utility processing is terminated.

CSQJ406E: EITHER KEYWORD kwd1 OR kwd2 MUST BE SPECIFIED
Explanation: A required keyword was not used on the control statement. Use either kwd1 or kwd2 with that control statement type.
System action: The current utility processing is terminated.

CSQJ407E

NO VALID CHECKPOINT RBA FOUND

Explanation

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

System action

The current utility processing is terminated.

System programmer response

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.

CSQJ408I: CHECKPOINT RBA FOUND, RBA=rba, TIME=date time
Explanation: 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.
System action: Utility processing continues.

CSQJ409E: I/O ERROR DURING READ PROCESSING OF RECORD - yyy
Explanation: An input/output error occurred during a READ of a record. yyy specifies the record in question.
System action: The current utility processing is terminated. This message is accompanied by message CSQJ212E.
System programmer response: Determine the cause of the error based on the error status information provided in message CSQJ212E.

CSQJ410E: I/O ERROR DURING WRITE PROCESSING OF RECORD - yyy
Explanation: An input/output error occurred during a WRITE of a record. yyy specifies the record in question.
System action: The current utility processing is terminated. This message is accompanied by message CSQJ213E.
System programmer response: Determine the cause of the error based upon the error status information provided in message CSQJ213E.

CSQJ411I: CRESTART CREATE FOR CRCRID=yyyy, DDNAME=ddd
Explanation: 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.
System action: Current utility processing continues.
System programmer response: Note the record identifier for future reference.

CSQJ412E: RESTART CONTROL RECORD NOT FOUND IN BSDS
Explanation: A CRESTART CANCEL keyword was specified but the conditional restart control record does not exist in the BSDS data set.
System action: Current utility processing is terminated.
System programmer response: None necessary, if CANCEL was the intended action. Otherwise, correct the control statement and rerun the utility.

CSQJ413E: INVALID LOG RANGE SCOPE OR CHECKPOINT SPECIFIED
Explanation: The values specified through the STARTRBA and ENDRBA keywords are invalid.
System action: Current utility processing is terminated.
System programmer response: 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.

CSQJ414I: COLD START WILL RESULT FROM THIS RESTART CONTROL RECORD. FORWARD AND BACKOUT SET TO NO
Explanation: 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.
System action: CRESTART processing continues.
System programmer response: No additional actions are needed if a cold start of the queue manager is required. If a cold start is not required, reissue the CRESTART and either CANCEL the current restart control record, or CREATE a new restart control record.

CSQJ415E: ENDRBA=rba IS INVALID, MUST BE A MULTIPLE OF 4K
Explanation: The specified ENDRBA at rba is not a multiple of 4K.
System action: CRESTART processing is terminated.
System programmer response: Correct the ENDRBA value on the CRESTART statement and rerun the utility.

CSQJ416I: WARNING - BSDS UTILITY TIME STAMP MISMATCH DETECTED. PROCESSING CONTINUES
Explanation: 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.
System action: Current utility processing continues.
System programmer response: 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.

CSQJ417E: REQUIRED xxxx PARAMETER FOR oper OPERATION IS MISSING
Explanation: Required parameter xxxx for a log utility operation was missing from the log utility control statement. The attempted operation is oper.
System action: 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.
System programmer response: Add the missing parameter to the control statements associated with the specified operation and rerun the utility.

CSQJ418I: NOTREUSABLE ACTIVE LOG DELETED FROM THE BSDS LOG INVENTORY, STARTRBA=sss ENDRBA=ttt
Explanation: The data set name specified on the DSNAME parameter of the change log inventory utility DELETE statement was a NOTREUSABLE active log.
System action: The change log inventory utility processing continues. It will terminate with a return code of 4.
System programmer response: No additional actions are required if we 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.

CSQJ421I: CRESTART CANCEL FOR CRCRID=yyyy, DDNAME=ddd
Explanation: 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.
System action: Current utility processing continues.
System programmer response: Note the record identifier for future reference.

CSQJ425E: INVALID VALUE OR FORMAT FOR xxxx PARAMETER (YYYYDDDHHMMSST)
Explanation: The xxxx parameter contains an incorrect value or incorrect format for the date and time.
System action: The current utility is terminated.
System programmer response: Correct the control statement and rerun the utility.

CSQJ426E: ENDTIME VALUE CANNOT BE LESS THAN STARTIME VALUE
Explanation: The STARTIME and ENDTIME parameters specify a time range. Therefore, the ENDTIME value must be equal to or greater than STARTIME value.
System action: The current utility is terminated.
System programmer response: Correct the control statement and rerun the utility.

CSQJ427I: CHECKPOINT RECORD ADDED TO QUEUE
Explanation: The checkpoint record specified has been added to the checkpoint queue in the BSDS.
System action: Processing continues.

CSQJ428I: CHECKPOINT RECORD DELETED FROM QUEUE, STARTRBA= ssss ENDRBA=ttt
Explanation: 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.
System action: Processing continues.

CSQJ429E: RBA RANGE CONFLICTS WITH EXISTING CHECKPOINT RECORD RBA RANGE
Explanation: The specified RBA range for the new checkpoint record either exists, or overlaps an existing RBA range in the checkpoint queue in the BSDS.
System action: The current utility is terminated.
System programmer response: 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.

CSQJ430E: SPECIFIED ENTRY CANNOT BE ADDED WITHOUT OVERLAYING EXISTING LOWEST ENTRY
Explanation: 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.
System action: The current utility is terminated.
System programmer response: 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.

CSQJ431E: STARTRBA SPECIFIED CANNOT BE FOUND IN CHECKPOINT QUEUE
Explanation: The specified STARTRBA could not be located in the checkpoint queue in the BSDS.
System action: The current utility is terminated.
System programmer response: 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.

CSQJ432E: kwd VALUE MUST END WITH ' xxx'
Explanation: The value specified for keyword kwd is not valid. It must end with 'xxx'.
System action: The current utility is terminated.
System programmer response: Correct the control statement and rerun the utility.

CSQJ440I: csect-name IBM MQ for z/OS version
Explanation: This message is issued as part of the header to reports issued by the utility programs.

CSQJ443I: csect-name CHANGE LOG INVENTORY UTILITY - date time
Explanation: This message is issued as a header to the report issued by the utility program.

CSQJ444I: csect-name PRINT LOG MAP UTILITY - date time
Explanation: This message is issued as a header to the report issued by the utility program.

CSQJ445I: csect-name BSDS CONVERSION UTILITY - date time
Explanation: This message is issued as a header to the report issued by the utility program.

CSQJ450E: csect-name VERSION n BSDS NOT SUPPORTED BY ALL QSG MEMBERS
Explanation: 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.
System action: The current utility is terminated with no action taken.
System programmer response: 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.

CSQJ451E: csect-name BSDS CI SIZE NOT CORRECT, DDNAME=ddd
Explanation: 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..
System action: The current utility is terminated with no action taken.
System programmer response: 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.

CSQJ452E

csect-name BSDS UTILITY TIMESTAMP MISMATCH DETECTED

Explanation

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.

System action

The current utility is terminated with no action taken.

System programmer response

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.

CSQJ453E: csect-name INPUT BSDS NOT IN CORRECT FORMAT, DDNAME=ddd
Explanation: 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.
System action: The current utility is terminated with no action taken.
System programmer response: 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.

CSQJ454E: csect-name UNRECOGNIZED BSDS RECORD, KEY=key-value
Explanation: 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.
System action: The current utility is terminated.
System programmer response: 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.

CSQJ455E: INVALID BSDS CONVERSION
Explanation: 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.
System action: The current utility is terminated with no action taken.
System programmer response: The procedure for running the BSDS conversion utility involves renaming the original BSDS. Restore the BSDS to the original pre-conversion copy, by renaming the data sets, then try the conversion again.

CSQJ456E: xxxx PARAMETER ARGUMENT EXCEEDS MAXIMUM VALUE FOR BSDS VERSION n
Explanation: 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.
System action: The current utility is terminated.
System programmer response: Correct the parameter argument on the control statement, then rerun the utility.

CSQJ491I: csect-name Log Data Set Preformatter Utility - date time
Explanation: This message is issued as a header to the report issued by the utility program.

CSQJ492I: Log data set name = dsname
Explanation: This identifies the name of the log data set to be preformatted.

CSQJ493I: Log data set is not VSAM
Explanation: The input log data set is not a VSAM data set.
System action: Utility processing is terminated.
System programmer response: 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.

CSQJ494E: VSAM OPEN failed, ACBERRFLG=ee
Explanation: Opening the log data set failed with the indicated ACB error code.
System action: Utility processing is terminated if the error code is 128 or more; otherwise processing continues.
System programmer response: See the DFSMS/MVS Macro Instructions for Data Sets for information about the VSAM error code.

CSQJ495E: VSAM PUT failed, RPLERREG=ee reason code=reason
Explanation: Writing the log data set failed with the indicated RPL error code and reason code.
System action: Utility processing is terminated.
System programmer response: See the DFSMS/MVS Macro Instructions for Data Sets for information about the VSAM error code and reason code.

CSQJ496I: Log preformat completed successfully, n records formatted
Explanation: The active log data set has been preformatted successfully.
System action: Utility processing is complete.

CSQJ497I: Log preformat terminated
Explanation: Preformatting the active log data set did not complete successfully.
System action: Utility processing is terminated.
System programmer response: See the preceding error messages for more information.

CSQJ498I: Log data set is not empty
Explanation: The input log data set is not an empty data set.
System action: Utility processing is terminated.
System programmer response: 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.

CSQJ499I: Log data set is larger than 4GB
Severity: 0
Explanation: The log preformat utility, CSQJUFMT, detected that the VSAM data set to be formatted is greater than 4 GB in size.
System action: 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.
System programmer response: 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.

Parent topic: Messages for IBM MQ for z/OS