ERRCOUNT (CICS)
ERRCOUNT specifies how many conditions of severity 2, 3, and 4 can occur per
thread before the enclave terminates abnormally. After
the number specified in ERRCOUNT is reached, Language Environment terminates with a U4091 abend and no further Language Environment condition
management, including CEEHDLR management, is honored.
Notes :
- ERRCOUNT only applies when conditions are handled by a user
condition handler, signal
handler, signal catcher, PL/I on-units, or a language-specific condition handler.
- COBOL consideration : Language Environment does not count severity 0 or 1
messages. However, the COBOL-specific run-time library does count its severity 1 (warning) messages. When the limit of 256 IGZnnnnW messages is reached, the COBOL library will issue message IGZ0041W, indicating that the limit of warning messages has been exceeded. Any
further COBOL warning messages are suppressed.
- PL/I consideration : ERRCOUNT(0) is recommended for applications containing
PL/I. Some conditions such as ENDPAGE, can occur many times in an application. Use
ERRCOUNT(0) to avoid unnecessary termination of you application.
- C++ consideration : Note that each thrown object is considered a severity 3
condition, but does not affect ERRCOUNT.
- z/OS UNIX System Services consideration : Synchronous signals that are associated with a condition of severity 2, 3, or 4 do not affect ERRCOUNT. Asynchronous signals do not
affect ERRCOUNT.
Valid values : integer, range 0 through 99. A value of 0 means that the Language Environment
condition handler will not terminate regardless of the severity 2, 3, or 4 conditions that are
generated. This setting allows previous existing infinite loop or runaway task conditions to persist. Note that Language Environment does not place an
upper limit on ERRCOUNT, but 99 is set here as a practical limit.