Program Temporary Fixes (PTFs) for Web Server/400 v1.3
General information about Program Temporary Fixes can be found at the
links below:
The PTFs listed below address several Web Server/400 v1.3 issues including
the following:
The WWW130001 PTF
The WWW130001 PTF is a performance PTF. After installation, if
statistics logging is disabled using the CHGWWWCFG command the maximum
throughput of the server, measured in number of requests that can be
processed per second, will increase significantly. On our B60 running
V3R2 we experienced an approximate 60% increase in throughput. The
status (i.e., enabled or disabled) of statistics logging is determined
when starting the server and can not be changed; you must restart the
server to change the status. When statistics logging is disabled, you
will receive a "Document contains no data" error when trying to view
the statistics dynamically through the administrative mode.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130001 PTF HAS BEEN SUPERCEDED BY WWW130020.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130002 PTF
The WWW130002 PTF only applies to customers using the Japanese version
of the product. Please see the text file for additional information.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
The WWW130003 PTF
The WWW130003 PTF contains an enhancement to Web Server/400 1.3 or
Commerce Server/400 1.0 that gives you the capability to index your
site so it can be searched by your customers. This new feature of
the server has been called Site Search.
After installation you can access the Site Search user guide through
the following URL:
| /shipped/pubs/wssusrgd.htm |
(provided /wwwserv/webdocs is your document root) |
Links off of the Site Search user guide include:
- Documentation (user and programming)
- Sample search forms
- Search scripts written in ILE C and RPG
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
The WWW130004 PTF
The WWW130004 PTF contains an enhancement to Web Server/400 1.3 or
Commerce Server/400 1.0 that gives you the capability to run scripts
that are written for IBM's AS/400 Web server (including DB2WWW/
Net.Data scripts). The current support is achieved using a script,
program is called WWWADOPT, that is called by I/NET's server that acts
as an interface between I/NET's server and IBM's scripts. In a future
version this capability will be integrated into the server's code.
Limitations/Restrictions:
- AS/400 must be running V3R2 or V3R7 or later
- The WWWADOPT program MUST be copied into each library containing the
IBM scripts to be called. You can copy WWWADOPT from the server's
product library (WWWSERVER). For users of DB2WWW/Net.Data this
means WWWADOPT must be copied into the QTCP library.
- The environment variable PATH_TRANSLATED is not set correctly. It
is currently being set to the PATH_INFO value.
- The SCRIPT_NAME environment variable is not set correctly.
- The IBM_CCSID_VALUE environment variable is always set to 37.
- Use aliases to use this feature transparently:
- Alias /db2www/ to /wwwadopt/db2www/
- Alias /ibmscriptlib/ to /ibmscriptlib/wwwadopt/
This PTF also adds the ability to call AS/400 Java applications.
The Java app MUST be placed in an IFS directory (or subdirectory)
of /INETJAVACGI. To access a Java app you would use a URL like
the following:
/cgi-bin/wwwadopt/inetjavacgi/javaappname
NOTE: The Java app must have an extension of .class but the .class
is not used when accessing the Java app through a URL.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130004 PTF HAS BEEN SUPERCEDED BY WWW130011.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130007 PTF
The WWW130007 PTF adds support of cookies that are larger then 256
bytes/characters. The maximum length of a cookie, or any other
request or response header, is now 4096 bytes.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130007 PTF HAS BEEN SUPERCEDED BY WWW130013.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130008 PTF
The WWW130008 PTF fixes the following problems found in the escape
and unescape APIs:
- WwwEscape and WWWESC APIs were not returning the escaped data.
- The escape APIs were not properly escaping spaces. A space was
being incorrectly escaped to a percent (%) instead of a plus (+).
- The unescape APIs were including the ending NULL character in the
number of unescaped bytes. The NULL is only returned now when
calling the ILE C interface and the NULL is no longer counted as
an unescaped byte.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130008 PTF HAS BEEN SUPERCEDED BY WWW130017.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130011 PTF
The WWW130011 PTF superceeds the WWW130004 PTF (i.e., you do not need
to install WWW130004 before installing WWW130011). Please read the
changes section for important information pertaining to
this PTF.
The WWW130011 PTF contains an enhancement to Web Server/400 1.3 or
Commerce Server/400 1.0 that gives you the capability to run scripts
that are written for IBM's AS/400 Web server (including Net.Data
scripts). The current support is achieved using a script, which is
called WWWADOPT, that is called by I/NET's server that acts as an
interface between I/NET's server and IBM's scripts. Using WWWADOPT,
you can also call the IBM scripts that are used to configure Network
Stations. In a future version of the servers this capability will be
integrated into the server's code.
Limitations/Restrictions:
- AS/400 must be running V3R2 or V3R7 or later
- The WWWADOPT program MUST be copied into each library containing the
IBM scripts to be called. You can copy WWWADOPT from the server's
product library (WWWSERVER). For users of DB2WWW/Net.Data this
means WWWADOPT may be needed to be copied into the QTCP library.
When duplicating WWWADOPT into other libraries be sure the owner
of WWWADOPT is set correctly (see notes below).
- The environment variable PATH_TRANSLATED is not set correctly. It
is currently being set to the PATH_INFO value.
- IBM CGI programs that WWWADOPT calls cannot call the I/NET server
APIs.
Changes made since WWW130004:
- The physical files used to perform I/O (STDIN,STDOUT) were changed
to match IBM's definition. CGI output that works fine with IC/400
is no longer truncated when running under our servers.
- WWWADOPT's activation group has been changed from *NEW to *CALLER.
This should improve performance by reducing the overhead associated
with initializing a new activation group, especially when using
Net.Data macros.
- WWWADOPT's user profile has been changed from *USER to *OWNER. When
duplicating WWWADOPT into other libraries be sure to set the owner
to the appropriate value. Under most circumstances, changing the
owner to WWWUSER will work fine.
- WWWADOPT can now handle IBM CGI programs with or without the '.PGM'
extension. Previously, IBM CGI programs could not be qualified with
'.PGM' extension.
- The SERVER_SOFTWARE environment variable was changed to indicate
IC/400 is running (IBM-AS/400-HTTP-Server/1.0). This change was
needed to support the Network Station configuration software.
- A fix was made to our internal trace code. You must delete "extra"
trace user spaces that were created by the WWW130004 code:
WRKOBJ OBJ(*ALL/TRCUSERSPC) OBJTYPE(*USRSPC)
Delete all of the trace user spaces except for the one in the
WWWSERVER library.
- If migrating from PTF WWW130004, ensure all of the existing copies
of WWWADOPT are replaced with the new version.
You can use aliases to use this feature transparently:
- Sample Net.Data alias
| Alias | Value | SrcType |
| /db2www/ | /wwwadopt/db2www/ | *QSYS |
- Sample IBM CGI library alias
| Alias | Value | SrcType |
| /ibmscriptlib/ | /ibmscriptlib/wwwadopt/ | *QSYS |
Using WWWADOPT to configure Network Stations:
- Copy WWWADOPT into the QYTC library and change WWWADOPT's owner to
IBM's CGI user profile (i.e., CHGOBJOWN QYTC/WWWADOPT *PGM QTMHHTP1).
The owner must be changed to QTMHHTP1 to access certain IBM CGI
programs that are used to configure Network Stations.
- Make sure the QTMHHTP1 user profile has *USE authority to the
following program: QYTC/QYTCMCLS.
- The following Web Server/400 - Commerce Server/400 configuration
changes must be made (NOTE: It is probably best to setup unique
configuration files to be used only for running a server that is
used to configure Network Stations):
- Set the document root to '/QIBM' (CHGWWWCFG)
- Add library QYTC to the list of script libraries (WRKWWWSCPL)
- Add the following aliases (WRKWWWALS):
| Alias | Value | SrcType |
| /QIBM/ | / | *ROOT |
| /QYTC/ | /QYTC.LIB/WWWADOPT.PGM/ | *QSYS |
| /QIBM/NetworkStation/ | /ProdData/HTTP/Protect/NetworkStation/ | *ROOT |
| /QIBM/NetworkStation/Admin | /QYTC.LIB/WWWADOPT.PGM/QYTCMAIN | *QSYS |
| /QIBM/NetworkStation/Admin.htm | /ProdData/HTTP/Protect/NetworkStation/Admin.htm | *ROOT |
- Start the server with the new configuration
- Access the Network Station setup from the browser:
http://system[:port]/QIBM/NetworkStation/Admin
or
https://system[:port]/QIBM/NetworkStation/Admin (Commerce Server/400)
WWWADOPT also supports the ability to call AS/400 Java applications.
The Java app MUST be placed in an IFS directory (or subdirectory)
of /INETJAVACGI. To access a Java app you would use a URL like
the following:
/cgi-bin/wwwadopt/inetjavacgi/javaappname
NOTE: The Java app must have an extension of .class but the .class
is not used when accessing the Java app through a URL.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130011 PTF HAS BEEN SUPERCEDED BY WWW130015.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130012 PTF
The WWW130012 PTF contains a change to the Web Server/400 code that
is only required by Commerce Server/400 customers who are also using
the new Merchant/400 product. Commerce Server/400 will not start
with a new Merchant/400 activation key until this PTF is applied.
Commerce Server/400 version 1.0C (DSPDTAARA WWWSERVER/VERSION)
customers do not need to apply this PTF.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
The WWW130013 PTF
The WWW130013 PTF superceeds the WWW130007 PTF (i.e., you do not need
to install WWW130007 before installing WWW130013). Please read the
changes section for important information pertaining to this PTF.
The WWW130013 PTF contains a code fix for Web Server/400 1.3 or
Commerce Server/400 1.0 and also a sample upload file script.
Changes made since WWW130007:
- Fixed a problem where the server was not properly handling data
when the input (POSTed) data was greater than 4K when the script
was also returning data.
The upload file script is called UPFILE and it is restored into
the WWWSERVER (product) library. UPFILE is owned by QSYS and has
public authority set to *EXCLUDE. Before UPFILE can be used it must
be copied into a script library and the server user profile (e.g.,
WWWUSER) must have access to the program. Care should be taken when
enabling the use of UPFILE so that only authorized users have access
to upload files.
Sample HTML form used to call UPFILE:
<HTML>
<HEAD><TITLE>Upload File</TITLE></HEAD>
<BODY>
<H1>Upload File</H1>
<HR>
<FORM ACTION="/cgi-bin/upfile" ENCTYPE="multipart/form-data" METHOD=POST>
From file:<INPUT NAME="FROM_FILE" TYPE="file" SIZE=40,5> <BR>
To file:<INPUT NAME="TO_FILE" TYPE="text" SIZE=80 MAXLENGTH=100> <P>
<INPUT TYPE="submit" VALUE="Upload File">
</FORM>
</BODY>
</HTML>
NOTES:
- The form variables must be in the above order for UPFILE to work.
- The input file is a standard PC file path (e.g., c:\dir\file.ext)
- The to file is an IFS path (e.g., '/dir/file.ext'). The data uploaded
and saved to this file is treated as binary data (no conversions take
place). By default, UPFILE will not replace/overwrite an existing
file. If you would like the ability to overwrite existing files then
copy UPFILE to UPFILER (the program checks the name of itself and if
the program name is UPFILER it enables overwriting files). Important:
UPFILE does not place any restrictions on the location of the to file.
- UPFILE has a verbose mode that is enabled by adding extra path info:
"/cgi-bin/upfile/verbose"
In verbose mode additional information about the request is returned
by the script. UPFILE, in verbose mode, will also write the received
standard input (POSTed) data to an IFS file called '/upfile.in'.
Examining the data written to '/UPFILE.IN' provides good starting
point for writing a script that can handle file uploads.
UPFILE is provided "as is". UPFILE is written in ILE C and uses internal
server routines, because of this the source is not available. Included
at the bottom of this section is a general description of the processing
performed by the UPFILE script. UPFILE has been tested briefly with
Netscape 3.0 and IE 3.02 (with the optional upload module installed).
UPFILE description (makes more sense after running UPFILE in verbose mode
and examining the UPFILE.IN data):
- Ensure the REQUEST_METHOD is "POST".
- Ensure the CONTENT_TYPE begins with "multipart/form-data".
- Read the input (POSTed) data.
- Convert input data from ASCII to EBCDIC into another buffer. The EBCDIC
buffer is needed by UPFILE to find the file to save the data to and to
also output HTML information about the upload request.
- The first thing in the input data is a multipart boundary that is terminated
with an ASCII CR,LF. The boundary is used to find the different parts of the
multipart form data.
- The input file data begins after the first set of 2 CR,LFs found.
- The input file data ends 2 bytes (CR,LF) before the next boundary found.
- Find the to file form variable (TO_FILE) in the EBCDIC buffer. The value
is found after the next set of CR,LFs.
- Store the uploaded file data into the to file (UPFILE uses IFS SPIs).
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130013 PTF HAS BEEN SUPERCEDED BY WWW130017.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130015 PTF
The WWW130015 PTF superceeds the WWW130004 and WWW130011 PTFs (i.e., you do
not need to install the superceded PTFs before installing WWW130015).
The WWW130015 PTF contains a recompile of WWWADOPT to fix a problem
where WWWADOPT would not work with the latest Net.Data PTFs (e.g.,
V3R2 5763TC1-SF43221, V3R7 5715TC1-SF43219, V4R1 5769TC1-SF43216).
Also, a new environment variable has been added (CGI_ASCII_CCSID)
which is used by Net.Data to determine the CCSID of the incoming
escaped characters.
Please see the WWW130011 PTF section for additional
information on WWWADOPT.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130015 PTF HAS BEEN SUPERCEDED BY WWW130021.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130016 PTF
Corrects an indexing problem with words containing numeric characters.
The WWW130016 PTF supersedes PTF WWW130010.
Prerequisites: Before installing the WWW130016 PTF, you must first install
the original Site Search PTF.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
The WWW130017 PTF
The WWW130017 PTF superceeds the
WWW130007,
WWW130008,
WWW130013 and
WWW130014 PTFs
(i.e., you do not need to install the superceded PTFs before installing WWW130017).
The WWW130017 PTF contains a code change to fix a problem where the
server would timeout trying to receive posted data using SSL when
the posted data was greater than 4k. The problem was first
encountered when uploading files using IE 4.01.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130017 PTF HAS BEEN SUPERCEDED BY WWW130019.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130018 PTF
The WWW130018 PTF contains code changes to fix a problem where the
server would insert invalid characters in the configuration file when
the CHGWWWCFG DISABLESVR() command and parameter were used on an AS/400
running with the Japanese language (QCPFMSG messages are defined with
double-byte characters). It also fixes a prompt override problem with
the PROTOCOLS parameter of the CHGWWWCFG command.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
The WWW130019 PTF
The WWW130019 PTF superceeds the WWW130017 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130019).
The WWW130019 PTF contains the following code changes:
- Fixed a problem where the server was incorrectly converting
escaped characters when running with a Latin 2 content CCSID
(e.g., 912 ISO-8859-2, 1250 Windows Eastern European). This
problem mainly effected scripts and Webulator sessions.
Detailed information on the fix: The server was converting all
of the characters escaped (%xx) by the browser from CCSID 819
to the server job's CCSID. The code has been changed to unescape
the characters from the configured content CCSID to the server
job's CCSID. This problem did not effect double-byte customers.
- Added a new environment variable: CGI_ASCII_CCSID. The
CGI_ASCII_CCSID environment variable value will always be set
to the configured content CCSID.
- Added code that strips leading spaces off of response header
lines returned by scripts. This code was added because some
browsers cannot properly process response headers that begin
with spaces.
- Added a new environment variable: HTTPS. The HTTPS
environment variable has two possible values:
- OFF - Indicates a HTTP (unsecure) request
- ON - Indicates a HTTPS/SSL (secure) request
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130019 PTF HAS BEEN SUPERCEDED BY WWW130022.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130020 PTF
The WWW130020 PTF superceeds the WWW130001 PTF
(i.e., you do not need to install the superceded PTF before installing WWW130020).
The WWW130020 PTF fixes a problem where additional request
processors (RPs) started with the STRWWWRP command were always
using the current job's user portion of the library list, even
when the configured initial library list was set to use the
job description's library list (i.e., CHGWWWCFG INLLIBL(*JOBD)).
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130020 PTF HAS BEEN SUPERCEDED BY WWW130034.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130021 PTF
The WWW130021 PTF superceeds the WWW130004, WWW130011 and WWW130015
PTFs (i.e., you do not need to install the superceeded PTFs before
installing WWW130021 unless you require the old WWWADOPT).
The WWW130021 PTF contains a new version of WWWADOPT called WWWADOPT2,
which should be used to interface with the newer versions of IBM
scripts (e.g., Net.Data).
WWWADOPT2 should be used on systems with V4R2 or greater. WWWADOPT2
may also be used on systems with prior OS/400 versions provided
appropriate PTFs have been applied. Contact IBM if you are unsure if
your version of OS/400 supports stream I/O for stdin/stdout.
WWWADOPT uses QSYS physical files internally to support stdin/stdout,
which is how IBM used to interface with CGI programs. WWWADOPT2 uses
IFS stream files internally to support stdin/stdout, which is IBM's
new way of supporting stdin/stdout. Using stream files eliminates
the former line length limitations.
After installation, WWWADOPT2 needs to be copied into your IBM
script libraries and aliases and/or links will need to be changed
to use the new WWWADOPT2.
Please see the WWW130015 PTF section and
other superceeded PTFs for additional information on using installing
and using WWWADOPT and WWWADOPT2.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
The WWW130022 PTF
The WWW130022 PTF superceeds the WWW130019 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130022).
The WWW130022 PTF fixes a problem where the output of a script
returning parsed HTML data was being corrupted when the parsed
data included an "exec" of another script (CGI program).
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130022 PTF HAS BEEN SUPERCEDED BY WWW130027.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130023 PTF
The WWW130023 PTF contains code changes to fix problems where the
server could insert invalid characters in the configuration file when
the ADDWWWCTP, CHGWWWCTP, ADDWWWINCL, CHGWWWINCL, ADDWWWICON,
CHGWWWICON, ADDWWWSCPL, or CHGWWWSCPL commands were used on an AS/400
running OS/400 level V4R2 or above. These problems could also
manifest themselves as memory errors (MCH3601 errors) while executing
the listed commands.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
The WWW130024 PTF
The WWW130024 PTF fixes a problem where spooled file lines were
being truncated when displayed through the server.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130024 PTF HAS BEEN SUPERCEDED BY WWW130025.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130025 PTF
The WWW130025 PTF superceeds the WWW130024 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130025).
The WWW130025 PTF fixes a problem where some double-byte data being
returned from a spooled file was displayed incorrectly. Double-
byte characters that included a single-byte '>', '<', or '&' were
being corrupted.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
The WWW130026 PTF
The WWW130026 PTF contains code changes to fix problems where the
server request processor ends abnormally with an MCH3601 error
unmonitored by function stricmp in the module WWWBUTIL. This occurs
when the authentication directive "REQUIRE none" is specified in a
limit section that involves dynamic indexing where a specialized
header or footer are used, effectively turning off authentication
for the specified directory. Typically the browser user will either
see a "Document contains no data" or "The server returned an invalid
or unrecognized response" message when attempting to view the index.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
The WWW130027 PTF
The WWW130027 PTF superceeds the WWW130022 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130027).
The WWW130027 PTF fixes a problem where authentication would not
work properly when posting data. The browser would display a
network error instead of the desired authentication dialog. This
problem was encountered when posting larger (e.g., >4K) amounts
of data. Another symptom of this problem is the browser displays
a network error instead of the proper server error on bad requests.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130027 PTF HAS BEEN SUPERCEDED BY WWW130028.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130028 PTF
The WWW130028 PTF superceeds the WWW130027 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130028).
The WWW130028 PTF fixes a problem caused by the WWW130027 PTF where
Webulator close session redirects and script redirects on posted requests no longer worked properly.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
The WWW130029 PTF
The WWW130029 PTF superceeds the WWW130028 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130029).
The WWW130029 PTF is only required by Commerce Server/400 customers
that install the COM100009 PTF. This PTF must be installed at the
same time the COM100009 PTF is installed.
This provides no functionality if you
are not running Commerce Server/400.
NOTE: This PTF has been integrated into the Web Server/400 1.3C and Commerce Server/400 1.0D products.
NOTE: THE WWW130029 PTF HAS BEEN SUPERCEDED BY WWW130033.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130030 PTF
The WWW130030 PTF fixes a problem where the CONTENT_LENGTH environment
variable was not set correctly in a mixed byte environment where the
length of the posted data changed due to conversion from ASCII to
EBCDIC.
Prerequisites:
- Web Server/400 installations:
- Web Server/400 version 1.3C installed or
WWW130028 PTF installed
- Commerce Server/400 installations:
- Commerce Server/400 version 1.0D installed or
WWW130029 PTF installed
NOTE: Commerce Server/400 customers can install the WWW130029 PTF
without installing the COM100009 PTF.
The WWW130031 PTF
The WWW130031 PTF superceeds the WWW130030 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130031).
The WWW130031 PTF fixes a memory problem when retrieving form variables in
a CGI program. Specifically, the corrected error is MCH0601 unmonitored
at statement 44 by WWW_InitFormData in WWWSREXT of WWWRP1SRV or at statement
39 by reUnEscapeURLChars in WWWRESC of WWWRP2SRV. This error has only been
reported to occur on some OS/400 V5R1 systems.
Prerequisites:
- Web Server/400 installations:
- Web Server/400 version 1.3C installed or
WWW130028 PTF installed
- Commerce Server/400 installations:
- Commerce Server/400 version 1.0D installed or
WWW130029 PTF installed
NOTE: Commerce Server/400 customers can install the WWW130029 PTF
without installing the COM100009 PTF.
NOTE: THE WWW130029 PTF HAS BEEN SUPERCEDED BY WWW130033.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130032 PTF
The WWW130032 PTF superceeds the WWW130025 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130032).
The WWW130032 PTF fixes a problem where some double-byte data being
returned as part of the display of database and spooled files was not
displayed as expected. Double-byte fields are typically shown with
spaces in place of the SO (Shift Out) and SI (Shift In) characters.
Previous Web Server/400 logic would remove these characters as part
of the conversion from EBCDIC to ASCII, resulting in the display of
the field without the spaces and a misalignment of the resulting data
(usually most evident in database columns). PTF WWW130032 inserts a
space/blank character whenever a SO or SI character is encountered,
so the field is appropriately formatted for display.
During testing of WWW130032, it was noted by some of the testers that
database and spooled file data seem to be presented best if the
character size is set to "Large" (in IE) or set to "10 point" (in
Netscape). It was also noted that the "SPACING" keyword also assists
the proper presentation of data (more information about the "SPACING"
keyword can be found in the product documentation).
The WWW130033 PTF
The WWW130033 PTF superceeds the WWW130029 and WWW130031 PTFs
(i.e., you do not need to install the superceded PTFs before installing WWW130033).
The WWW130033 PTF fixes a problem where server Request Processor jobs
(jobs named WWRxxx) remain in a TIMW state indefinitely. Viewing the
program call stack for these jobs reveals that they are processing a
write statement via the biSendSock2() function. This is a result of an
indefinite wait by the IBM write() API if the other side of the
connection (the browser) is not receiving the data and the internal
TCP send window has been closed. Typically, this happens because the
server is attempting to send more data than the browser can handle.
PTF WWW130033 changes how the write() API is called to enable the
detection of this situation, allowing the transfer of data to continue
normally.
Corequisites:
PTF WWW130034
NOTE: PTF WWW130034 must also be installed to correct this problem.
NOTE: THE WWW130033 PTF HAS BEEN SUPERCEDED BY WWW130035.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130034 PTF
The WWW130034 PTF superceeds the WWW130020 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130034).
The WWW130034 PTF fixes a problem where server Request Processor jobs
(jobs named WWRxxx) remain in a TIMW state indefinitely. Viewing the
program call stack for these jobs reveals that they are processing a
write statement via the biSendSock2() function. This is a result of an
indefinite wait by the IBM write() API if the other side of the
connection (the browser) is not receiving the data and the internal
TCP send window has been closed. Typically, this happens because the
server is attempting to send more data than the browser can handle.
PTF WWW130034 changes how the write() API is called to enable the
detection of this situation, allowing the transfer of data to continue
normally.
Corequisites:
PTF WWW130033
NOTE: PTF WWW130033 must also be installed to correct this problem.
NOTE: THE WWW130034 PTF HAS BEEN SUPERCEDED BY WWW130036.
YOU MAY WISH TO OBTAIN THAT PTF INSTEAD.
The WWW130035 PTF
The WWW130035 PTF superceeds the WWW130033 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130035).
The WWW130036 PTF corrects a problem where a customer running OS/400
V5R1 received reports that their clients were being notified by their
personal firewall software that the server was doing a port scan of
the clients machine. The shutdown process for the socket connections
to the clients was modified, which eliminated the problem with the
firewalls.
Corequisites:
PTF WWW130036
NOTE: PTF WWW130036 must also be installed to correct this problem.
The WWW130036 PTF
The WWW130036 PTF superceeds the WWW130034 PTF
(i.e., you do not need to install the superceded PTFs before installing WWW130036).
The WWW130036 PTF corrects a problem where a customer running OS/400
V5R1 received reports that their clients were being notified by their
personal firewall software that the server was doing a port scan of
the clients machine. The shutdown process for the socket connections
to the clients was modified, which eliminated the problem with the
firewalls.
Corequisites:
PTF WWW130035
NOTE: PTF WWW130035 must also be installed to correct this problem.
|
Features
