Post-Installation
Learn how to perform post-installation tasks before Datacom VSAM Transparency can be started, verified, and used in your environment.
Required roles: systems programmer, security administrator, database administrator |
|---|
This section describes the minimum post-installation tasks that are needed before
Datacom VSAM Transparency
can be started, verified, and used in your environment.Post-Installation Procedures
Complete the following items before beginning this post-installation process:
- Read the README file for the product located at the beginning of the Installation section.
- If you are upgrading from the previous version, read the Release Notes.
- See the Installation Worksheets. These procedure parameters are required for allDatacom VSAM Transparencyproduct installations. Verify that each parameter has a valid value.
- Using the Installation Worksheet as a guide, customize the macro$DCBGEDTwith your site-specific information and then copy the macro to your SYSPROC location. Replace the rightmost parameters for each ISREDITCHANGEcommand. Each time that you edit an installation member, type$DCBGEDTon the command line and pressto replace the defaults with your specifications. TheEnter$DCBGEDTmacro is used to edit the BGCUS00 member in CABGSAMP and all installation JCL members in INSTJCL.
Prepare for Post-Installation
This section provides step-by-step instructions for completing the installation and verification of your
Datacom VSAM Transparency
Version 15.1 in the z/OS environment. The post-installation procedure only supports new installations of Datacom VSAM Transparency
Version 15.1. If you are currently running a prior version of the product, there are notes during the post-installation as to steps you can skip. More topics and JCL members are available to assist you in migrating your Version 15.1 installation to replace your previous version after your initial testing is complete.Review the README file located at the beginning of the Installation section before beginning the post-installation process. This file contains information about various important topics, including product concerns, new features, and installation or maintenance issues that are not available elsewhere.
Sample JCL Data Sets
The following sample JCL data sets are required for post-installation:
- CABGSAMP target library contains the JCL required to allocate and populate the INSTJCL library where the post-installation jobs reside.
- INSTJCL contains the JCL to complete the post-installation and verification process.
After the SMP/E installation, copy the necessary post-installation jobs from CABGSAMP to the new INSTJCL library. Do not save member BGCUS00 in CABGSAMP since this is an SMP/E controlled data set. Use the provided BGCUS00 job to allocate the INSTJCL library and copy the required members to it.
Review the JCL for any DD statements that must be added or removed to reflect the environment at your site properly before you submit each step.
APF Authorized Library
To install the
Datacom VSAM Transparency
15.1 Subsystem, the CUSLIB data set must be APF authorized. If you have SYSVIEW
installed, use the BGADDAPF member from the INSTJCL library to authorize the data set temporarily with an IPL. This temporary authorization only lasts until the next IPL. Therefore, after the next IPL, either add the data set to the APF Authorized List or execute the BGADDAPF member again.You must know the disk volume on which the CUSLIB is to reside before
SYSVIEW
can be used to authorize the library. For that reason, the BGADDAPF is included after the execution of the BGCUS01 member that allocates the library. Once you know the disk volume, the member can be executed at any time before executing BGRIM01.INSTJCL Member Names
The INSTJCL member names can be easily identified during any installation.
The following members are grouped by the first five characters:
- BGCIC
- indicates a job to modify the CICS CSD entries to supportDatacom VSAM Transparencyunder CICS. This job may not be required if you have Version 14.0 and have current maintenance applied.
- BGCUS
- indicates a customization job to allocate and populate more libraries.
- BGIVP
- indicates a job to execute a sample job for installation verification.
- BGNEW
- indicates a job for new installations only. This process only supports new installations of the Version 15.1 product. Steps that may not be required if you have a previous version installed are noted.
- BGRIM
- indicates a job for installing theDatacom VSAM TransparencySubsystem.
- BGTRN
- indicates a job that is used in transitioning a production environment from a prior version ofDatacom VSAM Transparencyto the new version.
The following two jobs can undo a migration of Version 15.1 to replace the previous version, if necessary.
- BGFBK
- indicates a job for returning to the previous version after completing the upgrade installation and migration process.
- BGFFW
- indicates a job for falling forward back from a previous version to Version 15.1 at some future date.
The remainder of each name indicates the number of the step.
Member
BGAPFADD
is provided to allow SYSVIEW
, if installed, to be used to APF authorize the custom load library (CUSLIB).Complete each installation step before you begin the next step.
SMP/E Configuration
When upgrading from the previous release, consider that SMP/E not only supersedes all SYSMODs for the previous release but also deletes them when installing the current release. You can install the current release into a new CSI or target library, or you can copy the target library to another data set. This allows the previous version of the product to be available as needed.
Use Common Components and Services Utility CAIRIM
Common Components and Services
Utility CAIRIMDuring the Post-Installation process,
Datacom VSAM Transparency
uses the Common Components and Services
utility that is called CAIRIM to install and modify the Datacom VSAM Transparency
Subsystem. Use of the CAIRIM utility allows implementation and modification of the subsystem without requiring an IPL. Changes that are made using CAIRIM are only in effect until the operating system is IPLed. When the operating system is IPLed, the changes can be made permanent or you can make executing the CAIRIM utility a standard part of the IPL process. For more information, see Install a New Subsystem.