Resolving resource problems

This table provides information about the symptoms that indicate resource problems, their causes, and their solutions.

Follow this general procedure for resolving resource problems:
  1. Confirm that your diagnosis of the type of constraint is correct, by means of detailed performance analysis. Methods of performance analysis describes various techniques.
  2. Read Tuning your system for general advice on performance tuning.
  3. See the relevant sections in Improving the performance of a CICS system for detailed information on applying the various solutions.
  4. 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
    Such a system can deliver better internal response times, while minimizing DASD I/O constraint and reducing processor utilization.

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 response times (the length of the response time depends on the number of I/O operations, with a longer response time when batch mode is active)
  • High DSA utilization
  • High paging rates
  • MXT limit frequently reached
  • SOS condition often occurs
  • Reduce the number of I/O operations.
  • Tune the remaining I/O operations.
  • Balance the I/O operations load.

Slow transaction response on network: the average transaction response time for the network is unacceptably slow.

  • Slow response times
  • Good response when few terminals are active on a line, but poor response when many terminals are active on that line
  • Big difference between internal response time and terminal response time
  • Reduce the line utilization.
  • Reduce delays in data transmission.
  • Alter the network.

Slow response from remote system: the response time from a connected remote system is excessive.

  • SOS condition or MXT occurs when there is a problem with a connected region
  • CICS takes time to recover when the problem is fixed
  • Control the amount of queuing which takes place for the use of the connections to the remote systems.
  • Improve the response time of the remote system.

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.

  • Slow response times
  • Multiple loads of the same program
  • Increased I/O operations against program libraries
  • High paging rates
  • Frequent SOS condition
  • Tune the MVS system to obtain more virtual storage for CICS (increase the region size).
  • Make more efficient use of the dynamic storage area.

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.

  • High paging rates
  • Slow response times
  • MXT limit frequently reached
  • SOS condition often occurs
  • Reduce the demands on real storage
  • Tune the MVS system to obtain more real storage for CICS

Excessive processor cycling: storage buffering or cycle stealing with integrated channels is occurring, or the amount of the queue searching is excessive.

  • Slow response times
  • Low priority transactions respond very slowly
  • Low priority work very slow to complete
  • Increase the dispatching priority of CICS.
  • Reevaluate the relative priorities of operating system jobs.
  • Reduce the number of MVS regions (batch).
  • Reduce the processor utilization for productive work.
  • Use only the CICS facilities that you really require.
  • Turn off any trace that is not being used.
  • Minimize the data being traced by reducing the scope of the trace, or by tracing less frequently.
  • Use a faster processor.

For more information about resolving performance problems see the Resource Measurement Facility™ Performance Management Guide (SC33-7992).



dfht3kg.html | Timestamp icon Last updated: Monday, 5 June 2017