Creating a basic policy

Use the following procedure to build a basic policy, accepting mostly default values.

Important

You can also build detailed policies based on this procedure. To build a detailed policy, you should collect system information before you begin. For more information, see Collecting-system-information-to-build-iCap-policies.

Related topic

Getting-started-with-policies

If you are new to building policies, BMC recommends that you start by running iCap in observe or message mode and by using test LPARs or groups in the policy. This approach helps you understand how iCap works without affecting your high-importance workloads.

Important

This procedure is based on the windows-mode ISPF interface but provides alternative instructions for MainView Explorer.

To create a policy

  1. On EZICAP, hyperlink on Policy Admin UI.

  2. On the Policy Administration UI (POLICIES view), type NEW on the COMMAND line.

    Tip

    Alternatively, you can clone an existing policy by typing CLO in the CMD column next to the policy that you want to clone. (In MainView Explorer, right-click the policy and select Line action > Clone a policy.)

  3. In the Create a Policy for iCap dialog box, enter values for the parameters that have no defaults. For the other parameters, you can accept the default values. If required, you can change them later. For detailed descriptions of the policy parameters, see Policy-level-and-subpolicy-level-parameters.

    Enter values for the following parameters:

    Parameter

    Action

    Policy Name

    Enter a unique name for the policy.

    Description

    Enter up to 32 characters to describe the policy.

    Initial MSULIMIT

    Enter one of the following values:

    • If you want iCap to execute a dynamic MSU limit, specify the initial MSU limit value.
      For iCap to execute a dynamic MSU limit, you must also specify values for Max MSULIMIT, Inc MSULIMIT, and Adj MSULIMIT.

      For more information about using a dynamic MSU limit, see Overview-of-MSU-limit-CPCMSU-limit-and-cost-limit.

    • If you do not want iCap to execute a dynamic MSU limit, specify the maximum allowable MSUs to be consumed collectively by all LPARs and capacity groups that the policy or subpolicy manages.

    Possible values are 1 through 99999.

    Max MSULIMIT

    If you want 

    iCap

     to execute a dynamic MSU limit, enter the maximum allowable MSUs to be consumed collectively by all LPARs and capacity groups that the policy manages.Possible values are 1 through 99999.

    Important

    Consider the following information:

    • If you are building a policy for the first time, you can set this value to the sum of combined 4HRAs for all of the managed LPARs.
    • The MSU limit should not be greater than the maximum number of MSUs on the managed CPCs.

    Inc MSULIMIT

    If you want iCap to execute a dynamic MSU limit, enter the number of MSUs by which the initial MSU limit increases every ADJTIME.

    Adj MSULIMIT

    If you want iCap to execute a dynamic MSU limit, enter the percentage of low-importance work in the policy at which iCap starts to increase the MSU limit.

    If you want to specify which LPARs are used to calculate the low-importance percent calculation, enter a value of 1 through 5 to adjust MSULIMIT. For more information, see Scope.

    For detailed descriptions of the policy parameters, see Policy-level-and-subpolicy-level-parameters.

    (BMC.AMIOPS.SPE2301) Example: Create a Policy for iCap

     -------------------------- Create a Policy for iCap ---------------------------
     | COMMAND ===>                                              SCROLL ===> PAGE  |
     |                                                                             |
     |  Policy Name         TESTPOL                           Member name          |
     |  Description         TEST POLICY                       Description          |
     |  Initial MSULIMIT    600                               Range 1-99999        |
     |  Max MSULIMIT        1021                              Range 1-99999        |
     |  Inc MSULIMIT        50                                Range 1-999          |
     |  Adj MSULIMIT        95                                Range 1-99           |
     |  WLM Tuning          COMBINED                          Defaults to COMBINED |
     |  AdjFac Priority 1   0.6                               Defaults to .6       |
     |  AdjFac Priority 2   0.8                               Defaults to .8       |
     |  AdjFac Priority 3   1.0                               Defaults to 1.0      |
     |  AdjFac Priority 4   1.2                               Defaults to 1.2      |
     |  AdjFac Priority 5   1.4                               Defaults to 1.4      |
     |  Low Importance      5                                 Defaults to 5        |
     |  Manage Cost         NO                                Defaults to NO       |
     |  Dynamic Entitlement YES                               Defaults to YES      |
     |  Mobile Adjust       NO                                Defaults to NO       |
     |  Container Adjust    NO                                Defaults to NO       |
     |  Min Managed MSUs    400                               0 Means No Unmanaged |
     |  Unmanaged LPARS     YES                               Defaults to NO       |
     |  Management          TFP                               Defaults to MLC      |
     |  Scope               5                                 Defaults to 5   |
     |               |
     | END to exit saving changes                                                  |
     | CANCEL to exit without saving changes                                       |
     | HELP to view related help                                                   |
     | RESET to reset to initial data                                              |
     -------------------------------------------------------------------------------

  4. Press F3 to save the changes (or in MainView Explorer, click OK).
    The POLDSPLY view shows details of the new policy. From POLDSPLY you can add, update, or delete the LPARs, subpolices, and CPCIDs in a policy. 

    >W1 =POLDSPLY==========DYCM=====*========ddmmmyyyy==05:45:08====ICAP=====D===19
    CMD Type      SubPolicy LPAR or   CPCID Initial_ Maximum  Inc  Adj LPAR/ Group
    --- ----      --------- Cap Group ----- MSULIMIT MSULIMIT MSUL MSU Type  Name  
        POLICY                                   600     1021   50  95             
        LPAR/GRP            SYSM      FA817                            LPAR  DEFAUL
        LPAR/GRP            IMSA      FA817                            LPAR        
        LPAR/GRP            ESAJ      FA817                            LPAR  DEFAUL
        CPCID                         FA817                                        
        CPCID                         DCE07                                        
        SUBPOLICY DYNSUB1                        146      200   11  90             
        LPAR/GRP  DYNSUB1   DB2A      FA817                            LPAR  DB2GRO
        LPAR/GRP  DYNSUB1   SYSN      FA817                            LPAR  DB2GRO
        LPAR/GRP  DYNSUB1   DB2B      FA817                            LPAR  DB2GRO
        SUBPOLICY DYNSUB2                        125      150    7  87             
        LPAR/GRP  DYNSUB2   SJSC      FA817                            LPAR  SJTEST
        LPAR/GRP  DYNSUB2   SJSD      FA817                            LPAR  SJTEST

    If you are building a new policy from scratch, the POLDSPLY view will be empty, except for the CPCID. By default, iCap inserts the CPC on which the master PAS is running. If you want to manage LPARs and groups on multiple CPCs, you can add CPCIDs.

Where to go from here

After you have built a basic policy, you can proceed as follows:



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*