PQ59473: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
This APAR addresses defects in WebSphere Application Server
V4.0.1 for z/OS and OS/390.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390.                  *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ59473 addresses various problems *
*                      in WebSphere Application Server V4.0.1  *
*                      z/OS and OS/390.                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ59473 addresses the following problems in
WebSphere Application Server V4.0.1 for z/OS and OS/390:

(MD09328) The System Management End User Interface
(Administration and Operations applications), also known as the
SM EUI, can be used to set an SSL Keyring value for a server.
After this is done, however, the SSL_KEYRING environment
variable for that server still displays a value of "NOT SET"
in the log.  This creates confusion because the environment
variable listing for SSL_KEYRING seems to contradict the value
set in the SM EUI and that stored in the database.

(MD10052) When a failure occurs while the code is trying to
create a backup copy of an environment file, there is no
indication in the messages returned to the user or, in the
trace, of what exactly went wrong. The createBackupCopy method
in bbomutil.cpp and other code for renaming files in
bbomsbo2.cpp are using system() to directly issue a system mv
command to rename files.  Because system() returns only a return
code to indicate success or failure, with no information about
the specific problem that caused the rename to fail, the trace
records indicated only that a failure occurred.

(MD11101) During import, any problems with processing an EAR
file result in a non-specific error being returned to the
SM EUI. Examples:

   BBON1092E An internal error occurred while importing server
   XXX.
   BBON0126E CORBA system exception.

During EAR file processing, an UnableToProcessEARFile exception
was thrown, along with a message indicating that there was a
problem with a particular EAR file.  This was passed back to
ImportJ2EEServer in bbomsbo6.cpp, which had no specific catch
block for this exception, so a generic catch block caught it
and threw UnableToImportServer with only the BBOM1092 message.
This effectively "lost" the detailed information in the messages
on the UnableToProcessEARFile exception.

(MD12490) When activating a previously passivated CMT stateful
bean, the session sync object may not get set correctly.
Therefore updates made in a CMT session bean with at-tran
activation policy may be lost.

(MD12522) Changes are required to the order of steps in the
migration instructions produced by the "WebSphere for z/OS
Customization" Dialog. BBOMCFG must be run after the code
upgrade is complete in the HFS and after the servers are
warm-started.

1. If the HFS upgrade is not done ahead of the BBOMCFG,
the new resource type templates are not available to be
copied from the install HFS to the configuration HFS.

Example of symptoms when BBOMCFG fails because the
HFS is not up-to-date and copy failures result:

!!!!! Problems that occurred while processing !!!!!
===================================================
Could not copy file. RC=1
cp  /u/usr/lpp/WebSphere/samples/MQRRSQueueConnectionFactory.xml
bSphere390/CB390/PLEX1/resources/templates/MQRRSQueueConnecti
actory.xml
Could not copy file. RC=1
cp  /u/usr/lpp/WebSphere/samples/MQRRSTopicConnectionFactory.xml
bSphere390/CB390/PLEX1/resources/templates/MQRRSTopicConnecti
actory.xml
Could not copy file. RC=1
cp  /u/usr/lpp/WebSphere/samples/MQQueueConnectionFactory.xml
bSphere390/CB390/PLEX1/resources/templates/MQQueueConnectionFact
.xml
Could not copy file. RC=1
         .
         .
         .
/==============================================================/
/===> Processing log end                                    ===/
/==============================================================/

The EXEC has completed with Return Code 12

Please refer to the OS/390 UNIX Messages and Codes,
book to interpret the Return and Reason Codes.
Please correct and resubmit.

2. If the installation ran BBOWCMIG before all servers were
warm-started, depending on workload balancing in the SYSPLEX for
the server side processing (SMAPI server and SM scripting), a
system will be selected that has not yet been warm-started. As a
consequence, the SM scripting will operate on function level 1,
while the SMAPI server side code will operate on
function level = capability level = 2. This mismatch will lead
to an internal error or a property error and an RC4 to the
script, which ignores it and carries on. So the migration will
not run. The only way to tell is whether in the
RemoteWebContainer application the RemoteWebContainer component
has the resource connection IBMHttpSession defined. If defined,
the migration was successful. If is not defined then the
migration was not successful.

(MD12525) When a user attempts to export a server using the
"exportserver" or "exportj2eeserver" functionality of the SM
Scripting API, one of the parameters the user must supply in the
REXX script is the name of the server to export.  If the user
provides an invalid or non-existing server name, the SM
Scripting API should return a meaningful error message
indicating that the server could not be found.

Currently, the ExportServer and ExportJ2EEServer methods called
by the SM Scripting API check for the existence of the server
specified for export.  If the server is not found, however, the
code does not return any meaningful error text to the user.  The
user will see text like the following:
"message.1  =  BBON3199E Method exportserver failed."
"message.2  =  BBON1057E"
The user is told that the export has failed, but is not told
why.
Problem conclusion
APAR PQ59473 provides the following problem resolution:

(MD09328) The code in the CbEnvironment::print() method of
bbomenv.cpp was modified to check the MVS::ORBType prior to
printing out the environment variable SSL_KEYRING.  This
environment variable is now displayed only for client regions.
For all other cases, SSL_KEYRING is no longer shown in the
environment variable listing.

The code for the SCOI_Server_Impl::print() method of
bbomscsr.cpp, which is called only by servers and never for
client regions, was also modified to print out the value of
the SSL Keyring server property.  In the server logs,
therefore, the value of the SSL Keyring server property is
displayed correctly and the SSL_KEYRING environment variable
is not displayed at all.

(MD10052) Support was modified in the createBackupCopy method
in bbomutil.cpp and the WriteEnvironmentFiles method in
bbomsbo2.cpp to include information about the specific problem
that occurred.

(MD11101) ImportJ2EEServer in bbomsbo6.cpp was modified to catch
any UnableToProcessEARFile exception thrown from importServer,
and to include all associated messages on the
UnableToImportServer exception that it throws.

(MD12490) Support has been modified such that, upon activation
of a session bean, the session sync object is correctly set for
the bean being activated.

(MD12522) The following changes were made in the
"WebSphere for z/OS Customization" Dialog migration
instructions:

- For both procedures (system-wide restart and rolling warm
  start) move the step for running the BBOWCMIG job after the
  step in which the all run-time and application servers (in
  the monoplex or sysplex) have been warm-started.

- Remove step 9 in the procedure on system-wide restart and
  replace it with the step for running BBOWCMIG.

- Remove step 8 in the procedure on rolling warm start and
  replace it with the step for running BBOWCMIG.

- In the rolling warm start procedure, move the substep about
  switching the HFS before the substep in which the BBOMCFG
  job is run.

(MD12525) The ExportServer method in bbomsbo3.cpp and the
ExportJ2EEServer method in bbomsbo6.cpp were both modified to
provide a more meaningful error message when the server
specified by the user cannot be found.  Now, the user will
receive an error message like the following:
"message.1  =  BBON3199E Method exportserver failed."
"message.2  =  BBON1000E The Server object, FOOSERV1, could not
 be found"

APAR PQ59473 is associated with SERVICE LEVEL W401036 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ59473
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-03-26
Closed date 2002-03-27
Last modified date 2002-05-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ64634    UP02/04/02 P F204

  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


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ59473
IBM Group: Software Group
Modified date: May 2, 2002