PQ81153: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V5.0 FOR Z/OS.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
This APAR addresses defects in WebSphere Application Server
V5.0 for z/OS.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ81153 addresses various defects  *
*                      in WebSphere Application Server V5.0    *
*                      for z/OS.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ81153 addresses the following defects in
WebSphere Application Server V5.0 for z/OS:

(MD18386) getSharedDataMemberCDRSeq encounters an abend code 0C4
reason code 4 in the controller region.
getSharedDataMemberCDRSeq got back a zero when allocating
storage because there is no more storage available. Attempt to
copy into address zero results in an abend code 0C4 reason
code 4.

DUMP TITLE=COMPON=WEBSPHERE Z/OS,  COMPID=5655I3500,ISSUER=BBOR
LEXT,ABEND IN BBOBOA  /getSharedDataMemberCDRSeq

Traceback
 ORB_Request::getSharedDataMemberCDRSeq(ORB_Request_BigMember
            20E76780  +00000360
 ORB_Request::getLocatingIOR()
            20E892D8  +0000005E
 ORB_Request::comm_outbound_locate()
            20E1A1A8  +000011F2
 ORB_Request::comm_inbound_response(GIOP_Message*,unsigned ch
            20E20138  +0000116C
 ACR_ExecutionThread::ProcessInboundResponse(acrwObj*)
             20DD2E48  +0000018E
 ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*)
             20DD11D8  +00000772
 ACR_ExecutionRoutine

(MD18408) TrustedProxy Custom Property is being ignored when set
at the WebContainer level. The TrustedProxy Custom Property can
be set either as a property of the individual Http Transports or
as a property of the Web Container. If it is set at the Web
Container level, the value is not being propagated to all the
Transports as it should be.

(MD18425) In the administrative console application, clicking
the OK button on the Add Console Group page returns a blank
page. From the Console Group Add page (System Administration >
Console Groups > Add), if a group name that is not found in the
User Registry Repository is entered, a blank page is returned
after clicking the OK button.

(MD18428) Need to enable new HTTP Session
configuration/functionality made by WebSphere distributed. HTTP
session enhancements/configurability was added in the WebSphere
distributed base.  z/OS changes need to made to properly enable
the new Web Container custom properties: HttpSessionIdLength,
SessionRewriteIdentifier, HttpSessionCloneId,
NoAdditionalSessionInfo, SessionIdentiferMaxLength.

(MD18431) Steps in BBOJJINS are numbered incorrectly. Need to
renumber steps in BBOJJINS.

(MD18432) The message MSGS0351W is issued because the wrong
queue manager name was used. The connection to the queue manager
is unavailable.

When a queue is to be created, deleted, or listed, a connection
to the JMS Provider queue manager needs to be done. The wrong
queue manager name was used causing the connection to the queue
manager to be unavailable and the message MSGS0351W to be
issued.

(MD18434) When the dumpLocalNameSpace method on the NameServer
mbean is called, the following message is received. Step:
*** dumpJavaNameSpace() got naming exception during
MetaDataService
lookup: javax.naming.
ConfigurationException: NamingManager.
getURLContext cannot find the factory
for this scheme: services

The mbean is unable to find the local namespace, as it is in
the Servant Region.  However the mbean runs in the Controller.

(MD18436) This affects the wsadmin Scripting interface, when
using conntype NONE. The regeneration of the was.env after
AdminConfig save is processed does not take into account the
newly change XML data.

The call the the Transformer was too soon, and needed to only
occur after the save had completed.

(MD18444) If the cookie name is not set, the default value
"JESSIONID" is used. The default is incorrect and should
be "JSESSIONID".

The messsge:
BBOM0001I protocol_http_session_cookie_name: NOT SET,
DEFAULT=JESSIONID.

Will appear in the joblog.

The default protocol_http_session_cookie_name is incorrect
it should be JSESSIONID.

(MD18480) The App Server abends with user completion code,
USER COMPLETION CODE=4091 REASON CODE=00000025 when starting
queue manager with 5 digit port number.

When the server attempts to initialize the queue manager with a
5 digit port number, the actual port number is still set to
null. When the call is sent to the native code, the queue
manager does not start and the server abends with user
completion code, USER COMPLETION CODE=4091 REASON CODE=00000025.

(MD18485) Message WTRN0081 with errorCode 3 is issued when
commit one phase is driven on the IJP. During a global
transaction, if the IJP is the only resource involved in the
transaction, the transaction service will attempt to commit the
IJP in one phase.  If the IJP has no work to do, it will throw
an exception.  Since the IJP is the only resource, and there
was no work to do, the commit was successful.  However, the
transaction service still reports Message WTRN0081 indicating
that there was an error.

(MD18490) On the Administrative Console Application
Servers > Servers > <server> > ORB Service > Request Timeout
states the value is in seconds, when it was being treated as
1/10 of a second. The Request timeout, which corresponded to the
protocol_iiop_local_timeout needed to be multipled by 10
when put in the was.env.

(MD18499) This defect contains fixes for the following WebSphere
Distributed APARs:
174069 
PQ77785 DRS dead server detection
175729 
PQ78005 Fix CloseJMS behavior for multiple DRSs in a JVM
175781 
PQ78045 Fix DRS to not replicate to same node
176134 
PQ78204 Fix DRS bug which broke Dynacache in Push-Pull
               mode.
178388 
PQ79072 Appserver startup hangs with > 2 DRS instances
178863 
PQ79243 Fix DRS round-robin topic load-balancing in
               single-replica mode

PQ79493 MEMORY TO MEMORY REPLICATION FAILS WITH EOFEXCEPTION

(MD18510) The HttpRequest object's attribute
javax.servlet.error.request_uri may not contain the URI of the
failing request when a Servlet Error Page is dispatched in
response to a servlet error. The attribute
javax.servlet.error.request_uri of the HttpRequest object may
not contain the URI of the failing request when a Servlet Error
Page is dispatched in response to a servlet error.

(MD18522) The configuration file plugin-cfg.xml can not be
displayed at the administrative console. The IBM Http Server
plugin configuration file plugin-cfg.xml will not display when
the view configuration button is pressed in the administrative
console. This happens because the generated configuration file
plugin-cfg.xml has an encoding tag in the prologue for an
encoding not recognized by the browser.

(MD18528) ND configuration dialog does not create statements in
the bbodbrac rexx exec that is run as part of installation
configuration to create RACF certificates for the ID that owns
the controller region.  This will cause SSL Keyring not found
initialization errors. The first time the configuration dialog
is run, there are no saved dialog variables, and the value of
build_WebSphere_Profiles is not Yes or No.  Since the value is
not Yes, the code that generates the RACF commands to create
keyrings and certificates for the ID that owns the controller
region will not be generated.
Problem conclusion
APAR PQ81153 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD18386) Updated comm_outbound_locate in bboocomm.cpp to not
leak IORs.

****************************************************************

Defect MD18386, shipped in Cumulative Fix W502000, requires the
following documentation change:

NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:

www.ibm.com/software/webservers/appserv/zos_os390/library.html
________________________________________________________________
WebSphere Application Server V5 for z/OS
Messages and Codes
GA22-7915-00
_______________________________________________________________
Chapter 3, new code
C9C212F9
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
________________________________________________________________
Chapter 3, new code
C9C212FA
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
________________________________________________________________
Chapter 3, new code
C9C212FB
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.

(MD18408) The Web Container has been changed to reflect the
setting of the TrustedProxy Custom Property at the
WebContainer level to the individual Http Transports.

(MD18425) In this error scenario (specified group is not found),
the code did not set a "next page to display" as it should.
Code was modified to redisplay the current page with the error
message.

(MD18428) Add support to the HTTP transport, SM and Web
Container to completely support new Web Container custom
properties.

(MD18431) A change to the WebSphere Application Server
Customization Dialog will be made available To access the latest
WebSphere for z/OS online documentation, go to the product
library page at:

www.ibm.com/software/webservers/appserv/zos_os390/library/

The change is to file BBOJJINS, which now has correctly-number
steps, as follows:

1.  Review the number of system LXs defined for the target z/OS
    operating system. The value to be used is specified by the
    NSYSLX     parameter of the IEASYSxx member of
      &PARMLIB.
    The default number is 55.

    Each Integral JMS Provider defined in the subsystem name
    table     reserves one system linkage index at IPL time.
    This system linkage index is reused if the Integral JMS
    Provider is stopped and restarted.

    If your environment has a number of subsystems defined that
    use system linkage indexes (for example, DB2, IRLM, and IMS
    V5), you might need to increase the value of NSYSLX when
    you define Integral JMS Provider subsystems. Each Integral
    JMS Provider subsystem reserves one system linkage index,
    and each instance of the distributed queuing feature
    reserves one non-system linkage index.

    NOTE: This step is only required to be performed once per
    z/OS image for which Integral JMS Providers are to be
    configured.

    ------------------------------------------------------------

2.  Update the subsystem name table. The subsystem name table of
...

(MD18432) Supoort was modified to use the queue manager name
obtained from the JMSServer available at the current node.

(MD18434) The mbean needed to be moved to the Servant to
correctly execute the mbean methods.

(MD18436) The code was moved, and the was.env regenerated
correctly.

(MD18444) The default protocol_http_session_cookie_name has been
changed to JSESSIONID.

(MD18480) The actual port number used to start the queue manager
is set to the value obtained from the JMSServer endpoint before
doing any adjustments. The port number is only adjusted if the
port number consists of 1 through 4 digits, inclusive. If no
adjustment is needed, the actual port number contains the
correct 5 digit value.

(MD18485) The transaction service no longer issues WTRN0081 when
it has called commitOnePhase on the IJP and there is no work to
do.

(MD18490) Change was made to make the
protocol_iiop_local_timeout correct.

(MD18499) This defect contains fixes for the following
WebSphere Distributed APARs:
174069 
PQ77785 DRS dead server detection
175729 
PQ78005 Fix CloseJMS behavior for multiple DRSs in a JVM
175781 
PQ78045 Fix DRS to not replicate to same node
176134 
PQ78204 Fix DRS bug which broke Dynacache in Push-Pull
               mode.
178388 
PQ79072 Appserver startup hangs with > 2 DRS instances
178863 
PQ79243 Fix DRS round-robin topic load-balancing in
               single-replica mode

PQ79493 MEMORY TO MEMORY REPLICATION FAILS WITH EOFEXCEPTION WHE

(MD18510) Changes were made to IBM WebSphere Application Server
for z/OS such that when an error page servlet is dispatched,
method WebAppRequestDispatcher() in package
com.ibm.ws.webcontainer.webapp sets the ServletRequest object's
javax.servlet.error.request_uri attribute to be the URI of the
failing request.

(MD18522) Changes are made to WebSphere Application Server for
z/OS such that the plugin-cfg.xml is generated without an
encoding tag in the prologue.

(MD18528) Initialize the value of build_WebSphere_Profiles in
BBODBRAC the same way that BBOWBRAC does.

APAR PQ81153 is associated with SERVICE LEVEL W502000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ81153
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-11-19
Closed date 2003-12-07
Last modified date 2004-01-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
UQ82904

Modules/Macros
BBOACCEP BBOACTF BBOACTT BBOAPPLY BBOCASYH BBOCBRAJ
BBOCBYTO BBOCLOCT BBOCLSAC BBOCLSCC BBOCLSCP BBOCLS
***This field was truncated. To obtain
the full apar record, please contact
your local support center.***    

Publications Referenced
GA22791500        

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ82904    UP03/12/15 P F312

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ81153.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ81153
IBM Group: Software Group
Modified date: Jan 3, 2004