About the LSPRDATA Data Set in SAS^® IT Resource Management

SAS IT Resource Management supplies an initial copy of a SAS data set called ITMS_SMF_LSPRDATA. This data set is stored in the SASHELP library and contains Large System Performance Reference (LSPR) information that is based on the IBM table for z/OS V1 R9. The data set also contains columns that enhance the reporting of resource utilization for various categories of System Management Facility (SMF) activity. Among these categories are systems, logical partitions (LPARs), workloads, workload periods, and jobs. The additional columns are distinct from other MSU-related columns that are already present in the SMF raw data. They reflect MSU (millions of service units) and MIPS (millions of instructions per second), based on CPU time expended during the activity. The section "Staging Methodology for MIPS and MSU Columns" in the SAS^® IT Resource Management 3.2: Administrator's Guide contains detailed information about how SAS IT Resource Management merges the LSPR information with staged Resource Management Facility (RMF) interval data.

Hot Fix D49002 is available and is required. This is because, when processing SMF data into the SAS IT Resource Management 3.2 XASMCEL staged table from multiple LPARS from either a full-capacity or sub-capacity CPU model or machine, there is the potential for multiple observations to be generated. For more information, see SAS Note 44293.

When a staging job cannot match a machine from the information extracted from the LSPR table, missing values are assigned to the LSPRMSU and LSPRCPI columns. This results in other computed columns also having missing values. This situation is not statistically incorrect, but it can misrepresent MIPS and MSU usage in aggregations.

If the LSPR information and the subsequent calculations that are based on it are important to you, update your LSPR information as soon as possible. Follow the instructions outlined in "Initialization and Preparation of the MIPS and MSU Columns" in the SAS^® IT Resource Management 3.2: Administrator's Guide. Do not attempt to rerun the staging job until the updated table has been implemented and stored in your Admin library.

How Hot Fix D49002 Affects LSPR Resource Information

If you apply Hot Fix D49002, SAS IT Resource Management does two things, as described below.

• SAS IT Resource Management issues the following error when a machine cannot be matched from the LSPR table information, causing the staging job to stop processing:

  ERROR: The SMF data for system  is associated with a 
         mainframe model
  ERROR: <number> which does not appear in your LSPR table.
  ERROR: To preserve the integrity of your data mart, this job 
         will stop.

If you receive the error message about the mainframe model not matching the LSPR table, update your LSPR table and rerun your staging job. However, if you are not interested in the SMF data matching the LSPR information, you can bypass the error. Do so by setting the LSPR_ERROR_ON macro variable at the beginning of your staging job, as follows:

    %LET LSPR_ERROR_ON=N;

This causes SAS IT Resource Management to bypass the error, enables processing to continue, and sets all subsequent calculations that are based on the LSPR information to missing values. The SAS log also issues the following notes about this, instead of issuing errors:

     NOTE: The SMF data for system  is associated with a 
           mainframe model
     NOTE: <number> which does not appear in your LSPR table.
     NOTE: You coded LSPR_ERROR_ON=N to ignore this problem.



• The default SAS data set ITMS_SMF_LSPRDATA is updated with the next available version of the LSPR table, which is for z/OS V1 R11.
  
  If you have previously stored the LSPR resource information in the SAS IT Resource Management Admin library, the updates made by Hot Fix D49002 do not affect the Admin library.

How to Retain the Default LSPR Table

You can retain the default LSPR table information that was shipped with your original SAS IT Resource Management 3.2 installation of your SASHELP library. To do so, follow the steps below before you apply Hot Fix D49002. Note that you need to have exclusive access to the SASHELP library before you restore the original LSPR table in the SASHELP library.

1. Make a backup copy of the SASHELP library before applying Hot Fix D49002.
2. Install Hot Fix D49002.
3. After applying the hot fix successfully, submit the following SAS code:
   

       /*Allocate the backup copy of the SASHELP library      */
       /*that uses PROC COPY to copy only the LSPR table      */
       /*with the SELECT statement.                           */
       /*Make sure you have exclusive udate access to the     */
       /*SASHELP SAS library before you submit code.          */
         
       libname bkuphelp '<physical-location-of-backup-sashelp>';
       proc copy in=bkuphelp out=SASHELP;
         select ITMS_SMF_LSPRDATA;
       run;
   
   z/OS sites can submit the following batch job:
   
           //jobname JOB 
           //STEP1 EXEC SAS92,OPTIONS=’SASHELP=SASHELP’
           //SASHELP DD DSN='& prefix.llWn.SASHELP',DISP=OLD
           //SYSIN   DD *
              libname bkuphelp '<physical-location-of-backup-sashelp>';
              proc copy in=bkuphelp out=SASHELP;
                 select ITMS_SMF_LSPRDATA;
              run;
   
       /*Ouput contents of LSPR data information              */ 
     
      PROC PRINT=SASHELP.ITMS_SMF_LSPRDATA;
      RUN;
   

   Notes:

   • & prefix is the prefix specified at the time of your installation. ll is the code for the language of your installation. Wn is the encoding for your installation.
   • Sample names for the configuration file and SASHELP libraries are as follows:

         USERID.CONFIG(ENW0)
         USERID.ENW0.SASHELP
         USERID.D54002.ENW0.SASHELP
     

4. Review the output from the PRINT procedure to make sure that the SAS data set with the LSPR information has been updated.

Operating System and Release Information

A fix for this issue for SAS IT Resource Management 3.2 is available at: