|
I thought about that too, John, but since the colon indicates a program variable, so I guess the compiler knows how to translate that. Joel R. Cochran Director of Internet Services VamaNet.com (800)480-8810 mailto:webmaster@vamanet.com > -----Original Message----- > From: Rusling, John B. (Alliance) [mailto:jbrusling@alliancedev.com] > Sent: Friday, August 09, 2002 12:01 PM > To: 'rpg400-l@midrange.com' > Subject: Re: RPG SQL error... > > > Do you need apostrophe's around your date fields? > (top of my head) > > John B. > > I have the following SQL Statement: > > c/Exec SQL > c+ Update VMLOCAXES2 > c+ Set XBEGDATE = :sqlBegDate, > c+ XENDDATE = :sqlEndDate > c+ Where XCLIENT = :clientId and XPACKAGE = :AXLOC > c/End-Exec > > > --__--__-- > > Message: 17 > To: rpg400-l@midrange.com > Subject: Re: RPG SQL error... > From: rob@dekko.com > Date: Fri, 9 Aug 2002 10:54:14 -0500 > Reply-To: rpg400-l@midrange.com > > This is a multipart message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > Unless you have the file journaled you must compile your program with > COMMIT(*NONE) > > Rob Berendt > -- > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." > Benjamin Franklin > > > > > "Joel R. Cochran" <jrc@masi-brac.com> > Sent by: rpg400-l-admin@midrange.com > 08/09/2002 10:45 AM > Please respond to rpg400-l > > > To: "'rpg400-l@midrange.com'" <rpg400-l@midrange.com> > cc: > Fax to: > Subject: RPG SQL error... > > > As if I haven't been messing around with new satuff enough > recently I'm > trying to write my first SQLRPGLE program. I use SQL > frequently in Java > for > JDBC access, so I am not new to it just to doing so in RPG. > > I have the following SQL Statement: > > c/Exec SQL > c+ Update VMLOCAXES2 > c+ Set XBEGDATE = :sqlBegDate, > c+ XENDDATE = :sqlEndDate > c+ Where XCLIENT = :clientId and XPACKAGE = :AXLOC > c/End-Exec > > All variables are populated correctly (according to Debug) > just prior to > executing this statement. I am receiving the following error > information: > > SQLCOD = -7008 > > The description for this is: > &1 in &2 not valid for operation. > > SQLERM = VMLOCAXES2 CGILIB2 > > This is the correct library, so why would the file not be valid for > UPDATE? > Could it have something to do with Commitment control? > > TIA, > > Joel R. Cochran > Director of Internet Services > VamaNet.com > (800)480-8810 > mailto:webmaster@vamanet.com > > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) > mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > 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) > digest list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. > > > > End of RPG400-L Digest > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) > mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. >
As an Amazon Associate we earn from qualifying purchases.
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.