Defining Model Builder Tasks

The Model Builder Tasks tool provides you with the ability to build cost models based on current data from the CDB server. Once defined and scheduled, Model Builder Tasks generate the models required for the Software Contract Reporting, Monthly Reporting, and Planning tools.

You can build a variety of models to affect the scope of your analysis. In general, if you have multiple CDB servers, you must define multiple Model Builder Tasks to run. If you have more than one workload type you want to process, you can define one Model Builder Task for all of the workloads. It is not necessary to create a separate task for each workload type.

However, if you want to run a Model Builder Task for multiple workload types, you can specify only one filter. If you need to specify different filters for different workloads, you need to create a separate Model Builder Task for each workload that you want to filter.

Model Builder tasks provide advanced options where you can:

• Exclude particular LPARs from the cost calculations
• Designate the LPARs that use zNALC licensing for z/OS products
• Enable trace messages to the log file to assist in diagnostics

To define Model Builder Tasks

1. From the Cost Analyzer console, click Administration Tools.

2. In the Administration Tools window, click Manage Model Builder Tasks.The Model Builder Task Manager dialog opens, listing all of the tasks that have been defined:

   

   From the dialog you can add, modify, or remove Model Builder Tasks.

3. Perform one of the following actions:

   • To add a new Model Builder Task, click the Add button.
   • To modify an existing Model Builder Task, select the icon of the task you want to modify from the list, and then click the Modify button.

   The Add/Modify dialog is displayed as shown in the following figure:

   

Complete each field based on the following table:

1. (Optional) If you want to exclude particular LPARs from the cost calculation, designate zNALC LPARs, specify NO89 commands, specify SCRT commands, or enable Trace messages, click Advanced Options.The Advanced Options dialog displays as shown in the following figure:

   

   1. To designate zNALC LPARs, enter the name of the zNALC LPAR you want to include, and then click Accept.

      Warning

      Note

      You can enter LPARs either individually or you can list multiple LPARs separated by commas.

      Entries are case-sensitive, so be sure to enter the LPAR name exactly as it appears in z/OS, which primarily uses capital letters for all LPAR names.

   2. To exclude LPARs from the cost calculation click the Exclude tab, enter the name of the LPAR you want to exclude and then click Accept.

      Warning

      Note

      Exclude LPARs should be used only if all activity for a particular LPAR needs to be completely excluded from the cost calculation. If you need to exclude just data for a specific time period or for the activity of a specific MLC Product, you must use the EXCLUDE command. For more information, see EXCLUDE89-command.

   3. To specify the NO89 command for a MLC product or a priced feature that does not create SMF Type 89 records, click the NO89 commands tab, then enter the command as follows:NO89 productID[:featureCode]=[CPCSN:]lparName,... | *All

      The following table defines the value of the variables:

      Variable	Description
      productID	IBM product number
      featureCode	IBM priced feature number
      CPCSN	The CPC serial number
      lparName	List of LPAR names separated by commas Warning Note You must enter the LPAR name and not the SID

      Warning

      Note

      The following guidelines apply with regard to N089 commands:

      • You must enter a separate command for each MLC product or priced feature that does not create SMF type 89 records.
      • If the NO89 command was already specified in the JCL that runs the Universal Information Exchange batch job, you do not need to enter a command for that particular MLC product or priced feature.

      For more information, see NO89-command.

   4. To specify an EXCLUDE command for an interval that must be excluded from the peak R4HA calculation, click the SCRT commands tab, then enter the command as follows:

       EXCLUDE89 CPC=<xxxx> IMAGE_ID=<lparname>,... | *ALL
                        PRODUCT_ID=<productid>,...|*ALL
                        START=<yyyy m d h>
                        RESUME=<yyyy m d h>
                        ACTIVE=Y|N

      Error

      Warning

      When you specify an EXCLUDE89 command in a Model Builder Task, all previous EXCLUDE89 commands added to the UIE JCL for any other intervals are ignored. In order to maintain the correct cost data in the cost models, all of these EXCLUDE89 commands need to be added to the Model Builder Task. For more information, see EXCLUDE89-command.

   5. To specify a CONTAINER, UPDATE CONTAINER, or IGNORE CONTAINER command, click the SCRT commands tab, then enter the commands as follows:

      Command	Example
      CONTAINER	CONTAINER CPC=<tttt>-<sssss>,IMAGE_ID=(<image1>,<image2>,...,<imageN>),ID=<solutionID> The variables are defined as follows: tttt – CPU Type sssss – Last five characters of CPU serial number image1,image2,...ImageN – Names of the LPARs that are container LPARS SolutionID – Solution identification number Note: At least one image_ID required. Image_ID is LPAR name
      UPDATE CONTAINER	UPDATE CONTAINER,ID=<solutionID>,SET_NAME="<solutionName>" Note: This command is required.
      IGNORE CONTAINER	IGNORE CONTAINER,ID=<solutionID>,START=<yyyy>/<mm>/<dd>/<hh>,RESUME=<yyyy>/<mm>/<dd>/<hh> Note: The IGNORE CONTAINER control statement is only intended for use under rare circumstances and as directed by IBM.

   6. To specify an Integrated Workload Pricing (IWP) command, click the SCRT commands tab, then enter the commands as follows:

      IWP | Integrated_Workload_Pricing

   7. To enable Trace messages, click the Trace tab, and then click  to output trace messages to the log for the Model Builder Task.

      Warning

      Note

      Enabling Trace messages can dramatically increase the size of the log file and should only be enabled for troubleshooting.

   8. When finished with Advanced Options, click Accept.
2. When finished with all selections, click Add Task.The task appears as a listing in the Model Builder Tasks dialog.
3. Click Save Changes to save the Model Builder Task to the server.