Installation Considerations

This article identifies some items to consider and best practices to follow as you install your product. Reschedule.
This article identifies some items to consider and best practices to follow as you install your product. Reschedule.
If you are upgrading from an earlier release, we recommend that you completely replace the previous product. However, retain your ALIB files and any JCL that you converted for batch link.
Concurrent Releases
You can install this release of your product and can continue to use an older release in another SMP/E environment. If you plan to continue to run a previous release, consider the following points:
  • If you run Version 9.1 of the product and CAVHINIT initialized the product with a higher release, Batch link is not able to select the job from the queue for debugging.
  • When you install the product into an existing SMP/E environment, this installation deletes previous releases in that environment.
  • If you acquired your product with Pax ESD, select different target and distribution zones for your new release from where your current release is installed. The new zones use different libraries than your current release.
    CA Chorus Software Manager installs a product into a new SMP/E environment by default. You can select an existing SMP/E environment from your working set. For more information, see the online help that is included in CA CSM.
  • Define DDDEF entries in your new zones to point SMP/E to the proper libraries for installation. Ensure that they point to the new release libraries.
If you execute the application from LINKLIST, review your LINKLIST to ensure that the most recent version of your Common Symbolic Component executables (defined to the Common Symbolic Component FMID) are highest in the concatenation.
Installing an Individual Product
The following table lists each of the FMIDs that are shipped on the pax file and indicates which FMIDs for all 4 products are installed. Please use the following table if you would like to install a subset of the 4 products.
CA InterTest Batch
CA InterTest for CICS
CA SymDump Batch
CA SymDump for CICS
Common Symbolic Component
Common Eclipse UI Component
Common CICS Component
Common CICS DB2 Component
CA InterTest Batch Component
CA InterTest for CICS Component
CA SymDump Batch Component
CA SymDump Batch DB2 Component
CA SymDump for CICS Component 
Example: Installation of CA Intertest Batch and CA SymDump Batch
If you would like to only install CA InterTest Batch and CA SymDump Batch, you would install the following FMIDs:
  • CAVHB00– Common Symbolic Component
  • CAVHB01– Common Eclipse UI Component (optional)
  • CAMRB00– CA Intertest Batch Component
  • CARXB00–CA SymDump Batch Component
  • CARXB01–CA SymDump Batch DB2 Component (optional)
Symbolic Files
Symbolic files from previous releases are upward compatible with the current product release.
CICS Products
  • For detailed instructions on setting up your CA InterTest for CICS to support MRO, see Special Considerations for MRO Support.
  • If you require CA InterTest for CICS to support database system calls other than IBM's DB2 and DL/I, or CA IDMS and Datacom, or calls to software that should not be monitored by CA InterTest for CICS, see Calls to Software and User Macro Support.
  • If you plan to debug Hogan programs with CA InterTest for CICS, see CICS Interfaces and Compatibilities.
  • To use CA InterTest for CICS with IBM's Omegamon product, start Omegamon before you start CA InterTest for CICS and exclude the CA InterTest transactions from the Omegamon Resource Limit (Time Out) Specification.
  • To use CA InterTest for CICS with ASG's TMON product, exclude transactions from the TMON Resource Limit (Time Out) Specification.
Batch Products
  • If you use CA File Master Plus and you want to use the CA SymDump Batch FM viewer command, perform the following additional steps:
    • Set up the CA File Master Plus to use LIBDEFs (LIBALLOC='Y').
    • Ensure that the FM1 exec exists in a data set allocated to SYSPROC or SYSEXEC.
    • Allocate CAI.CAVHCLS0 to SYSPROC or SYSEXEC.
  • If you are using Compuware's AbendAid and CA SymDump Batch on the same LPAR, execute CAIRIM after AbendAid's initialization procedure. Also set the DUMP option to ON in the default options member CAOETABL.
  • If you are using Macro4 DumpMaster and CA SymDump Batch on the same LPAR, call the DumpMaster support group for the required PTF that lets DumpMaster pass control to other dump formatting products. If you initialize DumpMaster before executing CAIRIM to initialize your product, set the DUMP option to ON in the default options member CAOETABL.
Installation Best Practices
Use CA Chorus Software Manager for Installation
Use CA CSM to acquire, install, deploy, and maintain your product. Although CA CSM is the preferred method for installing CA Technologies mainframe products, some sites may decide to use the Electronic Software Delivery (ESD) installation method instead.
Business Value:
CA CSM provides a web interface, which works with ESD and standardized installation, to provide a common way to manage CA Technologies mainframe products. You can use it to download, install, and deploy your product.
CA CSM lets you download product and maintenance releases over the Internet directly to your system from the
Broadcom Support
website. After you use CA CSM to download your product or maintenance, you use the same interface to install the downloaded software packages using SMP/E. After installation, deployments allow system objects to be deployed across your enterprise's different environments.
Use Electronic Software Delivery
Although CA CSM is the preferred method for installing your CA Technologies mainframe products, some sites may decide to use the Electronic Software Delivery (ESD) method instead. For sites who have decided to use ESD, download the installation files from Broadcom Support and install directly from your disk.
Business Value:
Using electronic software delivery (ESD) avoids ordering, shipping, and processing physical tape media to install the application. It is more timely, more cost-effective, and environmentally friendly. It uses standard z/OS utilities to prepare the product installation image on your system.
For information about how to download your CA Technologies products from the
Broadcom Support
Online web site for installation using the enhanced ESD pax process, see Installing
No IBM APARs are required at this time.
Business Value:
There are no known IBM APARs that impact the operation or performance of the product. You may apply the most recent IBM APARs appropriate for your environment as needed.
Installation in a Test Environment
Perform your installation and initial evaluations of a new release of the product and its components on a test system.
Business Value:
New releases of CA Technologies testing tools can always co-exist with previous releases, letting you test a new release on a test system while still running the older version on a production system. Evaluating the product in a test environment lets you detect any possible problems before you roll out the product to a production system.
Additional Considerations:
Always be sure to review any migration considerations in Installing before upgrading your CA Technologies product.
Common Symbolic Component
When installing more than one of the CA Technologies mainframe testing tools, we recommend that you install and maintain only one version of CA Technologies common symbolic component that is shared by all of the testing tool products.
Several testing tool products (CA InterTest Batch, CA InterTest for CICS, CA SymDump for CICS, CA SymDump Batch, CA Optimizer/II, and CA Mainframe Application Tuner) each distribute the common symbolic component in the VH FMID. This FMID was named CVHrr00 in versions before Version 10 and is now named CAVHrr0. The
portion of the FMID contains the version number.
When installing any of these CA Technologies testing tool products, first query your Consolidated Software Inventory (CSI) to determine whether you already have a version of CVHrr00 or CAVHrr0 installed. If you use one CSI for all of your testing tool products then you need to perform only one query for these FMIDs. If you have one CSI for each testing tool product then you will need to query each CSI.
If you locate an installed version of CVHrr00 or CAVHrr0 during your query, compare the rr in your installed version of that FMID with the
in the FMID provided with the product you are installing. Replace your existing FMID only if the
in the product you are installing is higher than the
in your existing function.
Business Value:
By installing and maintaining a single version of the CA Technologies common symbolic component, you reduce your maintenance effort, save disk space, and eliminate the possibility of executing symbolic utilities that are not up to date with the latest maintenance.
Additional Considerations:
The APPLY job of the installation places an SMP/E copy of the CAVH
0 function in a library; however, many companies do not execute the testing tool products from this library. Therefore, always be sure to make the executables for the common symbolic component available for the testing tools products to use.
There are many ways to make the executables for the common symbolic component available, including:
    Always update your LNKLIST library after applying maintenance to CAVH
    0 if you have copied the executables for the common symbolic component from CAVH
    0 into a separate load library that you have added to your LNKLIST for all products to share.
  • CLISTs (for ISPF interfaces)
We recommend using the LNKLIST method because it has the specific advantage of making the executables available to all CA Technologies products with no additional changes to any JCL or CLISTs. If you cannot use LNKLIST for some reason (for example, your company has issues with updating LNKLIST or has specific rules prohibiting or limiting the use of LNKLIST), it is acceptable to add these executables to your STEPLIB or CLIST allocations. However, using STEPLIB or CLIST requires more initial setup and can be difficult to maintain if library names change.
CA InterTest Batch JCLCheck Function CAZ2C00
CA InterTest Batch uses the CA JCLCheck Common Component Function CAZ2C00 to provide a certain functionality which is outlined below. If you are already licensed for the full CA JCLCheck product on the CPU where you are installing your product, do not install function CAZ2C00 containing the CA JCLCheck common component.  
If you are not licensed for the full CA JCLCHECK product, install function CAZ2C00. The CAZ2C00 function is a separate Pax file installation. This Pax file is included and available for download along with the CA InterTest™ and CA SymDump® 11.0 product package For more information, refer to the installation documentation for CA JCLCHECK Common Component.
Business Value:
The CA JCLCHECK Common Component installation package includes the materials necessary to install the CA JCLCheck common component function CAZ2C00. However if you have already licensed and installed the CA JCLCheck product, you can save installation time, maintenance effort, and disk space by using your existing version instead.
Additional Considerations:
This common component is used to create ALIB members from your JCL for online allocations and to prepare JCL for use with the Batch Link facility. For the Batch Link facility, this JCL conversion is a convenience rather than a requirement, since JCL can be easily prepared manually for use with the Batch Link facility as described in Batch Debugging.
When converting a PROC needed for use with DB2-stored procedures, a manual conversion is required and the JCL conversion feature is not used.
If you do not already have function CAZ2C00 installed on the same CPU, you must install it so you can convert JCL with your product. The materials needed to install that function have been provided as part of the CA JCLCHECK Common Component installation package.
If you decide to install a second copy of function CAZ2C00 on the same CPU, be sure to maintain both copies when applying maintenance. Solutions required for this function will be provided to the application and CA JCLCheck customers. As a result of this condition you may have two different releases of function CAZ2C00 installed, one with the CA JCLCheck product and the other with the CA InterTest Batch product. This is acceptable and fully supported provided that the version used with your product meets the minimum release number requirements as described in