RE: [SQL7008] URLGROUP in TEFF not valid for operation.

Joe,

The only thing I can think of is the same as what Pete Hall suggested - a
difference in the commitment control level due to an override of the
defaults somewhere along the way.  If you have interactive SQL on your
system, you might get some better diagnostics if you run your SQL statements
from it.  Good luck!

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

> -----Original Message-----
> From: Joe Teff [mailto:joeteff@earthlink.net]
> 
> >By default, SQL updates and inserts on the /400 require
> >commitment control, which in turn requires journalling.  This
> >doesn't have anything to do with Java, per se, since the
> >same behavior occurs with any language that invokes SQL
> >to do its database work.  In my opinion, AS/400 programmers
> >and administrators need to get over their irrational fear of
> >database journalling - it doesn't cost all that much any more,
> >and it enables some wonderful capabilities.
> 
> I use jounalling frequently and am a big proponent of it. OTOH,
> there are plenty of situations where journalling is just not
> necessary. What I don't understand about this particular
> situation is that I am using another file the exact same way
> that is also not journaled and everything works fine. Why would
> it matter for one file and not another?
> 
> Joe Teff
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---