Installing

Includes steps to acquire, install, deploy and configure your product.
dm19
The 
CA Database Management Solutions for DB2 for z/OS
 installation process is typically performed by the systems programmer or database administrator who is responsible for installing products on your mainframe systems. You might also work with a storage administrator for DASD allocations and a security administrator for access to installation data sets and other security requirements.
Knowledge in JCL, TSO/ISPF, and DB2 for z/OS is assumed. An understanding of your z/OS environment and the IT environment, enterprise structure, and region structure at your site is also assumed.
The installation process performs an SMP/E installation and consists of the following major steps:
  1. Prepare for installation by reviewing best practices and confirming that the installation requirements (like software, hardware, security) have been met.
  2. Install the products using the CA Chorus™ Software Manager (CA CSM) web-based interface or Install Products Using Batch Jobs (Pax-ESD). This step creates the SMP/E environment and runs the RECEIVE, APPLY, and ACCEPT steps.
    An FMID list for the products and components is provided
  3. Configure the products. This step involves completing the following tasks to customize the SMP/E environment (SMP/E data sets, target libraries, and distribution libraries) and create the product runtime environment (configured product instance):
    1. Define session and environmental options (job cards, installation libraries, and data set allocation parameters).
    2. Create and edit parmlib members (global and product-specific).
    3. Execute product-specific customization (backup and recovery, general facilities, database administration, performance management, report facility, utilities, and value pack).
    4. Execute DB2 catalog customization tasks.
  4. Start the products by preparing the product CLIST for execution.
  5. Define user privileges for the products, log tables, and DB2 system catalog tables.
     For more information about defining user privileges and product-specific authorizations, see Required User Authorizations and Using the Product Authorizations Facility.
See Select an Installation Use Case review the most common installation scenarios: