Joel,

I have been using CvtDB and CGIParse for some time and have
never exerpieced the escaped characters that you are
speaking of.  I remember when I first started doing CGI that
I had that problem, but I'm positive the %%EBCDIC%%
extension fixed that.

I guess I dont know where to start with asking you what
you're doing.

Try these examples that I have online (the connection is
going up and down, so it may not work from time to time).
They're for my upcoming book.

Tests QtmhCvtDB
http://www.netshare400.com:3001/testcvtdb.html

Tests QzhbCGIParse using GET
http://www.netshare400.com:3001/testcgiparse1.html

Tests QzhbCGIParse using POST
http://www.netshare400.com:3001/testcgiparse2.html

If you get escaped characters in the output, let me know
what you used for input.  These ask for first and last name,
but you should be able to put any data you want in them.

The config for this HTTP instance is very simple as well.

Brad
www.bvstools.com
> -----Original Message-----
> From: Joel R. Cochran [mailto:jrc@masi-brac.com]
> Sent: Wednesday, December 19, 2001 9:07 AM
> To: 'web400@midrange.com'
> Subject: RE: [WEB400] unescape()
>
> Brad,
>
> All of my incoming parms do run through QtmhCvtDB but
> that doesn't do
> anything, it just leaves the '%xx' codes as part of the
> text string.  If
> I
> don't address the problem via my #escape routine, then
> the database gets
> updated with 'invalid' data.  A while back I tried adding
> the %%EBCDIC%%
> extension in my HTTP configuration but that didn't solve
> the problem
> either.
>
> I haven't messed with QzhbCGIParse yet, so I don't know
> if that would
> operate any differently but I was under the impression
> that this was
> just a
> different way to do the same things...
>
> Any insight would be great!
>
> Thanks,
>
> Joel
>
> -----Original Message-----
> From: Brad Stone [mailto:brad@bvstools.com]
> Sent: Tuesday, December 18, 2001 5:26 PM
> To: web400@midrange.com
> Subject: Re: [WEB400] unescape()
>
>
> Is there a a reason you're not letting QtmhCvtDB or
> QzhbCGIParse do this for you?
>
> Brad
> www.bvstools.com
>
> On Tue, 18 Dec 2001 17:33:50 -0500
>  "Joel R. Cochran" <jrc@masi-brac.com> wrote:
> > Remember Charlie Brown?
> >
> >
> "AAAAAAAAAAAAUUUUUUUUUUUUUUUUUUUGGGGGGGGGGGGGGGGGGGGGGGGGHHHHHHHHHHHHHHH
> HHHH
> > HHHHHHH!!!!!!!!!!!!!"
> >
> > Thanks Jim :-)
> >
> > -----Original Message-----
> > From: Jim Langston [mailto:jlangston@celsinc.com]
> > Sent: Tuesday, December 18, 2001 4:54 PM
> > To: 'web400@midrange.com'
> > Subject: RE: [WEB400] unescape()
> >
> >
> > try '\n' instead.
> >
> > -----Original Message-----
> > From: Joel R. Cochran [mailto:jrc@masi-brac.com]
> > Sent: Tuesday, December 18, 2001 1:58 PM
> > To: 'web400@midrange.com'
> > Subject: [WEB400] unescape()
> >
> >
> > I have a CGI-RPGIV web site.  I run all incoming parms
> > through an #escape()
> > routine to convert special codes (like %2F for '/') to
> > their actual
> > characters.  I have added a <textarea> to one of my
> > screens and for the
> > first time I have to deal with forced line breaks
> > (enter).  The code comes
> > in as '%0D%0A'.  I tried converting this to '/n'
> thinking
> > that the
> > JavaScript that re-populates the form later would read
> > that and break, but
> > instead it actually shows the '/n' as part of the text.
> >
> > My conclusion is that I need a simple #unescape()
> > routine, but what do I
> > convert this to so that the browser will understand
> this
> > is a line break?
> >
> >
> > Many thanks,
> >
> > Joel
> > _______________________________________________
> > This is the Web Enabling the AS400 / iSeries (WEB400)
> > mailing list
> > To post a message email: WEB400@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> > or email: WEB400-request@midrange.com
> > Before posting, please take a moment to review the
> > archives
> > at http://archive.midrange.com/web400.
> > _______________________________________________
> > This is the Web Enabling the AS400 / iSeries (WEB400)
> > mailing list
> > To post a message email: WEB400@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> > or email: WEB400-request@midrange.com
> > Before posting, please take a moment to review the
> > archives
> > at http://archive.midrange.com/web400.
> >
>
> Bradley V. Stone
> BVS.Tools
> www.bvstools.com
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400)
> mailing list
> To post a message email: WEB400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> or email: WEB400-request@midrange.com
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/web400.
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400)
> mailing list
> To post a message email: WEB400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> or email: WEB400-request@midrange.com
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/web400.
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400)
> mailing list
> To post a message email: WEB400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> or email: WEB400-request@midrange.com
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/web400.
>

Bradley V. Stone
BVS.Tools
www.bvstools.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2022 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.