× 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.



Mike,
You may or may not be aware that a while back IBM in fact implemented
the same functionality via a new *SRVPGM that also provides some
additional service procedures. The old *SRVPGM was QHTTPSVR/QTMHCGI. The
new *SRVPGM is QHTTPSVR/QZHBCGI. 

Obviously, you would expect that programs using the original interface
to operate without impact.  However, we found this not to be the case,
in particular with respect to the error parameter. After raising the
issue with IBM and explaining at length what the problem was, they were
somewhat surprised when able to demonstrate that there was indeed a
problem.

IBM's official response was to refer to some piece of documentation
(somewhere in the HTTP server doc) which indicated the existence of the
new *SRVPGM QZHBCGI with a recommendation that it should be used in
preference to QTMHCGI and implied that it would be hopeful for one to
expect any patch for the problem. 

Rather than recompile, I believe we just replaced the old QTMHCGI by
duplicating QZHBCGI but giving it the same name as the old one, QTMHCGI.
To avoid issues with subsequent development we changed the relevant
binding directory used by the compile so that it now references the new
*SRVPGM.

Cheers, Peter

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Silvers
Sent: Friday, 28 October 2005 5:57 a.m.
To: RPG400-L@xxxxxxxxxxxx
Cc: Christopher Peel
Subject: Problem with the API: QtmhWrStout

We are running into a problem with the API QtmhWrStout (used to write to
stdout).  We have a process that utilizes this API to interact with the
web.  The RPG program has been working for a few years with no problems.
WE now converted the web server from the original server to the apache
server.  Now, when writing to this api, it appears that the data is
partially encoded in ASCII and partly in EPCDIC.  It is really weird.
Has anyone else run into this problem?  Any ideas?
 
=======================================
Mike Silvers
Senior Programmer/Analyst
iSeries Websphere Certified
Hainey Business Systems
Branch Office:  (410) 219-2695 
Cell: (443) 521-3887
Main Office Direct: (717) 771-2358
Main Office General:  (717) 718-9601 ext 7139
Fax: (877) 804-9589
http://www.hbs-inc.com <http://www.hbs-inc.com/> 
AIM:  IBMJavaMan
=======================================
 

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.