PQ66464: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() 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 PQ66464 addresses various problems * * in WebSphere Application Server V4.0.1 * * for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ66464 addresses the following problems in WebSphere Application Server V4.0.1 for z/OS and OS/390. (MD13230) Some customers remove the STEPLIB to SGLDLNK from their BBONMS and BBOIRS procedures. WebSphere for z/OS will not run properly without the STEPLIB to SGLDLNK. A comment needs to be added to the generated procedures BBOIRS and BBONMS making it clear not to remove the STEPLIB to SGLDLNK. As a result, files bboirs.slib and bbonms.slib should be modified to add a comment to tell the user not to remove the STEPLIB to SGLDLNK. (MD14587) Requests through the HTTP Transport can have high WLM queue times. The enclave create time is being set as the time the connection was created or when data is first sent in, not when the entire request had been read in. So, the queue time could include time to read the remainder of the request. (MD14588) Excessive Error Log entries for HTTP connections can result since error Log entries are being recorded when asynchronous read failures occur. The error log entry is of the form: BBOU0046E Function BPX1AIO receive failed with... Such socket failure on HTTP connections are expected and as such should be suppressed. (MD14597) Kerberos principals are not tracked in the SMF Type 80 records produced by Audit. The Kerberos principal is not included in calls to checkAuth() when re-using an existing Kerberos credential. This will result in SMF Type 80 audit records for Kerberos users not containing the Kerberos principal. (MD14610) SSL HTTP Transport requests that are not matched by the BBOC_HTTPALL_TCLASS_FILE should use the transaction class specified by BBOC_HTTP_SSL_TRANSACTION_CLASS if specified, but instead the BBOC_HTTP_TRANSACTION_CLASS value is being used, resulting in the requests running under the wrong transaction class. MD14639) SQLException can occur when using CMP inheritance and single table mapping. The exception results because an incorrect subtype is returned. Support should be changed to return wrapper based on home of the correct subtype. Also, support must recognize subtypes and not perform FOR UPDATE sql editing for them because they may be leaf/root (i.e. multi-table mapping) which means SQL contains join, which does not support FOR UPDATE. Since it can not be determined at runtime if the inheritance mapping is single table or leaf/root, it is assumed to be leaf/root. (MD14667) Excessive classloader diagnostic messages are written to the operator console. Support should be changed such that these diagnostic messages are single instance per application per server instance. (MD14680) When BBOC_HTTPALL_NETWORK_QOS=TCLASS is set, the application data being passed to TCP/IP should be the Transaction Class used for the HTTP request and it is not. This data is being passed in an inconsistant form. It is passed as EBCDIC and identified as being ASCII. This mismatch can result in HTTP running at the wrong network QOS classification policy. (MD14721) When the Direct Deployment Tool, 390fy, is run under USS on z/OS, a java stacktrace is printed showing the fact that an internal conversion file is not found. This file name usually shows up as ...UMOFtoMOF2.jar. This error is wrapped by java.lang.reflect.InvocationTargetException: com.ibm.etools.archive.exception.OpenFailureException:IWAJ0048E. This open happens when 390fy is invoked under USS on z/OS. It works correctly when run under Windows environment due to JVM file handling differences between two platforms.Problem conclusion APAR PQ66464 provides the following problem resolution: (MD13230) Comments have been added to the bboirs.slib and bbonms.slib to warn the customer not to remove the STEPLIB to SGLDLNK. (MD14587) Support has been modified such that the enclave create time will be set to the time the entire request was read in for HTTP Transport requests. (MD14588) Support has been modified to expect such socket failures on HTTP connections, and not log errors. (MD14597) Support has been modified to save the RACO generated by Kerberos authorization, which contains audit information, and re-use the RACO when using the existing Kerberos credential to check authorization. (MD14610) Support has been modified such that the correct BBOC_HTTP_SSL_TRANSACTION_CLASS value will be used on SSL HTTP Transport requests. (MD14639) Support has been modified to return the correct subtype from Finder with EJB Inheritance. (MD14667) Support has been modified to issue classloader diagnostic messages to the operator console once per application per server instance. If a classloader diagnostic message has already been issued to the operator console, for an applciation associated with a server instance, it will be directed to error log. (MD14680) Support has been modified such that when BBOC_HTTPALL_NETWORK_QOS=TCLASS is set, the application data being passed to TCP/IP will be the Transaction Class passed back in ASCII. (MD14721)The Direct Deployment Tool, 390fy, has been updated to handle this special case when run under USS on z/OS. The following publication was revised as a result of defect PQ66464: ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Installation and Customization GA22-7834-05 ________________________________________________________________ APAR PQ66464 requires changes 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: http://www.ibm.com/software/webservers/appserv/zos_os390/ ________________________________________________________________ Chapter 3, pg. 75 (changed section) SGLDLNK Your existing LDAP run-time load module library. Attention: Do not go into your BBONMS or BBOIRS proc and remove the STEPLIB to SGLDLNK. LDAP ships two pre-linked versions of module GLDCLDAP (the LDAP client DLL): The regular version of GLDCLDAP is linkedited into the LPA and HFS. A special WebSphere for z/OS version of GLDCLDAP is linkedited into SGLDLNK, which is typically added to the LINKLIST. The special version for WebSphere for z/OS exists because the CORBA naming code talks directly to the LDAP database instead of sending requests to the LDAP server to do the work. The STEPLIB is necessary because, while the correct DLL is in LINKLIST, the "non-WebSphere for z/OS" one is in the LPA. The LPA is searched first in MVS, so the regular version of GLDCLDAP would normally (incorrectly) be used. By putting SGLDLNK in the STEPLIB, it is put ahead of LPA in the search order, and the correct DLL is therefore used. Non-WebSphere for z/OS customers can run with either version (J2EE servers use the LDAP server and can therefore use the DLL in LPA), but WebSphere for z/OS customers must run with the special copy that is in SGLDLNK. There is a link in /usr/lib (or whichever location you specify) for GLDCLDAP to point to /usr/lpp/ldapclient/. This is where the DLL lives in the HFS (non-WebSphere for z/OS copy). ________________________________________________________________ Additional Keywords: /bboocomh.cpp+594 ... BBOU0742E HTTP asynchio routine failed with RV=-1, RC=122, RSN=00000001, ,EDC5122I INPUT/OUTPUT ERROR. APAR PQ66464 is associated with SERVICE LEVEL W401401 of WebSphere Application Server V4.0.1 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: UQ70381 Modules/Macros
|
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 #: PQ66464
IBM Group: Software Group
Modified date: Apr 17, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.