Resolving resource problems
This table provides information about the symptoms that indicate resource problems, their causes, and their solutions.
- Confirm that your diagnosis of the type of constraint is correct, by means of detailed performance analysis. Methods of performance analysis describes various techniques.
- Read Tuning your system for general advice on performance tuning.
- See the relevant sections in Improving the performance of a CICS system for detailed information on applying the various solutions.
- Improve virtual storage exploitation by ensuring the following:
- Large data buffers above the 16 MB line or in Hiperspace™
- Programs that run above the 16 MB line
- Large amounts of real storage to support the virtual storage exploitation
Typical resource problems, their symptoms, and their solutions:
| Problem | Symptom | Solution |
|---|---|---|
Excessive DASD I/O operations: the amount of I/O operations needed to locate and fetch modules from DASD storage is excessive. |
|
|
Slow transaction response on network: the average transaction response time for the network is unacceptably slow. |
|
|
Slow response from remote system: the response time from a connected remote system is excessive. |
|
|
Excessive use of virtual storage: excessive use of common storage is occurring, or storage is not being freed at the end of a job or address space. |
|
|
Insufficient real storage: a program issued a request for real (processor) storage that specified a variable length with a maximum value that was too high. |
|
|
Excessive processor cycling: storage buffering or cycle stealing with integrated channels is occurring, or the amount of the queue searching is excessive. |
|
|
For more information about resolving performance problems see the Resource Measurement Facility™ Performance Management Guide (SC33-7992).