Install and Maintain z/OS

This section describes how to acquire, install, deploy and configure CA IDMS to make it available to the staff who implement and use the product.
This section describes how to acquire, install, deploy and configure CA IDMS to make it available to the staff who implement and use the product.
Audience
There are multiple steps in the CA IDMS installation process, and some steps can be performed in multiple ways. Different steps may be performed by different people, depending on access authority, skill set, site policies, etc. This section is for people taking part in the installation of CA IDMS. The following installation breakdown is intended to aid you in identifying the people required and coordinating their efforts.
Configuration (creating customized loadlibs and creating or updating database files) should be done by the CA IDMS DBA. The DBA may need to work with the following personnel:
  • Systems programmer, for VTAM definitions, SVC selection, CV key, LMP keys, library names.
  • Storage administrator, for DASD allocations.
  • CICS administrator, for CWA displacement, CICS library names.
Methodologies
There are several methods you can use to acquire your software, set up your SMP/E environment, apply maintenance, and configure your software after installation is complete.
Acquisition Methods
Use one of the following methods to acquire (download) CA IDMS:
  • CA CSM
    CA Chorus Software Manager (CA CSM) standardizes the installation process for CA mainframe products. To acquire your product using CA CSM, you must have CA CSM installed. A Broadcom Support account is required.
  • SMP/E JCL
    With this option, you acquire a product pax file and the latest product updates from Broadcom Support and then install, maintain, deploy, and configure the products on your systems. Batch jobs are provided to create the SMP/E environment. A basic understanding of UNIX System Services (USS) is required.
  • Tape
    This acquisition method is not encouraged, but is still available for sites where security rules disallow acquiring files from the internet.
SMP/E Environment Create Methods
Use one of the following methods to create your SMP/E environment:
  • CA CSM
    Using CA CSM to create your SMP/E environment requires no SMP/E knowledge, and there is no JCL to customize or submit. However, the authority to execute the SMP/E program, GIMSMP, is required. You can set up your SMP/E environment using CA CSM after acquiring your software using CA CSM or by Pax-Enhanced ESD. You cannot use CA CSM if you acquired your software from tape. If acquisition is by PAX, execute the CA CSM dialog, Insert New Product, before using CA CSM to create the SMP/E environment.
  • Manual
    The SMP/E environment can be created manually (JCL in SAMPJCL) following ESD or tape acquisition. It requires customizing an edit macro and making the edit macro available to a TSO session.
As a result of either method, the same SMP/E environment containing the same uncustomized software is set up at every site.
Maintenance Application Methods
Use one of the following methods to apply any available maintenance to CA IDMS:
Note:
Applying maintenance should be done before performing deployment.
  • CA CSM
    Using CA CSM standardizes the application of maintenance for CA mainframe products. Minimal SMP/E vocabulary is required. To acquire your product using CA CSM, you must have CA CSM installed. If you created the SMP/E environment manually, run the CA CSM Import CSI dialog before installing maintenance.
  • Manual
    There is JCL to install maintenance in the same SAMPJCL library containing the jobs to create the SMP/E environment. You must be able to download PTFS and HOLDDATA from Broadcom Support.
Deployment Methods
Deploying CA IDMS can be done with CA CSM and requires that CA CSM be installed at your site. Deployment copies the SMP/E target libraries (or a subset of them) to a different system or location. Performing deployment using CA CSM is a prerequisite to performing configuration using CA CSM. Otherwise deployment is optional.
Note:
SMP/E does not update the deployed libraries. If you have performed deployment, perform the deployment again after you install maintenance to update your deployed libraries.