PL/I conditions and condition handling

All PL/I conditions are recognized by z/OS® Debugger. They are used with the AT OCCURRENCE and ON commands.

When an OCCURRENCE breakpoint is triggered, the z/OS Debugger %CONDITION variable holds the following values:

Triggered condition	%CONDITION value
`AREA`	`AREA`
`ATTENTION`	`CEE35J`
`COND ( CC#1 )`	`CONDITION`
`CONVERSION`	`CONVERSION`
`ENDFILE ( MF )`	`ENDFILE`
`ENDPAGE ( MF )`	`ENDPAGE`
`ERROR`	`ERROR`
`FINISH`	`CEE066`
`FOFL`	`CEE348`
`KEY ( MF )`	`KEY`
`NAME ( MF )`	`NAME`
`OVERFLOW`	`CEE34C`
`PENDING ( MF )`	`PENDING`
`RECORD ( MF )`	`RECORD`
`SIZE`	`SIZE`
`STRG`	`STRINGRANGE`
`STRINGSIZE`	`STRINGSIZE`
`SUBRG`	`SUBSCRIPTRANGE`
`TRANSMIT ( MF )`	`TRANSMIT`
`UNDEFINEDFILE ( MF )`	`UNDEFINEDFILE`
`UNDERFLOW`	`CEE34D`
`ZERODIVIDE`	`CEE349`

Note: For Enterprise PL/I programs, the following condition is not supported:

AT OCCURRENCE CONDITION conditions (name)

Note: The z/OS Debugger condition ALLOCATE raises the ON ALLOCATE condition when a PL/I program encounters an ALLOCATE statement for a controlled variable.

These PL/I language-oriented commands are only a subset of all the commands that are supported by z/OS Debugger.