|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[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! |
|
|
|
|
Asked by softechnics in DB2 Database, Databases Miscellaneous
Hello,
We have an application which we are in the process of porting from Windows to Linux. The ultimate target is an IBM S390X 64-bit zLinux machine. We are using unixODBC 2.2.13 and DB2 v9.1. We have successfully ported the code to another 64-bit machine (i386 architecture) run Gentoo Linux and it works. However, on the zLinux machine I have the following problem, and it is very strange. If I ever repeat the same query, it fails. For example, if I have a query of the form SELECT * FROM SomeTable, it will work the very first time. If that same query is every performed again it fails. The failure seems to be related to the SQLFetch that retrieves the result set. I am using the SQLBindCol API to bind my data structure to the expected result set. The query is execute by SQLExecDirect. The second time the query is run, I appear to get garbarge. More specifically, some of the expected field data is in the structure if you look at it as a chunk of memory, but it is offeset in the wrong locations, and in some cases missing. I have run both ODBC and CLI traces and everything appears normal at that point. The failure appears to be in the SQLFetch call itself.
Again, the failure only occurs on this particular platform. We have used this code on other platforms successfully. I should add we are working in C/C++.
Has anyone ever encountered a problem such as this? I don't have a code snippet because the SQL calls are encapsulated in our own library calls.
Thanks much.
20091118-EE-VQP-93 / EE_QW_2_20070628
