× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: [SQL7008] URLGROUP in TEFF not valid for operation.
  • From: "Shaw, David" <dshaw@xxxxxxxxxxx>
  • Date: Mon, 1 May 2000 12:50:49 -0400

Don,

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.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

> -----Original Message-----
> From: Don [mailto:dr2@cssas400.com]
> 
> Frances,
> 
> I'm no Java guru, but why would the insert(write) or update REQUIRE
> journaling?  This would make Java the only language running 
> on the box tha
> I'm aware of that has this requirement.  Alot of people just don't
> want to deal with journaling....and in alot of cases it's just now
> warranted.
> 
> Please explain...
> 
> tks
> 
> Don in DC
> 
> 
> On Sat, 29 Apr 2000 francess@us.ibm.com wrote:
> 
> > Every time I have seen this message, it is because the file is not
> > journaled (e.g. it wasn't created as part of a collection 
> through SQL;
> > probably was created using DDS).  When using SQL and the 
> default isolation
> > level (or generally any isolation level other than NONE), 
> an insert or
> > update requires that the file be journaled (CRTJRNRCV, CRTJRN, then
> > STRJRNPF).  Sorry for the brevity.
> > 
> > Frances Stewart
> > 
> > 
> > "Joe Teff" <joeteff@earthlink.net> on 04/29/2000 01:50:03 AM
> > 
> > Please respond to JAVA400-L@midrange.com
> > 
> > To:   JAVA400-L@midrange.com, "Ignite400" <ign_list@ignite400.org>
> > cc:
> > Subject:  [SQL7008] URLGROUP in TEFF not valid for operation.
> > 
> > 
> > 
> > 
> > I am connecting to an AS/400 using
> > 
> >    DriverManager.registerDriver(new
> > com.ibm.as400.access.AS400JDBCDriver());
> >    con = 
> DriverManager.getConnection("jdbc:as400://xxx.xxx.xxx.xxx");
> > 
> > <my IP here>
> > 
> > This prompts me for a user id & password and connects. Then 
> I build a
> > listbox with the contents of a file and this works great. 
> When I try to add
> > a record, I get the SQL error. My statement is
> > 
> >    addSql = con.prepareStatement("INSERT INTO TEFF.URLGROUP 
> (R1KEY, R1DESC)
> > VALUES(?, ?)");
> > 
> > In my add logic I do
> > 
> >    try {
> >    addSql.setInt(1, nextKey);
> >    addSql.setString(2, edtField.getText());
> >    addSql.executeUpdate();
> >    }
> > 
> > These are the only two fields in the file. I use an SQL 
> statement prior
> > to the add that gets MAX(R1KEY) and I add 1 to that. I've 
> printed this
> > value to the console and it is correct.
> > 
> > I checked security and everything looks fine. I can't find any
> > documentation
> > on this SQL error except that the SQL State is 55019. Can 
> anyone help me
> > here or at least point me in the right direction. Thanks.
> > 
> > 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.