Re: SQL loval date/timestamp

[rob@xxxxxxxxx]

Then go with the flow.  Have you tried:
     C/EXEC SQL
     C+ Set Option
     C+     DatFmt    = *Iso,
     C+     Naming    = *Sys,
     C+     Commit    = *None,
     C+     UsrPrf    = *User,
     C+     DynUsrPrf = *User,
     C+     CloSqlCsr = *EndMod
     C/END-EXEC

This is the precompiler's version of the H spec.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Schadd Gray" <list@xxxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
10/14/2003 11:03 AM
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: SQL loval date/timestamp






Joel,

I have ran into this issue and the only solution that has worked for me is
to prompt the compile and change the parameter DATFMT to *ISO.  In my 
shop,
I changed the command default so I would not have to remember to do this
every time.

Adding DATFMT(*ISO) to the H spec does not help because it is the
precompiler that is causing the issue and it does not look at the H specs.

Schadd Gray
Damon Technologies, Inc.

----- Original Message ----- 
From: "Joel Cochran" <jrc@xxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, October 14, 2003 6:41 AM
Subject: RE: SQL loval date/timestamp


> I've tried that but with no effect, I still get SQLState = '22008'.
>
> Still churning...
>
> Joel
> http://www.rpgnext.com
>
> On Tue, 2003-10-14 at 15:01, DeLong, Eric wrote:
> > Joel,
> > Can you simply add DATFMT(*ISO) to your Control spec (H)?
> >
> > Eric DeLong
> > Sally Beauty Company
> > MIS-Project Manager (BSG)
> > 940-898-7863 or ext. 1863
> >
> >
> >
> > -----Original Message-----
> > From: Joel Cochran [mailto:jrc@xxxxxxxxxx]
> > Sent: Tuesday, October 14, 2003 4:31 AM
> > To: RPG programming on the AS400 / iSeries
> > Subject: RE: SQL loval date/timestamp
> >
> >
> > Here is the basic layout of the program in psuedo-code:
> >
> > d mainDS        e ds                  extname( MYFILE )
> >
> >  // prepare and declare the cursor...
> >
> > c/exec SQL
> > c+  fetch next from mainCursor into :mainDS
> > c/end-exec
> >
> > The layout of MYFILE includes a Date field (defined as "L" in the 
DDS).
> > Since Date fields themselves do not have data types this should not be
> > an issue.
> >
> > Just to be sure I checked the compiler settings for CRTSQLRPGI and
> > DATFMT is *JOB.  Since the system always defaults to *ISO I assumed 
that
> > so would the program ... BUT ... when I DSPSYSVAL(QDATFMT) it says 
that
> > the value is MDY.  In fact, the option list doesn't even include ISO.
> >
> > I think this must be the problem, maybe I need to specify *ISO when I
> > create an SQLRPG module.  This is something you do not have to do in
> > RPGIV, so to say this bothers me a little is an understatement.  I'm
> > going to try and test this some more today and I'll share the results.
> >
> > Thanks Eric,
> >
> > Joel
> > http://www.rpgnext.com
> >
>
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing 
list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.