Upgrade CA View

Administrators use these instructions to upgrade to CA View Release 14.0 from CA View Version 12.0, Release 12.1 or Release 12.2. They consist of the original steps and a series of modifications.
view140
Administrators use these instructions to upgrade to CA View Release 14.0 from CA View Version 12.0, Release 12.1 or Release 12.2. They consist of the original steps and a series of modifications.
To upgrade to Release 14.0, use the steps in the following sections. Modify the steps according to the supplementary instructions in the tables in the following sections. Existing Version 12.0, Release 12.1 or Release 12.2 users install the product in almost the same way as new users with one exception: Instead of creating a database you version your existing database. This process updates several records in the database and executes in a few minutes.
Installation Steps to Upgrade to Release 14.0
To upgrade to Release 14.0, perform each installation step exactly as presented in the previous sections, unless the step has upgrade instructions in the table that follows:
 
Installation Step
 
 
Supplementary Upgrade Instructions
 
Step BRM60RCH
No supplementary instructions.
Step BRM00ALL
Comment out or delete the allocations for the target libraries that exist.
 
Note: 
Beginning with Release 11, to help simplify installations and upgrades, the foreign language panel FMIDs have been incorporated into the CA View base FMID. This change requires that all four panel libraries exist; otherwise, the Apply step fails.
Also, it is likely that any existing panel libraries must be enlarged before you run the Apply step. See Hardware Requirements to determine the required amount of space for these libraries and adjust the space accordingly. If you are upgrading from Version 12.0, Release 12.1, or Release 12.2, and the panel libraries are sufficiently allocated, skip this step.
Step BRM03ALU
No supplementary instructions. This step is required only if installing CA Output Management Web Viewer 14.0 or higher.
Step BRM10CSI
 
Comment out or delete the allocations for any libraries that already exist. Comment out or delete the step that creates the CSI. If you are upgrading from Version 12.0, Release 12.1, or Release 12.2, comment out or delete the DDDEF statements for SYSPUNCH (three occurrences). Change all ADD statements to REP statements. Condition code 04 is acceptable.
 
Note: 
The default middle level qualifier name of the SMP/E CSI has been removed beginning with Release 11.6. If you are upgrading from a previous release, verify that the correct, complete name of your CSI is specified in the PARM= on the execute card.
Steps BRM15CSU, BRM06MKD
No supplementary instructions. 
These steps are required only if installing CA Output Management Web Viewer 14.0 or higher.
Steps BRM20RCB, BRM30APB, BRM40ACB
No supplementary instructions.
However, note that the default middle level qualifier name of the SMP/E CSI was removed beginning with Release 11.6. If you are upgrading, verify that the correct, complete name of your CSI is specified in the PARM= on the execute card.
Configuration Steps to Upgrade to Release 14.0 Without CA CSM
To upgrade to Release 14.0, perform each configuration step exactly as presented in the earlier sections, unless the step has upgrade instructions in the following table.
The Step column lists the step and the Upgrade Instructions column explains what you must do to modify or replace the step.
 
Configuration Step 
 
 
Supplementary Upgrade Instructions 
 
Step 1-3
No supplementary instructions.
Step 4
Optionally set the version of your database up to Release 14.0. Release 14.0 provides full compatibility with Version 12.0, Release 12.1 and Release 12.2 databases. If you want to use Release 14.0 features, upgrade the database to Release 14.0.
 
Note:
 If you do not want to upgrade from a previous release or version databases, skip this step.
This step replaces the Create the Database step.
Instead of creating a CA View database, use the VERSION control statement of the SARDBASE utility to version your database to Release 14.0. This procedure executes in a few minutes.
The high-level name of the database must have been previously defined with the NAME control statement (or the PARM parameter of the EXEC JCL statement) for the SARDBASE utility. The format of the VERSION control statement is:
Release 14.0
Sample JCL to version the database is provided in member
HBRMVERS in CAI.CVDEJCL
For more information, see Database Utilities.
Save your initialization parameter settings. Some parameter settings have been added or eliminated in this release. However, you might need the original settings if you need to revert to a previous release.
Step 5
No supplementary instructions
Step 6
Load Online Panels and JCL Library
If online panel members were customized in previous releases, copy those members to the appropriate Release 14.0 online library.
Follow the instructions in this step in Configure Using CA CSM or Configure Without CA CSM (whichever applies). Next, load the online panels for each language you are using to the database. Because some online panels have changed, you must OLOAD the new panels.
 
Note
: Only perform the OLOAD of the new panels if the database has been versioned to Release 14.0.
Step 7
Load the Model Banner Pages
If model banner page members were customized or added in previous releases, copy those members to the Release 14.0 model banner page library.
Follow the instructions in this step in Configure Using CA CSM or Configure Without CA CSM (whichever applies). Next, load the model banner panels to the database.
Step 8
Add the Microfiche Option (Optional)
Follow the instructions in this step in in Configure Using CA CSM or Configure Without CA CSM (whichever applies). If you plan to use microfiche, add or adjust the start procedure in the PROCLIB.
Step 9
Set up Job Accounting (Optional)
Skip this step if you want to continue to capture job accounting data in the same way you captured it in the previous releases. Otherwise, follow the instructions in this step in Configure Using CA CSM or Configure Without CA CSM (whichever applies).
Step 10
Set up Backup Tape Tracking (Optional)
Skip this step if you want to continue to automatically track backup tapes the same way you used it in the previous releases. Otherwise, follow the instructions in this step in Configure Using CA CSM or Configure Without CA CSM (whichever applies).
Step 11
Install System Extensions (Optional)
Follow the instructions in this step in in Configure Using CA CSM or Configure Without CA CSM (whichever applies). Next, if you use system extensions, add or adjust the start procedure in the PROCLIB.
Before you install a new version of SARXTD, verify that the old system extensions have been withdrawn. Issue the following command:
S SARXTD,PARM=OFF
Include the system extensions parameter in the started task JCL. Verify that the system extensions JCL procedure is pointing to the new version of CVDELOAD through the STEPLIB statement.
If the CA View load modules are copied to your linklist library, remove the STEPLIB statement in the system extensions Proc.
Step 12
Exceptional Condition Checking (Optional)
Skip this step if you want to continue to use exceptional condition checking the same way that you used it in the previous releases. Otherwise, follow the instructions in this step in in Configure Using CA CSM or Configure Without CA CSM (whichever applies) to modify the system defaults for checking exception conditions.
Step 13
Replace or Modify User Exits (Optional)
Perform this step if you modified any of the CA View user exits; otherwise, go to the next step.
For each user exit that you have tailored in previous releases, copy your changes to the new CA View skeleton version and assemble it.
Sample JCL is provided to assist with the installation of most CA View user exits in two formats. One sample format provides JCL for SMP/E-controlled USERMOD installation, and one sample format provides JCL to install outside of SMP.
The non-SMP/E samples have been provided in this release to help facilitate improved management of multiple sets of target libraries that have been deployed on more than a single LPAR and have different configuration criteria. To safely manage user exits outside of SMP/E, link the exits into a separate, independent load library that can be link-listed or concatenated before the CA View product load library.
Save a copy of your user exits in case you revert to the previous release.
The SARFVCUX and SARSTCUX user exits are now called with a new entry code 12 starting with Release 11.6. If you are tailoring these user exits, verify that your user exits correctly handle this new entry code. If your user exit code performs a simple check for entry code 4 and assumes that a higher value is the close call, you might need to an additional check for entry code 12. In most cases, the entry code 12 call can be ignored by exiting from the user exit.
If desired, the original sysout records can be monitored or altered through the entry code 12 call.
If you use prior release code in the EBCCICUX user exit, replace the “EXEC CICS RETURN” CICS command-level statement with a DHFEIRET macro.
For more information about user exits, see Programming.
Step 14
Set Up for Multiple CPUs
Review the instructions in this step in Set up for Multiple CPUs. Verify that ENQs and RESERVEs are defined sufficiently to maintain integrity of the data sets.
Note the following points:
No active tasks must be running that are pointing to the CVDELOAD and database that are being upgraded.
If multiple versions of CA View are running on multiple CPUs and share the database, all PROCs, JCL, CLISTS, and so forth, that access a given CA View database must also be upgraded.
Step 15
No supplementary instructions
Step 16
Install Optional Features (Optional)
Verify that the LMP key has been supplied for each feature that you want to install; see the Enter the LMP Code step in Configure Using CA CSM or Configure Without CA CSM (whichever applies). Next, follow the installation instructions in the Installing Features section.
You should not have to make any changes in your current use of those programs.
Use a new CVDELOAD and new ERO parameters.
Cross-memory (one of the CA View optional features) includes the following minor update: The cross-memory program name was changed to EE0DRV. Update the name to EE0DRV or EBCDRV in any JCL that specifies the names from earlier releases.
For more information, see Install Cross-Memory Services in the 
Install Online Interfaces
 section.
Step 17
Download the EMC Centera API for CA View (Optional)
Follow the instructions in EMC Centera Disk Option to download and configure the EMC Centera Disk Option.
Step 18
Add the Archival Task Start Procedure
Follow the installation instructions and add or adjust the archival start procedure in the PROCLIB. Verify that STEPLIB points to the new CAI.CVDELOAD load library.
You might want to add the following statements, if you do not already have them:
  • The SARBKLST DD statement provides information about reports that are backed up to tape, reports deleted from the database by the backup cycle, and uncataloged tapes.
  • The SARD2LST DD statement provides information about reports that are backed up to the DR tape.
  • The SARDRLST DD statement provides information about optical migration.
Step 19
Use SARINIT to Set the Final Initialization Parameter Values
Follow the instructions in this step in Configure Using CA CSM or Configure Without CA CSM (whichever applies).
Save a copy of your initialization parameters in case you want to revert to a previous release.
Step 20
Customize and Configure CA DRAS (Optional)
Perform this step if you have installed the CA DRAS component to enable cooperative viewing with CA Output Management Web Viewer. For compatibility, if you versioned your CA View database to the most recent version, verify that your DRAS task is using the most recent libraries.
Note that the CA Spool SAS/C-based AFP-to-PDF transformer is no longer distributed or supported by CA View, beginning with CA View Release 14.0. CA View now supports only the Java transformers.  If you are using the SAS/C based transformers with a previous release of CA OM Web Viewer, you must make some changes to your DRAS parameters to enable the new JAVA Transformers to function correctly.  See sections ‘CA Spool Java Transformers’ and ‘CA DRAS Operations’ for additional information.
For more information about customizing and configuring CA DRAS, see CA DRAS Operations.