Re: General Debugging Question

It disappears, the problem does not manifest itself after debugging.

It happened both in online and batch. For example, an RPG program was
reading all records in a file, so I created a logical, and I only wanted
the  last 30 days of records, so I added a subdur on the date and used the
result as the SETLL. Yet the output was listing records beyond the 30
days.

Then after putting it through a debugging, the output was blank, as it
should have been.

I also saw this w/ subfile programs, where a program would hang, and then
just correct itself after being in debug.

I would not post this, but I have never seen anything remotely like this
ever.
> steema@xxxxxxxxxxxxx wrote:
>> ON more than one occassion I have noticed a problem in  a program, that
>> will disappear after I have debugged the program. Is this rational, or
>> there must be some other explanation?
>
> Disappear entirely after debugging ... or just not manifest when
> debugging?
>
> I've had situations where I can't get a problem to manifest while
> debugging ... but I've never had a problem go AWAY after debugging
> (unless, of course, I fixed it as part of the debug <grin>).
>
> david
>
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>