|
Like I used to tell my kids when they would ask "Dad, when are you going to be finished and come upstairs?" I would answer... "Just one more compile." <g> -Bob Cozzi www.RPGxTools.com RPG xTools - Enjoy programming again. -----Original Message----- From: rpg400-l-bounces+cozzi=rpgiv.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+cozzi=rpgiv.com@xxxxxxxxxxxx] On Behalf Of Mike Silvers Sent: Monday, October 31, 2005 8:02 AM To: RPG programming on the AS400 / iSeries Cc: Christopher Peel Subject: RE: Problem with the API: QtmhWrStout (Solved!) Thanks -- looks like the final change, I hope :) -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob Cozzi Sent: Monday, October 31, 2005 8:39 AM To: 'RPG programming on the AS400 / iSeries' Subject: RE: Problem with the API: QtmhWrStout (Solved!) Good, now change the X'15' to a X'25' and it'll be correct. <g> The X'15' is the old Linefeed symbol and was printed by mistake in the manuals. It should be X'25' although IBM continues to support X'15', you should always use X'25', or in the case of the Context-Type header, X'2525' -Bob Cozzi www.RPGxTools.com RPG xTools - Enjoy programming again. -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Silvers Sent: Monday, October 31, 2005 5:49 AM To: RPG programming on the AS400 / iSeries Subject: RE: Problem with the API: QtmhWrStout (Solved!) Wow -- this was a fun one. There was a problem was a relatively simple one, once we narrowed it down. There were actually two issues. The first is that the content-type (content-type: text/html) was not written. The second is when writing to stdout, we used the CRLF (x'OD25') after each line. We changed it to the New Line (x'15') and it worked. It seems that the original server permitted CRLF where the Apache server likes New Line.... Mike -----Original Message----- From: rpg400-l-bounces+msilvers=hbs-inc.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+msilvers=hbs-inc.com@xxxxxxxxxxxx] On Behalf Of Mike Silvers Sent: Friday, October 28, 2005 8:00 AM To: RPG programming on the AS400 / iSeries Subject: RE: Problem with the API: QtmhWrStout Peter, I just double checked and we are using the newer QZHBCGI service program for the API. Any other ideas? Thanks Mike -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Peter Connell Sent: Thursday, October 27, 2005 4:26 PM To: RPG programming on the AS400 / iSeries Subject: RE: Problem with the API: QtmhWrStout 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 ======================================= -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. ######################################################################## ############# This correspondence is for the named person's use only. It may contain confidential or legally privileged information, or both. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this correspondence in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of Baycorp Advantage. If you need assistance, please contact Baycorp Advantage on either :- Australia 133124 or New Zealand +64 9 356 5800 -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.