Preparing for Installation › Configure CA Insight DPM for Use with CA Cross-Enterprise APM › CA Insight Customization

CA Insight Customization

If you are installing CA Insight, review the product customization member and execute the following customization tasks:

• Specify CA Insight customization parameters in the installation JCL (IDB2SYS), and submit for execution. Output from this step includes:
  • JCL to run the program call (PC) task as a batch job or started task
  • New SOURCE library containing common customized members
  • The user interface profile data set
  • Common exception definition data
  • Customized SOURCE members to set up and run the VTAM user interface
  • Customized CLIST members for executing CA Insight tasks
  • Default SECURITY profile data set

  Note: When migrating from a previous release, you are prompted for information from the previous release so that the information can be migrated.

  Note: The post installation processing does not describe the installation of GSS or the archive tables. For more information about completing these tasks after the IDB2SYS member is created, see the CA Insight System Reference Guide.

• Execute the CA Insight DB2-specific installation task.

  The task customizes a data collector for the DB2 subsystem. Each DB2 subsystem has one data collector task.

• Review the CA Insight System Reference Guide for more information about:
  • Product authorization
  • Installing components as started tasks
  • Scheduling high-level and detailed DB2 reports using system management facility (SMF) data
  • Managing data collector DASD output
  • Implementing the CICS monitoring facility
  • Implementing data sharing
  • Using the data collector (online and batch)
  • Operating the program call (PC) owner
  • Installing optional components:
    • Global Subsystem (GSS)
    • VTAM User Interface
    • Remote Access Facility (RAF)
    • NATURAL for DB2 Support
    • System Condition Monitor (SCM)
    • Shadow catalog tables for EXPLAIN
  • Controlling CA Insight commands, DB2 IFCIDs, and data through the CA Insight security
  • Using online history
  • Archiving DB2 performance data
  • Integrating with CA NSM Database Option
  • Starting program call (PC) owner tasks per z/OS image.
• Review the CA Database Management Solutions for DB2 for z/OS Best Practices Guide for more information about:
  • Starting data collector and PC tasks automatically at IPL.
  • Assigning appropriate authorizations for the user ID associated with the data collector task.
  • Setting the dispatching priority to avoid lost trace data.
  • Creating an OBID table translation file.
  • Allocating adequate trace collection buffer space.
  • Using one exception data set for all data collector tasks.
  • Enabling the data sharing option for data collectors
  • Adjusting the default REGION parameter value
• Review the migration considerations.

We highly recommend that you read the CA Insight installation and upgrade considerations, and known issues in the Release Notes for information you should know as you plan your installation.

If you install the online history component, you should only change the primary allocation as needed when allocating the online history files. The maximum data set size supported by data-in-virtual (DIV) data sets is 4 GB or approximately 5825 cylinders.

Secondary extents should not be specified as the data set initialization routine will keep extending the data set until space allocations fails. If you are allocating the data set using an SMS class that supports extended addressability (EA), ensure the allocation attributes will honor the primary allocation with no secondary extents. Otherwise, unused space may be allocated and wasted.

Note: For more information about estimating space calculations, see the CA Insight System Reference Guide.