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

(MD17236) An ABENDSC78-A8 while trying to use local
communications to contact a server that has terminated.

When trying to establish a local comm session to a server,
a previous connection may be found to exist.  If the server
has gone down since that connection was established, the
connection is no longer valid and needs to be removed from the
list.  A logic error exists in the code which removes entries
from the local comm connection list which results in an attempt
to free the same element twice, resulting in the C78 abend.

(MD17244) Application server and Deployment manager can get
error(s) for IWMECREA with RC=8, REASON=0330083B when stopped.
An internal request is being generated for the Servant while
WebSphere application server is coming down, causing errors for
function IWMECREA to be seen in the controller output and on the
system log.

(MD17252) Need to provide WAS zOS runtime compatibility with
applications developed in WSADIE Version 4.1.2 and WSADIE
Version 5.0.1. Without this fix, users may hit a problem like:
  "Unchecked exception detected: java.lang.NoSuchFieldError:
  fieldProvidersInitialized".

(MD17257) Users can not perform addNode or removeNode from the
administrative console. The operation hangs until
the administrative console receives an HTTP timeout, error 505.

When add or remove node is requested from the Network Deployment
administrative console, it directs the app server to
launch the addNode.sh or removeNode.sh script. The target script
is invoked through the BBOW5SH procedure, which is started by
the application server.  The application server wraps the target
script in a temporary shell script written to the /tmp
directory.  The temporary shell script is used to ensure the
length of the script name plus parameters does not exceed the
126 character SVC 34 command length restriction. The application
server creates the temporary shell script, but delegates
responsibility to the BBOW5SH procedure for issuing chmod to
turn on the execute bit on the temporary shell script. Since
chmod can be execute successfully only by the file owner or a
superuser - and the user identity assigned to the BBOW5SH
procedure is typically neither - the chmod fails.  Since the
chmod fails, the execute bit is not on.  Since the execute bit
is not on, the temporary shell script cannot be executed.  Since
the temporary shell script cannot be execute, the addNode or
removeNode operation does not take place.  Since the operation
does not take place, the administrative console receives no
feedback. Since the administrative console receives no feedback,
it waits until it gets a HTTP timeout.  When this
problem occurs, the BBOW5SH job log contains the follow errors:

chmod: FSUM6180 file "/tmp/addNode2487.sh": EDC5139I Operation
not permitted.

ICH408I USER(WSADMIN ) GROUP(DSOMTEAM) NAME(WAS ADMIN)
  /tmp/addNode2487.sh CL(FSOBJ   )
  FID(01D6D4F2C2F2C2000F04000BB4F20000)
  INSUFFICIENT AUTHORITY TO OPEN
  ACCESS INTENT(--X)  ACCESS ALLOWED(OWNER      RW-)
  EFFECTIVE UID(0000002565)  EFFECTIVE GID(0000002268)

(MD17258) Successful stop of servers gives unsuccessful message
in administrative console. The following message appears on the
administrative console when a server is successfully stopped:

  <server-name> server could not be stopped View server logs
  for further details.

This problem is caused by the fact that the Server MBean runs
within both the control process and each servant process for
an application server. Each instance of the Server MBean
registers to listen for Component.STATE changes. When the state
changes to Component.STOPPING each instance of the Server MBean
issues a j2ee.state.stopping notification. Each of these
j2ee.state.stopping notifications get forwarded to the node
agent. The node agent, in turn, issues a
websphere.process.stopping notification for each
j2ee.state.stopping notification that it receives. This means
that n+1 websphere.process.stopping notifications are issued
(where n is the number of servants for the application server
that is being stopped). These multiple
websphere.process.stopping notifications are causing the
administrative console to (incorrectly) determine that the stop
action failed.

(MD17268) In the administrative console, if you navigate
as follows:
  AppServer > <server> > ORB Service > AdvancedSettings

The panel for the description of the "Workload Profile" field:
"Specifies server wrokload profile: ISOLATE, IOBOUND,
CPUBOUND, or LONGWAIT."

The is a typo. "wrokload" should be "workload".

(MD17282) Users can not Start or Stop cluster from
administrative console or wsadmin script.

The cluster mbeans which are part of the wlm components not
activated because the workloadmanager component is not loaded
by the server runtime . The wlmserver.jar and wlmclient.jar
files are not installed in the WebSphere lib directory.
Hence, the WorkloadManager component will not be started.

(MD17285) Users can not sign on to the administrative console
with security enabled. User will get Role based authorization
check failure message:

Enable check access permission for the config repository.

(MD17286) Installing a Resource Adapter file through the
administrative console, can fail with a message similar to the
following:
 ICH408I USER(ASCR1   ) GROUP(WSCFG1  ) NAME(WAS APPSVR CR     )
  /WebSphere/V5R0M0/AppServer/installedConnectors
  CL(DIRACC  ) FID(000000000000000001060000000A0000)
  INSUFFICIENT AUTHORITY TO MKDIR
  ACCESS INTENT(-W-)  ACCESS ALLOWED(GROUP      R-X)
  EFFECTIVE UID(0000002431)  EFFECTIVE GID(0000002500)

When WebSphere customization dialog created HFS, the AppServer
directory was created with permission 755. The group permission
must be 775.
Problem conclusion
APAR PQ77019 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD17236) Updated the logic to move to the next element in the
list after freeing an old entry.

(MD17244) Support has been modified such that a application
server will wait for associated work to complete before
undergoing termination. This wait will eliminate errors for
IWMECREA.

(MD17252) Shipped new versions of physicalrep.jar, marshall.jar,
wsatlib.jar to provide compatibility in WAS zOS runtime up to
the level of these jars within WSADIE version 4.1.2 as well as
WSADIE version 5.0.1.

In addition to fixing the problem mentioned above, this fix,
more generally, brings  the WAS zOS runtime up to the
WSADIE 5.0.1 level.  This adds features such as support for
WSDL output messages with multiple parts in EJB, Java, and
JMS services, as well as other features.  For more information,
and to obtain the latest fixes for the WSADIE product, see:


http://www.ibm.com/software/awdtools/studiointegration/support/

Look for the section "Support Downloads" or "Software Downloads"

Note that the fix provides backwards compatibility so
users of earlier versions of WSADIE, such as WSADIE version 5.0,
will still be able to run their applications unchanged.

Users of WSADIE versions 4.x who have not applied the
WSADIE "e-fix" to upgrade their WSADIE environment to
version 4.1.2 should do so in order to fix the critical memory
leak which was fixed at the 4.1.2 level. This will require
re-generating applications once the WSADIE environment has been
updated.  For example, for a CICS application, start from
the COBOL representation of the CICS transaction and recreate
the CICS Service Project.

The instructions for upgrading WSADIE versions 4.x to WSADIE
version 4.1.2 are also at the URL:


http://www.ibm.com/software/awdtools/studiointegration/support/

Look for the section "Support Downloads" or "Software Downloads"

(MD17257) Support has been modified to do the chmod in the
application server.

(MD17258) As there is no need for the Server MBean to run in
servant processes (only the instance of the Server MBean in the
control process is actually used), a modification was made to
not create the Server MBean in servant processes. This
eliminates the multiple websphere.process.stopping
notifications and causes the administrative console to display
the correct message when a server successfully stops:

  <server-name> server stopped successfully View server logs
  for further details.

(MD17268) The typo "wrokload" has been corrected to "workload"
for the description of the "Workload Profile" field.

(MD17282) Support has been provided to enable the
WorkloadManagerServer component and the wlm management MBeans
code has be provided to enable the ClusterMgr and Cluster
MBeans. start/stop/rippleStart/immediateStop clusters support
is now available throught the administrative console and
wsadmin.

(MD17285) Support has been modifed such that the
RoleBasedAuthorizer is enabled. Calls to configRepository
with security turned on will be checked for access permission.

(MD17286) Support was modified such that the owner was changed
to WSADMIN to facilitate maintenance of the HFS (without the
need to change via a superuser).

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

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOCLCLR BBOCWBAL BBOCWCRR BBOCWSMP BBODASRC BBOMRDTA
BBOOASAD BBOOASAP BBOOASCA BBOOASCC BBOOASCP BBOOAS
***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 UQ79132    UP03/08/08 P F308

  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: swg1PQ77019.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 #: PQ77019
IBM Group: Software Group
Modified date: Sep 5, 2003