Re: SQL loval date/timestamp - RESOLVED

[Joel Cochran <jrc@xxxxxxxxxx>]

This is just a quick recap and closure for this issue for the archives:

To prevent getting SQLSTT = '22008', Date or timestamp invalid errors
for dates in the database less then 1940-01-01, I had to change the
DATFMT option of the CRTSQLRPGI command to *ISO.  Otherwise it reads the
SYSVAL for DATFMT which is MDY (and doesn't even have an ISO option).

This could be accomplished three ways:

1.  Prompt the command every time and change it.  - Unacceptable, my
memory isn't that good.

2.  Change the command default.  - Not bad but I have to manage those
changes across different boxes and reinstate them when versions change.

3.  Add an SQL "Set option" block to the source code.  -  Great!  Like
an H-Spec, since it is in the code it should always be set at runtime.

I took this a step further and put the Set Option block in a /copy book
so that I can use it again and again with a single entry point for
future changes. - Thanks Rob for confirming this for me.

Thanks to all who responded.

Joel
http://www.rpgnext.com