I am upgrading to release 14.0 of CA View/Deliver. Is there a Best Practice Guide available that outlines the basic steps and phases of the upgrade process and that references the areas of documentation that provide any additional details we will need to complete the upgrade process successfully?
Release : 14.0
Component : CA View/Deliver
CA View
CA Deliver
I). Downloading the CA View/Deliver product installation package and maintenance from the Support Portal:
- The SPECIFIC pax.z file you will use to install the base CA View/Deliver 14.0 (GA 0000) product is:
Release: 14.0
Servicepack: 0000
File: CA View,CA Deliver,CA OM Web Viewer 14.0 0000-Product Package
DVD0000000000961.pax.z
Date: Sep 20 2019 6:47AM
- You will also want to download and apply all maintenance for CA View/Deliver 14.0 created since the GA 0000 install level.
II). Overview of CA View/Deliver 14.0 upgrade phases and steps are as follows:
Phase 1: Acquire the new code & create execution libraries -
. Install the View/Deliver 14.0 code.
. Update all View/Deliver related jobs and tasks to use the 14.0 load library.
. If you are using XMS and accessing View via CICS and VTAM you need to:
a. Update the XMS task program name.
b. Reinstall the CICS interface.
c. Reinstall the VTAM interface.
Options:
a. Add 14.0 load library to LINKLIST "BEFORE" previous release load library - LLA REFRESH.
b. Add STEPLIB DD's to tasks and jobs that point to the 14.0 load library.
c. Optionally, both 'a' and 'b'.
NOTE:
- Higher release load libraries are downward compatible to lesser release database files.
- However, lesser release load libraries are NOT upward compatible to higher release database files.
. Start the CA View, CA Deliver and other associated tasks if applicable.
Phase 2: When it's time to upgrade the database files -
. Shut down all View tasks (SARSTC, SARFSS, SARXTD, SARXMS, SAREAS, etc.)
. Shut down all Deliver RMOSTC tasks, using "/F rmostc,OFF".
For the CA View databases (Data and Index extents):
. Run SARDBASE UNLOAD (or other utility) to back database files up at the 12.2 level.
. Run SARDBASE VERSION 14.0 on the View databases.
. Populate your appropriate 14.0 libraries with any user customized panel and/or banner members.
. Edit the CVDEPENU(SARJCL1) member, either changing or removing the //STEPLIB.
. Run SARDBASE OLOAD, using input of the 14.0 CVDEPENU library.
. Run SARDBASE BLOAD, using input of the 14.0 CVDEDATA library.
. RE-Install any user customized exits into the 14.0 load library.
For the CA Deliver databases (Data and Index extents):
. Run RMODBASE UNLOAD (or other utility) to back them up at the 12.2 level.
. Run RMODBASE VERSION 14.0 on the Deliver databases.
. Populate your appropriate 14.0 libraries with any user customized panel and/or banner members.
. Edit the CVDEPENU(RMOJCLB) member, either changing or removing the //STEPLIB.
. Run RMODBASE OLOAD, using input of the 14.0 CVDEPENU library.
. Run RMODBASE BLOAD, using input of the 14.0 CVDED133 library.
. RE-Install any user customized exits into the 14.0 load library.
- If accessing CA View/Deliver via XMS Cross-Memory task (i.e. CICS,VTAM,IMS,ISPF,ROSCOE)
. Update XMS proc's execution program to PGM=EBCDRV
. Update any //STEPLIB DD's (If applicable)
. Modify, Assemble, and Link the EE0XMCTR Table/Module to invoke the 14.0 macros.
- Startup:
. Start the CA View, CA Deliver and other associated tasks if applicable.
NOTES:
- In case of fallback, any backout steps would be a reversal of the above.
- VERSION processes must point to 14.0 load library (With version control set as VERSION 12.2).
- The OLOAD and BLOAD processes would point to your 12.2 CVDEPENU and CVDED133 libraries.
III). Detailed Installation and Upgrade documentation references are as follows:
- Install Products Using CA CSM
- Install Products Using SMP/E JCL
IV). Best Practices - Acquisition and installation of Maintenance:
- If your site is not using Chorus CSM/MSM then we HIGHLY ENCOURAGE you to use the SMP/E Internet Service Retrieval/Receive Order process for the acquisition and application of product maintenance (which would include all HOLDDATA).
SMP/E Internet Service Retrieval can automate the download of CA product maintenance, eliminating the need to manually search for solutions, create solution carts, process zip files, and RECEIVE maintenance. You can download specific solutions, CA Recommended Service, or all available solutions – all without ever having to access the Downloads page!
SMP/E Internet Service Retrieval / Receive Order automates the download of PTF maintenance and HOLDDATA for the products. This service uses the IBM SMP/E RECEIVE ORDER command and can reduce hours of maintenance time to only minutes. Submit the SMP/E Receive Order job to download missing PTFs and HOLDDATA. PTFs are received directly into the global zone. Use a job scheduler to automate the acquisition and eliminate time-consuming fix searches and the need to select maintenance manually through the Broadcom Support portal. When you are ready, you can receive and apply the maintenance per your site guidelines.
- For additional information on the Receive Order method for acquiring and applying maintenance, please refer to the "MAINFRAME COMMON MAINTENANCE PROCEDURES" documentation available at the following links:
MAINFRAME COMMON MAINTENANCE PROCEDURES
Configure CA SMP/E Internet Service Retrieval
- If you are not using MSM/CSM and your are not going to subscribe to the SMP/E Internet Service Retrieval / Receive Order method for the acquisition and application of maintenance, then you are going to need to download the necessary maintenance manually.
- The easiest way for you to do it manually is as follows:
- Access the View/Deliver Detailed Maintenance Grid
- Click on the "SINCE GA" link over on the right side of the grid.
- There are a LOT of PTFs that you will need to download and install. These PTF were created after the GA base install level of View/Deliver 14.0 that was provided by the PAX file that you installed from.
- You can download the necessary PTF's directly from this screen. Or, add them to your CART and download them all in one big ZIP file.