Re: source line # in a dump for an SQLRPGLE pgm

That is what I mean - the compiler statement numer, not the source line
number. What you probably have is the line number in the program object
as understood by OS/400, not the line number in the source as understood
by you. These two things are not one and the same. I don't know how to
relate one to the other.

The line number in error is probably not the READE. Look for EVALs and
other RPG 4 op codes in your code that could result in a numeric
overflow. The answer is out there.

If you could reproduce the error (in test mode) for the data that was
being processed at that time, then debug can be used to find the
location of the error.

Syd Nicholson


rich herdman wrote:

>The problem is that the compiler statement # is a READE (that was the first 
>thing I
>checked).
>
>I don't see how I could get that message on a READE statement, espesciallyif 
>the file is extrernally described.
>
>
>On Mon, 18 Mar 2002 16:31:33 +0000, Dr Syd Nicholson wrote:
>
>>The line number is probably the compiler statement number not the source
>>line number in error. It can help if you compile programs with
>> OPTION(*SRCSTMT). This allows the source statement number to be included
>>in program messages, debug, etc.
>>
>>Syd Nicholson
>>