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




Can anyone tell why the following is happening?

I have a CGI program called CGIPGM0. When I enter /cgi-bin/CGIPGM0 in a
browser, it outputs a page with a form (method=”POST”) that ask for input.
Let us call this page as Page0. I enter ‘AAAAAAAAAA’ into input field #1 and
‘999999.99’ into input field #2. Then I click submit, CGIPGM1 is called to
process the input from Page0. I put CGIPGM1 in debug mode and I can see that
the input string is:

INPUT01=AAAAAAAAAA&INPUT02=999999099


Now, I save the html source code of  Page0 (generated by CGIPGM0) to IFS
(also tried save to a QSYS source member).  I enter its URL in a browser. I
get EXACTLY the same page, Page0. I fill the input.
I click submit, the same CGIPGM1 is called (we are still in the same debug
session).  BUT I can see that the input string is like this:

INPUT01NAAA-=AAAAAAAAAA%D5AAA-%18%2C3%98&INPUT02NAAA-=
999999%D5AAA-AAA-%18%2C3%98&

API QtmhCvtDB errors out because only INPUT01 and INPUT02 are defined in the
mapping database file used by this API. However the input string says the
input field names are INPUT01NAAA- and INPUT02NAAA-!

Any idea?


Bj






+---
| 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
+---


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.