RPCV to RUV migration considerations
This topic describes RPCV to RUV migration considerations and contains the following information:
Supported file structures
Purpose | RUV supports and recovers the following file structures and organizations: KSDS, ESDS, RRDS, VRRDS, and QSAM. |
|---|---|
New | None |
Changed | None |
Obsolete | BDAM file type is no longer supported. |
Repository information for VSAM file recovery
Purpose | The repository records information on data sets, associated journal records, and backups. The information is used by the RUV automatic recovery facility. |
|---|---|
New | A new repository (and a REGISET2 repository) are now required. The following repository administrative commands are available: BACKUP REPOSITORY, RESTORE REPOSITORY, and PURGE REPOSITORY. |
Changed | None |
Obsolete | Migration program RUVZCDA converts data set names and group definitions from the CDS to the new RUV product repository. |
System requirements
Purpose | RUV requires sufficient memory and storage for subsystems. |
|---|---|
New | The RUV subsystem requires a minimum CSA storage of 568K for product modules. |
Changed | The RUV ISPF interface requires the IBM Interactive System Productivity Facility (ISPF) version 4.2 or later. |
Obsolete | None |
Rule sets
Purpose | RUV uses rule sets to determine which VSAM files should be protected. |
|---|---|
New | The ADD USER_VARIABLES command creates user variables. The ADD JOURNAL_MODEL command defines log and journal models named in the job set rule. The ADD JOB_SET command identifies the user's jobs that will trigger batch journaling activity. The ADD RULE_SET command identifies the set of rules that combines all the options a user has defined to control the batch journaling environment. The ADD VSAM_SET command identifies the recoverable VSAM files by DSN and the type of recovery to support at the DSN level. The ADD JOB_JCL creates a recovery JCL record to be used in the event of a user abend. The ADD INTERNAL_READER command creates a rule set element that controls the processing of recovery JCL that is generated when a job abends. The ISPF online interface and the ACTIVATE RULE_SET command activates a rule set. |
Changed | None |
Obsolete | None |
Security
Purpose | RUV uses APF interfaces to allow flexibility for the user to implement security. |
|---|---|
New | RUV has specific security parameters in addition to standard site security. |
Changed | The product load library must be APF-authorized. |
Obsolete | None |
ISPF interface
Purpose | The ISPF interface allows you to perform a VSAM recovery, display backup and archive data sets, display a log of logs list, display subsystem and rule set information and create rule sets, and look up message information. |
|---|---|
New | The ISPF interface can be used as an automated recovery tool, and provides online interaction for repository data. |
Changed | None |
Obsolete | None |
Using BMC Software Subsystems
Purpose | BMC Software subsystems activate or facilitate RUV and other BMC Software products. |
|---|---|
New | The BMC Software Primary Subsystem (BMCP) and the BMC Software Consolidated Subsystem (BCSS) are now required to implement and use the RUV and to access the repository. |
Changed | In RPCV, the BMCP and BCSS subsystems were required only when the customer implemented the JOB STEP logging and backout features. Use the SET SUBSYSTEM command to connect a batch job to a specific subsystem. |
Obsolete | The RPCV subsystem and the Backup Subsystem (RPCS) are not valid for RUV product. |
Batch journaling and job step logging
Purpose | Provides recovery data for batch processing. |
|---|---|
New | Batch journaling requires a rule set to be defined in the RUV repository. The rule set contains all of the information that is necessary to indicate what VSAM files will be protected (journaled or logged). The default rule set is # DEFAULT. This member is located in the RUV.CNTL library. The BMCP and the BCSS are now required for this feature. Program RUVZCJC converts an ISIJCT to RUV rule set. |
Changed | One output journal or log is created per job step. Dynamic backout is provided if the proper recovery JCL is defined in the rule set and logging is requested for the step. |
Obsolete | Programs ISIREP and ISI0192A are no longer required. The ISIOPT, ISIJCT, and ISICOPT tables are no longer required. The RPCV subsystem option tables (global option, write-ahead log, backout exclude data sets, and initialization list) are no longer required. An equivalent program to perform a backout to the beginning of a job step has been dropped. |
Backing up master data sets
Purpose | The backup command writes one or more copies of a VSAM base cluster to sequential data set(s) in RUV prefixed format. |
|---|---|
New | The backup command has a new syntax. The registration of the backup is done automatically. The BMCP and the BCSS are now required for this feature and for the Backup-While-Open (BWO) feature. The CICS file definition for VSAM files that are to be processed through the BWO feature must include the update attribute. |
Changed | Program RUVZSM0 is used to process the Backup command. The CICS RDO entries for PLTPI and PLTSD have changed. See members RUVPLTPI and RUVPLTSD of the RUV.CNTL library. If you plan on using BWO, RUVB8020 is required in the PLTPI and PLTSD. This is the BWO CICS Controller, which communicates with the RUV subsystem. The setting of the CICS transient data destination ID used for Subsystem Backup information messages has a default setting of "CSMT". The setting of the first three characters of the RUV CICS transaction IDs has changed. The default transaction ID prefix is "RUV". Use the SET SUBSYSTEM command to connect a batch job to a specific subsystem when performing backup (or BWO) so the registration is done in the correct repository. |
Obsolete | The CIMODE feature is dropped. |
Purge processing
Purpose | The PURGE command purges obsolete repository records. |
|---|---|
New | None |
Changed | The number of days and cycles per file can be set using the UPDATE/ADD VSAM_FILE commands. |
Obsolete | None |
Archiving with RUV
Purpose | The ARCHIVE command will register recovery information in the repository. |
|---|---|
New | The ARCHIVE command causes a CICS journal or log stream to be read and reformatted into RUV archive records. |
Changed | Program RUVZSM0 is used to process the Archive command. |
Obsolete | The JOURNAL command is obsolete. |
RUV recovery
Purpose | Recover VSAM files in parallel. |
|---|---|
New | The RESTORE command has a complete new syntax. The RECOVER command is used to perform recover forward or backout. The RUV recovery processing performs parallel restore, recovery, and BLDINDEX tasks. Use the Set READER_TASKS(nn) command to control the maximum number of parallel tasks per command. RUV product recovery processing restores the latest RUV or SMS backup master file. The RESTORE VSAM_FILE command restores VSAM master file from the latest RUV or SMS backup master file in preparation for a forward recovery. The RECOVER FORWARD command performs a forward recovery. The RECOVER BACKOUT command performs a backward recovery. |
Changed | None |
Obsolete | None |
Creating RUV reports
Purpose | The REPORT command creates a report on data in the repository. |
|---|---|
New | RPCV-created journals and logs can be processed by the RUV utilities, but they must be registered by the ARCHIVE or REGISTER command. The reports have a new format. You can use the SET command with the REPORT option to set the reporting level (SUMMARY | DETAIL | FULL). |
Changed | None |
Obsolete | None |
Miscellaneous items
Purpose | Many features have been augmented with additional functionality or changes. |
|---|---|
New | Most commands allow wildcards. |
Changed | The group feature lets you process many files at the same time and in the same way. For example, you can recover related files as a group rather than individually. |
Obsolete | In-flight processing is supported as a result of changes in the CICS Transaction Server. See Recovery-process-in-RUV. |