Something must have changed. I have seen weirdness happen with both JDBC and ODBC when a system is upgraded or the SQL Package files get corrupted. It wouldn't hurt to stop the application so that the package files are no longer locked and either rename the SQL page files or back them up and delete them. I have seen them in both QGPL and in the file or other libraries in the library list of the ODBC connection (it's driver dependent) so I'd search for objects of *SQLPKG type and delete them (back them up or rename). It won't hurt because the packages are automatically rebuilt and if they happen to be corrupted, you may fix the problem...
GIAC Secure Software Programmer-Java
On 6/15/2014 12:48 AM, Chella R wrote:
I have an application invoking stored proc in the AS400 system. I know that the stored procedure execution is through the ODBC connection from the Appln to AS400. But for past couple of days, when the stored procedure is invoked, no response is being received at the application. All these stored procedures were working well until this issue. We have checked the I-Series drivers on the application, network connectivity at both ends.
What could be the issue? And after an ODBC connection is made, how does the stored procedure invocation gets processed?
Chella Govindarajan R,
Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailadmin@xxxxxxxxx <mailto:mailadmin@xxxxxxxxx>. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result
software viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com <http://www.igate.com>.
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact