How to avoid SQL7008 error from DB2 on iSeries?

0 pts.
Tags:
Database Management Systems
DB2
Development
J2EE
Java
We are deploying a J2EE application on a Websphere 5.2 Application Server. This application accesses a DB2 database on an iSeries server which is not supporting transactions. We have already removed all transactions from the XML configuration files. We cannot find a way to configure the datasource resource on WAS to avoid an error from de iSeries server. I'm sure there is a way to configure an application not to use transactions, but we cannot find it. I'll apreciate any help. Thanks in advance Carlos Duran
ASKED: December 17, 2004  6:17 PM
UPDATED: December 20, 2004  11:22 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

If the error is returning reason code 3, this means that you are accessing a native AS/400 file that is not journaled. Even though you have tried to remove transactions from your application, your SQL access is defaulting to COMMIT(*CHG). you have 2 options:
1. start journaling the files on the iSeries
2. call a service program on the iSeries to do the database access.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Rchevalier
    The first suggestion I would make is to gather more information about the SQL7008 error. Find the error in the job log for the job. It will tell you the specific reason why the error occurred. There are 16 possible causes for this error. The most common cause usually has to do with commitment control. By default iSeries SQL access runs with commitment control active. As mentioned you can journal the file if it is not already journaled, or if commitment control is not a concern try the SQL SET statement to change the commit value. The statement would look something like SET OPTION COMMIT = *NONE. If the error isn't related to commitment control issues post the error information for more help. Rick
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following