I haven't used the PHP program call stuff yet, but in general if you're
doing program calls from a web application you want to make sure your
program call handles errors without a hard halt resulting in a QSYSOPR
message.

This appears to the end user as if the web application locked up when in
fact it's waiting for a CPF response in QSYSOPR.

If you're getting odd decimal data problems you may want to pass values
to your programs as strings and convert the data in the RPG program.

Food for thought.

Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
----------------------------------------------------------------------

message: 1
date: Tue, 15 Sep 2009 10:43:52 -0400
from: MattLavinder@xxxxxxxxxxxxxxxxxxx
subject: Re: [WEB400] PHP Question - Finding Errors in i5_program_call


Alfred said:

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

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

Problem is not with finding my PHP errors. These are printed out on our
development server. The problem is the message sometimes doesn't give
any
useful information.

Kevin said:
Do you have an example of one of these errors?

Sometimes the PHPJOB will hang on a message. Other times I will just
get
something like this on the screen:

Could not call program: QWX2221

...or something like that. I had a similar message yesterday when a
decimal data error occurred. I had to dig around in my PHPJOB jobs
until I
found a message that clarified what happened. Perhaps something in my
configuration is causing this?

Thanks,
Matt


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.