Re: *ISO date in COBOL?

Copied the data as you suggest - same error, same bogus record number (there
are only 864774 record in the file).

TomH

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Friday, November 29, 2013 6:14 PM
To: cobol400-l@xxxxxxxxxxxx
Subject: Re: [COBOL400-L] *ISO date in COBOL?

On 29-Nov-2013 08:06 -0800, Tom Hightower wrote:

<<SNIP>>
The date field in record number 4294967295 is: 2013-05-20

The error message:

Rewritten partially in symptom kwd form: msgCPF5035 rc17

Presumably that error was followed by a CPF5029 with all of the same
information for its replacement variables?

17 -- The format of the data in a date, time, or timestamp field is
not valid.
<<SNIP>>

The numeric value 4294967295 is 2**32-1 which is larger than the largest
possible Relative Record Number (RRN); i.e. the internal representation of a
special value [intended to be] represented by the value -1, is instead
presented as that large 4-billion-plus number. The claim of what data is in
the diagnosed row number, is obviously flawed; i.e. no such row number is
possible.

I do not recall what the value -1 implies. The value for Record Number
of 0 implies that the operation was an insert [put] into the file.

If you create new files, copy the data to the new files, and then run the
program against the new version of those files with the copied data, does
the problem persist?

--
Regards, Chuck
--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L)
mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/cobol400-l.