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.
If you apply Hot Fix D49002, SAS IT Resource Management does two things, as described below.
ERROR: The SMF data for systemis 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 systemis 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.
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.
/*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:
USERID.CONFIG(ENW0) USERID.ENW0.SASHELP USERID.D54002.ENW0.SASHELP
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS IT Resource Management | Microsoft® Windows® for x64 | 3.2 | 9.2 TS2M3 | ||
Microsoft Windows Server 2003 Datacenter Edition | 3.2 | 9.2 TS2M3 | ||||
Microsoft Windows Server 2003 Enterprise Edition | 3.2 | 9.2 TS2M3 | ||||
Microsoft Windows Server 2003 Standard Edition | 3.2 | 9.2 TS2M3 | ||||
Microsoft Windows Server 2003 for x64 | 3.2 | 9.2 TS2M3 | ||||
Microsoft Windows Server 2008 | 3.2 | 9.2 TS2M3 | ||||
Microsoft Windows Server 2008 for x64 | 3.2 | 9.2 TS2M3 | ||||
Microsoft Windows XP Professional | 3.2 | 9.2 TS2M3 | ||||
Windows 7 Enterprise 32 bit | 3.2 | 9.2 TS2M3 | ||||
Windows 7 Enterprise x64 | 3.2 | 9.2 TS2M3 | ||||
Windows 7 Home Premium 32 bit | 3.2 | 9.2 TS2M3 | ||||
Windows 7 Home Premium x64 | 3.2 | 9.2 TS2M3 | ||||
Windows 7 Professional 32 bit | 3.2 | 9.2 TS2M3 | ||||
Windows 7 Professional x64 | 3.2 | 9.2 TS2M3 | ||||
Windows 7 Ultimate 32 bit | 3.2 | 9.2 TS2M3 | ||||
Windows 7 Ultimate x64 | 3.2 | 9.2 TS2M3 | ||||
Windows Vista | 3.2 | 9.2 TS2M3 | ||||
Windows Vista for x64 | 3.2 | 9.2 TS2M3 |
A fix for this issue for SAS IT Resource Management 3.2 is available at:
http://ftp.sas.com/techsup/download/hotfix/HF2/D49.html#40936Type: | Usage Note |
Priority: | medium |
Date Modified: | 2011-09-16 10:44:19 |
Date Created: | 2010-09-17 11:55:24 |