Derivation: ERRor COUNTer
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, no further Language Environment condition
management, including CEEHDLR management, is honored.
- Non-CICS default
- ERRCOUNT=((0),OVR)
- CICS® default
- ERRCOUNT=((0),OVR)
Syntax
.-OVR----.
>>-ERRCOUNT--=--(--(--number--)--,--+-NONOVR-+--)--------------><
- number
- The number of severity 2, 3, and 4 conditions per individual thread
that can occur while this enclave is running. If the number of conditions
exceeds number, the thread and enclave terminate
abnormally.
- OVR
- Specifies that the option can be overridden.
- NONOVR
- Specifies that the option cannot be overridden.
z/OS® UNIX considerations
Synchronous
signals that are associated with a condition of severity 2, 3, and
4 do not affect ERRCOUNT. Asynchronous signals do not affect ERRCOUNT.
Usage notes
- ERRCOUNT(0) means that the Language Environment condition
handler will not terminate the task regardless of the severity 2,
3, or 4 conditions that are generated. This setting allows previously
existing infinite loop or runaway task conditions to persist.
- ERRCOUNT only applies when conditions are handled by a user condition
handler, signal catcher, PL/I on-units, or a language-specific condition
handler.
Language Environment does
not count severity 0 or 1 messages. However, the COBOL specific runtime
library does count its severity 1 (warning) messages. When the limit
of 256 IGZnnnnW messages is reached, the COBOL library issues message
IGZ0041W, which indicates that the limit of warning messages was exceeded.
Any further COBOL warning messages are suppressed.
- C++ considerations
- The ERRCOUNT option sets the threshold for the total number of
severity 2, 3, and 4 synchronous conditions that can occur. Note that
each thrown object is considered a severity 3 condition. However,
this condition does not affect ERRCOUNT.
- PL/I considerations
- 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 your application.
- PL/I MTF
considerations
- 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. If
the number of conditions exceeds the threshold, the application terminates
normally.