RE: **Debug options**

Hi Scott,

I am not sure, I understood you clearly, when you said putting the compile
listing in the program object. Also is there any need to debug a program
after it is moved to production. What I mean is we move a program to
production only after removing the errors. ( that is won't there be only run
time errors - if at all- any when the  program is into production ).

Sunil



-----Original Message-----
From: Scott Mildenberger [mailto:Smildenber@Washcorp.com]
Sent: Thursday, June 13, 2002 8:17 PM
To: 'rpg400-l@midrange.com'
Subject: RE: **Debug options**


Sunil,

The *list debug option puts the compile listing inside the program object
for debugging.  One benefit that we take advantage of is being able to debug
the object without the source being available.  As we have one development
machine and several production machines this makes it easier to debug
programs on the production machines.

Scott Mildenberger

> -----Original Message-----
> From: Sunil Ramakumar [mailto:Sunil_Ramakumar@USSWI.COM]
> Sent: Thursday, June 13, 2002 8:33 AM
> To: 'rpg400-l@midrange.com'
> Subject: **Debug options**
>
>
> Hai,
>       I am bit of a novice to RPG. I would like to know where
> and why do
> we use the various debug options.
> I always use the option *stmt when compiling and *source when
> debugging. I
> would like someone to tell me why we use the other options
> namely *list,
> *copy *all and *none.
> I was able to understand something regarding *copy *all and
> *none. But I
> have not understood what and where *list is for.
> Can somebody help me.
>
> Sunil
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.