PQ57771: EXCESS DATA RETURNED ON CALLS TO IMS

APAR status
Closed as fixed if next.

Error description
Customer is testing connection management and is receiving:
javax.servlet.http.HttpUtils.getRequestURL(req).toString()
throws a null pointer exception
req.getParameterValues('aFormField')  0
throws a null pointer exception when a null output byte
is given to the Interaction.execute, the byte     returned
should contain only the IMS tran output data for the correct
length.  It appears to contain extra junk data.  In this
case the output is 128 bytes while the buffer returned is
256 bytes.
.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390 who use the       *
*                 IMSAPPC Connector.                           *
****************************************************************
* PROBLEM DESCRIPTION: When an EJB that is running with a      *
*                      transaction policy of TX_NotSupported   *
*                      uses the IMSAPPC connector to issue     *
*                      a request to IMS, the resulting output  *
*                      record contains the proper response     *
*                      plus additional garbage data at the     *
*                      end of the valid response data. As a    *
*                      result of the garbage data, the         *
*                      application may fail with a null        *
*                      pointer exception when it attempts to   *
*                      process all the returned data.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the IMSAPPC connector is used with a policy of
Tx_NotSupported to process a request, the request to IMS is
performed as a Sync-On-Return request. In this case, processing
to receive the output and final session status from IMS is
performed in a loop. When the complete data is received, the
total output count is incremented by the length of the data
received. Processing then loops again to receive final session
status. When the final "Deallocate Normal" status is received
from IMS, the total output count is again updated (generally by
the same amount as the first time). This is incorrect since the
complete data had already been received. As a result, an output
area twice the size of the actual response is returned to
the caller with garbage data in the last half of the output
area. To correct this, the loop needs to be changed to remember
if the "Complete Data" had already been received. If it had,
the total output count would not be updated.
Problem conclusion Temporary fix Comments
This APAR is being closed FIN with concurrence from the
submitting customer. A solution to this problem will be
delivered within the next 18 months in the next version of the
beta connector support located on the WebSphere Application
Server for zOS and OS/390 download web-site:


http://www.ibm.com/software/webservers/appserv/download_v4z.html
APAR information
APAR number PQ57771
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2002-02-12
Closed date 2002-02-26
Last modified date 2002-05-01

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels
R401 PSN    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ57771
IBM Group: Software Group
Modified date: May 1, 2002