Install Product Software Using z/OSMF Deployments

As a systems programmer, your responsibilities include installing product software in your z/OS environment. After the portable software instance or software instance is registered in z/OSMF, you can use z/OSMF Deployments to install the product software and create the product data sets (global, CSI, target libraries, and distribution libraries) for the new software instance. The deployment jobs create a copy of the source product data sets to create the product target runtime environment. Creating a copy of the SMP/E target data sets keeps the SMP/E environment clean and it also isolates the product runtime environment for maintenance activities. You can also perform z/OSMF workflows to customize the SMP/E data sets, mount UNIX System Services (USS) files if required, and configure the new software instance on the target system.
To install Broadcom mainframe products using z/OSMF and make the product software available for use on a system by users and other programs, define a new deployment. This step defines the SMP/E environment name and the prefix of the CSI data set in z/OSMF. You also specify data set allocation parameters for all SMP/E data sets, target libraries, and distribution libraries. To define a new deployment, complete the deployment checklist (specify the USS path, DSN, VOLSERs), and submit the deployment jobs through the z/OSMF user interface. When the deployment is complete, you have a source and target copy of the software.
For more information about these tasks, see Deploying software in the IBM Knowledge Center.
Subsequent maintenance activities for the product updates the SMP/E environment without affecting your active product runtime environments. You decide when to redeploy the maintenance-updated SMP/E target data sets to each of the product runtime environments.
Before you begin this process, we recommend that you review the installation best practices and verify that the installation requirements in Prepare for Installation.
The installer requires read, create, update, and execute privileges in z/OS. Write access is also required to the USS directories that are used for the installation process.
Follow these steps:
  1. Display the Deployments table in z/OSMF (
    Software Management, Deployments
    ).
  2. Define a new deployment by selecting
    New
    from the Actions menu.
    The deployment checklist displays. You can also modify, view, copy, cancel, or remove existing deployments.
  3. Complete the deployment checklist items as described in Defining new deployments in the IBM Knowledge Center.
    As you complete the deployment checklist, be sure to make the following selections:
    1. Specify the properties for this deployment (name, description, and optional category).
    2. Select the software to deploy.
      For this step, select the
      Portable Software Instance
      button and select your package.
    3. Select the objective for this deployment to indicate where and how you want to install the selected portable software instance.
      For this step, indicate that you want to create a new software instance and specify the global zone CSI and the system where the target software instance will reside.
    4. Check for missing SYSMODs and view missing SYSMOD reports.
      For this step, deselect the following report options:
      • Requisite SYSMODs and Fix Categories reports
      • Regressed SYSMODs and HOLDDATA Delta reports
    5. Configure this deployment to define the target software instance.
      • For
        DLIBs
        , specify
        Yes
        to copy the distribution zones and libraries that are associated with the source software. You can customize the names and the storage class or volumes of the new data sets.
      • For
        Model
        , indicate
        The source software
        to use as a model. z/OSMF uses the data sets, volumes, mount points, catalogs, and SMP/E zones that are associated with the model to specify default values for the target software instance.
      • For
        SMP/E Zones
        , the DLIB and TLIB names do not typically need to be changed.
      • For
        Data sets
        , change the target data set name prefix to the one that you want to use for your deployment. Specify a volume or storage class to identify where to create the target data sets.
      • For
        Catalogs
        , no action is required assuming that your target data set prefix is defined in a user catalog.
      • For
        Volumes and Storage Classes
        , no action is required. A summary is presented of the target data sets to be created and how much space is required.
    6. Define the job settings to generate JCL to install the software and view the deployment summary.
      For this step, update the JOB statement as needed.
    7. Submit the deployment jobs in sequential order, wait for each job to complete, and then select
      Refresh
      to register job completion in z/OSMF.
      A return code of zero is expected.
      When all deployment jobs have executed successfully, you have unzipped and renamed the product data sets, and updated the CSI data sets. The product data sets have also been successfully copied and the properties for the target software instance have been specified.
    8. Execute workflows if any exist for the software being deployed. Most products have at least
      one
      of the following workflows:
      • Post SMP/E Workflow
        Updates the CSI with site-specific external data sets, relinks load modules, and optionally mounts USS directories. CA IDMS requires that you execute the Post SMP/E Workflow first to complete the deployment. CA IDMS does not install a USS directory.
        If prompted for the data set name of a load library for an IBM product that you do not have installed, specify your installed CA Common Services for z/OS
        CCS_hlq
        .CAW0CALL data set name.
        The Post SMP/E Workflow is where you specify the load libraries to obtain interface modules to other products. CA IDMS supports interfaces to FCS (Financial Control System), RDMS Auditor, TOTAL, and IBM products. In the second step of the Post SMP/E Workflow, you can specify the names of the libraries where the interface modules can be obtained.
        • FCSLIB DSNAME
          Specify your FCS load library to link the Culprit interface to FCS.
        • RDMSLIB DSNAME
          Specify your RDMS Auditor load library to link the Culprit interface to RDMS Auditor.
        • TOTALLIB DSNAME
          Specify your TOTAL load library to link to Culprit interface to the TOTAL database.
        If you do not have any of these products, specify the CA Common Services for z/OS
        CCS_hlq.
        CAW0CALL data set for your environment.
        In addition, standard interface modules for IMS and CICS are obtained from the
        CCS_hlq
        .CAW0CALL data set. Your
        CCS_hlq
        .CAW0CALL data set should be specified for the RESLIB DSNAME and SDFHLOAD DSNAME fields in this step of the workflow.
      • Base Installation Workflow
        Configures a new software instance for your product software.
      • Upgrade Workflow
        Updates an existing software instance for your product to a new product release.
      • Add-On Product Installation Workflow
        Adds new CA IDMS product components to an existing configuration.
      For a list of products with workflows to complete post-install configuration, see Mainframe Products using z/OSMF in the Mainframe Common Maintenance Procedures documentation.
    9. Specify a name and description for the new target software instance.
The deployment process is complete. The new software instance is defined to z/OSMF. You are now ready to Import Product Information into z/OSMF before you install product maintenance.