PQ49461: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0 FOR Z/OS AND OS/390. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V4.0 for z/OS and OS/390.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ49461 addresses various problems * * in WebSphere Application Server V4.0 * * for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ49461 addresses the following problems in WebSphere Application Server V4.0 for z/OS and OS/390: WebSphere Application Server V4.0 for z/OS and OS/390 does not support standard WebSphere JNDI context factory. This factory is required for interoperable JNDI between WebSphere Advanced and WebSphere Application Server V4.0 for z/OS and OS/390. There is an incorrect DTD in initial.xml file. The DTD for datasource and datasource_instance differs from the export generated, it's also missing some attributes for the two items. The code in the method SupportedSecurities::initSupportedSecurities() does not handle IORs that are improperly formed and may cause an abend. This problem would surface with CEE dumps indicating a storage access problem. While recycling servers which have naming registration work to do the Naming registration/deregistration is putting too many messages on the console.The messages that are written out to the console should be restricted to telling the begin/end of the Naming registration work for every specific server, so that automation tools can react on these events, all other messages for homes, components, etc. should be written to the server logs only. The client_environment file contains the wrong mount point name web/usr/lpp/CB390. It should be usr/lpp/WebSphere. EJB applications that use the WebSphere Application Server V4.0 for z/OS and OS/390 IMSAPPC Connector beta support to send a transaction request to IMS may receive an output record back that is greater than the actual message text that was received from the transaction. This will not cause a failure or an error to occur, but it does result in inefficient data movement since the returned output record is larger than necessary. The problem occurs because the IMSAPPC connector invokes IMSAPPC communication support in the WebSphere/390 product to do the actual send/receive of a transaction request. In doing so, a maximum output size equal to the OutputSize property specified in the connector's InteractionSpec is passed to the IMSAPPC communication support in the WebSphere/390 product. The IMSAPPC communication processing in the WebSphere/390 product upon completion of the send/recieve request then returns the resulting transaction message in an output area equal to the OutputSize rather than the message text size.Problem conclusion Standard JNDI context factory: com.ibm.websphere.naming.WsnInitialContextFactory is now provided by WebSphere Application Server V4.0 for z/OS and OS/390. The DTD in bbom.initial.xml has been corrected. The code was changed to check the validity of the length fields encounted in the IOR before any memory access is made. Code has been changed such that messages for homes and component are written to the server logs. Only begin/end of naming registration is logged to the console. The path statements in sample file /usr/lpp/WebSphere/samples/smapi/client_enviroment has been been modified to be /usr/lpp/WebSphere. The IMSAPPC communication processing in the has been changed so that transaction message text that it receives will be returned to the IMSAPPC Connector in an output area that is equal to the size of the message text. The WebSphere IMSAPPC connector beta support will then propagate the resulting message text area back to the output record that the EJB application specifies when it initiates a transaction request. As a result, the EJB application will receive an output record back that contains only the message text that was received from the transaction request. A change is required to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/ The following document must change: ________________________________________________________________ Document Name: WebSphere Application Server V4.0 for z/OS and OS/390 Installation and Customization Document Number: GA22-7834-00 ________________________________________________________________ Messages BBOU0696I and BBOU0698I are now written only to the JESMSGLG of the systems management server. Thus, on page 239, in the section entitled "Steps for running the WebSphere for z/OS bootstrap and re-initializing application servers," step 2 should read: 2. After the bootstraps are complete and the Daemon has been re-initialized, start one server instance for each of your application servers. Wait for initialization to complete before starting new server instances. RESULT: You should see messages like the following: BBOU0694I Naming registration started for server SERVER BBOU0695I Naming registration completed for server SERVER where SERVER Is the name of the application server. ________________________________________________________________ WebSphere Application Server V4.0 for z/OS and OS/390 Messages and Diagnosis GA22-7837-00 ________________________________________________________________ Appendix B, pg. 495 (changed section) Appendix B. Automation-geared messages Table 12. Messages that can help with automation |---------------|---------------| |BBOU0001I |BBOU0158E | |---------------|---------------| |BBOU0002I |BBOU0174E | |---------------|---------------| |... |... | |---------------|---------------| |BBOU0127E |BBOU0694I | |---------------|---------------| | |BBOU0695I | |---------------|---------------| ________________________________________________________________ The WebSphere Application Server V4.0 for z/OS and OS/390 Assembling J2EE Applications (SA22-7836-00) will be changed as follows: ________________________________________________________________ Chapter 8. Creating and running J2EE application clients Change the rule listed for Steps 2 and 6 under the topic, "WebSphere Application Server Standard Edition for z/OS or OS/390 clients" on page 57: Rule in Step 2 ("Code and test the servlet and JSP components of your J2EE application"): J2EE application clients must set the Java property key java.naming.factory.initial to com.ibm.websphere.naming.WsnInitialContextFactory Rule in Step 6 ("Define your J2EE application clients to the WebSphere Application Server by setting Web Application properties in the was.conf file"), for setting initial context and naming provider properties: * deployedwebapp.<webapp_name>.java.naming.factory. initial=com.ibm.websphere.naming.WsnInitialContextFactory * deployedwebapp.<webapp_name>.javax.naming.provider.url= iiop://x.x.x.x:ppp where x.x.x.x:ppp is the IP address and port of the WebSphere for z/OS systems management server. You must specify a value for this property to access the WebSphere for z/OS naming service on another sysplex, or to access the JNDI on an Advanced Edition WebSphere Application Server running on a workstation platform. Change the rule for naming provider property, listed under the topic, "Native z/OS or OS/390 clients" on page 60: * To access the WebSphere for z/OS naming service, clients must set the property: javax.naming.provider.url=iiop://x.x.x.x:ppp where x.x.x.x:ppp is the IP address and port of the WebSphere for z/OS systems management server. You must specify a value for this property to access the WebSphere for z/OS naming service on another sysplex, or to access the JNDI on an Advanced Edition WebSphere Application Server running on a workstation platform. APAR PQ49461 is associated with SERVICE LEVEL W400018 of WebSphere Application Server V4.0 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ54982 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ49461
IBM Group: Software Group
Modified date: Aug 3, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.