Derivation: ABnormal PERColation
ABPERC
percolates an abend whose code you specify. This provides
Language Environment condition
handling semantics for all abends, except for the one specified. TRAP(ON)
must be in effect. When you run with ABPERC and encounter the specified
abend:
- User condition handlers are not enabled.
- Under z/OS UNIX,
POSIX signal handling semantics are not enabled for the abend.
- No storage report or runtime options report
is generated.
- No Language Environment messages
or Language Environment formatted
dump output is generated.
- The assembler user exit is not driven for enclave termination.
- The abnormal termination exit, if there is one, is not driven.
- Files that are opened by HLLs are not closed by Language Environment, so records
might be lost.
- Resources that are acquired by Language Environment are not
freed.
- A debugging tool, if one is active, is not notified of the error.
Tip: You can also use the CEEBXITA assembler user
exit to specify a list of abend codes for Language Environment to percolate.
For more information about CEEBXITA, see z/OS Language Environment Programming Guide.
The
default value for non-CICS applications is ABPERC(NONE).
ABPERC
is ignored under CICS®.
Syntax
.-NONE---.
>>-ABPerc--(--+--------+--)------------------------------------><
'-abcode-'
- NONE
- Specifies that all abends are handled according to Language Environment condition
handling semantics.
- abcode
- Specifies the abend code to percolate. The abcode can
be specified as:
- Shhh
- A system abend code, where hhh is the
hex system abend code
- Udddd
- A user abend code, where dddd is a decimal
user abend code. Any 4-character string can also be used as dddd.
z/OS® UNIX consideration
ABPERC
percolates an abend regardless of the thread in which it occurs.
Usage notes
- Language Environment ignores
ABPERC(S0Cx). In this instance, no abend
is percolated, and Language Environment condition
handling semantics are in effect.
- You can identify only one abend code with this option. However,
an abend U0000 is interpreted in the same way as S000.