AW: Dates Higher Than 2050?

Hi,

the SQL precompiler creates for each host variable used in an SQL statement
an additional variable.
For date fields the precompiler does not consider the H-Specs but adopt the
date format either specified in the compile command or in a SET OPTION
statement.
The default date format is *JOB, which normally uses a 2 digit year.
The valid range for a 2 digit year date is between 01/01/1940 and
12/31/2039.

If you either specify date format *ISO, *USA, *EUR or *JIS in the compile
command or add a SET OPTION statement with
C/EXEC SQL Set Option DatFmt = *ISO
C/End-Exec
To your source code, the valid range for dates will be between 01/01/0001
and 31/12/9999.

When using a SET OPTION statement, keep in mind the SET OPTION Statement
must be physically the first SQL statement within your source.
And only a single SET OPTION statement is allowed.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Mike
Gesendet: Monday, 20. July 2009 20:15
An: RPG programming on the AS400 / iSeries
Betreff: Dates Higher Than 2050?

I have an SQLRPGLE program that I have inserted some test data. Originally I
used the year 2999, then I tried 2100, then 2050. Both cause:

Data mapping error on member CCEVMASTP.
Value in date, time, or timestamp string not valid.

I then set it to 2029 and it works. I assume it is something to do with the
2-digit year conversion. But both the field in the file and in the program
are defined as a date.

In the h-specs I added datfmt(*iso). Any ideas?