|
I haven't written any CGI programs, but could this info from the V4R2 Memo To Users hold any clues ? (Also make sure you have PTF SF49764 - the latest in a chain of PTF's for HTTP/CGI). TCP/IP CONNECTIVITY UTILITIES/400 (5769-TC1) STANDARD IN/STANDARD OUT (STDIN/STDOUT) FOR CGI PROGRAMS For V4R2, the stdin/stdout interface for Common Gateway Interface (CGI) programs is enhanced so that several limitations are removed. o If a CGI program writes more than 254 bytes of data to stdout that contains no imbedded new line characters, the data is no longer truncated as it was previously. o If a form attempts to pass in more than 254 bytes of data through POST to a CGI program, the data is no longer truncated as it was previously. o If a CGI program writes data to stdout, then calls another program which runs in a *NEW activation group, the initial CGI program's data is no longer overwritten as it was previously. o A CGI can run in a named activation group. If you have applications that have been written to deal with these limitations, those applications now can be changed. Neil Palmer DPS Data Processing Services Canada Ltd. AS/400~~~~~ Thornhill, Ontario, Canada ___________ ___ ~ Phone: (905) 731-9000 x238 |OOOOOOOOOO| ________ o|__||= Cell.: (416) 565-1682 x238 |__________|_|______|_|______) Fax: (905) 731-9202 oo oo oo oo OOOo=o\ mailto:NeilP@DPSlink.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ http://www.DPSlink.com AS/400 The Ultimate Business Server -----Original Message----- From: Stone, Brad V (TC) [SMTP:bvstone@taylorcorp.com] Sent: Wednesday, September 16, 1998 6:41 PM To: 'MIDRANGE-L@midrange.com' Subject: RE: V3R2 to V4R2 - HTTP gets all messed up.... help? Ken, thanks for your help. It has to be a bug, and it worked before even with sending seperate paratmeters seperated by the "+" sign. For example... ?RPG+0000001 will pass two parameters (or should..haha) to the *ENTRY portion of my RPG program (RPG and 0000001). But, it fills the last seven characters of the first variable, which is 10 long, with X'00' instead of X'40', which it did before. I would use C, but we don't have a C compiler. Also, speed doesn't seem to be a problem for us using RPG/IV. (Running on a 50S, and even or 30S was lickety split!) Thanks.. if you find anything, please let me know. I've tried using all the different modes on the EXEC statement in the HTTP configuration (%%EBCDIC%%, etc) but the only one that made a difference was %%BINARY%%, and then it was stuff I didn't want. On V3R2, it had to have been doing translation differently, and now on V4R2 it just doesn't work the same, and I'm getting frustrated... YIKES!!! Thanks again. > -----Original Message----- > From: Ken Yamasaki [SMTP:yamasaki@hh.iij4u.or.jp] > Sent: Wednesday, September 16, 1998 11:06 AM > To: MIDRANGE-L@midrange.com > Subject: Re: V3R2 to V4R2 - HTTP gets all messed up.... help? > > Brad, > > Stone, Brad V (TC) wrote > in <4EC96B864C1CD211BBC500805FE6FDBC1B44D7@tcexch1.taylorcorp.com> > on Wed, 16 Sep 1998 09:20:53 -0500 > > >I am not using GET to pass this information. It is being passed > >directly into the *ENTRY plist. I'm not using ?var=value, I'm simply > >using ?value as the ending portion of the URL. > > I understand about your way. It may be bug on V4R2M0. I don't test y > et. If I can have time to test, I will do. Anyway, I don't recomennd > your way. Because I think it is not supported in case of > passing several parameters. If you can, try to use QtmhGetEnv API. > > P.S. > If you have a plan to return data to browsers from pgm, I recomennd > to use ILE/C. The performance of CGI with ILE/C is better than > ILE/RPG. Because, QtmhWrStout(make stream to standard output) API > makes tempoary files in QTEMP before transfer data to browsers.(in > case > of ICS) > # If you know, sorry. > > Thanks. > > -- > Ken Yamasaki > Yokohama Kanagawa,JAPAN +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.