Minimum configuration tasks that are needed before CA Datacom/DB can be started, customized, and used in your environment.
This section describes the minimum configuration tasks that are needed before
CA Datacom®/DBcan be started, customized, and used in your environment.
This install process uses DISP=(MOD,DELETE,DELETE) to allow JOBs to run multiple times. For this post install process, use the correct High Level Qualifier for your data set names when running these JOBs. The first part of these JOBs does the clean-up using this technique.
The following topics are discussed on this page:
If you are installing
CA Datacom®for the first time, read all of the installation content before you begin the installation process. Some pre-installation considerations apply directly to new installations.
After completing the steps commonly required for all installations, complete the steps that are listed in New Installation Phase. Do not perform the steps in the section for the upgrade installation phase.
When you finish the last step, you have completed your new installation. Verify the successful installation of your
CA Datacom®products as shown in Installation Verification Phase.
Upgrading Existing Products
If you are upgrading your existing
CA Datacom®products from Version 14.0 to Version 15.x, some pre-installation considerations apply directly to upgrades. To determine if there are more requirements, see the README File.
The upgrade process is intended to be performed in multiple phases.
- Phase 1: Execute the DDSDCLM program.This program is used to determine the status of yourCA Datacom® Datadictionary™database and should be executed against each multi-user region before beginning the upgrade. Member ADSDC14 in the CABDSAMP library contains sample JCL to perform this step. For information about running this utility, see DDSDCLM - Comparing DATA-DICT Prior to Upgrading.
- Phase 2: InstallCA Datacom®/DB15.x into a new MUF region using the new install members of INSTJCL.This phase is optional but highly recommended. Also, you can use this phase for the initial testing.
- Phase 3: Select a test multi-user region for the first upgrade.
- Phase 4: Upgrade the multi-user region from Version 14.0 to Version 15.x.You can continue to run CICS and batch regions that are still at the 14.0 level against this multi-user. This phase allows you to test the following against a multi-user at 15.x with minimum impact if a fallback to 14.0 is necessary:
- DB utilities
- CA Datacom® Datadictionary™batch and online
- Dataquery batch and online
- Your applications
- Phase 5: Upgrade theCA Datacom® Datadictionary™to 15.x.This upgrade can be fully performed against the 15.x multi-user with no need to recycle the multi-user or close theCA Datacom® Datadictionary™or DDD databases. You can still continue to execute 14.0 level batch and online against the 15.x multi-user.
- Phase 6: Upgrade your batch and CICS jobs to run at the 15.x level.If you have multiple CICS regions executing against the Multi-User Facility (MUF), you do not have to upgrade them all simultaneously. Both the 14.0 and 15.x level CICS regions can run against the multi-user at the 15.x level.When you are comfortable with the 15.x release code, the following actions must be considered per CICS region that communicates with the MUF instance:1. DFHRPL must be changed to point to the new release libraries (CUSLIB and CABDLOAD) for 15.x.2. Update the ADRPNL VLS library with the new 15.x signon and signoff panels for Datadictionary (BDUPG09A). Be aware that ADRPNL might be shared across a number of CICS regions.3. At your convenience, recycle the CICS regions as needed with the new DFHRPL.
- Phase 7: Perform Phases 3 through 4 for each of your test and production multi-user regions.
Each of these phases can last for any length of time from minutes to months.
APF Authorized Libraries
The MUF must be run as an APF authorized job or task.The CUSLIB data set and all product target libraries that occur in the JOBLIB/STEPLIB must be APF authorized. Your current Version 14.0 libraries should already be APF authorized. This is required before the upgrade and fall back procedures.
If you have SYSVIEW, INSTJCL member APFADD can be used to add the libraries to the APF list dynamically. This is not a permanent change for APF authorization.
Certain functions of DBUTLTY require that the job run APF authorized. To find out which features require APF authorization, see the