RE: Challenge for IBM. QzhbCGIParse API.

Brad,
Yes, RdStin was the solution I also arrived at when, in the early days, we
developers decided that we'd like to hook into stuff that net.data did not
give us control over and QzbhCGIParse was not an option. I've just
revisiting the parse API to see if it's worth going beyond the "tried THAT
much stage". While I wouldn't use the word "flaky' when discussing such
API's, I agree that the words "frustration" and "clarity" would certainly
figure strongly.

It appears that, when attempting to "do both", the problem that I have with
the QS variable not showing the last value has nothing to to with the API
since it is apparent without ever calling it. It's got something to do with
the wretched %%EBCDIC%% CGIConvMode.

Cheers, Peter   

-----Original Message-----
From: Stone, Brad V (TC) [mailto:bvstone@taylorcorp.com]
Sent: Friday, February 02, 2001 2:31 AM
To: 'RPG400-L@midrange.com'
Subject: RE: Challenge for IBM. QzhbCGIParse API.


I know I had trouble doing both in one shot (Standard Input and Query
String).  I haven't tried THAT much, but I'd assume if you do both you'd
need to read QS first, then standard input (ie don't -init until you've read
QS).

I used to use RdStin and GetEnv APIs and it worked ok reading both with
these APIs.

Brad

> -----Original Message-----
> From: Peter Connell [mailto:peterc@baycorp.co.nz]
> Sent: Wednesday, January 31, 2001 7:43 PM
> To: 'RPG400-L@midrange.com'
> Subject: RE: Challenge for IBM. QzhbCGIParse API.
> 
> 
> Brad,
> I'm observing a strange behaviour and wonder if you've also noticed.
> I've used -init with QzhbCGIParse to return the form data.
> This will only work if the CGIConvMode is %%EBCDIC%%
> Firstly, it appears that when the method is POST then, 
> although the form
> elements are extracted OK, any query string variables that 
> may be appended
> to the url in the form ACTION value eg ?fld1=ABC&fld2=DEF are 
> ignored since
> only stdin is read.
> Secondly before the API is ever called the value the server 
> has placed in
> QUERY_STRING contains only the data up to the last = sign eg 
> fld1=ABC&fld2=
> the DEF has vanished.
> Bummer.
> 
> Peter
> 
> -----Original Message-----
> From: Stone, Brad V (TC) [mailto:bvstone@taylorcorp.com]
> Sent: Friday, December 08, 2000 10:53 AM
> To: 'RPG400-L@midrange.com'
> Subject: Challenge for IBM. QzhbCGIParse API.
> 
> 
> Barb, Hans, et al...
> 
> The following link is to the description of the fields that 
> you can use for
> the QzhbCGIParse API.
> 
> http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/QB3AEQ03/2.6.1
> 
> What I would like is an example of how you are supposed to 
> use the -POST
> command.  Even if it is something as simple as "after a POST, your
> processing program calls QzhbCGIParse with a command string 
> of -POST, and
> after that you should be able to get your data by (whatever 
> you would do)."
> 
> People have been asking me, and I've been fighting with it.  
> This is some of
> the poorest documentation I've seen, yet it's one of the best APIs.  
> 
> So, Barb, Hans, could you pass this along to someone who may 
> be able to
> help?  Solve a mystery for us.  :)
> 
> Brad
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to 
> RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> 
> This communication is confidential and may be legally privileged. 
> If it is not addressed to you, you are on notice of its status. 
> Please immediately contact us at our cost and destroy it.  
> Please do not use, disclose, copy, distribute or retain any of it 
> without our authority - to do so could be a breach of confidence. 
> Thank you for your co-operation.  
> Please contact us on (09) 356 5800 if you need assistance.
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to 
> RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: 
> david@midrange.com
> +---
> 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---

This communication is confidential and may be legally privileged. 
If it is not addressed to you, you are on notice of its status. 
Please immediately contact us at our cost and destroy it.  
Please do not use, disclose, copy, distribute or retain any of it 
without our authority - to do so could be a breach of confidence. 
Thank you for your co-operation.  
Please contact us on (09) 356 5800 if you need assistance.
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---