PQ77961: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V5.0 FOR Z/OS. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() 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 PQ77961 addresses various defects * * in WebSphere Application Server V5.0 * * for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ77961 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (MD16463) In order to specify a backend_id other than the current default (DB2 for z/OS) customers can set the com.ibm.ws.ejbpersistence.backendid system property via the administrative console. This is unacceptable for the samples. The reasons for the system property have been negated with the current version of ejbdeploy/wccm and so we can once again discover the backend_id at runtime. (MD16482) startServer.sh, startNode.sh and startManager.sh do not function because the initial code (Java) launched from the shell to issue the console commands to start a server is not authorized. The shell code calls java which makes a call to the native code, which in turn calls the MGCRE macro to issue the console command. We are unauthorized running in problem state, Key > 7 and therefore cannot issue the authorized macro. (MD16963) Using security with SSL ID Tracking Enabled can result in the following exception: java.lang.ClassCastException at com.ibm.ws390.wc.http.HttpConnection.getConnectionSessionId (HttpConnection.java:216) SSL ID is not being set in the cookie. (MD17072) Technology Samples javadoc along with sample jacl scripts for MessageDrivenBeans are in the wrong encoding. This causes the javadoc to be unreadable in a web browser and the jacl scripts are unusable. All files located under: samples/javadoc are in the EBCDIC encoding when they should be i ASCII. Also, the jacl script files: samples/bin/MessageDrivenBeans/startMDBSamples.jacl samples/bin/MessageDrivenBeans/stopMDBSamples.jacl are also in EBCDIC when they should be in ASCII. (MD17118) When an application that uses a DB2 390 Local JDBC Provider datasource is configured to run under a Local tran with Resolution-Control set to ContainerAtBoundary, connection management never enlists on the current unit of work to ensure all requests from the application to DB2 will be managed as a single unit under a local transaction. Instead all requests are performed with auto-commit set to true. This causes DB2 to commi each change as it is processed instead of waiting for the Container to commit all the changes as a single unit at the Local Transaction Containment boundary. (MD17180) Currently startServer, startManager, startNode, stopServer, stopManager, stopNode all appear in both AppServer and DeploymentManager bin directories. That is incorrect. For instance, if you invoke /.../AppServer/bin/startManager.sh it fails with "NoSuchServerException' - this happens because there is no dmgr server configuration under the AppServer directory. Here's how it should look: /WebSphere/V5R0M0/AppServer/bin startServer.sh startNode.sh stopServer.sh stopNode.sh /WebSphere/V5R0M0/DeploymentManager/bin startManager.sh stopManager.sh (MD17275) WLM checks either a three or four part entity name in the RACF SERVER class depending on whether dynamic application environments are being used. The WebSphere servant always check a three part name. WebSphere should be consistent with WLM in the entity name that it checks in the server class. (MD17299) ABENDS306-C from BBOSSRVA starting Server Region. When the SR proc STEPLIB's to SBBOLOAD and the STEPLIB also contains non-APF authorized datasets (SBBOLOAD should be APF authorized), then the ?LOAD which BBOSSRVA does for BBO3SBCP fails with a 306-C and SR wouldn't start. Because it loads from authorized code and the only copy load can find is not from an APF authorized source (steplib). (MD17329) This is a problem in the administrative console. Navigate to: Servers > Clusters; Select one of the clusters from the collection and go to its detail view; Enter a new short name; Click APPLY... short name goes back to the original value instead of the new value. Also field is not validated for 1-8 characters; not numeric first char. (MD17350) ABEND0D6/ABENDS0D6 Reason 22 when trying to establish a local IIOP connection to a server whose Daemon is not active. When trying to establish a local IIOP connection to a server, if the server's Daemon has been up, but is not presently up, local communications code will attempt to PC to the Daemon anyway, resulting in an 0D6 abend. (MD17361) When a server starts, it issues a message with its cell name, node name, cluster name, and server name. When it is initialized, it issues a message with just the server name. Since server names are not unique by themselves, it may be difficult to determine which server is actually initialized.Problem conclusion APAR PQ77961 fixes various defects in WebSphere Application Server V5.0 for z/OS. (MD16463) In order to specify a backend_id other than the current default (DB2 for z/OS) customers can set the com.ibm.ws.ejbpersistence.backendid system property via the administrative console. This is unacceptable for the samples. The reasons for the system property have been negated with the current version of ejbdeploy/wccm and so we can once again discover the backend_id at runtime. (MD16482) Support has been modified such that instead of making a JNI call to the native code, if we are running from the shell, we now use Runtime.exec(...). Runtime.exec(...) spawns a new process and calls a new C++ main rountine (bbo3csl.exe). This new C++ part is link-edited AC=1 and is APF-Authorized. Bbo3csl.exe takes the creation parms passed to it on the command line and invokes the orginal native code which issues the console commands. (MD16963) Code needs to be implemented for the SSL ID Tracking code path for both the WebContainer and Control Region in order for the SSL ID to be set in the cookie and used when running with SSL ID Tracking turned on. (MD17072) Specified files are now all shipped in the ASCII encoding. (MD17118) Connection Management processing has been changed to properly enlist on the current unit of work so the resolution control defined for local transaction processing is correctly performed. (MD17180) bbowhfs1.sh has been updated to exclude files from being copied to the AppServer or DeploymentManager directories. (MD17275) Support added to servant authorization check to build a three or four part name consistent with name checked by WLM. (MD17299) Changed the processing sequence to load and call BBO3SBCP from unauthorized code. (MD17329) Code has been added to store the new value of the shortName in the form object. Also fixed the validation rule for the shortName field. (MD17350) Support was modified such that before trying to establish a local IIOP connection to a server, WebSphere for z/OS will verify wheather that server's Daemon presently up. (MD17361) Support has been modified such that initialization complete messages now contain four fill-ins: CELL/NODE/CLUSTER/SERVER. A change to WebSphere Application Server for z/OS V5: Messages and Codes GA22-7915-00 will be available in the next refresh of the documentation. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/library/ ______________________________________________________ BBOO0246I INITIALIZATION COMPLETE FOR DAEMON string/string/string/string. Explanation: Initialization is complete for the WebSphere for z/OS daemon indicated. The process name strings are cell name, node name, cluster name, server name. Programmer response: None. BBOO0247I INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS CONTROL PROCESS string/string/string/string. Explanation: Initialization is complete for the WebSphere for z/OS control process address space indicated. This address space is defined as a server instance in the WebSphere for z/OS Administration end-user interface. The process name strings are cell name, node name, cluster name, server name. Programmer response: None. BBOO0248I INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS SERVANT PROCESS string/string/string/string. Explanation: Initialization is complete for the WebSphere for z/OS application servant address space indicated. The process name strings are cell name, node name, cluster name, server name. Programmer response: None. APAR PQ77961 is associated with SERVICE LEVEL W500104 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ79825 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ77961.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 #: PQ77961
IBM Group: Software Group
Modified date: Oct 8, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.