Category
Error checking and debugging
Pragma equivalent
None.
Purpose
Enables programmers to provide LE CEL4CASR, CELHCASR, and __CEL4CASR CWI (compler-writer interface) notifications for each specified function upon function entry.
Syntax
.-NOFUNCEVENT-. >>-+-FUNCEVENT---+----------------------------------------------> >--(--+-ENTRYCALL---+--+-----------------------------+--)------>< '-NOENTRYCALL-' | .-,-----------------. | | V | | '-(------Function name---+--)-'
Defaults
NOFUNCEVENT
Parameters
- ENTRYCALL
- All functions have entry event calls generated.
- NOENTRYCALL
- No functions have entry event calls generated.
- Function name
- Specifies the name of functions that have entry event calls generated or not.
Usage
The FUNCEVENT option is cumulative.
For example, the following specifications have the same behaviour
for a source file that contains functions x, y, and z. Entry event
calls are generated for functions x and y, but not for function z.
FUNCEVENT(NOENTRYCALL(x)) FUNCEVENT(ENTRYCALL(x,y,z)) FUNCEVENT(NOENTRYCALL(z))
FUNCEVENT(ENTRYCALL(x,y))
FUNCEVENT NOFUNCEVENT FUNCEVENT(ENTRYCALL(x, y))
FUNCEVENT(ENTRYCALL(x,y)) FUNCEVENT
NOFUNCEVENT(ENTRYCALL(x,y)) FUNCEVENTThe FUNCEVENT option requires TARGET(zOSV2R1) or a higher level.
If the FUNCEVENT option is specified, the COMPRESS option is forced to NOCOMPRESS.
The FUNCEVENT option is not accepted in METAL C program compilation.
The functionality of this option is an addition to debug hooks and it does not replace function entry or call begin hooks.
Functions that do not occur in the source file but are specified by the option are ignored.
Inlined functions do not have event handler calls.
IPA effects
None.
Predefined macros
None.