This command outputs statistics regarding the load being placed on the server for all isolated regions. Use loadstatus periodically to get a feel for the rate at which requests or errors normally occur on the system. Once you have determined this rate, execute loadstatus when response time is slow to see if any of the error counters are going up at a rapid rate.
By default, the loadstatus command does not always count all statistical events. You can set it to display exact statistics using the resetloadstatus command.
The loadstatus command outputs two types of statistics:
Remote procedure call (RPC) counters show how many RPCs of various types have been processed on the server, as well as the average number processed per minute and per hour.
The RPCs listed in the report are intended to provide an idea of the amount of activity on the server. The counts for the total number of RPCs display as well as the counts for the most common RPC activities (query, lock, dispatch). To view more detailed information on RPCs processed by the server, use the trace command.
Error counters show how many times a function must be retried due to an error on the server.
The error counters increment occasionally on a system that is running normally, so do not expect these counters to remain at zero. Under normal circumstances, however, the counters do not increase at a steady rate.
Use the resetloadstatus command to reset the statistics to zero.
See RPC and error counters for a description of each RPC and error counter. The counters are initialized each time the Process Engine (PE) software is restarted.
Syntax
loadstatus
Parameters
None