The way in which you initiate Debug Tool is different for Enterprise COBOL programs. When you use Debug Tool, the application program starts first and the Language Environment TEST runtime option controls the invocation of Debug Tool. (With VS COBOL II, you are required to invoke COBTEST first; it then starts the application to be debugged.)
You can also invoke Debug Tool directly from your application by using the Language Environment callable service CEETEST. A brief description of these two methods follows.
The IBM-supplied default is NOTEST. This specifies that Debug Tool is not to be initialized to process the initial command string nor is it to be initialized for any program condition that might arise when you run the program. However, if debugging services are needed, you can invoke Debug Tool by using the library service CEETEST.
For detailed information on the Language Environment TEST option subparameters and suboptions, see Language Environment Programming Reference.
When using CEETEST to invoke Debug Tool, the string parameter containing a command list is optional. If you do use a command list, the commands are passed to Debug Tool and executed. If the command list does not contain any GO, GOTO, STEP, or QUIT commands, commands will then be requested from the terminal or the primary commands file. If the GO command is encountered at any point (command list, terminal, or commands file), Debug Tool returns to the application program at the point following the service call and your program continues running.
For detailed information and examples of the Language Environment callable service CEETEST, see Language Environment Programming Reference.