ERRCOUNT

Derivation: ERRor COUNTer

ERRCOUNT specifies how many conditions of severity 2, 3, or 4 can occur per thread before the enclave terminates abnormally. When the number specified in ERRCOUNT is exceeded, Language Environment ends with ABEND U4091 RC=B.

The default value for non-CICS applications is ERRCOUNT(0).

The default value for CICS® applications is ERRCOUNT(0).

Read syntax diagramSkip visual syntax diagram
Syntax

>>-ERrcount--(--+--------+--)----------------------------------><
                '-number-'      

number
An integer of 0 or greater value that specifies the number of severity 2, 3, and 4 conditions allowed for each thread. An unlimited number of conditions is allowed if you specify 0. If the number of conditions exceeds the limit, the application ends with abend 4091 RC=B.

z/OS® UNIX considerations

Synchronous signals that are associated with a condition of severity 2, 3, or 4 affect ERRCOUNT. Asynchronous signals do not affect ERRCOUNT.

Usage notes

  • Language Environment does not count severity 0 or 1 conditions toward ERRCOUNT.
  • ERRCOUNT only applies when conditions are handled by a user condition handler, signal catcher, PL/I on-unit, or a language-specific condition handler. Any unhandled condition of severity 2, 3, or 4 causes the enclave to terminate.
  • COBOL consideration: The COBOL runtime library separately counts its severity 1 (warning) messages. When the limit of 256 IGZnnnnW messages is reached, the COBOL runtime library will issue message IGZ0041W, which indicates that the limit of warning messages has been reached. Any further COBOL warning messages are suppressed and processing continues.
  • PL/I consideration: You should use ERRCOUNT(0) in a PL/I environment to avoid unexpected termination of your application. Some conditions, such as ENDPAGE, can occur many times in an application.
  • PL/I MTF consideration: In a PL/I MTF application, ERRCOUNT sets the threshold for the total number severity 2, 3, and 4 synchronous conditions that can occur for each task.
  • C++ consideration: C++ throw does not affect ERRCOUNT.

For more information

For more information about condition handling, see z/OS Language Environment Programming Guide.