To debug a Web application created in COBOL using the debugger, start the debugger from the program to be debugged.
The Web application can be remotely debugged from the client which starts a WWW browser by using a remote debugger. Please refer to "NetCOBOL Debugging Guide" for the usage of a remote debugger.
Note the following points when you debug a Web application using the debugger because IIS reads and invokes Web applications in the same memory space.
If a Web application performs an invalid operation, not only the Web application becomes abnormal but also other Web applications loaded at the same time or even IIS may become abnormal. It is recommended that you first debug a Web application while no other Web application is loaded and then later do so while some other Web applications are loaded.
The debugger debugs not only a Web application but also other Web applications and even IIS. Since terminating the debugger also terminates other Web applications and IIS, you must restart IIS.
IIS provides ways of operating a Web application in the memory space of IIS (IIS process) or in a different memory space than IIS (isolated process or pool). Specifying a Web application as an isolated process or pool eliminates the above problem, thus facilitating the debugging process.
Note
For IIS 7.0 or later, in order to run a Web application created in COBOL it is necessary to create an application pool. Please refer to the IIS Configuration steps (In case of IIS 8.5) and create application pool.
Neither the just-in-time debugging function nor the COBOL Error Report is tripped by an application error occurring in a Web application, which is detected and handled by IIS instead.
