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



Gary,
Did you ever get this resolved? I've been struggling with a very similar
problem. I'm trying to update a linked Microsoft Access table and I get the
SQL7008 unless the file is journaled. I've changed the commit mode to Commit
immediate (*None) but I still get the SQL7008. I've done a lot of testing and
the only thing that works is journaling, which is not an option
What were your results?
Thanks,
Bryan Burns
ECHO, Incorporated

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Gary Segal
Sent: Wednesday, March 21, 2007 2:03 PM
To: Midrange Systems Technical Discussion
Subject: RE: ODBC Connection Error - "[IBM][iSeries
AccessODBCDriver][DB2UDB]SQL7008 - "FedV0001" in QGPL not
validforoperation. (#-7008)"


WHERE WOULD I CHANGE COMMITMENT CONTROL? I did not see any options for that?
Never had to deal with it before.
Thanks


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]
On Behalf Of Elvis Budimlic
Sent: Wednesday, March 21, 2007 12:11 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: ODBC Connection Error - "[IBM][iSeries Access
ODBCDriver][DB2UDB]SQL7008 - "FedV0001" in QGPL not valid foroperation.
(#-7008)"

Finally a person whose morning starts when mine does :)

This message almost always indicates that your connection is using commitment
control other than *NONE and your file is not being journaled.
Easy solution is to ensure your connection is not using commitment control or
change your SQL statement and append WITH NC to it.

Alternative is to journal the file, but that is usually more work the
workarounds I mentioned.

Elvis

Celebrating 10-Years of SQL Performance Excellence

-----Original Message-----
Subject: ODBC Connection Error - "[IBM][iSeries Access ODBC
Driver][DB2UDB]SQL7008 - "FedV0001" in QGPL not valid for operation.
(#-7008)"

Good morning,
I need some help.
I am trying to export MS Access table to iSeries(V5R2 - 9406-820).
I've set up iSeries ODBC connection. (also tried Client Access ODBC - no
difference)
Every time I get a msg:
"ODBC - Call Failed."
"[IBM][iSeries Access ODBC Driver][DB2 UDB]SQL7008 - "FedV0001" in QGPL not
valid for operation. (#-7008)"

Any Ideas? I've tried different libraries - same result

Thank You in Advance.

Gary



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To
post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment
to review the archives at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.