Are the system definition parameters wrong?

The system definition parameters for your system might be causing it to stall, possibly at a critical loading. Check what is specified, paying particular attention to the following items:
  • The CICS® maximum tasks (MXT) and transaction class (MAXACTIVE) limits. If these parameters are too low, new tasks might fail to be attached. If you think that one of these limits might be the cause of the stall, read Are MXT or transaction class limits causing the stall? for advice about further investigation.
  • ICV system initialization parameter, the system region exit time. If this parameter is set too high, CICS might relinquish control to the operating system for longer than intended when it has no work to do, and might give the impression of a stall.
  • ICVR system initialization parameter, the runaway task time interval. If this parameter is set too high, a runaway task might stop other tasks from running for a relatively long time. The maximum ICVR value is 2,700,000 milliseconds, in which case, a runaway task would not time out for 45 minutes. CICS could, in the meantime, be stalled. If the ICVR parameter is set to 0, the runaway task does not time out at all.

    You should already have an indication if the ICVR is the problem, from the CPU usage.

For more details about the choice of these and other system definition parameters, see Interval control value parameters and Improving the performance of a CICS system.



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