Configuring Products Using CA CSM

INLINE
ce17
As a system programmer, your responsibilities include configuring products using CA Chorus™ Software Manager (
CA CSM
). A
configuration
is a
CA CSM
object that you create to tailor your installed software or
CA CSM
deployed software. Configuration makes your software usable in your environment. A configuration contains the profiles, variables, and resources specific to your environment.
Use this scenario to guide you through the process:
Configuring_products
Configuring_products
  1. Determine the source of your configuration based on your site environment:
    • If you configure a product from an SMP/E environment, you can only configure it on a staging system.
    • If you configure a product from a configurable
      CA CSM
      deployment, you can configure it on a staging system and a nonstaging system.
  2. Although validation is optional, we recommend that you validate the configuration before implementation.
  3. (Staging systems only) Activate the configuration.
The product configuration process completes.
Sometimes, there are other product-specific steps to perform manually outside of
CA CSM
. Perform any manual configuration steps now.
For more information about configuring products, see the
CA CSM
online help.
Create a Configuration
You can create a configuration for a product that is installed in an SMP/E environment, or a product from an existing configurable
CA CSM
deployment.
The configuration wizard consists of several steps that let you set up your configuration as you prepare to implement it. When you go through the wizard, you define a set of properties for your configuration. For example, you define the product that you want to configure and the system you are targeting for the configuration. Optionally, you can select to import product configuration settings and variable values from a previous configuration for the selected product.
Each product configuration includes various settings, such as:
  • The functions and options for the product
  • Settings and preferences that are associated with the specified target system
  • Resources for the product
    To avoid a conflict of resources between two or more configurations of a product, SCS manages the resources that are associated with previously defined configurations. To resolve any conflicting (not unique) resource in your configuration, perform one of the following actions:
    • Change the appropriate target setting to create a unique resource name.
    • Delete the older configuration containing the existing resource name and release the conflicting resource.
    If you import values from another configuration, you can optionally delete the configuration that you are importing the values from to avoid conflicts.
Follow these steps:
  1. From the Configurations tab, click Create Configuration from the Actions section.
    The configuration wizard opens to step 1.
    You can also start the configuration wizard from the following locations:
    • The SMP/E Environments tab - for a product in a particular SMP/E environment.
    • The Deployments tab - for a product from an existing configurable CA CSM deployment. Starting the configuration wizard from the Deployments tab opens it to step 2.
  2. Follow the instructions on the wizard to navigate through the wizard steps.
  3. When you are on the Review and Build step, review the configuration summary.
    You are ready to build the configuration.
    If you do not want to build configuration now, click Save to save the configuration and close the wizard. You can build it later.
Considerations when Configuring to a Staging System
Configuring a product that targets a staging system implies the DASD resources that are created as part of a product implementation will be local to the
CA CSM
driving system. The
CA CSM
driving system is the system where the
CA CSM
is running.
Configurations that you create for a staging system are implemented in the following phases:
  1. CA CSM
    creates and customizes the product run-time data sets on the
    CA CSM
    driving system.
    When a configuration targets a staging system, the configuration wizard provides a set of catalog preference variables as part of the target settings. You can choose whether the customized run-time data sets that are created in the first phase should be cataloged in the catalog that is associated with the
    CA CSM
    driving system. This setting is default.
    If you choose not to catalog the data sets to the
    CA CSM
    driving system catalog, you can optionally specify the name of a user catalog where the customized run-time data sets will be cataloged into. If you do not provide the user catalog name, the data sets will be uncataloged.
    The support for creating uncataloged run-time data sets assumes that the following statements are true:
    • The volume that is specified for the run-time data sets is not SMS-managed.
    • The rules that are established at your site allow the run-time data sets to be created as uncataloged data sets.
    When an optional user catalog name is specified, you can specify optional alternate, or indirect, system residence volumes (SYSRES). By default, no SYSRES preference is specified.
    • If no SYSRES preference is specified, the user catalog entries are created with the actual volume serial numbers of the run-time data sets.
    • If a SYSRES preference is specified, the user catalog entries are created with an indirect reference to a system residence volume (or its logical extensions). Specifying a SYSRES preference allows you to later change the volume serial numbers of the system residence volume (or its logical extensions) without having to recatalog the run-time data sets on those volumes.
    For more information about non-VSAM user catalog entries and indirect volume serial references, see the description of the DEFINE NONVSAM command in the IBM DFS
    MS Access Method Services for Catalogs
    (SC26-7394).
  2. You make the data sets accessible and activate the configuration.
    Systems that do not share DASD with the
    CA CSM
    driving system do not have access to the run-time data sets. For those systems, move the run-time data sets to DASD that is accessible to the remote system. For moving the data sets, select and use a method that is appropriate for your site and environment.
    CA CSM
    does not endorse a specific technique or provide support for transmitting the customized run-time data sets that are created when configuring a product to a staging system.
    After making the data sets accessible, activate the configuration.
Build the Configuration
You can build a previously saved configuration, or you can rebuild your configuration (for example, if there is a problem with the build).
You can only build configurations with a status of Under Construction (8) (resume the configuration first), or Build failed.
Follow these steps:
Perform one of the following actions:
  • If you are on the Review and Build step of the wizard, click Build.
  • If your configuration is saved in a step before the Review and Build step, resume the configuration from the Configurations tab. Then, follow the instructions on the wizard to navigate through the wizard steps. When you are on the Review and Build step, click Build.
  • If your configuration is in Build failed status, click the Actions drop-down list to the right of the configuration, and select Build.
    Optionally, you can edit the configuration before you build it again. Then, navigate to the Review and Build step of the wizard, and click Build.
A dialog that shows the progress of the task opens. When the task completes, you can click Show Results on the Progress tab to close this dialog. The task output browser opens and you can view the action details. Click Close to close the task output browser.
While a task is in progress, you can perform other work. You can click Hide to exit the dialog and view the task status later on the Tasks tab.
The configuration is built.
Built configurations are ready to be optionally validated or implemented. Before you start implementing a configuration, you can still edit the configuration.
You can build your configuration again later (for example, if there is a problem with the build).
Validate the Configuration
Before you implement a configuration, you can validate it. Validation verifies access to resources that are going to be utilized when you implement the configuration.
Although validation is optional, we recommend that you validate the configuration before implementation.
You can only validate configurations with a status of Build completed, Validated, Validation error, Implementation stopped, or Implementation error.
While validation of a configuration is in progress, do not use the configuration data sets that are outside of
CA CSM
. Doing so helps avoid data set contention between the
CA CSM
validate processing and data sets being accessed outside of
CA CSM
.
Follow these steps:
  1. Click the Configurations tab and locate the configuration that you want to validate.
  2. Click the Actions drop-down list to the right of the configuration, and select Validate.
    The validation dialog opens. This dialog contains status information and a table of numbered configuration steps.
    The validation process is started and continues until it has successfully completed or fails. The steps in this dialog automatically update as operation data changes.
  3. Review the operation steps. You can perform the following actions:
    • Click the link of a step name to display information about the actions that are associated with this step.
    • Click the icon in the Text column to see details about the processing that is associated with this step. If this step is manual, you can use this information to perform the step manually. Click Show Details to open a detailed summary for all steps in the configuration.
    • For the steps that have prerequisites, hold the mouse over the icon in the Prereq column to see details about the prerequisites.
    When the validation is completed, a message appears confirming that the validation succeeded or failed.
    While a validation is in progress, you can perform other work. You can click Hide to exit the dialog without stopping the validation process. Click the configuration status link to bring back the validation dialog while the validation is still in progress, or view the status of the validation task later from the Tasks tab.
    After the validation finishes and before you start implementing, you can still edit the configuration.
After a validation has finished successfully for a configuration on a staging system, you can review the activation instructions, if any. Click Activation Instructions from the validation dialog. Doing so opens the required steps that you will have to complete after you implement the configuration to activate this configuration.
Edit the Configuration
You can edit configurations that you have previously created and built. You can edit a configuration if the build fails, or when validation fails because of an errant value.
You can only edit configurations in a status of Build complete, Build failed, Validated, or Validation error.
You can only edit a configuration that has not started implementing yet. After a configuration has started implementing, you cannot edit it.
You can only edit one configuration at a time.
Follow these steps:
  1. Click the Configurations tab and locate the configuration that you want to edit.
    You can click the Status column to sort by status and identify all configurations that you can edit.
  2. Click the Actions drop-down list to the right of the configuration, and select Edit.
    The configuration wizard opens to step 4.
  3. Change data on this step as needed, and navigate and make edits to the remaining steps in the wizard.
Implement the Configuration
When you start the implementation,
CA CSM
evaluates the defined steps and determines what steps to execute. The selected steps are presented as a list. Release them so that they can be eligible to execute after their prerequisite steps have successfully completed.
Validation and implementation of a configuration may require exclusive access to data sets that the configuration specifies. Using data sets outside of
CA CSM
, such as ISPF edit and browse data sets, can introduce data set contention. Data set contention can result in validation and implementation errors. Therefore, while validation or implementation of a configuration is in progress, do not use the configuration data sets that are outside of
CA CSM
.
Implementation completes the configuration process for configurations on a nonstaging system. For configurations on staging systems, you may be required to perform extra steps to activate your configuration.
Implementation executes on the target system, applying the variables, resources, and operations that are defined in the configuration.
You can only implement configurations with a status of Build completed, Validated, Validation error, Implementation stopped, or Implementation error.
Follow these steps:
  1. Click the Configurations tab and locate the configuration that you want to implement.
  2. Click the Actions drop-down list to the right of the configuration, and select Implement.
    The implementation dialog opens. This dialog contains status information, and a table of numbered operation steps.
  3. Review the operation steps. You can perform the following actions:
    • Click the link of a step name to display information about the actions that are associated with this step.
    • Click the icon in the Text column to see details about the processing that is associated with this step. If this step is manual, you can use this information to perform the step manually.
    • For the steps that have prerequisites, hold the mouse over the icon in the Prereq column to see details about the prerequisites.
  4. (Optional) Select one or more steps and perform the following actions using the action links:
    • Set Automatic
      Changes the mode of the selected manual steps so that
      CA CSM
      automatically performs them as soon as they are released and all prerequisites are satisfied.
      You cannot change the mode of external steps.
      CA CSM
      cannot perform them automatically.
    • Set Manual
      Changes the mode of the selected automatic steps so that they become manual steps that you must perform outside of
      CA CSM
      .
    • Release
      Releases the selected steps. The steps become eligible for execution when all of their prerequisite steps are complete.
    • Bypass
      Skips the selected steps. These steps are not released when you click Release All. If the bypassed steps are prerequisites for other steps, the prerequisites are considered satisfied. The dependent steps are executed when they are released.
  5. For manual or external steps, click the Actions drop-down list to the right of a step, and select Confirm.
    The step is confirmed as completed successfully. Any prerequisites that other steps within the implementation define are satisfied.
  6. Perform one of the following actions:
    • Click Release All to release all steps at once and execute them. However, steps do not execute if they have prerequisite steps that have not completed. Perform and confirm manual and external steps.
    • Click Release Next to release and execute the next step in sequence. However, the step do not execute if it has prerequisite steps that have not completed. Continue to click Release Next for each subsequent step, and confirm manual and external steps.
    The implementation process is started and continues until it has successfully completed, is stopped manually, or fails. The steps in this dialog automatically update as operation data changes.
    While an implementation is in progress, you can perform other work. You can click Hide to exit the dialog without stopping the implementation process. Click the configuration status link to bring back the implementation dialog while the implementation is still in progress, or view the status of the implementation task later from the Tasks tab.
    You can click Stop to stop the implementation process. No non-executing steps will be started. You can start another run of the implementation from the Configurations tab by selecting the configuration and clicking Implement.
    When the implementation is completed, a message appears confirming that the implementation succeeded or failed.
  7. (For successful configurations on staging systems) Click Activation Instructions to open the required steps that you must complete next to activate this configuration.
If the configuration fails, address implementation failures.
View Step and Action Details
The validation and implementation dialogs contain links that let you drill down for more information about steps and actions that are associated with each step.
Follow these steps:
  1. On the Validate Configuration or Implement Configuration dialog, click the link for the step you want to view details for.
    An Actions dialog opens. The dialog contains the actions that are associated with this step as links if more information is available. This dialog contains the following columns:
    • Name
      Identifies the name of an action.
    • Type
      Identifies one of the following types for this action:
      • Action
        This is an actual action.
      • Backup
        This action performs a backup operation if the action is recoverable.
      • Commit
        This action makes the changes from previous actions permanent.
      • Rollback
        This action reverts the changes from previous actions.
    • Group
      Identifies one of the following groups that are associated with this action:
      • Operation action
        Describes the set of actions that perform the function of the operation.
      • Preop recovery
        Describes the set of actions to be performed before all other actions in the operation.
      • Postop recovery success
        Describes the set of actions to be performed if all actions complete successfully.
      • Postop recovery failure
        Describes the set of actions to be performed if any action completes unsuccessfully.
      • Cleanup
        Describes the set of actions to be performed after all other actions in the operation.
    • SRVC-CC
      Identifies the
      CA CSM
      services completion code for this action.
      This is an internal
      CA CSM
      completion code that is returned from the executed service in the SCS address space.
    • SRVC-RC
      Identifies the
      CA CSM
      services return code for this action.
      This is similar to the z/OS completion code.
    • Status
      Identifies the status for this action.
  2. Click the link for the action you want to view details for.
    Another dialog that contains details about this action opens.
Activate the Configuration
Activation of a configuration may be required when you configure a product on a staging system.
Configuring a product on a staging system can help you if you want to:
  • Create a customized set of run-time data sets that you will then move to a target system for the final activation
  • Create a fully implemented version of the product and test it locally
Activating the configuration makes your configuration fully functional on the target system.
You perform the following high-level process to activate the configuration:
  1. (In
    CA CSM
    ) Configure a product on a staging system.
  2. (In
    CA CSM
    ) Obtain the activation instructions that are available after the configuration is successfully built, validated, or implemented on a staging system. The activation instructions include extra steps that you have to perform on the configuration outside of
    CA CSM
    . For example, update data set members, or APF-authorize data sets.
  3. (Outside of
    CA CSM
    ) Perform one of the following actions:
    • If you activate a configuration on a staging system, follow the activation instructions on the staging system. Doing so activates the configuration and completes the configuration process.
    • If you activate a configuration on a remote system, deploy the configuration to the remote location. To do so, select and use a method that is appropriate for your site and environment. Then, follow the activation instructions on the remote system to activate the configuration and complete the configuration process.
Follow these steps:
  1. Click the Configurations tab and locate the configuration that you want to activate.
  2. Click the Actions drop-down list to the right of the configuration, and select Activation Instructions.
    A dialog that shows activation instructions opens. This dialog contains information about steps that you have to perform to activate the configuration.
  3. Review the steps.
  4. (Optional) Click Export to print the activation instructions, or export them to a TXT file or a ZIP file.
  5. Close the dialog.
  6. Perform the steps that are described in the activation instructions.
    Your configuration is activated and fully functional.
How to Address Implementation Failures
The process of addressing a failed implementation includes the following steps:
  1. Determine the cause of the failure. Drill down into the step and action details and analyze the details.
  2. If the error is related to a problem in your environment, make the necessary changes to your environment to correct the issue causing the failure. Implement this configuration again.
  3. If the error is related to the configuration settings in
    CA CSM
    , create a new configuration and import values from the failed configuration:
    1. When in step 3 (Import Values), select Import from Previous and Delete. Doing so imports the values from the failed configuration, and deletes the failed configuration. This action prevents duplicate resource problems.
    2. Modify the values in the new configuration as you need.
    3. Complete the remaining steps of the wizard.
  4. Validate the configuration to discover and clean up any data sets that may have been created as part of the failed implementation attempt.
  5. (Optional: Staging systems only) Activate the configuration.