[COBOL400-L] Re: STRISDB and COBOL

[Simon Coulter <shc@xxxxxxxxxxxxxxxxx>]

On Saturday, January 31, 2004, at 09:04  AM, Brown, Keith wrote:

>         Thanks for the fast response to my inquiry about getting 
> CBLSQL program to work with STRISDB.  Have you actually been able to 
> do this?  I compiled with the option *LSTDBG and still get the same 
> message when I try execute STRISDB for the program; message is " 
> Program MKCB0202 was not compiled with the correct compiler."

You should ask follow-up questions on the list. That way everyone will 
benefit from the answer.

It would seem your question wasn't clear. Although the title says 
Interactive Source Debugger both Bruce and I thought you meant the 
normal system debugger (STRDBG).

STRISDB requires that OPTIONS(*SRCDBG) was specified when compiling 
COBOL programs however it does not need this option for CL or RPG. That 
is what made me think you were asking about the system source debugger. 
I have never used ISDB to debug COBOL and I gave up on it for 
everything else many years ago--mostly because I use ILE languages for 
all my HLL code.

The system debugger has provided support for OPM source since at least 
VRM420. As a result ISDB has been stabilised--it hasn't changed since 
VRM310. You should be using the system source debugger unless you are 
still on an ancient version of OS/400 in which case you have other 
problems. You have two options:

1. Compile your SQL COBOL source using CRTSQLCBL and specify 
OPTION(*LSTDBG), then start debug using STRDBG your-program OPMSRC(*YES)

2. Change the source type of your program from SQLCBL to SQLCBLLE and 
compile the source using CRTSQLCBLI and specify DBGVIEW(*SOURCE), then 
start debug using STRDBG your-program

Note that changing the source type will put you in ILE where you may 
need to give some consideration to environmental changes. However ILE 
is where IBM is providing language improvements and therefore it is 
where you should be too. None of the OPM languages, except possibly CL, 
can expect language enhancements.

If you **really** want to use ISDB then you can perform a two-stage 
compile by specifying the name of the output file on the CRTSQLCBL 
command and also specify OPTION(*NOGEN) so only the pre-compile step is 
performed. Then you can run the CRTCBLPGM against the generated output 
(specify OPTION(*SRCDBG) which will cause the program object to contain 
the information ISDB requires.

This seems such an awkward approach that you would be better off 
specifying OPTION(*LSTDBG) on the CRTSQLCBL command and the using the 
STRDBG command with OPMSRC(*YES). The advantage to this is that you 
will be using the same debugger as that for ILE programs thus preparing 
you for the move to ILE COBOL.

NOTE! My system is currently doing its weekly backup so I cannot verify 
the command parameters but an assiduous check of the prompted command 
and help text will let you determine the correct values.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------