Messages BMC202300 through BMC202399

RUV RUVZOBJ text

Explanation: RUV encountered an internal error. The variable text can be one of the following problems:

• Invalid token

• Invalid base token

• Token missing

• Request out of range

• Request not supported

• Method not found

• Copy / base invalid.

User response: Contact BMC Support.

RUV DSName dataSetName is not a registered backup.

Explanation: The restore request specified an unregistered backup dataSetName. The restore request was refused.

User response: Specify a registered backup and rerun the job.

RUV End of data encountered while reading repository.

Explanation: This is a normal condition unless some other error occurred.

User response: To determine what action to take, see any associated messages. Otherwise, no action is required.

RUV DSName dataSetName is not a registered VSAM file.

Explanation: The restore request specified an unregistered VSAM file dataSetName. The restore request was refused.

User response: Add the VSAM file to the repository and rerun the job.

RUV record record not found on repository: key (key).

Explanation: This is a normal condition unless some other error occurred.

User response: To determine what action to take, see any associated messages. Otherwise, no action is required.

RUV Item (item) not found.

Explanation: This is a normal condition unless some other error occurred.

User response: To determine what action to take, see any associated messages. Otherwise, no action is required.

RUV DSName dataSetName backup is registered but not active.

Explanation: The restore request specified an inactive backup file dataSetName. The restore request was refused.

User response: Select another backup or activate the selected backup.

RUV Duplicate type record found.

Explanation: A record of the specified type with the same key is already on the repository. This is a normal condition unless some other error occurred.

User response: No action is required.

RUV Duplicate item (item) found.

Explanation: The indicated item is already present in the record. This is a normal condition unless some other error occurred.

User response: No action is required.

RUV No current record found.

Explanation: No record currently exists in the repository buffer.

User response: Contact BMC Support.

RUV Commit is pending.

Explanation: The repository was updated in memory, but no request was made to commit the changes to DASD.

User response: Run the RELEASE REPOSITORY command.

RUV The update function is not allowed.

Explanation: The repository object is in read-only mode.

User response: Contact BMC Support.

RUV Time stamp mismatch found in the repository record, RC(returnCode).

Explanation: RUV found conflicting time stamps in the repository record. Multiple concurrent updates to the repository can cause this condition.

User response: Rerun the job. If this does not correct the problem, contact BMC Support.

RUV Other repository error, RC(returnCode).

Explanation: RUV received an unexpected return code in response to a request for repository I/O.

User response: Contact BMC Support.

RUV Insufficient access authority. RS(reasonCode).

Explanation: You do not have sufficient authority for the requested operation. Access to the repository requires at least UPDATE authority for the repository data sets.

User response: Contact your RACF administrator to obtain the required authority.

RUV Invalid record length; length is too short.

Explanation: Repository records must be at least 64 bytes long.

User response: Contact BMC Support.

RUV Invalid record length; length is too long.

Explanation: Repository records must be shorter than 16 MB.

User response: Contact BMC Support.

RUV Invalid record type code (type).

Explanation: The indicated type is not valid for a repository record.

User response: Contact BMC Support.

RUV Invalid item length length; length is less than sixteen.

Explanation: The repository item is too short. All items must be at least 16 bytes long.

User response: Contact BMC Support.

RUV Invalid item length length; length is too long.

Explanation: The repository item is too long. Unstructured items (format 0) must be less than 32 KB. Structured items (formats 1 and 2) must be less than 16 MB.

User response: Contact BMC Support.

RUV Invalid item code itemCode found.

Explanation: The repository item code is invalid. Repository item codes consist of four uppercase, alphabetic characters.

User response: Contact BMC Support.

RUV Invalid item length length; length is not a multiple of eight.

Explanation: The repository item length is invalid. Repository item lengths must be a multiple of eight.

User response: Contact BMC Support.

RUV No Active rule set on repository. Will use $DUMMY. ssid

Explanation: No previously active rule set exists to be reactivated. This is not an error, but RUV cannot protect your data without an active rule set.

User response: Activate a rule set. RUV will save the name in the repository and automatically reactivate it during initialization.

RUV Return from subsystem, RC(returnCode) SPLRC(SPLRC) RPLFDBWD(RPLFDBWD).

Explanation: An error occurred while attempting to access the repository.

User response: Contact BMC Support.

RUV Invalid RPL length length found on the repository.

Explanation: The indicated RPL length is not maximum size, and this is not the last segment of a record. The repository has been corrupted.

User response: Rebuild the repository.

RUV Invalid data found on the repository.

Explanation: The length field in the record conflicts with the actual length. The repository has been corrupted.

User response: Rebuild the repository.

RUV Invalid (non RUV) record read from the repository.

Explanation: The record key is invalid. The repository has been corrupted.

User response: Rebuild the repository.

RUV Repository Access Object - SSID ssid.

Explanation: This message identifies the subsystem ID for the repository access object.

User response: No action is required.

RUV Public subsystem not available; RS (00000001).

Explanation: The public subsystem was requested but is not available.

User response: Request a specific subsystem or activate a public RUV subsystem.

RUV ssid subsystem not available; RS (00000002).

Explanation: The specified subsystem is not found on the SSCT chain.

User response: Start the specified subsystem.

RUV Subsystem ssid is not an RUV subsystem.

Explanation: The RUV REINIT command was not executed on the identified subsystem.

User response: Ensure that the SET SUBSYSTEM command identifies a subsystem on which RUV is active.

RUV Failure to attach a writer.

Explanation: Accumulation processing was not able to attach a writer for output processing.

User response: Contact BMC Support.

RUV Failure to attach a reader.

Explanation: During accumulation processing, a reader could not be attached for input processing.

User response: Contact BMC Support.

RUV Registration of accumulation failed.

Explanation: The registration statement for the accumulation process could not be written to the repository.

User response: Verify that the repository is available and that you have the authority to access it.

RUV Inactive subsystem ssid.

Explanation: The identified subsystem is not active for RUV.

User response: Ensure that the SET SUBSYSTEM command identifies a subsystem on which RUV is active.

RUV Concatenated file not allowed for DDName ddname.

Explanation: RUV does not support concatenated files for the input file.

User response: Modify the input ddname so that it does not refer to concatenated files and rerun the job.

RUV Accumulation Repository error.

Explanation: The registration of the accumulation process failed.

User response: Verify that the repository is available and that you have the authority to access it.

RUV Invalid SSCT chain.

Explanation: A program check occurred while looking for the subsystem.

User response: If the SSCT chain has been corrupted, you must IPL your system.

RUV DDName ddname not open.

Explanation: A request cannot be honored because the ddname is not open.

User response: Contact BMC Support.

RUV No writers are available for the output processing of the accumulation data.

Explanation: All writers failed for the accumulation processing.

User response: Check the accumulation output data sets for errors.

RUV No IADS item found.

Explanation: A repository search did not find the IADS item.

User response: Contact BMC Support.

RUV DDName ddname is already open.

Explanation: An open request was made for the specified ddname, but it is already open.

User response: Contact BMC Support.

RUV Get not allowed, DDName ddname is open for output.

Explanation: RUV encountered an internal logic error.

User response: Contact BMC Support.

RUV Put not allowed, DDName ddname is open for input.

Explanation: RUV encountered an internal logic error.

User response: Contact BMC Support.

RUV Wrong TCB for close of DDName ddname.

Explanation: A close request was made for the specified ddname, but the task requesting the close is not the correct task.

User response: Contact BMC Support.

RUV Unexpected concatenation encountered on DDName: ddname.

Explanation: The indicated ddname was found to be concatenated but concatenated data sets are not supported in this context.

User response: Specify a nonconcatenated input data set and rerun the job.

RUV I/O error on DDName ddname, IEA000IText.

Explanation: The SYNAD exit was entered for a sequential data set and a hardware I/O error was encountered.

User response: For a detailed description of IEA000IText, see the IBM message documentation. For input files, ensure that the actual data agrees with the DCB information for the data set.

RUV End of data on DDName ddname; value records read.

Explanation: Read processing of value records reached the end of the data in the indicated ddname. This is a normal condition.

User response: No action is required.

RUV Invalid or missing DDName ddname.

Explanation: RUV received a DEVTYP (SVC 24) return code, indicating that the indicated ddname is not valid.

User response: Correct the JCL and rerun the job.

RUV Blank or missing DDName.

Explanation: RUV cannot open the file because the ddname is missing or blank.

User response: Contact BMC Support.

RUV Unable to get value bytes for DDName ddname input buffer.

Explanation: RUV is unable to get a value-byte record buffer for ddname. Abend U104 follows this message.

User response: Contact BMC Support.

RUV Archive registration skipped.

Explanation: A repository access error occurred that prevented the registration of the archive.

User response: Correct the repository access error and re-archive the archive.

RUV Repository access error actionID; RC(returnCode); RS(reasonCode).

Explanation: An error occurred while accessing the repository.

User response: Contact BMC Support.

RUV Item item (format 1) does not contain all required sub-items.

Explanation: Sub-item lengths appear to overlap the end of item item.

User response: Contact BMC Support.

RUV The entries do not exactly fit into array item item.

Explanation: RUV encountered an internal logic error.

User response: Contact BMC Support.

RUV An item was passed a pointer that had a value of zero.

Explanation: A pointer of zero was passed to the item validation routine. Low memory is not a valid item.

User response: Contact BMC Support.

RUV Item itemCode reserved field not set to zeros (hexValue).

Explanation: RUV encountered an internal error.

User response: Contact BMC Support.

RUV No IAFD item found.

Explanation: A repository search did not find the IAFD item.

User response: Contact BMC Support.

RUV Not able to identify file for record.

Explanation: The file to which this record applies is unknown.

User response: The record is accumulated but is not included in reports.

RUV Archive Record for DSName dataSetName is not active. Data set will NOT be accumulated.

Explanation: The latest repository record for this archive dataSetName is not active. Accumulation continues without the data set.

User response: Change the status of the archive to active and rerun the job.

RUV STOW failed for DDName ddname member memberName RC(returnCode).

Explanation: RUV was unable to update the PDS directory. The following table describes the return codes:

User response: Perform the appropriate action according to the return code received:

RUV Beginning segment was not found in block blockNumber of file DDName ddname.

Explanation: RUV read an invalid record from the indicated block of the indicated ddname. A beginning segment was expected, but the segment descriptor word (SDW) indicates that this is not the first segment of a record.

User response: This is a normal condition when processing a damaged or incomplete archive. Attempt to use another copy of this archive. Refer to active or inactive archive status.

RUV Ending segment missing in a record in block blockNumber of DDName ddname.

Explanation: RUV read an invalid record from the indicated block of the indicated ddname. A continuation segment was expected, but the segment descriptor word (SDW) indicates that this is the first segment of a record.

User response: This is a normal condition when processing a damaged or incomplete archive. Attempt to use another copy of this archive. Refer to active and inactive archive status.

RUV Beginning and ending segments missing from block blockNumber of DDName ddname.

Explanation: RUV found an invalid record in the indicated block of the indicated ddname. A middle segment was encountered. The segment descriptor words (SDWs) indicate that the first and last segments are both missing.

User response: This is a normal condition when processing a damaged or incomplete archive. Attempt to use another copy of this archive. Refer to active and inactive archive status.

RUV Record record in block blockNumber of DDName ddname is less than 8 bytes long.

Explanation: The indicated record is less than eight bytes long. An RUV archive record must be long enough to contain length and count fields. The data set is probably not an RUV archive.

User response: Ensure that the data set being processed is an RUV archive. Contact BMC Support.

RUV Record record in block blockNumber of DDName ddname is shorter than its llll length.

Explanation: The actual length of the indicated record is less than its llll field. The data set is probably not an RUV archive.

User response: Ensure that the data set being processed is an RUV archive. Contact BMC Support.

RUV Record record in block blockNumber of DDName ddname is longer than its llll length.

Explanation: The actual length of the indicated record is greater than its llll field. The data set is probably not an RUV archive.

User response: Ensure that the data set being processed is an RUV archive. Contact BMC Support.

RUV Invalid record sequence in DDName ddname; expected record1; actual record2.

Explanation: RUV encountered an invalid record sequence on ddname. Record number record1 was expected, but record number record2 was read. This is a normal condition when processing a damaged, incomplete, or modified archive. All jobs except the Accumulation job will fail. The Accumulation job will receive return code 8, but the job completes successfully unless RUV encounters other errors.

User response: Check for a BMC202153I message to determine whether the Accumulation job completed successfully. Ensure that the data set being processed is an RUV archive and that it is not being modified.

RUV Abend intercepted for DDName ddname; abend code abendCode, record number recordNumber.

Explanation: RUV encountered an abend intercepted by a DCBABEND or ESTAE exit. The error occurred in ddname, and recordNumber indicates the number of the record being processed at the time of the error.

User response: No action is necessary for out of space conditions (x37) during batch journaling. Otherwise, correct the problem and rerun the job.

RUV Record recordNumber intended for DDName ddname with length length is too long.

Explanation: For RECFM=F or FB, the record length (including wrapping) of ddname must equal the LRECL.

User response: Check the RECFM and LRECL of the output data set.

RUV Record recordNumber intended for DDName ddname with length length is too short.

Explanation: For RECFM=F or FB, the record length (including wrapping) of ddname must equal the LRECL.

User response: Check the RECFM and LRECL of the output data set.

RUV End of data encountered in item itemCode.

Explanation: RUV encountered an internal logic error.

User response: Contact BMC Support.

RUV Sub-item or entry does not exist.

Explanation: RUV encountered an internal logic error.

User response: Contact BMC Support.

RUV Invalid format format in item itemCode, A(address).

Explanation: RUV encountered an internal logic error. Valid formats are 0, 1, or 2.

User response: Contact BMC Support.

RUV No current item found.

Explanation: No item currently exists in the object’s buffer.

User response: Contact BMC Support.

RUV No current sub-item or array entry found.

Explanation: RUV encountered an internal logic error.

User response: Contact BMC Support.

RUV Item itemCode is too short; length= length, A(address).

Explanation: All items (and sub-items) must be at least sixteen bytes long.

User response: Contact BMC Support.

RUV Item itemCode is too long for format format items; length=length, A(address).

Explanation: The indicated item is too long. Format 0 (unstructured) items must be less than 32 KB. All others must be less than 16 MB.

User response: Contact BMC Support.

RUV Invalid Item itemCode found; hex value= (hexValue), A(address).

Explanation: The indicated item contains invalid eye-catchers. Valid eye-catchers consist of four uppercase characters, from A through Z.

User response: Contact BMC Support.

RUV Incorrect format format found.

Explanation: The item has an unsupported format for the function requested.

User response: Contact BMC Support.

RUV Invalid RDW on variable length DDName ddname. Block number blockNumber RDW(rdw).

Explanation: For RECFM=V, VB, VS, or VBS, the first four bytes must be a valid record descriptor word.

User response: Ensure that the actual data agrees with the DCB information from the VTOC, label, or JCL.

RUV Repository backup for SSID: ssid complete. count records; kcount K bytes.

Explanation: Repository backup for the indicated subsystem is complete, and count records were backed up. The size of the backup is kcount KB.

User response: No action is required.

RUV Repository restore for SSID: ssid complete. count records; kcount K bytes.

Explanation: Repository restore for the indicated subsystem is complete, and count records were restored. The size of the data restored is kcount KB.

User response: No action is required.

RUV File: ddname Data set: dataSetName

Explanation: This message displays the file ddname and data set name.

User response: No action is required.

RUV File: ddname Data set: dataSetName(member)

Explanation: This message displays the file ddname, data set name, and member name.

User response: No action is required.

RUV File: ddname Data set: dataSetName Error.

Explanation: This message displays the ddname and data set name of the file that is in error.

User response: No action is required.

RUV File: ddname Data set: **simulated**.

Explanation: This message displays the ddname and data sets that are simulated.

User response: No action is required.

RUV Rule set (ruleSetName) not found or not activated. ssid

Explanation: The repository control record for this subsystem contained a rule set name that could not be found.

User response: Activate the correct rule set.

RUV Repository Print for SSID: ssid.

Explanation: This message indicates the subsystem for which the repository is displayed.

User response: No action is required.

RUV Archive record for DSName dataSetName has no status. Data set will be accumulated.

Explanation: The latest repository record for the indicated data set has no status. Accumulation will continue with the data set.

User response: No action is required.

RUV recordCount records; bytes K bytes.

Explanation: This message reports the number of records and number of bytes of data that have been processed.

User response: No action is required.

RUV parameter is missing.

Explanation: The required parameter was not supplied for accumulation processing.

User response: Supply the missing data and rerun the job.

RUV DSName dataSetName is duplicated in the ARCHIVE_OUT parameter.

Explanation: The specified data set is listed two or more times in the ARCHIVE_OUT parameter.

User response: Remove any duplicate archive specifications and resubmit the job.

RUV DSName dataSetName base is not found.

Explanation: RUV could not find the dataSetName base.

User response: Correct the data set name, or ensure that the data set name is in the repository

RUV DSCB function failed RC(returnCode) RS(reasonCode).

Explanation: RUV encountered an error in DSCB functions.

User response: Contact BMC Support.

RUV Accumulation selection error.

Explanation: RUV encountered an error in accumulation processing.

User response: To determine what action to take, see previous error messages.

RUV No archives were selected for input.

Explanation: RUV found no active archives for the input.

User response: Verify that valid, active archives exist for the VSAM_FILE input.

RUV Build Queue failure.

Explanation: RUV encountered an error in creating a queue from reader to writer.

User response: Contact BMC Support.

RUV Accumulation writer allocation error.

Explanation: RUV encountered a failure in the allocation of a writer.

User response: Contact BMC Support.

RUV Mount plan failure.

Explanation: RUV encountered a failure in the mount plan.

User response: Contact BMC Support.

RUV Generated end of batch job for Job: job at gmt GMT.

Explanation: RUV generated the end of the indicated batch job by using the available journals. The message shows the time stamp in GMT.

User response: Ensure that all journals from the batch job were input to the ACCUM job. Correct and rerun the ACCUM job if input journals were missing. If the generated end time is acceptable, no action is required.