×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of MattLavinder@xxxxxxxxxxxxxxxxxxx
Sent: Monday, September 14, 2009 3:05 PM
To: web400@xxxxxxxxxxxx
Subject: [WEB400] PHP Question - Finding Errors in i5_program_call
We have been using PHP more and more. One gripe I have about the
i5_program_call function is that no information is really provided in
the
error message when a program call fails. If you are using persistent
connections, as far as I can tell, you have to go dig around in the
EasyCom
jobs that are running to find out what went wrong. Is there a better
way
to find out what went wrong when i5_program_call fails?
As a side note, I know some Zend folks monitor this group, and you guys
should really get on those guys over at EasyCom to have their component
return more meaningful error messages,
Matt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
