AW: CRTSQLRPGI errors out with DBGVIEW(*SOURCE) but passes with DBGVIEW(*NONE)

Hi,

to make it easier (and not to forget it the next time you'll recompile your
program), you may add it in an SET OPTION statement at the beginning of your
C-Specs.
If there is already a set option statement in your program, just add the
compile option:

C/Exec SQL Set Option CompileOpt('DBGVIEW(*SOURCE')
C/End-Exec

But to use CompileOpt you need at least release V5R3 (or even V5R4).

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Barbara Morris
Gesendet: Thursday, 17. September 2009 21:57
An: rpg400-l@xxxxxxxxxxxx
Betreff: Re: CRTSQLRPGI errors out with DBGVIEW(*SOURCE) but passes with
DBGVIEW(*NONE)

(From: "Jszarlik" <jszarlik@xxxxxx>)

I found calling command CRTSQLRPGI and changed DBGVIEW(*SOURCE) for
DBGVIEW(*NONE) and the all is OK.
But I have to debug this program to find error.

How to compile with DBGVIEW(*SOURCE)?

Jarek, you could try compiling this way:

CRTSQLRPGI COMPILEOPT('DBGVIEW(*SOURCE)')

That would let you debug from the intermediate source file that the SQL
precompiler generates. DBGVIEW(*SOURCE) for the CRTBNDRPG step of the
compile produces the smallest possible debug information.

By default, the intermediate source file is placed in QTEMP. If you
want to debug the program from another job, you should also specify the
TOSRCFILE parameter for CRTSQLRPGI so that the intermediate file goes
into a permanent library.

CRTSQLRPGI TOSRCFILE(mylib/myfile) COMPILEOPT('DBGVIEW(*SOURCE)')