Debugging user programs that use system prefixed names
z/OS® Debugger assumes that load module and compile unit names that begin with specific prefixes are system components. For example, EQAxxxxx is a z/OS Debugger module, CEExxxxx is a Language Environment® module, and IGZxxxxx is a COBOL module.
z/OS Debugger does not try to debug load modules or compile units that have these prefixes for the following reasons:
- z/OS Debugger might perform improper recursions that might result in abnormally endings (ABENDs) or other erroneous behavior.
- z/OS Debugger assumes users do not have access to the source for these load modules and library routines.
- Creating debug information for these routines would waste significant amounts of memory and other resources.
If you have named a user load module or compile unit with a prefix
that conflicts with one of these system prefixes, you can use the NAMES
INCLUDE
command and the instructions described in this section
to debug this load module or compile unit.
IMPORTANT: Do not use the
NAMES
INCLUDE
command to debug system components (for example, z/OS Debugger, Language Environment, CICS®, IMS,
or compiler run-time modules). If you attempt to do debug these system
components, you might experience unpredictable failures. Only use
this command to debug user programs that are named with prefixes
that z/OS Debugger recognizes
as system components.