Re: Problems with old data...really old data.

[Sam_L <lennon_s_j@xxxxxxxxxxx>]

Jim,

My suspicion is that the first time you hit a date before 1940 your 
program thinks you've hit EOF.

I'd guess that you need something like this in your program:
c/exec sql
c+  set option datfmt=*iso
c/end-exec

Check out this article I wrote back in 2007:
http://www.mcpressonline.com/tips-techniques/sql/techtip-sqlcod-end-of-file-gotcha.html


Sam

On 8/19/2015 7:07 AM, James Newman, CDP wrote:
> I have a program which reads FILE1, does some calculations, and writes the
> results to FILE2.  The key on both files is the same - text field (10) and
> date field.  FILE1 contains 24 million records.  FILE1 is accessed via SQL,
> which selects all the data in the file, selects the fields desired, and
> orders the records coming into the program.
>
> When I ran the program I would only get 5,979,168 records in FILE2.  As I
> started to look more closely, the last record in FILE2 was at the same
> point each time - where a set of data begins that has data back to 1915.
> The program was not issuing an error message.
>
> To test my theory that the old data was the problem, I created a set of
> test data without the old data.  The program ran as expected and completed
> processing all 24,000,000 records.
>
> When I do STRSQL and select this old data, I've noticed that SQL shows
> "++++++++" for the date but I figured RPG knew how to handle these old
> dates.  Apparently not.
>
> What do I need to do so RPG can handle the old data?  TIA.
>
>
> Jim Newman