Previous Topic: Installation Steps to Upgrade to Release 12.2Next Topic: Reverting to a Previous Installation


Configuration Steps to Upgrade to Release 12.2 without CA CSM

To upgrade to Release 12.2, perform each configuration step exactly as presented in the Starting Your Product chapter unless the step has upgrade instructions in the table that follows.

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 12.2. Release 12.2 provides full compatibility with Release 11.7, Version 12.0, and Release 12.1 databases. If you want to utilize specific Release 12.2 features, upgrade the database to Release 12.2.

Note: If you do not want to from a previous release or version databases, skip this step.

This step replaces the Create the Database step in the chapter "Starting Your Product."

Instead of creating a CA View database, use the VERSION control statement of the SARDBASE utility to version your database to Release 12.2. 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 12.2

Sample JCL to version the database is provided in member

HBRMVERS in CAI.CVDEJCL

For more information, see the SARDBASE utility in the chapter "Database Utilities" in the Reference Guide.

Note: Save your initialization parameter settings; some parameter settings have been added or eliminated in this release, but you may need the original settings if you have 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 12.2 online library.

Follow the instructions in this step in the "Starting Your Product" chapter and 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 12.2.

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 12.2 model banner page library.

Follow the instructions in this step in the "Starting Your Product" chapter and load the model banner panels to the database.

Step 8

Add the Microfiche Option (Optional)

Follow the instructions in this step in the "Starting Your Product" chapter. 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 the "Starting Your Product" chapter.

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 the "Starting Your Product" chapter.

Step 11

Install System Extensions (Optional)

Follow the instructions in this step in the "Starting Your Product" chapter. If you use system extensions, add or adjust the start procedure in the PROCLIB.

Before installing a new version of SARXTD, be sure that the old system extensions have been withdrawn.

Do this by issuing the following command:

S SARXTD,PARM=OFF

Include the system extensions parameter in the started task JCL. Be sure that the system extensions JCL procedure is pointing to the new version of CVDELOAD through the STEPLIB statement.

Note: 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 you used it in the previous releases. Otherwise, follow the instructions in this step in the "Starting Your Product" chapter to modify the system defaults for exceptional condition checking.

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 need to 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, be sure that your user exit(s) 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, an additional check may have to be added 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.

For more information about user exits, see the "User Exits" chapter in the Programming Guide.

Step 14

Set Up for Multiple CPUs

Review the instructions in this step in the "Starting Your Product" chapter. Verify that ENQs and RESERVEs are defined sufficiently to maintain integrity of the data sets.

Be aware of the following:

  • 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 the "Starting Your Product" chapter, then 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.

There has been a minor change to cross-memory (one of the CA View optional features): the cross-memory program name was changed to EC2DRV to permit concurrent execution of the releases.

For more information, see Installing Cross-Memory Services (XMS) in the Installing Online Interfaces section

Step 17

Download the EMC Centera API for CA View (Optional)

Follow the instructions in the chapter
"EMC Centera Disk Option" in the Reference Guide to download and configure the EMC Centera Disk Option.

Step 18

Add the Archival Task Start Procedure

Follow the instructions in the Installation chapter you are using and add or adjust the archival start procedure in the PROCLIB. Ensure that STEPLIB points to the new CAI.CVDELOAD load library.

You may 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 the Starting Your Product chapter. Some initialization parameters have been added, changed, or eliminated in Release 12.2. Be sure to review the initialization parameters in the "Initialization Parameters" chapter in the Reference Guide.

For more information about all initialization parameter changes, see the Release Notes.

Note: Be sure to review any changes made to the FEATURE initialization parameter for this release and adjust your values removing any feature codes that have been deactivated.

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.

For more information about customizing and configuring CA DRAS, see the CA DRAS Operations Guide.