Introduction › How to Proceed › System Use Report Generation

System Use Report Generation

To generate System Use Reports, simply code the SELECT statement to indicate which reports are desired. SMF input or a history input file level 6 or 7 created from SMF input must be specified for System Use Reports to be meaningful. No other control statements, except SELECT, are required if System Use Reports are the only output desired, with the following exceptions:

• When a level-6 history file is used as input, the SYSUSE1 control statement must have a J in position 11.
• The processor count field on the OPTION control statement, positions 35-36, needs to reflect the number of processors.

At this time, you may want to run some System Use Reports against your SMF data. The JCL required to run CA JARS is documented in the "Operating Instructions" chapter. You should read the detailed explanation of System Use Reports in the "System Use Reporting" chapter, comparing the examples provided with the System Use Reports you generate to gain a full understanding of how these reports should be used.

Customization is optional but can be performed using two additional control statements: SYSUSE1 option and SYSUSE2 option.

Synchronize the writing of SMF interval records with the recording of RMF data to help ensure correspondence between RMF reports and system use reports.

In order to ensure accuracy of system use reports in a multiple LPAR environment, it is necessary to run separate reports for each LPAR. This is accomplished by including a SYSUSE1 statement and coding the first character of the LPAR name in column 10 of that statement.