There are several considerations that you must make when you debug programs that do not run under the Language Environment. Some of these are unique to programs that contain no Language Environment routines, others pertain only when the initial program does not execute under control of the Language Environment, and still others apply to all programs that have mixtures of non-Language Environment and Language Environment programs.
Refer to the following topics for more information related to the material discussed in this topic.
When Language Environment is not active, you can debug only assembler, disassembly, or non-Language Environment COBOL programs. Debugging programs written in other languages requires the presence of an active Language Environment.
If the initial program that is invoked does not run under Language Environment, and you want to begin debugging before Language Environment is initialized, you must use the EQANMDBG program to start both Debug Tool and your user program.
You do not have to use EQANMDBG to initiate a Debug Tool session if the initial user program runs under control of the Language Environment, even if other parts of the program do not run under the Language Environment.
When you use EQANMDBG to debug an assembler program that creates a COBOL reusable runtime environment, Debug Tool is not able to debug any COBOL programs. You can create a COBOL reusable runtime environment in one of the following ways:
Refer to the following topics for more information related to the material discussed in this topic.
The non-Language Environment assembler or non-Language Environment COBOL program that you specify in a DTCN or CADP profile that starts a debugging session must be one of the following: