Advertisement

11.12.2008 at 05:50AM PST, ID: 23898004
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
7.7

ISeries ODBC Disconnection With UPS Worldship

Asked by ctsuhako in AS / 400

Tags: ,

We are trying to connect UPS' Worldship (Version 10) to a database on an ISeries that contains all the relevant shipping informmation via an ODBC connection. The connection works fine except for two issues. Firstly, the initial connection take about 3-4 minutes to establish itself. Once the connection is established, the data is populated in a timely fashion. I have heard that the UPS Worldship software indexes every table on its initial connection and not being an ODBC or Client Access guru I was wondering if there was a way to tell the ODBC connection to only look at the table that actually has the information we need.

Secondly, the ODBC connection times out after about 30 minutes of non-use with the following message:

ODBC Error: State=08S01 Error=[IBM} ISeries Access ODBC Driver
Communication link failure, comm rc=10054
CWBC01047-The ISeries server application disconnected the connection.

I had the system value of "QINACTITV" on the ISeries changed to the Max Value of 300 minutes, but the error is still occuring. When this occurs, the users must re-establish the connection and are stuck waiting for the connection like in issue one.

I am not an expert on either Client Access or ODBC, but we are transitioning to the Worldship software and need to get either a quicker startup on the initial connection or eliminate the timeout issue. UPS has not been very helpful in this matter, so once again I turn to the Experts.

Thank you very much for any insight!Start Free Trial
[+][-]11.12.2008 at 02:10PM PST, ID: 22944862

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: AS / 400
Tags: ISeries Client Access, Version 5 Release 4 (SI29771)
Sign Up Now!
Solution Provided By: JBart_17
Participating Experts: 1
Solution Grade: B
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 - Hierarchy / EE_QW_2_20070628