Debugging

NOTE: This information is valid if your programs have been compiled by an isCOBOL version 2020 R1 or earlier. In versions after 2020R1, the source code is included in the class and the debug.code_prefix is not needed. Question: My source code and... Read More

Compile the programs without -d or -dx except for the one you want to debug. Compile the one you want to debug with -d or -dx. Run your program with the -d switch iscclient -d PROG1 Both your application and the debugger will run, but you won... Read More

To specify properties for isCOBOL, Java or the application server on the java, iscc, isrun, iscrun, isserver or iscserver command line, use the -J-D option. For instance: iscc -J-Discobol.compiler.const.const1=1 PROG1 The -J option passes the... Read More

IsCOBOL Debugger offers the ability to show the program's variables in a 'tree structure'. This is very useful when you need to see the content of grouped variables (under 01 level) in Working-Storage or Linkage sections, or FD... Read More

isCOBOL Debugger, starting from the 2016R1 release, automatically shows the Current Variables to easily follow the program execution step by step. As depicted in Figure, Current Variables View, in the right part of Debugger window, an area is... Read More

The Pause key on the keyboard makes the debugger to re-enter in debug mode after a "continue" command has been issued. On some laptops the Pause key is missing from the keyboard, therefore you need to associate the same function to another key. ... Read More

isCOBOL has a feature that will enable you to start a new trace log for the current run unit. When a COBOL program sets "iscobol.logfile" using SET ENVIRONMENT the isCOBOL framework will close the current log and open the new one for the current... Read More