× 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.



This command also shows the cause of the SQL7008 error:

DSPMSGD RANGE(SQL7008) MSGF(QSQLMSG)

Bruce

----- Original Message -----
From: <P.Goovaerts@Clipper.Be>
To: <java400-l@midrange.com>
Sent: Thursday, October 11, 2001 6:05 AM
Subject: Re: AS400-DB2-JAVA SQLException error -7008 (solved)


>
> After 4 day's of searching, writing mails, trial and tests... I found the
> reason right under my nose...  I decided to try emulate the problem in
> VAJAVA with Debugger.  This allowed me to find and read the complete
> errordescription and explanation of this code 7008.    Error SQL7008,
cause
> (3) : JOURNALLING!
>
> Yes, I never work on productionlibs directly when creating new
> applications.  Surely not when it's in a domain which I'm still learning
> (only working on it for a year...) and which is so complex as the whole
> internet/intranet application development.  In other words : Java, Html,
> SQL, Application Server, VAJAVA, Studio,...  I created a testfile in a
> testlib on our AS400.  These are not journalled and therefore I cannot
> update records in these files without commit(true) !
>
> And, believe this or not...
> When I was moving my lib and files in a journalled environment, I got a
> message from Bruce Jin asking me if this file was journalled!  grrrrrr....
> Should have put this question into java400-l@midrange.com 4 day's
> earlier...
>




As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.