3. REPORTS › 3.1 Postprocessor Reports › 3.1.2 Running the Postprocessor Reports › 3.1.2.1 Report Control Statements › 3.1.2.1.1 Specifying Reports to be Produced (REPORTS)

3.1.2.1.1 Specifying Reports to be Produced (REPORTS)

Postprocessor report selection is accomplished by means of a
SAS global variable assignment statement.  The statement is
required and must be present after the //CONTROL DD statement
in the report JCL.  The report selection statement has the
following format:

%LET REPORTS = rpt1 rpt2 ... rptn;

Multiple report requests must be delimited by a blank.  The
valid requests are:

o  CACHEDTL  - Cache Subsystem Activity Detail Report
o  CACHESUM  - Cache Subsystem Activity Summary Report
o  CHANNEL   - Channel Path Activity Report
o  CPU       - CPU Activity Report
o  CRYPTO    - Crypto Hardware Activity Report
o  DEVICE    - Device Activity Report
o  DEVSG     - Storage Group Device Activity Report
o  ENQUEUE   - Enqueue Activity Report
o  FCD       - FICON Director Activity Report
o  IOQ       - I/O Queuing Activity Report
o  PAGESP    - Page/Swap Data Set Activity Report
o  PAGING    - Paging Activity Report
o  SUMMARY   - RMF Summary Report
o  USS       - USS Kernel Activity Report
o  VSTORDTL  - Virtual Storage Detail Report
o  VSTORSUM  - Virtual Storage Summary Report
o  WLMGL     - Workload Activity Goal Mode Reports (see Note
               below)
o  XCF       - XCF Usage by System Report
             - XCF Usage by Member Report
             - XCF Path Statistics Report
o  XES       - Coupling Facility Usage Summary Report
             - XES Structure Activity Report
             - Coupling Facility Subchannel Report

Note:  The WLMGL report supports additional options described
in section 3.1.1.13.

The following reports are only available as MICF inquiries
and, thus, cannot be requested with the batch report
selection statement:

o  Shared Device Activity Report
o  Enterprise Disk Systems Report

See section 3.2 for information on running the postprocessor
reports under MICF.

Invalid report requests are ignored.  If no valid report
requests are found, the report run is aborted with a message
indicating a control statement error.

Examples:  %LET REPORTS = CPU;
           %LET REPORTS = PAGING PAGESP;