ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CA View/Deliver - Migration/Upgrade Questions

book

Article ID: 145845

calendar_today

Updated On:

Products

Deliver View

Issue/Introduction

In upgrading View and Deliver r12.2 to r14.0, what are some of the best practices for the install? 
  
Which libraries should be copied in order to migrate around?  Should all of the **.CVDE** datasets be migrated?

We are currently running View and Deliver from their own **.RMO.LOAD and **.VIEW.LOAD libraries.
Is it possible (or recommended) to separate VIEW or RMO?

Will it be an issue to have only one load library for both VIEW/RMO?

Some systems may get upgraded to zOS 2.4 before the migration to View/Deliver/ 
Will 12.2 run on z/OS 2.4 without issue?

Environment

Release : 14.0

Component : CA View

Resolution

In a SARDBASE VERSION nn.n, the View index records are adjusted to those that are in the defined version (nn.n).

No data is affected in the process, only the index.

There are no compatibility PTFs for View 12.2 regarding tapes created in 14.0.

With that, the tape format is similar between the two versions, so either release can process the other's tapes.

----------------------------------------------------------------------------------

In the event of needing to fall back:

. Run SARDBASE/RMODBASE VERSION 12.2, using 14.0 code.
. Implement 12.2 code and libraries.
. Run SARDBASE 12.2 OLOAD and BLOAD.
. Run RMODBASE 12.2 OLOAD and BLOAD.

The overall recommendation is to move forward with the upgrade.

Falling back, in most cases, would occur due to something not being planned right, or there being a flaw in the upgrade's execution.