RE: DATE field wont accept value '1902-01-01'

Thanks! Problem resolved!
Igor Bešlić, dipl. ing. rač. 
VOLKSBANK d.d.
OJ Informatika
Varšavska 9, 10000 Zagreb
tel: +385 1 4801 895



"Tyler, Matt" <mattt@xxxxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
13.01.2006 00:36
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
RE: DATE field wont accept value '1902-01-01'






Igor,
                 In STRSQL, press F13 and then select option 1.  Look for 
that date format.  Change it to anything but *MDY or *YMD.  The system has 
a problem showing dates out side the range of 1940 to 2039 in short date 
formats. 

                 Since you do not mention who you import in to MSSQL, I 
will assume you are using an ODBC connection (probably IBM's?) to connect 
and get the data. You have to also specify the date format for the 
connection.  If you have client access, it has a MS Excel connection piece 
that allows you to test ODBC type transfers. 

Thank you,
Matt Tyler
WinCo Foods, LLC
mattt@xxxxxxxxxxxxxx


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] 
On Behalf Of Igor.Beslic@xxxxxxxxxxxx
Sent: Thursday, January 12, 2006 4:10 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: DATE field wont accept value '1902-01-01'

Hi all!

I have weird behaviore of DDS defined DATE field so I need help.

In DDS described PF field is defined as follows:

A            DATUMFILE       L         DATFMT(*ISO)


In RPG in control spec I coded DATFMT(*ISO) and I have defined

D datum0          S               d   inz(D'1902-01-01')

variable to hold default value in case that DATUMFILE field value can't be 

calculated.

Thi is example of code where DATUMFILE is evaluated:

/free
....
....
        If datumOK;
                DATUMFILE=calculatedDate;
        Else;
                DATUMFILE=datum0;
        EndIf;
....
....
        write record;
....
/end-free

After procession well calculated dates have expected values but, at other 
side, dates evaluated with datum0 are represented (in SQL) with ++++ 
signs. *ISO date year has range 0001-9999 so I can't gess why default 
dates aren't displayed correctly. What is more confusing when thise dates 
are importted to DB table on MS SQL server, all ++++ dates on DB2 has 
0001-01-01 value on MSSQL.

Is it possibile that some system definition overrides program and DDS 
definitions maybe? My Admin says that RPG and DDS datum format definitions 

have higher priority than system definitions?!

Anyway is there something I missed?? The code is pretty trivial (as you 
see from example) so I can't figure why I cant get right value.

Thanks!
Igor Bešlić, dipl. ing. rač. 
VOLKSBANK d.d.
OJ Informatika
Varšavska 9, 10000 Zagreb
tel: +385 1 4801 895