Step

Upgrade Instructions

Steps 1-2

No supplementary instructions

Step 3

Define Security Rules

If you modified the RMOATHUX authorization user exit or installed authorization tables, copy your changes into to the new CA Deliver skeleton version and assemble them in Step 23.

If you have external security rules, review the "Security" chapter in the CA Deliver Reference Guide to determine if new security rules are necessary.

Step 4

Optionally, set the version of your database up to Version 12.0. Version 12.0 provides full compatibility with releases r11.5, r11.6, and r11.7 databases.

If you want to utilize specific Version 12.0 features the database must be upgraded to Version 12.0.

Note: If you do not want to upgrade your release r11.5, r11.6, or r11.7 database, skip this step.

This step replaces the Create the Database step in the chapter "Installation." Be aware of the following:

• Instead of creating a CA Deliver database, you use the VERSION control statement of the RMODBASE utility to version your database to Version 12.0. You can tailor and submit CAI.CVDEJCL(HBRNVERS).
• 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 RMODBASE utility. The format of the VERSION control statement is:

Version 12.0

For more information, see the RMODBASE Utility section in the chapter "Database Utilities" in the CA Deliver Reference Guide.

Note: Save your initialization parameter settings; some parameter settings have been added or eliminated in Version 12.0, and you may need the original settings if you have to revert to releases r11.5, r11.6, or r11.7.

Step 5

Create the Initialization Parameter Statements

Follow the instructions in the "Installation" chapter. Some initialization parameters have been added, changed, or eliminated in Version 12.0.

Be sure to review the initialization parameters presented in the chapter "Initialization Parameters" in the CA Deliver Reference Guide.

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

Save a copy of your initialization parameters in case you have to revert to releases r11.5, r11.6, or r11.7.

Step 6

No supplementary instructions

Step 7

Load Online Panels and the JCL Library

• If online panel members were customized in releases r11.5, r11.6, or r11.7, copy those members to the appropriate Version 12.0 online library.
• If the customized panels are maintained in a separate library, load those online panel members after loading the Version 12.0 panel members to the database.

Follow the instructions in the "Installation" chapter and load the online panels to the database. Because some online panels have changed, you must OLOAD the new panels.

Important! Only perform to the OLOAD of the new panels if the database has been versioned to Version 12.0.

Step 8

Load the Model Banner Pages

• If model banner page members were customized or added in releases r11.5, r11.6, or r11.7, copy those members to the Version 12.0 model banner page library.
• If the customized banner pages are maintained in a separate library, load those banner page members after loading the Version 12.0 banner page members to the database.

Follow the instructions in the "Installation" chapter and load the model banner panels to the database.

Step 9

Add the Start Procedure to PROCLIB

Follow the instructions in the "Installation" chapter and add or adjust the start procedure in the PROCLIB.

Be sure that STEPLIB points to the new CAI.CVDELOAD.

Steps 10-11

No supplementary instructions

Step 12

Set Up for Multiple CPUs

Follow the instructions in the chapter "Installation." If you use a system integrity product, make the changes needed to accommodate the new CA Deliver database.

Note: There have been no changes to the way releases r11.5, r11.6, and r11.7 interact with products of this type, so changes should be minimal.

Be aware of the following:

• No active tasks can be running that point to the CVDELOAD and database that are being upgraded.
• If multiple versions of CA Deliver are running on multiple CPUs and share the same database, all PROCs, JCL, CLISTS, and so forth, that access a given CA Deliver database must also be upgraded.

Step 13

No supplementary instructions

Step 14

Set up the Viewing Interface

Skip this step if the Deliver databases have already been defined to CA View.

Step 15

Replace or Modify User Exits (Optional)

If you modified any of the CA Deliver user exits perform this step; otherwise, go to the next step. Note the following:

• For each user exit that you tailored in release r11.5, r11.6, or r11.7, you must copy your changes to the new CA Deliver skeleton version and assemble it.
• All modifications to these exits must be done as an SMP/E USERMOD with the load module installed into CVDELOAD.
• For your convenience, CVDEOPTN members are provided for all of the user exits.

Save a copy of your user exits in case you need to revert to release r11.5, r11.6, or r11.7. For more information about user exits, see the chapter "User Exits" in the Reference Guide.

Step 16

No supplementary instructions

Step 17

Install Optional Features (Optional)

Review the chapter "Installing Features".

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 "Installation" chapter), then follow the installation instructions in the chapter "Installing Features."

Be sure that all STEPLIB statements in your JCL reference the new CAI.CVDELOAD.

There has been a minor change to cross-memory (one of the CA Deliver optional features):The cross-memory task program name has been changed to EC0DRV. Any JCL that contains the earlier release names, must be changed to EC0DRV.

For more information about installing cross-memory services, see the "Installing Online Interfaces" chapter.