The following describes the parameters that you can set in the workload monitor (Transaction ST03) for programs RSSTAT80/83 and RSSTAT87/88/89.
In the R/3 System, the job SAP_COLLECTOR_FOR_PERFMONITOR or COLLECTOR_FOR_PERFORMANCEMONITOR is executed hourly and in turn activates the report RSCOLL00. This report in turn activates further reports according to the entries in the table TCOLL (for example, report RSSTAT80 or RSSTAT83). These reports read the statistics file of every R/3 instance, format and compress the data, and then store it in table MONI.
The report RSSTAT80 is activated hourly by table TCOLL on all instances. Report RSSTAT83 runs in parallel on all servers in the system, which reduces the runtime of report RSCOLL00 considerably. As RSSTAT83 runs in parallel on servers, it cannot calculate TOTAL server statistics. To calculate these statistics, if needed, you must run RSSTAT82. For more information, see R/3 Note 127642 in SAPNet.
Report RSSTAT89 reads the application statistic records, compresses the information and then stores it in the database. In place of this report, you can run report RSSTAT88 (runs in parallel on multiple servers, see R/3 Note 127462) in SAPNet. RSSTAT88 is started by report RSSTAT87 approximately a half an hour after SAP_COLLECTOR_FOR_PERFMONITOR.
The parameters (and the fields in which you set the parameters) are grouped in the workload monitor under the following headings on the Workload Analysis: Parameters Relevant to MONI Reorg. screen.(To call this screen, call Transaction ST03 and choose Goto ® Parameters ® Performance database.)
These parameters specify how long statistics are retained for each time period (days, weeks, months).
You can influence the runtime behavior of the statistics collector using several parameters. If there are collector performance problems, you can reduce the runtime by excluding some of the statistics details.
· Cumulate statistics for period ‘Week’.
Generate weekly statistics.
· Cumulate statistics for period ‘Month’.
Generate monthly statistics.
· Cumulate hitlists (Top time & Top Requests).
Display 40 dialog steps within selected period with the highest response times and database requests.
· Cumulate memory profile.
Transaction memory use.
· Cumulate accounting & client profile.
Generate statistics according to user or client.
· Cumulate RFC profiles.
· Cumulate terminal in/out messages (Req. Bytes profile).
Data exchange between application server and clients.
· Cumulate CUA proc. profile.
Statistics for function codes (only generated by report RSSTAT80).
· Cumulate server statistics to a systemwide total statistics (only valid for the RSSTAT80/RSSTAT89).
Creates systemwide TOTAL statistics across all servers (for RSSTAT80).
· Max. number of parallel RFCs (only valid for RSSTAT83/88).
Maximum number of RFCs executed in parallel (“999” means a RFC is started simultaneously for all servers).
· Delete seq. statfile after cumulation if size > (default: 100Mb).
This parameter specifies from what file size the system should delete the statistics file. The statistics file is required for individual statistics and is therefore not deleted until the file size has passed a specified maximum file size. Of course, the file is only deleted if it was completely processed by RSSTAT80 or RSSTAT83..
· Max. no. of records cumulated per call (default: 20.000).
This is the maximum number of entries in the statistics file that can be processed by RSSTAT80 or RSSTAT83 in one session. This parameter is used to restrict the runtime of the collector.
· Delete appl. statfile after cumulation if size > (default: 30Mb).
This parameter specifies from what size the system should delete the application statistics file. Of course, the file is only deleted if it was completely processed by RSSTAT88 or RSSTAT89.
· Max. number of records cumulated per call (default: 20.000).
This is the maximum number of entries in the application statistics file that can be processed by RSSTAT80 or RSSTAT83 in one session. This parameter is used to restrict the runtime of the collector.