|
As I am getting ready to update one of my systems to V5R3 I am reviewing the support of this product - which is dead and has been for a while. While I'm trying to track down some sort of official missive so I can pass it on to the development group I am wondering what do other people use? I'm sure they will ask for options - beyond saying use the native debugger or use the native WDSC are there any other alternatives?
There's the green-screen debugger (STRDBG)There's the iSeries System Debugger (this is a GUI Java program that runes on the PC, but debugs stuff on the iSeries, and it also can be invoked with STRDBG)
There's the CODE/400 debugger. There's the WDSC debugger.There's also STRISDB (though, it only works for obsolete languages, so I don't recommend it.)
So, there are 5 different debuggers that come with the iSeries (or, with the WDS product, which you'd need for the RPG/COBOL/C compilers, anyway). None of them are satisfactory to your programmers?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
