Was there recently a change to Client Access or the ODBC provider that triggers the SQL7008 error more often? We have applications that have worked for years, but after getting a new computer, they crash with SQL7008. Journaling the file fixes the problem but it was not needed until now.
This may be related to the default commit level of the ODBC DSN. You may choose to change the commit level to solve the problem (rather then start journaling):
Go into the configuration for the DSN you're using to access your AS/400. Open the Server tab, in the DSN's ODBC setup panel, and click the advanced button. In the "advanced server options" screen that appears, you'll see a variable called commit mode. Click the drop-down box for commit mode and select commit immediate. (*NONE).
MORE INFORMATION ON THIS TOPIC
Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.
The Best Web Links: Tips, tutorials and more.
PC/Windows connectivity expert Shahar Mor is available to answer your toughest networking questions. Ask Shahar a question or read his previously answered questions here.
Dig Deeper on Physical connections to iSeries
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.