What about debugging? Have you found an easier way?
Posted: Fri Apr 23, 2010 3:03 pm
Question:
What about debugging? Have you found an easier way to do that? Traditional CGI debugging is sometimes painful, though SEP's in RDi have helped that.
Answer:
There are a few ways that you can debug Profound UI applications. From a 5250 command line, you can use STRSRVJOB and STRDBG on the programs. This would normally be challenging to set up because your program will run in a new batch job when you call it.
However, our session controller provides a debug flag that you can launch with, which automatically holds up the batch job with an inquiry message before launching your application. If you look at the inquiry message, it contains the necessary info for the STRSRVJOB command. You can enter this command, and then STRDBG. Then, all you have to do is set a breakpoint in your program and reply to the inquiry message to allow your program to run.
You can also use the debuggers supplied with WDSc and RDi, and also the stand-alone System Debugger application. The easiest way to use these debuggers with Profound UI is to use Service Entry Points, which allow the debuggers to activate based on the user profile that is running the program, rather than the job which it is running in.
What about debugging? Have you found an easier way to do that? Traditional CGI debugging is sometimes painful, though SEP's in RDi have helped that.
Answer:
There are a few ways that you can debug Profound UI applications. From a 5250 command line, you can use STRSRVJOB and STRDBG on the programs. This would normally be challenging to set up because your program will run in a new batch job when you call it.
However, our session controller provides a debug flag that you can launch with, which automatically holds up the batch job with an inquiry message before launching your application. If you look at the inquiry message, it contains the necessary info for the STRSRVJOB command. You can enter this command, and then STRDBG. Then, all you have to do is set a breakpoint in your program and reply to the inquiry message to allow your program to run.
You can also use the debuggers supplied with WDSc and RDi, and also the stand-alone System Debugger application. The easiest way to use these debuggers with Profound UI is to use Service Entry Points, which allow the debuggers to activate based on the user profile that is running the program, rather than the job which it is running in.