PQ77964: 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 PQ77964 addresses various defects  *
*                      in WebSphere Application Server V5.0    *
*                      for z/OS.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ77964 addresses the following defects in
WebSphere Application Server V5.0 for z/OS:

(MD17555) Support is needed to make the Daemon register with
the WLM DNS configurable.

Currently,  'WAS_DAEMON_ONLY_daemon_wlmable' hard coded with the
value of 'false' in the cell level variables.xml (dialog
skeleton: bbowvaa1.slb2).  We need to allow this value to be
configurable through  the ISPF dialog panels.

Also, we need to provide a way for the customer doing WARM
START to easily change the value for
'WAS_DAEMON_ONLY_daemon_wlmable' from 'false' to 'true'.


(MD17591) When running in PRR mode, the transaction service is
unabled to display information about unresolved transactions on
other WebSphere for z/OS servers. The systems management
functions to determine server name from UUID are no longer
sufficient.  In WebSphere V5.0, the complete server name
requires access to information about the cell, node, and cluster
as well as the server name.

(MD17603) exception id: CORBA::MARSHAL minor code: c9c20d1d
from filename: ./bbocior.cpp at line: 937 received when trying
to manipulate a 1.0 IOR during initial reference resolution.

IIOP 1.0 IORs used for resolving initial references included
an invalid multicomponent tag count.

This problem was exposed when the default level used for initial
reference IORs was changed to IIOP 1.0, as specified by
CORBA 2.3 as the default for ObjectURLs with no IIOP major/minor
version specified.

(MD17611) The disable JIT check box on the server's Process
Definition does not work. It is accessed on the Administrative
Console at:

Application Servers -> <servers> ->
Process Definitions -> <control|servant> ->
Java Virtual Machine -> disable JIT.
The required property was not added to the servant.jvm.options
or control.jvm.options, depending on which was modifed.
The property that was needed is: -Djava.compiler=NONE

(MD17716) Transactional ENQs are obtained by the Controller
region to ensure the proper routing of Transactional work.  The
ENQs are obtained in 2 distinct functions within the Controller
region.  They must generate the same ENQ Rname in both functions
to ensure the proper routing of the Transactional work.
Currently, there is a difference between the 2 functions.  One
issues an ENQ with an Rname that includes the Cluster Name
followed by a truncated GTID (bbo3mvs.h). The GTID is missing
its last 8-bytes.
The difference between these two functions can lead to routing
mistakes.  This can cause locking problems such as deadlocks.

The DEQ will attempt to release 1 version of the ENQ Rname.
So, because of the difference in generating the ENQ Rnames,
for every ENQ obtained with the Cluster Name followed by a
truncated GTID, the ENQ will be "leaked".

(MD17747) During the dialog step BBOMCFG, the installed HFS
structure will be created and populated with files from the
SMP/E install directory.  However, files customized by the
dialog should not be copied/linked at this time.  Doing the
copy/link for these will-be-customized files will cause the copy
job BBOWCPY2 (this job copies the dialog-customized files into
the installed HFS) to fail if it is not run with a UID=0 userid.

Support should be modified to exclude those will-be-customzied
files from being copied or linked during the BBOMCFG
(invokes bbowhfs1.sh) step.

Files to exclude are:

<WAS_HOME>/bin/setupCmdLine.sh

<WAS_HOME>/properties/wsadmin.properties
<WAS_HOME>/properties/sas.client.props
<WAS_HOME>/properties/soap.client.props

(MD17780) When applications that use either the DB2 390 Local
JDBC Provider or the Cloudscape Jdbc Provider attempt to get a
connection, a ClassNotFound exception will occur because the
class, DB2Wrapper, cannot be found. This occurs because the
db2Interfaces.jar which contains this class does not exist in
the lib directory.

(MD17803) When starting a clustered server, created using
wsadmin, the server does not start. The message:
BBOM0053E FOR ENVIRONMENT VARIABLE server_generic_short_name A
VALUE MUST BE ASSIGNED.
is found in the logs.

The problem was caused by the cluster="" attribute not being
set correctly in the XML.  As a result the Transformer did not
have the necessary information to create the
server_generic_short_name.  This only affects users of wsadmin.

(WS17417) Service support that ship changes to the "install
root" during a PTF install may require a corresponding
change to the  "config root". For example, if a new
executable or script is added to the config root,
a symbolic link needs to be created from the "config
root" back to the new executable or script in the
"install root". Other problem such as xml files in the
"config root" may need updated.
Problem conclusion
APAR PQ77964 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD17555) ISPF Dialog files will be updated to add an option
allow 'register Daemon with WLM DNS' configurable.  Also, a
shell script will be provided to allow customers doing a WARM
START to change 'WAS_DAEMON_ONLY_daemon_wlmable' from 'false'
to 'true'.

With this PTF, if you want to enable (or disable) the daemon
registering with WLM DNS, then you will need to do the following

For each WAS_HOME:

1. stop the server

2. copy daemon_wlmable.sh  and daemon_wlmable.jacl from
   the  <smpe root>/bin directory to your <WAS_HOME>/bin

3. To enable the daemon registering with WLM DNS,
   go to the directory <WAS_HOME>/bin and run
   daemon_wlmable.sh with a 'true' parameter:
          daemon_wlmable.sh true

   To disable the daemon registering with WLM DNS,
   go to the directory <WAS_HOME>/bin and run
   daemon_wlmable.sh with a 'false' parameter:
          daemon_wlmable.sh false

4. the daemon's was.env file should have the entry:
     daemon_wlmable=1   (if you run it wit the 'true' parameter)

     daemon_wlmable=0   (if you run it wit the 'false' parameter

5. re-start the server

(MD17591) The object keys used for transaction service related
CORBA objects have been extended to include information about
the server that created the object key.  This information will
be used (if available) when issuing messages about unresolved
transactions involving other WebSphere for z/OS servers.

(MD17603) Support was modified to correct the generation and
management of IIOP 1.0 IORs used to resolve initial references.

(MD17611) Code was added to ensure the disable JIT option
(if checked) places the -Djava.compiler=NONE flag into the
jvm.options files.

MD17716) The ENQ Rname generated across the 2 functions have
been modified to generate the same format.

(MD17747) bowhfs1.sh will be updated to exclude files from being
copied o the AppServer or DeploymentManager directories.

(MD17780) The build/component information for the db2Interfaces
jar will be corrected to ensure the db2Interfaces.jar is
included in the lib directory.

(MD17803) Support was modified to ensure the cluster="<cluster>"
attribute is added to a Cluster Member.

(WS17417) A new "post install" framework is necessary to correct
all the aforementioned problems and any future problems that may
arise. It allows developers to perform any post-install actions
on the config root they see fit for their particular defect
(i.e. modify the content of existing files  in a config root).
It is performed automatically for most cases after first server
restart. Finally, it is able to backout a service change to a
previous level (backout the post install actions)

APAR PQ77964 is associated with SERVICE LEVEL W500104 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ77964
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-08-30
Closed date 2003-08-30
Last modified date 2003-10-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

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

Applicable component levels
R500 PSY UQ79825    UP03/09/10 P F309

  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: swg1PQ77964.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 #: PQ77964
IBM Group: Software Group
Modified date: Oct 3, 2003