How do I debug just one program in Application Server environment?
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't see any code in the debugger, and control won't pass to the debugger.
Run through your application to the program you want to debug. When the runtime starts the program that was compiled with the -d or -dx, it will pass control to the debugger, and you'll be able to step through your code.
DEFAULT DEBUG PORTS SPECIFIED WITH SERVER STARTUP
The default debug ports are 9999 through 10099. Each debug session started will take the next available port. If you have two instances of the Application server running, or if those ports are unavailable, you can change the defaults by setting the "iscobol.as.debugport_range" in the server's properties file, either listing the debug ports:
Or specifying the range by using minimum and maximum port number:
DEBUG PORTS SPECIFIED IN CLIENT COMMAND
If you want to specify a specific port when you run isclient, you can do this with the -debugport option.
Here's an example that specifies port 9090 as the debug port:
iscclient -debugport 9090 -d PROG1
THE EFFECT OF MULTITASKING SETTING
The options above are affected by the value of iscobol.as.multitasking.
The default is 2, which creates two processes, one for clients that connect without the -d and one for clients that use the -d.
This is best for production environments and will allow you to debug without blocking the users. You can use both "iscobol.as.debugport_range" and "-debugport" options listed above
Option 1 creates a separate JVM process for every client, which can cause memory or space problems on a server used for production. You can use both "iscobol.as.debugport_range" and "-debugport" options listed above
Option 0 creates a new thread in the current JVM for every client. "iscobol.as.debugport_range" has no effect with this setting of multitasking and you must use the -debugport option if you want to use a port other than the default 9999.
by: Veryant Support
This question has been viewed 8224 times so far.
Here to View all the questions in Debugging
|There are no attachment file(s) related to this question.
| User Comments
|There are no user comments for this question. Be the first to post a comment. Click Here
| Related Questions
- How do I configure the debugger to find source code that is not in CLASSPATH?
- How do I specify isCOBOL, Java or application properties on the command line?
- Starting a new trace log file for the current run unit
- How to tell the Debugger to pause with a different key than the Pause key?
- Did you know you can see the content of variables while debugging?
- Did you know how to show variables in Debugger using a tree structure?