Hello all!
I have a problem that I didn't have with version 6 of WDSC. I have to maintain OPM COBOL programs. When I compile for debugging, I liked to use the *LSTDBG option instead of *SRCDBG. By using *LSTDBG, I could debug my COBOL code on the output listing. This was extremely useful, because it allowed me stepping through copybooks and seeing other compiler-generated information (e.g., statement number).
However, starting version 7, the environment default (actually, forces you) to use the option *SRCDBG.
I can't specify *LSTDBG any more. If I prompt the compile option and remove the default option *SRCDBG and replace it with *LSTDBG, it will add the *SRCDBG option after I submit the compilation.
The result is nasty, because I get an error saying something like *SRCDBG and *LSTDBG can't be used at the same time, so the compiler just compiles without debugging information.
I also tried to edit the compile command, but WDSC still adds the *SRCDBG option.
Is there a way to get rid of the *SRCDBG option when compiling?
Thank you all!
Luis
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Wednesday, January 30, 2008 10:18 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] IBM Rational Developer for System i V7.1
Trevor Perry wrote:
Jon,
Would it be prudent for IBM to offer to run CVTRPGSRC over all of JDE's code
for them? I know there are some logistics issues for delivery, etc... but
for a small amount of effort by IBM, a large number of JDE customers could
be moved away from the legacy compilers?
Just a small PR investment could positively impact our community??
Trevor
If IBM does indeed decide to make a modernization center, I'd like to
see this as one of their pilot projects.
However, remember that many of these shops will have large amounts of
customized code, and so all of that code will need to be converted as
well, and I don't think IBM will want to do all of that for free.
Joe
midrange.com
