Installation Verification Phase

After you have finished all installation steps for your site, start your customized version of your MUF with all your options activated. 
datacom
After you have finished all installation steps for your site, start your customized version of your MUF with all your options activated. To demonstrate successful product installation for batch processing, execute the jobs following the section about IVP jobs for a new installation process. The customizations must be completed and your customized MUF must be enabled (active) before any IVPs can run. INSTJCL library member names begin with IVP. The IVPNEW* (new install) members support the new naming standard for the Simplify option. The IVPUPG* members use the older naming standard from previous releases. Do not use any of the MUFs as delivered for the upgrade processes, because the delivered MUFs are configured specifically for the upgrade or new install processes only. Use only members from the **.INSTJCL: MUFSTRTS (new install) and MUFSTRTU (UPGRADE) for this process.
The IVPs must be performed in the sequence shown following the section about IVP jobs for a new installation process, and the MUF must be active for these jobs to run.
The following topics are discussed on this page:
 
 
IVP Jobs for the New Install Process
After modifying DBDATIN2 to support your site, start your MUF instance. Review the documentation for any questions about options you need to configure your MUF.
Use the IVPNEW* members for sites performing a new install. For your licensed products, start a MUF that is configured for your site. Review DBDATIN2 in your CAI.NEWHLQ.9CXX_NAME.V150.CUSMAC. Start your MUF instance with this member once it is modified for your site requirements. For an example of the MUF startup JCL usage for new installs, see member MUFSTRTS in the INSTJCL.
Once the MUF is started, you can run the IVPNEW* members to verify the install.
Step 1. Execute Sample 
CA Datacom®/DB
 Programs
Edit and submit INSTJCL library member IVPNEW01. This executes multiple programs for 
CA Datacom®/DB
 execution.
 Ignore message code CSV003I if it appears.
Step 2. Execute Sample SQL Program
Edit and submit INSTJCL library member IVPNEW02 if you installed 
CA Datacom®/DB
 with the SQL Option.
Step 3. Execute Sample Program for Building Sample Database
Edit and submit INSTJCL library member IVPNEW03 if you configured your 
CA Datacom®/DB
 MUF with the SQL option. This member has two jobs. Run the jobs one at a time and sequentially from this member. The second job is optional if you want to delete what the first job in this member defined.
If you installed 
CA Datacom®/DB
 with the SQL Option, edit and submit this member. This job includes a series of steps to demonstrate the procedure for allocating, defining, initializing, and loading the sample database that is used in the 
CA Datacom®
 SQL training documentation that is available on support.ca.com.
This INSTJCL member also contains a job that optionally uninstalls the sample database.
Step 4. Execute DQBATCH Program
Edit and submit INSTJCL library member IVPNEW04 if you configured your 
CA Datacom®/DB
 MUF with the DQ option.
Step 5. Create a Custom DCT for Presspack
Edit and submit INSTJCL library member IVPNEW05 if you configured your 
CA Datacom®/DB
 MUF with the Presspack option.
Step 6. Execute DBUTLTY from 
CA Datacom®
 Fast Restore
Edit and submit INSTJCL library member IVPNEW06 if you configured your 
CA Datacom®/DB
 MUF with the Fast Restore option.
IVP for Upgrades
After modifying DBDATIN2 to support your site, start your MUF instance. The upgrade process assumes that Simplify is not turned on and is using the old naming standards from previous releases.
IVPUPG* members are only used for sites performing upgrades. For your licensed products, start a MUF that is configured for your site.
Once the MUF is started, you can run the IVPUPG* members to verify the install.
Step 1. Execute Sample 
CA Datacom®/DB
 Programs
Edit and submit INSTJCL library member IVPUPG01. This executes multiple programs for 
CA Datacom®/DB
 execution.
 Ignore message code CSV003I if it appears.
Step 2. Execute Sample SQL Program
Edit and submit INSTJCL library member IVPUPG02 if you installed 
CA Datacom®/DB
 with the SQL Option.
Step 3. Execute Sample Program for Building Sample Database
Edit and submit INSTJCL library member IVPUPG03 if you configured your 
CA Datacom®/DB
 MUF with the SQL option. This member has two jobs.
If you have CA Sample SQL base 1001 already defined, run the second job in this member before running the first job. If the delete process has been run, the first job may receive a -118 on the create schemas due to them already existing and is expected.
If you installed 
CA Datacom®/DB
 with the SQL Option, edit and submit this member. This job includes a series of steps to demonstrate the procedure for allocating, defining, initializing, and loading the sample database that is used in the 
CA Datacom®
 SQL training documentation that is available on support.ca.com.
This INSTJCL member also contains a job that optionally uninstalls the sample database.
Step 4. Execute DQBATCH Program
Edit and submit INSTJCL library member IVPUPG04 if you configured your 
CA Datacom®/DB
 MUF with the DQ option.
Step 5. Create a Custom DCT for Presspack
Edit and submit INSTJCL library member IVPUPG05 if you configured your 
CA Datacom®/DB
 MUF with the Presspack option.
Step 6. Execute DBUTLTY from 
CA Datacom®
 Fast Restore
Edit and submit INSTJCL library member IVPUPG06 if you configured your 
CA Datacom®/DB
 MUF with the Fast Restore option.
Post-Installation Considerations
 
CA Datacom® CICS Services
 Modifications
Include a DD statement for the 
CA Datacom®
 Custom Load Library (CUSLIB) and the 
CA Datacom®
 Target Load Library (CABDLOAD) in the DFHRPL concatenation of the CICS startup JCL.
CICS requires the addition of DD statements for the 
CA Datacom®
 files. The 
CA Datacom®
 installation creates these statements for you. Fetch the DDFILE member from the Custom Macro Library (CUSMAC) and insert it into the CICS startup JCL.
The 
CA Datacom®
 installation also produces all source members for CICS table modification. These source members are in either the CABDSAMP or CUSMAC libraries and contain all of the entries for all of the 
CA Datacom®
 products being installed or upgraded. All of the required CICS table entries for these products that are defined to CICS are produced as a part of the installation.
For those sites using an existing CICS that already references a 
CA Datacom®
 MUF, it is necessary to replace the CICS groups for the earlier version. Using the following charts, replace all references to the Version 14.0 copybooks. Then reassemble and relink your CICS table DFHFCTxx and add the new CICS groups to your DFHCSD.
For those sites using an existing CICS that does not already reference a 
CA Datacom®
 MUF, 
CA Datacom® CICS Services
 must be installed, as specified in Software Requirements. Although they are included as illustrations only, the following JCL member in the INSTJCL library can be used to define the 
CA Datacom®
 products to CICS.
 The BDCSD. BDGRP, and BDCSDV CSD copybooks are part of and provided by 
CA Datacom® CICS Services
 (DBC) starting with DBC 11.0.
For more information about creating the INSTJCL job B1CICS that is used to create the CSD entries, see Step 1. Modify CICS in the 
CA Datacom® CICS Services
 documentation.
 
 
CA Datacom® Datadictionary™
 
 
 
Version 15.1 Copybook for CICS Table Assemblies
 
 
Version 15.1 Copybook for CICS RDO
 
 
CICS CSD Group Name
 
 
ADCSD
ADGRP
ADFCT
 
ADGRP
 
ADCSDV
ADGRP
 
 
CA Dataquery
 
 
 
Version 15.1 Copybook for CICS Table Assemblies
 
 
Version 15.1 Copybook for CICS RDO
 
 
CICS CSD Group Name
 
 
DQCSD
DQGRP
 
DQCSDV
DQGRP
For information about the required DCT and PLT entries and copybooks, see the 
CA Datacom®
 CICS Services System documentation and the 
CA Datacom®
 VSAM Transparency System documentation.
Double-Byte Character Set and Katakana Character Support
To use the double-byte character set or the Katakana, change the 
CA Datacom® CICS Services
 control files from what is delivered for 
CA Datacom® Datadictionary™
 online (DDOL) and 
CA Dataquery
 (DQRY). The PROFILEs for DDOL, DQRY, and SCFD (for CA IPC) must have UCTRAN=NO. For each terminal type (TYPETERM) used on 
CA Datacom® CICS Services
, the value of UCTRAN must be TRANID instead of NO.
For 
CA Datacom® Datadictionary™
 online, change both the profile for the DDOL transaction and the profile for the SCFD transaction which is part of CA IPC. For 
CA Dataquery
 only, change the profile for the transaction DQRY.
Online Product Verification
 
 
CA Datacom® Datadictionary™
 
 
To verify the 
CA Datacom® Datadictionary™
 installation online, see Using the Online Facilities.
 
 
CA Dataquery
 
 
To verify the 
CA Dataquery
 installation online, see Signing On and Off .
Checking the README File
Review the README file to confirm if any additional tasks are required after the installation, upgrade, or maintenance procedure. For more information, see README File.
Planning for Initial MUF Roll Out
The installation and upgrade process is designed to simplify those processes during the implementation of your upgrade or new installation. 
Broadcom
 delivers a DBSYSID macro (which is used to assemble a DBSIDPR module) used only for the installations and upgrades. That is, the delivered DBSYSID is not meant to be used after the upgrade or new install process is completed. You are expected to customize the DBSYSID macro to meet your needs for each MUF after installing or upgrading. To support this rollout of the MUF, review the 
CA Datacom®/DB
 documentation in the following key areas. Plan ahead by listing the specifications that you need to make or change for your site.
  • DBSYSID macro
  • MUF startup options
  • Simplify feature
 Before the MUF is rolled out to your first environment, when making your changes in the key areas just listed we recommend reducing the risk of an outage by first using a test environment to verify the new specifications work as intended.
 We recommend that you customize the DBSYSID macro before you roll out 
CA Datacom®
 Version 15.1 to any of your environments. Your first rollout takes more time because of this initial recommended review. However, choices that are made during this process can be used for future rollouts to other MUFs in your environment.
Customizing the DBSYSID Macro
Review the 
CA Datacom®/DB
 documentation to learn about the features and options of the DBSYSID macro. Modify the existing DBSIDPR member in the CUSMAC PDS to fit your needs for the rollout of your first MUF. Your customized DBSIDPR is your model for other MUFs that are upgraded later if you have more than one MUF in your environment.
MUF Startup Options
Review the 
CA Datacom®/DB
 documentation for any enhancements or modifications that need to be made to the DBDATIN2 member in the CUSMAC for this MUF. Your customized DBDATIN2 is your model for other MUFs that are upgraded later if you have more than one MUF in your environment.
Initial MUF Rollout Using Simplify
 With the Simplify feature, the new install process builds and makes certain assumptions to be true, taking advantage of all the protections offered by Simplify. Depending on the special needs of your environment, Simplify can provide the protection that you want.
 The CXX name and MUF name have to be unique to use this feature.
Tailoring the 
CA Datacom®
 Products
After demonstrating successful installation of the products, tailor them according to your site requirements before designating them as production systems. Be sure to back up the data sets before starting the tailoring process. For instructions about tailoring individual products, see the appropriate documentation.
 
Defaults
 
Defaults were established during the installation process. Consider these defaults as you determine the tailoring necessary for your site.
 The following tables in this section describe each job that can be found on support.ca.com in the Sample download page. For more information about accessing this site, see How to Obtain the Sample Members.
 
 
CA Datacom®/DB
 Samples
 
 
Job
 
 
Description
 
DBSAM01
Assemble and link sample online User Requirements Table for DBID 001.
DBSAM02
Assemble and link sample batch User Requirements Table for DBID 010.
DBSAM03
Assemble and link the sample Master List.
DBSAM04
Assemble and link the sample DB system ID module (DBSIDPR).
DBSAM05
Assemble and link the sample SQL batch User Requirements Table.
DBSAM06
Assemble and link the sample SQL online User Requirements Table.
DBSAM07
Assemble and link for DL/I access support in 
CA Datacom®/DB
 Reporting Facility.
 
 
CA Datacom® Datadictionary™
 Samples
 
 
Job
 
 
Description
 
DDSAM01
Assemble and link the DDSRTLM module.
DDSAM02
Assemble and link 
CA Datacom® Datadictionary™
 User Requirements Table modules.
DDSAM03
Assemble and link VPE online file table.
DDSAM04
Assemble and link VPE batch file table.
DDSAM05
Assemble and link the SC00TRAN module for 
CA Datacom® Datadictionary™
 online.
DDSAM06
Assemble and link the block data utilities (DDBDULM AND DDDDULM).
DDSAM07
Assemble and link the Log Area (LXX) trace VPE file table.
DDSAM08
Execute DDCFBLD followed by DBUTLTY to post the PRODuction version of the DATA-DICT database to the CXX.
DDSAM09
Execute DDCFBLD followed by DBUTLTY to post the PRODuction version of the DDD database to the CXX.
DDSAM10
Link for CA Librarian access support in DDICF.
 
 
CA Dataquery
 Samples
 
 
Job
 
 
Description
 
DQSAM01
Assemble and link DQEIBPR for CA-Email access support in 
CA Dataquery
.
DQSAM02
Assemble and link the VPEDQRFT module for using 
CA Dataquery
 in TSO.
DQSAM03
Assemble and link the DQSYSTBL module.
DQSAM04
Execute the DQLIBRMT Utility.
DQSAM05
Execute the DQWFINIT Utility.
DQSAM06
Execute the DQLANGMT Utility.
DQSAM07
Execute the DQCRRPT Utility.
DQSAM08
Execute the DQUSERMT Utility.
DQSAM09
Execute the DQPANPRT Utility.
DQSAM10
Assemble and link 
CA Dataquery
 User Requirements Table.
DQSAM11
Assemble and link DQDECPR module for 
CA Datacom® CICS Services
.
 
Maintaining the 
CA Datacom®
 Products
If CSM is used to apply maintenance to your products see “Maintain the Installed Products” in the chapter on Install Your Product Using CA CSM. This method is recommended for applying maintenance.
If you intend to install maintenance using SMPE directly, see “Apply Preventative Maintenance” in the chapter on Install Your Product Using Pax ESD.
Activating 
CA Datacom®
 for CA Auditor z/OS Support
For 
CA Datacom®
 to be fully auditable by CA Auditor, it is necessary to have a specific load module available in the LPA. The CAIXCTT$ module is provided in the CABDLPA library for this purpose. If you are using the 
CA Datacom®
 CAIXCTT$ module, it must reside in the currently active LPA. You can do this in one of two ways:
  1. APF authorize the CABDLPA library and add it to the LPA.
  2. Copy the CAIXCTT$ module into an APF Authorized library already in the LPA.
See the CA Auditor documentation for more information about using the product.