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

(MD15654) WebSphere Application Server V5.0 for z/OS does not
provide an assembler mapping of its SMF type 120 records.
Assembly of assembler parts using the names specified in
the Operations and Administration book will fail because
the names given to the fields of the SMF records are not
unique.

(MD17948) The following exception was encountered when
installing an application using Admin Scripting.
"Unexpected exception caught while:
java.lang.IllegalArgumentException: argument number too large
at"
The problem is due to a particular message text "ADMA0080W"
not containing the supported format for displaying a argument.

(MD18482) When a client does a lookup of a WSN namingcontext
object on a server1 and server1 forwards the lookup to server2,
where the object being requested lives, the lookup returns
NULL to the client. In this case a WSN namingcontext gets
resolved with method resolve_complete_info which is designed
to marshal serialized data.  In this case we went into server1
with resolve_complete_info but in server1 the object was
assumed to be a cos-naming-context and went to server2 as a
resolve, which does not handle serialized data. So the
serialized data, which was the object to be returned, was not
returned.  This resulted in a null being returned to the
client.

(MD18708) On the Web Container Advanced Settings update page
in the Administrative Console (Servers > Application Servers >
servername > Web Container > Advanced Settings), the
Transaction Class Mapping field is required, but should not be.

(MD18733) A client (or a server acting as a client) sends a
GIOP LocateRequest message and receives back a LocateReply
message with status code 4 (LOC_SYSTEM_EXCEPTION).  This
causes the client to loop repeatedly issuing the same
LocateRequest. Code is missing to detect and process status
code 4.

(MD18740) The WebSphere for z/OS documentation needs to
properly document the definition for the "Enable SAF
authentication using LTPA or ICSF login tokens" field in the
Customization Dialog Security Domain help files and
corresponding InfoCenter article.

(M18793) There is no performance improvement when the "Pass by
Reference" checkbox is checked on the ORB section of a server
on the Administrative Console. If you Navigate to the ORB Panel:

Servers > <server name> > ORB Service
When checking the checkbox: "Pass by Reference"
the Transformer does not write the expected jvm option:
-Dcom.ibm.CORBA.iiop.noLocalCopies=true
into the servant.jvm.options file.

(MD18796) Certain PMI metrics that are suppose to always
increase over time, such as 'total number of requests sent to
the ORB,' are decreasing when servants stop if client was not
polling for the PMI data while servants stop and reconnect
later.

While using Tivoli Performance Viewer to monitor performance
data, the performance data that are monotonically
non-decreasing actually decrease over time especially when
servants are being stopped and the Tivoli Performance Viewer
was disabled when the servant stopped. PMI data is polled from
the client in order for proper aggregation even during servant
stop, but if the client temporarily stops polling for the PMI
data when the servant stops then always increasing PMI metrics
decrease when the client connects again after the servant
stops.

(MD18811) If a max string is specified for the field "WAS Home"
on panel BBOWPW11, the generate will fail when it tries to
generate BBOMCFGW.  The error is as follow:

 ISPF156

 Output overflow
 Line to be written greater than data set LRECL 80

 File tailoring input line:
 '/WebSphere/V5R0M0/Servers/xxxx/xxxx/xxxxx/AppServer/xxxx/xxx
    /xxxx/xxx

The reason for the failure is that the value entered on the
panel can be greater than 80 characters and the max string that
it allow in BBOMCFGW is 74 characters.  Any strings greater
than 74 characters will result in generate error.

(MD18821) Servant region abends with:

BBOO0037E Function IWMSSEL failed with RC=8, REASON=11090854.
BBOO0035W TERMINATING THE CURRENT PROCESS, REASON=C9C21231.

After selecting work from wlm the servant checks to
see if the work timed out. If so the servant does not process
the work because the controller region already responded. The
servant region then asks wlm for the next piece of work without
issuing IWMSTBGN and IWMSTEND. IWMSSEL responds with a bad
return code and reason code saying the caller is
attempting to select more work units than it has tasks to
execute the work.

(MD18832) An Ant build file that uses the core Ant Input task
<Input ... /> does not return when enter is pressed. Due to
the differences in encoding between the system running in
EBCDIC and Ant running in ASCII, an input handler will be
needed to handle the ASCII/EBCDIC conversion when using the
standard Input Ant task.

(MD18872) While handling a PrivilegedActionException, the
WSManagedConnectionFactoryImpl class attempts to use the message
FAILED_DOPRIVILEGED_J2CA0060, which is found in the J2C resource
bundle.  This class can only access messages in the Adapter
resource bundle, and so if the user encounters this code, they
will see a java.util.MissingResourceException that references
the missing key FAILED_DOPRIVILEGED_J2CA0060 as opposed to the
error text that they are supposed to see. The actual handling of
the PrivilegedActionException works correctly, but the user will
not see the intended error message.

(MD18879) The Modify command DISPLAY,HELP shows help text for
all the options of the display command. Text for the new two
new options 'WORK' and 'ERRLOG' is missing.

(MD18896) Need to update Japanese files for the WebSphere for
z/OS Customization Dialog. Currently, in the WebSphere for z/OS
Customization Dialog, the Japanese and English dialog files are
out-of-sync. The purpose of this defect is to update the
Japanese dialog files so that they will match the English files.
Problem conclusion
APAR PQ83624 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD15654) Provide an assembler mapping, bboos120, that has
unique field names.

(MD17948) Fixed the message format to display "ADMA0080W"
correctly.

(MD18482) Code was modified to narrow the context being
looked up. In narrowing, the code would have recgonized the
context as a wsn-naming-context. Then naming would have
resolved the context using resolve_complete_info and the
serialized data would be marshalled correctly, completing the
lookup successfully.

(MD18708) The console-defs.xml and validation.xml files have
been updated so the Transaction Class Mapping field is no
longer required.

(MD18733) Code is added to detect status code 4 and to raise
the system exception contained within the LocateReply message
to the client.

(MD18740) A change to the WebSphere for z/OS Customization
Dialog help panel BBOWDH12 has been made to document the
definition for the "Enable SAF authentication using LTPA or
ICSF login tokens" field in the Customization Dialog Security
Domain.

A change to the WebSphere Application Server InfoCenter file
rins_defvar1 will be made. To access the latest online
documentation, go to the product library page at:

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

The change to each will read as follows:

Enable SAF authentication using LTPA or ICSF login tokens

Specify "Y" to enable the WebSphere Application Server for z/OS
servant to authenticate users to the SAF registry without
providing a password or SAF-specific authenticator. This is
required when:
  - WebSphere Application Server for z/OS security is enabled
  - Local OS is the active registry
      and either:
  - ICSF or LTPA is the authentication mechanism OR
  - A Trust Association Interceptor is in use.

Setting this value to "Y" permits the WebSphere Application
Server for z/OS servant runtime (an unauthorized application) to
log on to z/OS with a z/OS userid but no z/OS authenticator. Thi
is required to establish a z/OS userid via the verification of a
WebSphere Application Server for z/OS login token verification o
Trust Association Intercepter.

Note: Easing some traditional z/OS system restrictions places
additional responsibility on the WebSphere Application Server fo
z/OS administrator to ensure that installed applications do not
contain malicious code. You can use Java 2 security to minimize
this exposure.

(MD18793) Modified Transformer to write this JVM option for the
servant region.

(MD18796) Current PMI MBeans have been enhanced to be able to
store stopped servants' performance data in support of
monotonically non-decreasing performance data even if the PMI
clients are not constantly polling for PMI data while servants
stop. Current design of only aggregating stopped and/or
terminated servants' PMI data when PMI clients poll for PMI
data is updated with hybrid poll/push model for PMI data
aggregation to avoid monotonically increasing PMI metrics from
decreasing when servants' stop by pushing the latest PMI metrics
for the stopping servant upto the controller for proper
aggregation without polling.

(MD18811) The dialog skeleton file BBOMCFGW has been updated to
split the value for "WAS Home" into two lines. With this change,
BBOMCFGW will generate without any error.

(MD18821) Updated bbooboat.cpp to issue IWMSTBGN and IWMSTEND
for work selected from wlm that is not being processed by the
servant because it timed out and the controller already
responded to the client.

(MD18832) The new Input Handler is used as the default handler,
using the -inputhandler parameter on Ant.

(MD18872) The exception handling code for the
PrivilegedActionException was reworked to emulate the exception
handling for the same exception a few lines later.  This not
only fixes the problem with the bad message, but makes the
exception handling for PrivilegedActionExceptions the same
throughout this method.

(MD18879) Added help text for the two new options.

(MD18896) The dialog hass been updated so that the Japanese and
the English dialog files will be in-sync.

APAR PQ83624 is associated with SERVICE LEVEL W502001 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
&#158;**** PE04/02/04 FIX IN ERROR. SEE APAR 
PQ84216  FOR DESCRIPTION
APAR information
APAR number PQ83624
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 2004-01-22
Closed date 2004-01-29
Last modified date 2004-02-12

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOCCFMT BBOCGIOP BBOCSESS BBOLRT BBOMREQI BBOMSCO
BBOOBOAI BBOOBOAT BBOOCOMM BBOOEJSB BBOOORB BBOOORBR
BBOSSRIB BBOSTOS BBOUBINF BBOZ1514 BBOZ1548 BBOZ1558
BBOZ1569 BBOZ1575 BBOZ1585 BBOZ1587 BBOZ1592 BBOZ1596
BBOZ1605 BBOZ1610 BBOZ1617 BBOZ1632 BBOZ2313 BBOZ2642
BBOZ2643 BBOZ2651 BBOZ2667 BBOZ4271    

Publications Referenced

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

Applicable component levels
R500 PSY UQ84418    UP04/01/30 P F401

  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: swg1PQ83624.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 #: PQ83624
IBM Group: Software Group
Modified date: Feb 12, 2004