Messages BMC202200 through BMC202299

RUV Processing terminated due to error(s).

Explanation: The task terminated because at least one error was detected.

User response: To determine what action to take, see the previous message or messages.

RUV Processing continued after GAP detected, user requested GAP = IGNORE.

Explanation: A LOGR gap was detected. You requested that RUV ignore the gap and continue processing.

User response: Normally, no action is required. If data does not exist, it cannot be gathered. However, you should attempt to identify the reason for the gap.

RUV Processing continued after GAP detected, user requested GAP = WARN.

Explanation: The z/OS log stream indicated a GAP error. Processing of the log stream continues.

User response: No action is required.

RUV Processing terminated after GAP detected, user requested GAP = STOP.

Explanation: The z/OS log stream indicated a GAP error. Processing of the log stream terminated.

User response: Correct the error and rerun the job.

RUV No new data on type: fileid.

Explanation: An archive of a log did not find any new data to process.

User response: No action is required.

RUV type: logStreamName is empty.

Explanation: A log stream or journal was opened but contained no data.

User response: No action is required.

RUV number blocks copied.

Explanation: This message reports the number of blocks that participated in a COMPLETE_COPY operation.

User response: No action is required.

RUV Previous archive JOB: jobName on: date1 time1 ending block ID: blockID Timestamp: date2 time2.

Explanation: Each archive records information about the job and the last log stream block ID that was archived. When a new archive begins, the block ID is verified against the one that was last archived. If this block ID is not found, the previous information is displayed as the status. The next message shows the block ID of the current (first) block that was read for this job.

User response: Determine by the block ID and time stamp whether any user data has been lost. Recover any lost data records.

RUV Current archive JOB: jobname on: date1 time1 beginning block ID: blockID timestamp: date2 time2.

Explanation: The current job began reading with the indicated block ID and time stamp.

User response: Determine by the block ID and time stamp whether any user data has been lost. Recover any lost data records.

RUV Data before gap detected was blockid: blockNumber with timestamp: date time.

Explanation: This message provides relevant time stamp information to help with GAP error correction.

User response: No action is required.

RUV Data after gap detected was blockid: blockNumber with timestamp: date time.

Explanation: This message provides relevant time stamp information to help with GAP error correction.

User response: See the associated messages.

RUV LOGR block does not begin with >DFH. LSN: lsn

Explanation: All blocks must contain the >DFH eye-catcher. The block is printed and then skipped.

User response: From the record content, determine the system or application that wrote this data.

RUV LOGR record type is invalid.

Explanation: RUV determined that the LOGR record type is invalid. The valid record types are 80, 81, 82, 83, 84, 86, 8E, and 8F. The record is printed and skipped.

User response: If you need more detail about the printed record, contact BMC Support.

RUV Log type is invalid.

Explanation: The log type is not hex 00. The record is printed and skipped.

User response: If you need more detail about the printed record, contact BMC Support.

RUV LSN lsn is not a log of logs.

Explanation: The log type is not hex 01 DFHLGLOG. Log stream registration is canceled.

User response: Correct the log stream name and rerun the job.

RUV type on: lsname for journal journal at: date time.

Explanation: A failure record was written by CICS to the log of logs. The record is skipped.

User response: No action is required.

RUV lsname is not defined in the LOGR policy.

Explanation: The log stream name is invalid. An attempt to connect failed.

User response: Verify that the name is spelled correctly. If the name is correct, verify that the log stream is defined in the LOGR policy. After making the appropriate change, rerun the job.

RUV lsname is temporarily not available for connection.

Explanation: A temporary NOT AVAILABLE state was detected during an attempt to connect to the log stream.

User response: Retry the request after the conflicting process has completed.

RUV z/OS system logger not available.

Explanation: For more information, see IBM reason code (00000814).

User response: Retry the request after the IPL of the system logger is initialized.

RUV No log of logs selected for automatic scanning.

Explanation: No active log of logs records were found in the repository. The automatic log of logs scan was not performed.

User response: No action is required.

RUV fileID registration data not sufficient to process this request.

Explanation: The VSAM file is not fully defined in the repository. This condition might be caused by receiving an applid/fileid combination from either a log stream or CICS journal without having received a prior tie-up record.

User response: Add the VSAM file with the correct applid/fileid information, and rerun the job.

RUV fileID catalog data not sufficient to process this request.

Explanation: The VSAM file is not currently available.

User response: Define the VSAM file and rerun the job.

RUV Unable to determine file type for fileid.

Explanation: RUV could not determine whether this file is a KSDS, ESDS, or RRDS.

User response: No action is required.

RUV actionCode request failure for LSN lsn; RC(returnCode) RS(reasonCode).

Explanation: An error occurred during processing of a log stream.

User response: To determine what action to take, see the associated messages.

RUV ACTION action request failure for LSN lsname; RC(returnCode) RS(reasonCode) DIAG1(diagnose1) DIAG2(diagnose2).

Explanation: An error occurred during processing of a log stream.

User response: To determine what action to take, see the associated messages. If the IBM IXG063I message accompanies this message, RUV detected a possible GAP and issued this warning regardless of whether a GAP actually occurred. RUV performs logging based on the specified GAP option: GAP(STOP), GAP(WARN), or GAP(IGNORE).

RUV Error in service, RC(returnCode) RS(reasonCode).

Explanation: An IBM service that RUV is using detected an error. Other messages usually accompany this message.

User response: For information about the return and reason codes, see the appropriate IBM documentation.

RUV dataSetName is in INACTIVE status.

Explanation: Processing for this data set stopped due to the inactive attribute. Processing can occur only on data marked as ACTIVE.

User response: Run a report for this data set and determine whether the data set should be marked ACTIVE. If the data set status needs to be changed to ACTIVE, use the UPDATE command to correct the status.

RUV DSN: dataSetName is too large, more than 44 characters.

Explanation: The generated data set name is longer than 44 characters, which is the z/OS maximum.

User response: Revise the output model to generate shorter names. Resubmit the job.

RUV No DSN= or it was followed with no data in the OUTPUT MODEL expansion.

Explanation: The DSN keyword is missing or does not include a data set name.

User response: Review and revise the output model being used for this job. Resubmit the job.

The next start time for APPLID= applid in Store Clock format is: START_TIME (XhexTime)

Explanation: hexTime is the time of the first instance after the last processed record for APPLID applid in a UOW recovery.

User response: No action is required.

RUV Which is equal to systemDate systemTime GMT

Explanation: This message provides a time report.

User response: No action is required.

RUV Archive created for RECOVER FORWARD only with USE_AUTOJOURNAL(YES).

Explanation: USE_AUTOJOURNAL(YES) must be indicated.

User response: No action is required.

RUV USE_AUTOJOURNAL(YES) was indicated, user assumes the risk of compromising data integrity!

Explanation: The USE_AUTOJOURNAL(YES) keyword was specified. There is a risk of compromised data integrity.

User response: Validate integrity before using this data.

RUV xbmid is not at a high enough version to allow snapshot. It is realVersion but must be at least baseVersion.

Explanation: The version of XBM for the specified XBM ID is not at the required level.

User response: Rerun the job with an XBM subsystem that is at the required minimum version or later.

RUV xbmid is not at a high enough version to allow snapshot. It is realVersion but must be at least baseVersion.

Explanation: The version of XBM for the specified XBM ID is not at the required level.

User response: No action is required.

RUV dataSetName could not be restored using XBM.

Explanation: RUV encountered a problem when attempting to use the snapshot function.

User response: No action is required.

RUV Unselected Unit Of Work Archive dataSetName report.

Explanation: Data set dataSetName is an unselected unit-of-work archive.

User response: No action is required.

RUV Unable to get dataSetName DISP=OLD, will try DISP=SHR.

Explanation: Data set dataSetName has system SHAREOPTIONS of 4, but RUV could not obtain the data set with a disposition of OLD. RUV will attempt obtaining the data set with a disposition of SHR. If the job ends with return code 4, the job was successful.

User response: If the job ends with return code 8, allow RUV access to the data set and rerun the job.

RUV Processing halted due to previous VSAM messages: Informational, Warning, or Error.

Explanation: The job encountered fatal errors and stopped processing.

User response: For information about what action to take, see previous error messages.

RUV text

Explanation: This messages provides the content of the INVENTORY_ONLY report.

User response: No action is required.

RUV Archive input is incorrect Version.

Explanation: The input for the RUV is from an incorrect version of RUV. RUV ignores this data.

User response: Verify the recovered file. If necessary, rerun the job with correct version of RUV.

RUV recordCount Auto Journal Forward records created.

Explanation: This message reports the number of records that were created by auto journaling.

User response: No action is required.

RUV dataSetName RESTORE was canceled by the Operator.

Explanation: The operator responded to the WTOR to restore the indicated dataSetName with a cancel request. Processing of the indicated dataSetName stopped.

User response: No action is required.

RUV **** RECOVER FILE SUMMARY ****

Explanation: This message is the recovery report title.

User response: No action is required.

RUV dataSetName From: startDate startTime To: endDate endTime CC: returnCode

Explanation: This message provides the recovery summary.

User response: No action is required.

RUV dataSetName No Archive data applied - Data set is unchanged.

Explanation: No archive data was applied to the indicated data set because the data set had not been changed.

User response: No action is required.

RUV dataSetName No Archive data applied - Restore completed successfully.

Explanation: No archive data was applied to the indicated data set. Restore processing completed successfully.

User response: No action is required.

RUV dataSetName No Archive data applied - Restore Error

Explanation: No archive data was applied to the indicated data set because a restore failure or warning condition occurred.

User response: Check for additional restore failure or warning messages.

RUV DSName dataSetName was already selected for recovery.

Explanation: A previous base or path selected this file for recovery. The current request is ignored.

User response: No action is required.

RUV DSName dataSetName records cannot be backed out because it is an IAM ESDS file. Use RECOVER FORWARD instead.

Explanation: The indicated data set is an IAM ESDS file. You can recover IAM ESDS files only with the RECOVER FORWARD command.

User response: Run a forward recovery to recover this file.

RUV No Archives since the current backup to be Last Imaged

Explanation: Last Image accumulation processes archives created only since the current backup. RUV ignores all other archives.

User response: No action is required.

RUV XBM xbmid has returned an error code but no error messages.

Explanation: XBM subsystem xbmid returned a failure code, but no further information is provided.

User response: Contact BMC Support.

RUV XBM xbmid unknown, ensure XBM load library is available to job.

Explanation: XBM subsystem xbmid could not be found. XBM load modules are probably not available. Snapshot processing is canceled.

User response: Ensure that the XBM load modules are in the STEPLIB or the LINKLST.

RUVZSSI Command Fail Return Code=returnCode

Explanation: The RUVZSSI command has failed.

User response: Contact BMC Support with the error messages.

RUV PSW at failure: word1 word2 word3 word4. ssid

Explanation: An abend occurred at the location shown in the message.

User response: Save the information for debugging purposes if you need to contact BMC Support.

RUV Abend at offset: offset in: program version date time. ssid

Explanation: This message displays the following information:

• The name of the program in which the abend occurred

• The program's version

• The date and time of the program's assembly

User response: Save the information for debugging purposes if you need to contact BMC Support.

RUV Data at failure: address SDWA0 SDWA4 SDWA8. ssid

Explanation: This message displays the contents of the six bytes before and after the point at which the abend occurred.

User response: Save the information for debugging purposes if you need to contact BMC Support.

RUV Register: registerRange: regxx regxx regxx regxx. ssid

Explanation: The contents of all registers are displayed in the following groups of 4, as identified by the register range value: 0 through 3, 4 through 7, 8 through 11, and 12 through 15. The subsystem ID to which these register values correlate is identified by the ssid value.

User response: Record the register values and contact BMC Support.

RUV Abend abendCode occurred during end-of-memory processing. ssid

Explanation: The job terminated abnormally because of an out-of-memory condition. The subsystem ID to which this abend value correlates is identified by the ssid value.

User response: Record the abend value and contact BMC Support.

RUV Abend abendCode occurred during end-of-task processing. ssid

Explanation: The job terminated abnormally because of an error in out-of-task processing. The subsystem ID to which this abend value correlates is identified by the ssid value.

User response: Record the abend value and contact BMC Support.

RUV SNAPSHOT BACKUP FAILURE. Input dataSetName had nn records, but backup dataSetName had nn records.

Explanation: The input data set has a different number of records than the backup data set.

User response: Capture the XBM log and contact BMC Support.

RUV Backup Copy Failure. Input backup dataSetName should have had nn records, but backup copy dataSetName has nn records.

Explanation: The input backup data set has a different number of records than the backup copy data set. The backup copy data set was not registered but is a copy of the backup data set. You can manually register the backup copy data set as a backup of the original data set, if desired.

User response: Check the record count of the backup copy data set:

• If the record count is correct, RUV had an error. Contact BMC Support.

• If the record count is not correct, the backup copy has been modified and is no longer a correct backup.

DSName dataSetName records cannot be backed out because it is an EXTENDED ESDS file. Use RECOVER FORWARD instead.

Explanation: The indicated data set is an extended ESDS file. You can recover extended ESDS files only with the RECOVER FORWARD command.

User response: Run a forward recovery to recover this file.