Re: PHP Question - Finding Errors in i5_program_call

[ADelgado@xxxxxxxxxxxxxxxxxx]

   Have you looked in the Apache error logs in /usr/local/Zend/apache2/logs/
   ?

   You can also use ini_set in your dev script to turn display_errors on.
   e.g. ini_set( 'display_errors', 1 );

   You can also inspect i5_error( ), i5_errno( ), or i5_errormsg( ) after
   your call.

   If you have Platform you should familiarize yourself with the Event List
   under PHP Intelligence. It's a great feature well worth a portion of the
   Platform licensing price.

   Alfred
   --
   Alfredo Delgado / Web Development
   6800 Broken Sound Pkwy, Suite 150
   Boca Raton, Florida 33487
   -----web400-bounces@xxxxxxxxxxxx wrote: -----

     To: web400@xxxxxxxxxxxx
     From: MattLavinder@xxxxxxxxxxxxxxxxxxx
     Sent by: web400-bounces@xxxxxxxxxxxx
     Date: 09/14/2009 16:04
     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

     ______________________________________________________________________
     This email has been scanned by the MessageLabs Email Security System.
     ______________________________________________________________________
     --
     This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
     To post a message email: WEB400@xxxxxxxxxxxx
     To subscribe, unsubscribe, or change list options,
     visit: [1]http://lists.midrange.com/mailman/listinfo/web400
     or email: WEB400-request@xxxxxxxxxxxx
     Before posting, please take a moment to review the archives
     at [2]http://archive.midrange.com/web400.

References

   Visible links
   1. http://lists.midrange.com/mailman/listinfo/web400
   2. http://archive.midrange.com/web400