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

(MD17269) Unable to start daemon on second and subsequent
systems in sysplex, C9C22837.

The problem is that by default, the daemon configured for a
base server configuration on different systems in the sysplex
each have the same specific name. That works fine, because
each base server configuration represents a distinct cell, with
a unique cell name. Once these base server configuration are
joined into the same ND cell, then each system ends up having
a daemon definition that has the same cell name and the same
server specific name. That lack of uniqueness results in only
one daemon being started on one of the systems in the cell.
Attempts to start daemons on other systems in the ND cell result
in failure and hence WebSphere cannot be used on those systems.

(MD17958) WebSphere will sometimes incorrectly attempt to
change the autocommit setting on a connection while enlisted in
a global transaction.  The underlying connection will refuse to
do this and will throw an SQLException similar to the following:

ExtendedMessage: mapException(SQLException);
java.sql.SQLException:
JDBC Connection setAutoCommit() did not call commit
successfully.
at COM.ibm.db2os390.sqlj.jdbc.DB2SQLJConnection.setAutoCommit
  (DB2SQLJConnection.java:1658)
at com.ibm.db2.jcc.DB2LogicalConnection.setAutoCommit
  (DB2LogicalConnection.java:210)
at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl
  .enforceAutoCommit(WSRdbManagedConnectionImpl.java:454)
at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection
  .beginTransactionIfNecessary(WSJdbcConnection.java:527)
at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection
  .createStatementCommon(WSJdbcConnection.java:742)

WebSphere at the W501000 Cumulative Fix level featured a
delayed autocommit where a call to setAutoCommit() on a
WebSphere connection would not be immediately passed on to
the underlying connection.  In some circumstances, a global
transaction can be started in between the time the
setAutoCommit() was called and when WebSphere enforces the
autocommit on the underlying connection.

(MD17975) The Transformer does not correctly allow server level
security to be disabled. Even after security is turned off
com_ibm_Server_Security_Enabled=1 is left in the was.env
The logs would have something like:
CORBA::NO_PERMISSION with a minor code of c9c240b2
when an IIOP client is trying to connect.

(MD18029) The plugin-cfg.xml file is generated at the wrong HFS
location in the wrong code page. The IBM Http Server plugin
configuration file plugin-cfg.xml is generated into a location
in the HFS which is different than that documented.  The
configuration file is generated with an encoding of ISO-8859-1
and is thus not readable by the IBM Http Server.

(MD18031) Dialog generated file BBOWSECD is not setting up
unauthenticated userid to something other than WSGUEST.
The problem turns out to be when you are running the dialogs
and have both a base and ND version of SAVECFG with a value of
unauthenticated userid other than WSGUEST at a service level of
W500100, W500101, W500102, or W500103, and you migrate to
W500104 or later.  The base version will migrate cleanly, but
the ND SAVECFG is not automatically updated.

(MD18038) The WSADMIN client does not have a RACF Keyring with a
WAS certificate authority certificate in it.  When the client
attempts to connect to the server, the following message is
seen:
RACFInputStream caught
java.io.IOException: profile for ring
not found java.lang.RuntimeException:
profile for ring not found

When using wsadmin.sh to connect to a WAS server using the SOAP
protocol, a keyring not found message is issued, and the
connection fails. This occurs because the a RACF Keyring was not
created for the WSADMIN userid during installation/configuration
and the soap.client.props file specifies the RACF Keyring as
a keystore.

(MD18043) Permission Bits are not correctly set on the dll's
that are in a RAR file when that RAR is an embeddeded RAR.  The
external symptom is exception java.lang.UnsatisfiedLinkError
when you use the connector.

A JCA connector archive (RAR file) can contain DLLs (.so files)
A connector can be installed either standalone or as a module
in an application archive (embedded EAR file).
When a RAR containing DLLs is installed as an embedded RAR, the
execute permissions are not enabled for the DLLs and need to be.

(MD18071) RACFInputStream caught java.io.IOException:
profile for ring not found java.lang.RuntimeException:
profile for ring not found
when trying to use wsadmin.sh or addNode.sh to connect to the
server using the SOAP protocol.  The problem occurs after an
initial configuration (cold  start) start of W501000, and occurs
on both the Application Server and the Deployment Manager.

The files specify a RACF Keyring as the keystore for
certificates used by JSSE.  The JSSE/JCE RACF Keyring support is
in a release that is not required by this level of WAS.  The
support should be removed until the level of java that supports
RACF Keyrings in JSSE/JCE ships. This problem occurs on a
cold-start of W501000. An apply of this PTF on top of an
existing WebSphere V5.0 configuration (Warm start) are
unaffected. This error could also occur if the ++HOLD
information for W501000 was not followed with respect to
soap.client.props.

(MD18076) WASX7017E: Exception received while running file
"MD17790_apply.jacl";
exception information:
com.ibm.bsf.BSFException: error while
eval'ing Jacl expression: invalid
command name "-"

The code page for the MD17790_apply.jacl, MD17790_backout.jacl
MD17790_apply.xsl and MD17790_backout.xsl files is incorrect.
Problem conclusion
APAR PQ79314 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD17269) Support was provided such that during addNode
operation update node-level variable
WAS_DAEMON_ONLY_server_specific_short_name to be equal to the
system name.

(MD17958) Support has been modified such that calls to
setAutoCommit() are now passed on immediately.

(MD17975) The security.xsl transform was updated to take into
account, both the cell level security setting and the server
level security setting.

(MD18029) An additional file plugin-cfg-ascii.xml is generated
for viewing at the browser.  Also, the pluginCfg.jsp is modified
to display the plugin-cfg-ascii.xml.

(MD18031) Support was modified to use the variable ALLUSRD
(instead of WEBUUSR) for all unauthenticated ids. Dialog files
have been updated to ensure the generated file BBOWSECD to have
other values than WSGUEST.

(MD18038) BBOWBRAC was updated to create a RACF keyring owned by
the default WS Admin id, and connect the WAS certificate
authority certificate to the keyring so that SSL will be able to
complete the handshake. By placing the code to create the
keystore in BBOWBRAC, the fix will be run automatically as part
of initial configuration of WebSphere (cold start).

(MD18043) Code was added to the RAR Install Process to ensure
the bits are set.

(MD18071) The correct soap.client.props files for both the
Application Server and the Deployment Manager are now shipped by
default.

(MD18076) The post installer files are provided in the correct
code page.

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

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOALLOC BBOCCINJ BBOCCINS BBOCR2FD BBOCSMGR BBODCFG
BBODCFG2 BBODCHFS BBODCPYD BBODCPY2 BBODC2N BBODIA
***This field was truncated. To obtain
the full apar record, please contact
your local support center.***    

Publications Referenced

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

Applicable component levels
R500 PSY UQ80952    UP03/10/14 P F310

  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: swg1PQ79314.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 #: PQ79314
IBM Group: Software Group
Modified date: Nov 2, 2003