Re: CGI API change ??

["Jim Franz" <franz400@xxxxxxxxxxxx>]

In the Web400 list this was posted in Feb under the heading "HTTP 500".
(IBM removed one of the early service pgms)

>I found the cause of the problem:  I had QTMHCGI *SRVPGM bound to the
program and it needs to be changed to QZHBCGI in V5R1.

Here's the link:

http://www-912.ibm.com/supporthome.nsf/document/24825731

hth
jim franz


----- Original Message -----
From: "Vernon Hamberg" <vhamberg@attbi.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, March 12, 2002 6:55 PM
Subject: Re: CGI API change ??


> Found this in APAR technical at IBM support site:
>
> Abstract
> COMPATIBILITY ISSUES WITH CGI PROGRAMS AT OS/400 VERSION 4.
>
>
> Error Description
> When migrating your AS/400 system from V3R7 to V4R2, some existing CGI
> programs may not function correctly. Changes were made in V4R2 to the CGI
> interface to improve performance, in addition, these changes also brought
> the HTTP server into closer compliance with the 'industry-standard'. These
> changes were not possible prior to V4R2, due to limitations with certain
> AS/400 system functions. Some CGI programs may have been inadvertently
> written that function correctly prior to V4R2 due to the unique
> characteristics of the V3 HTTP server CGI interface.
>
> What was the change?
>
> The AS400 runtime environment was enhanced in a way that allows the HTTP
> server to implement byte streams for CGI standard in and standard out.
>
> Why was the change made?
>
> The change was motivated by customer requirements to remove the line
length
> limitations on standard in and standard out.
>
> What problems are detected/flagged?
>
> 1.) Programs that call QtmhRdStdin multiple times to reread the standard
in
> data are incorrect and will not work.
>
> 2.) All programs that read from standard in (QtmhRdSdtin) need to check
the
> Content-Length environment variable to determine the number of bytes to
> read. Programs that do not use the Content-Length environment variable and
> read more than the Content-Length will not work.
>
> Why was the change made?
>
> The change was motivated by customer requirements to remove the 250 byte
> limit on standard in and standard out.
>
> What problems are detected/flagged?
>
> 1.) Programs that call QtmhRdStdin multiple times to reread the standard
in
> data are incorrect and will not work.
>
> 2.) All programs that read from standard in (QtmhRdSdtin) need to check
the
> Content-Length environment variable to determine the number of bytes to
> read. Programs that do not use the Content-Length environment variable and
> read more than the Content-Length will not work.
>
> When was the change made?
>
> The change was made available via the following ptfs:
>
> V4R1 - 5769SS1 SF46810
>         5769TC1 SF47332
>
> V4R2 - 5769TC1 SF46558
>
> What can the customer do?
>
> The customer can use the Web Programming Guide to ensure that his programs
> meet the standards/guidelines described in the documentation.
>
>
> At 03:44 PM 3/12/02 -0800, you wrote:
> >I've got a client moving from v4r4 to v5r1 and has several websites
> >running. There may be a large amount of CGI programming in use and the
> >person who maintained it is long gone. Now I thought I remember an API
> >change that affected CGI programming somewhere at v4r5 or v5r1 but can't
> >find the ref.
> >
> >I've search the archive but 'cgi' is in every darn message... Anyone
> >remember the API and/or have a ref for the change?
> >
> >
> >Thanks
> >
> >__________________________________________________
> >Kirk Goins
> >IBM Certified iSeries Technical Solutions Design
> >IBM Certified iSeries Technical Solutions Implementation
> >Pacific Information Systems - An IBM Premier Business Partner
> >503-674-2985           kirkg@pacinfosys.com
> >
> >_______________________________________________
> >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> >To post a message email: MIDRANGE-L@midrange.com
> >To subscribe, unsubscribe, or change list options,
> >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> >or email: MIDRANGE-L-request@midrange.com
> >Before posting, please take a moment to review the archives
> >at http://archive.midrange.com/midrange-l.
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>