Execute DB2 Catalog Customization Tasks

Execute the Db2 catalog customization tasks on each Db2 subsystem where the CA Database Management Solutions for Db2 for z/OS are installed after you have executed the product-specific customization tasks.
Execute the Db2 catalog customization tasks on
Db2 subsystem where the
CA Database Management Solutions for DB2 for z/OS
are installed after you have executed the product-specific customization tasks.
Db2 catalog customization tasks can be executed only for subsystems on supported Db2 versions.
These customization tasks require and interact with the Db2 subsystems that you identified in the SETUP global parmlib members. Db2 SYSADM authority is required.
Review the instructions for each Db2 catalog customization task before execution. In some instances, it might not be necessary to execute a task, especially when you are applying maintenance.
We recommend that you have at least two people available to execute the Db2 tasks. If a problem is encountered on one subsystem during execution, the second installer can submit and verify the Db2 tasks while the other installer tracks down problems and performs subsystem checkout.
To prevent contention errors like MIM1099, only one user at a time can access the Executing Db2 Tasks online dialog for a specific environment.
Follow these steps:
  1. Access the Post-Install Tailoring menu.
  2. Select option
    (Tasks - Execute Db2 catalog customization tasks) and press Enter.
    A list of defined Db2 subsystems appears on the Select DB2 Subsystems panel.
  3. Select one or more Db2 subsystems and press Enter. (Select all subsystems using the ALLS command. Reorder rows using the SORT SSID (by DB2 subsystem) or SORT SETUP commands.)
    Execute the Db2 tasks on each of the listed subsystems.
    A list of DB2 tasks that must be performed for the selected subsystems is displayed on the Select DB2 Tasks panel.
    Install and general (INS and GEN) tasks for all products appear first:
    • INS Start Xmanager
    • INS Determine Db2 object sizes (Recommended)
    • INS Compare Db2 Objects
    • INS Create Required Db2 Objects
    • INS Create Catalog Indexes (Optional)
    • INS Bind Product Packages and Plans
    • INS Copy Plan Authorizations
    • INS Free Obsolete Packages and Plans
    • GEN Grant Public Access to Global Defaults
    • GEN Grant Public Access to General Services Plan
    • GEN Grant Public Access to Object List Manager Plan
    • GEN Grant Xmanager Execute for UPM Functions
    The product-specific tasks follow, shown here in alphabetical order by product name:
    • CA Database Analyzer: PDA Database Analyzer - Install/Upgrade Customization
    • CA Plan Analyzer:
      • PPA Plan Analyzer - Install/Upgrade Customization
      • PPA Plan Analyzer Stored Procedure Installation
    • CA RC/Migrator:
      • RCM Load and Customize the Model Services Table
      • RCM Load the Automapping Mask Services Table
      • RCM Load the Rule Set Table
      • RCM Install RCM SQL Stored Procedure Processor
    • CA RC/Query: RCQ Initialize the RC/Query Report Table
    • CA RC/Secure: RCS Initialize the RC/Secure Department Definition Table
    • CA Recovery Analyzer:
      • PRA Define PRA Table Backup GDG Datasets
      • Setup PRA#LOAD Batch JCL
      • Load Disaster Recovery Backup Types Table
    • CA Report Facility and CA Compile/PRF:
      • PRF Table Initialization Utility (PRFINIT/PRFX)
      • PRF Table Conversion Utility (PRFCNVRT)
      • QRF Compile/PRF Table Conversion Utility
    • CA SYSVIEW for DB2: IDB2 CA Sysview for DB2: DB2 Specific Install Task
  4. Review the instructions for each Db2 task using the V line command or ALLV command. The instructions describe when to execute the task and provide other useful information.
  5. Select a task or multiple tasks and press Enter.
    The JCL for each DB2 task is generated in a member that is named with the subsystem ID and a task number.
    • If you selected multiple subsystems, the task appears for each subsystem selected.
    • If additional information is needed to create the JCL for the task, you are prompted to provide this information before the JCL is submitted.
    You can change the member names if needed; however, if you are performing a distributed installation, retain the numerical order of the suffixes to ensure proper job submission order at the remote site.
    To prevent the member names from being overwritten when a subsystem name is used on multiple systems and you are using the same output data set, we recommend that you copy the members or target a different output data set before generating new jobs.
  6. Submit the generated JCL for execution.
    You can browse and edit the generated JCL before submission.
    The member name where the job is stored in the
    .CDBASAMP library appears in the Member field for the currently selected DB2 subsystem. If the job has been generated for more than one subsystem, MULTIPLE appears instead. If more that one subsystem has been selected but a job has been generated only for one of of the selected SSIDs, a plus sign displays after the member name to indicate this. N/A appears if the task is informational and does not generate a JCL member.