Verifying the CICSplex control settings and saving the updated SLA definitions

The CICSplex control settings determine the workload-management system your site is using to monitor its SLA compliance and also how often the OMEGAMON XE for CICS on z/OS agent will accumulate the SLA data and send it to the Tivoli Enterprise Monitoring Server for processing and display by the Tivoli Enterprise Portal. When you have set the control parameters as appropriate, you are ready to activate your CICSplex's SLA environment. To set these values and activate your current SLA definitions:

  1. If not already selected, select the CICSplex icon within the CICSplex—SLA window's left pane: This graphic shows the CICSplex icon..

    The right pane changes to show your installation's current CICSplex—Control settings:

    Figure 22. The CICSplex control settings within the CICSplex—SLA window
    This graphic shows the CICSplex control settings, which affect your entire SLA environment.
  2. Within the CICSplex—Control pane, first select the source of the workload-management rules you want to use, either z/OS's native z/OS workload manager or the workload manager provided with OMEGAMON XE for CICS on z/OS or both.
    z/OS WLM
    Enables you to monitor your SLA environment using the workload manager native to z/OS. The z/OS workload manager balances workloads across all z/OS computing resources, including CICS regions, to prevent bottlenecks.
    Notes:
    1. If you select the z/OS WLM, the service policies, workloads, and service classes you create using the CICS SLA view are ignored. OMEGAMON XE for CICS on z/OS instead uses the rules defined for the z/OS workload manager.
    2. If your site chooses the z/OS workload manager when monitoring its CICS service-level compliance, this is the only procedure you need complete to activate it.
    OMEGAMON WLM
    OMEGAMON XE for CICS on z/OS offers its own service-level analysis based on workload definitions similar to those provided by the z/OS workload manager. Using the CICS SLA view, you can define your own service policies, workloads, and service classes and activate a service policy to report on the performance of CICS transactions. Benefits of the OMEGAMON WLM:
    • It provides similar function in collecting service-level data when your installation is not running the z/OS workload manager in goal mode.
    • It reports service-level data collected by OMEGAMON XE for CICS on z/OS in a manner similar to the z/OS workload manager.

    The service-level analysis capabilities native to OMEGAMON XE for CICS on z/OS help you ensure SLA compliance without requiring the assistance of the system programmer who configures and maintains your site's z/OS workload manager, nor does it require that the z/OS workload manager even be active. The OMEGAMON workload manager makes ensuring CICS SLA compliance independent of the z/OS workload manager and its WLM definitions.

    Unlike the z/OS workload manager, the native OMEGAMON workload manager does not perform workload balancing. Other differences:

    • The OMEGAMON workload manager does not support velocity-goal definitions. Velocity goals do not apply to CICS transactions.
    • The OMEGAMON workload manager does not support definition of different periods.
    Auto
    Provides service-level analysis using first the z/OS and then the native OMEGAMON workload managers. OMEGAMON XE for CICS on z/OS's workload-summarizer component ensures it can communicate with the z/OS WLM and get a copy of its service classes and goals. If for any LPAR the z/OS definitions cannot be obtained, OMEGAMON XE for CICS on z/OS uses the OMEGAMON service classes and goals.
  3. Set the Collection Interval, in multiples of five minutes. This parameter determines how often response data for service classes, CICS regions, and individual transactions is summarized and reported by the Service Class Analysis workspace.
    Note:
    If your site set the collection interval to 1 minute by specifying the INTERVAL=1 parameter in the configuration settings for the agent's collector subtask, that setting overrides any value you specify for Collection Interval using the CICS SLA view.
  4. Press the Save button.

    Your updated SLA objects and monitoring settings are written to the Tivoli Enterprise Portal Server, and the monitoring settings are then passed to the Tivoli Enterprise Monitoring Server. The OMEGAMON XE for CICS on z/OS agent will pick them up within the next 60 seconds.

After you have set the CICSplex SLA monitoring values and activated them, you are ready to close the CICS SLA view and return to the Tivoli Enterprise Portal's Physical view; see Returning to the Physical view.