Gathering performance information: Information supplied by end users

Comments from users are a necessary part of the data for performance analysis and improvement. Reporting procedures must be established, and their use encouraged.

Log exceptional incidents. These incidents should include system, line, or transaction failure, and response times that are outside specified limits. In addition, you should log incidents that threaten performance (such as deadlocks, deadlock abends, stalls, indications of going short-on-storage (SOS) and maximum number of multiregion operation (MRO) sessions used) as well as situations such as recoveries, including recovery from DL/I deadlock abend and restart, which mean that additional system resources are being used.

The data logged should include the date and time, location, duration, cause (if known), and the action taken to resolve the problem.

Related tasks
Gathering performance information: Requirements definition phase
Gathering performance information: External design phase
Gathering performance information: Internal design phase
Gathering performance information: Coding and testing phase
Gathering performance information: Post-development review
[[ Contents Previous Page | Next Page Index ]]