Here's the compile command I'm using...

CRTSQLRPGI OBJ(NHP09/NHBLDCLS)
SRCFILE(NHP09/QRPGLESRC)
SRCMBR(NHBLDCLS)
COMMIT(*NONE)
OBJTYPE(*PGM)
CLOSQLCSR(*ENDMOD)
REPLACE(*NO)
DBGVIEW(*SOURCE)
USRPRF(*OWNER)
DYNUSRPRF(*OWNER)

And I added the DatSep in the Set Option command because it defaulted to '/'
when I looked at the PRTSQLINF results. So, I added the DATSEP option to
make sure it was a dash.

I am populating this date field with the %date() command. Could that be
doing something other than I'm assuming?

Tom Garvey


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Luis Rodriguez
Sent: Monday, July 09, 2012 3:49 PM
To: Midrange Systems Technical Discussion
Subject: Re: SQL0180 on SQL insert

Thomas,

What have you in your COMPILEOPT specs (RPG's, not SQL's). BTW, IIRC if you
specify DATFMT = *ISO, the DatSep is unnecessary..

Regards,
Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.