RE: CGI programs failing after OS/400 upgrade from V4R1 to V4R2

[Neil Palmer <npalmer@xxxxxxxxxxx>]

Well, does this APAR sound like it describes your problem ?  Do you have
PTF SF45218 applied ?


Item SA69345 

  APAR Identifier ...... SA69345       Last Changed..98/04/30  
  TCPIP-HTTP UNABLE TO WRITE TO STDERR
 
 
  Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
  Severity ................... 2      Date Closed ......... 97/11/18
  Component .......... 5769TC1WW      Duplicate of ........
  Reported Release ......... 420      Fixed Release ............ 999
  Component Name 5769 TCP/IP WWW      Special Notice
  Current Target Date ..              Flags
  SCP ...................
  Platform ............
 
  Status Detail: SHIPMENT - Packaged solution is available for
                            shipment.
 
  PE PTF List:
 
  PTF List:
  Release 410   : PTF not available yet
  Release 420   : SF45218 available 98/02/11 (8028 )
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  The CGI stdin/stdout/stderr interface has changed on V4R2.  Part
  of this changes included preventing a CGI from writting to
  stderr since nothing is being done with the data.  This is
  causing a problem with a REXX program that function properly on
  V4R1.  For compatibility reasons, CGI programs should continue
  to be allowed to write to stderr.
 
 
  PROBLEM CONCLUSION:
  Write to stderr will not cause an error condition, however the
  data written will not be saved.
 
 
  TEMPORARY FIX:
 
 
  COMMENTS:
  Write to stderr will not cause an error condition, however the
  data written will not be saved.
 



Plus, I don't know if this is relevant, but this is from the V4R2 Memo
To Users:

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                                AS/400~~~~~      
NxTrend Technology - Canada   ____________          ___  ~     
Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
http://www.NxTrend.com

> -----Original Message-----
> From: mahi@hyd.mgsl.com [SMTP:mahi@hyd.mgsl.com]
> Sent: Monday, June 22, 1998 12:10 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      CGI programs failing after OS/400 upgrade from V4R1 to
> V4R2
> Importance:   High
> 
> We have an AS/400 as web server and we recently upgraded it from V4R1
> to
> V4R2. When we were at V4R1 all the CGI programs used to work fine.
> After
> the upgrade none of them are working. When I tried to access CGI
> programs
> from the web browser, the respective CGI program is getting invoked
> but it
> is not recieving any data from the web browser.  CGI programs were
> written
> in ILE RPG using QTMRDSTIN and QTMHWRSTOUT APIs to read/write date
> to/from
> stdin and stdout. QTMHRDSTIN    API  is returning *BLANKS, not the
> data
> sent by the web browser. Any solution???
> 
> Thanx in advance.
>  Mahendra I Reddy
> 
+---
| 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
+---