OVW

You can use the OVW control statement to create Overview reports and Overview records. Depending on the condition names, the SMF data, and the optional parameters SYSTEMS|NOSYSTEMS, you get single-system and sysplex reports or records.

Note: There is a limitation of 253 OVW control statements for one step of the Postprocessor.

The OVW syntax is:

OVW(control-statement-name(condition-name(qualifier))[,SYSTEMS])
or
OVW(control-statement-name(condition-name(qualifier))[,NOSYSTEMS])

If in the past you have performed overview processing with EXCEPT control statements, you should exchange them to OVW control statements because OVW statements enable you to create sysplex reports. The OVW syntax just requires a control statement name, but no threshold, as required for the EXCEPT control statement.

Refer to EXCEPT for an explanation of the parameters control-statement-name and condition-name(qualifier).

Note: For information on exception/overview duration reporting, refer to DINTV.
SYSTEMS
You get a single-system report for each system of the sysplex, and you get an additional sysplex report for all sysplex-related overview conditions (based on the records for the CF, SDEVICE, and WLMGL reports). This optional parameter (which is the default) is valid only in combination with sysplex-related overview conditions, but is tolerated for single-system overview conditions.
NOSYSTEMS
Only sysplex-wide overview data is generated.

You find a list of all condition names in Overview and exception conditions.

Example: You want to get the sysplex-wide response times for all TSO users running in service class TSOSERV, and you have defined three service class periods. You want to get the data for all intervals between 10:00 AM and 2:00 PM, and you want to create a report as well as records.

You specify the following control statements:

ETOD(1000,1400)
OVERVIEW(REPORT,RECORD)
OVW(RTIMEP1(RTIMETOT(S.TSOSERV.1)),NOSYSTEMS)
OVW(RTIMEP2(RTIMETOT(S.TSOSERV.2)),NOSYSTEMS)
OVW(RTIMEP3(RTIMETOT(S.TSOSERV.3)),NOSYSTEMS)

Note that you specify your own appropriate control-statement-names (in our example RTIMEP1, … , RTIMEP3) that appear as column headings for the desired measurements in the resulting report or record.