|
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, espescially if 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 > > > >rich herdman wrote: > >>Help!!! >> >>I have a fairly long-running RPG program that had a 'The target for a numeric >operation >>is too small to hold the result" message over the weekend. The program is an >SQLRPGLE >>program (no modules or anything - just a regular RPG 4 pgm w/ some embedded >SQL). It >>is running on a system running V5R1. However, the object was originally >compiled under >>V4R3 and has run every weekend since 03/05/2000 with no problems. >> >>Anyways, I dumped the program to get the statement # that it blew up on. The >problem is that >>I don't think the line number is right. The statement in error is 804, and >the program is only >>642 lines long. In the compile listing, line 804 refers to a READE statement >on a file. >> >>First question: is it even possible to get a 'target too small' on a READE? >The program does not >>redefine any if the fields in that file and the file has not been modifed. >> >>Secondly, how can I get the line # it actually blew up on? Should I >recompile it under V5R1 and >>let it run until it blows up again and hope I get the right number this time? >> >> >> Rich Herdman email: rherdman@columbus.rr.com www: http://home.columbus.rr.com/herdman/ "It never does to leave a live Dragon out of the equation." - Bilbo Baggins, 'The Hobbit'
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.