Deploying transaction group definitions to CICSPlex SM

After you build a CICSPlex® SM Workload Manager (WLM) transaction group file that contains affinity-transaction-group definitions that are suitable for input to CICSPlex SM, you can deploy the transaction group definitions to a CICSplex.

Before you begin

You need a CICSPlex SM WLM transaction group file. See Building a CICSPlex SM Workload Manager transaction group file.

You must have a z/OS® connection to your z/OS system. See Configuring a z/OS FTP system connection.

About this task

To set the default values to use to generate JCL for deployment to CICSPlex SM, you use the CPSM Deployment pane in the Preferences window.

To specify parameters for the CICSPlex SM deployment job, modify the input to CICSPlex SM, review the generated JCL, and deploy the transaction group definitions, you use the Affinity Build view.

Procedure

  1. Set the default values to use to generate JCL for deployment to CICSPlex SM:
    1. From the workbench menu, click Window > Preferences, expand CICS Interdependency Analyzer, then click CPSM Deployment.
    2. Optional: Edit the job card to meet the requirements of your own system.
    3. In the Load Library field, enter the load library for the CICSPlex SM data set.
    4. In the Auth Library field, enter the authorized load library for the CICSPlex SM data set.
    5. Click OK.
  2. Specify parameters for the CICSPlex SM deployment job:
    1. Open the required CICSPlex SM WLM transaction group file in the Affinity Build view. From the Report Explorer view, either double-click the CICSPlex SM WLM transaction group file name, or right-click the file name then click Open report.
    2. Click the CPSM Input tab.
    3. Enter the following information in the Deployment Parameters section:
      Data Set
      The data set to store the transaction group definitions. If you have a z/OS connection to your z/OS system, you can use the Open data set Open data set icon or Create data set Create data set icon icons to select or create a data set, respectively.
      Member
      The data set member to store the transaction group definitions.
      CMAS Name
      The name of the CMAS for the CICSplex to which you are deploying. Deployment updates the data repository for this CMAS.
      Output user name
      A 1- to 8-character user identifier to associate with the output from the deployment.
      Print Node
      A 1- to 8-character print node identifier to route the output from the deployment.
  3. Optional: Use the CPSM Definitions section of the CPSM Input tab to modify the input to CICSPlex SM:
    • To include or exclude specific objects from input to CICSPlex SM, select or clear the relevant check boxes.
    • To change the Affinity, Lifetime, State, or Match parameters for the TRANGRP resource, right-click on the CREATE TRANGRP NAME statement, then use the relevant menu options. For example, to change the Affinity parameter, click Set Affinity, then click the required value on the menu.
    • To change the Context, the Trangroup name, or the Transaction name, right-click on the name, then click Set Name. Type the new name in the resulting dialog, then click OK.
  4. Optional: If you want to check the transaction group definitions before you deploy them, select Check. A CHECK statement is added to the generated JCL on the Deployment JCL tab.
  5. Click the Deployment JCL tab and review the generated JCL.

    The JCL job to deploy the transaction group definitions to the specified CMAS is displayed in a JCL editor. The generated JCL uses the default values and deployment parameters that you specified earlier. You can use the facilities of the JCL editor to view and edit this JCL. Any change to a deployment parameter in the JCL that is on the CPSM Input tab is updated in the corresponding field on the CPSM Input tab. Similarly, any change to a deployment parameter on the CPSM Input tab is updated in the corresponding JCL on the Deployment JCL tab.

  6. Optional: To check the transaction group definitions, ensure that the deployment JCL includes the CHECK statement, then click the Deploy to CPSM icon Deploy to CPSM in the toolbar of the tab. Use any error messages to correct the JCL. When you are ready to deploy the JCL, edit the JCL or use the Execute option on the CPSM Input tab to change the CHECK statement to an EXECUTE statement.
  7. When the JCL job is complete, ensure that the deployment JCL includes the EXECUTE statement, then click the Deploy to CPSM icon Deploy to CPSM in the toolbar of the tab. The transaction group definitions in the CICSPlex SM WLM transaction group are saved to the specified data set member, and a job for deployment to CICSPlex SM is submitted. Deployment uses the facilities of z/OS Explorer.