PQ74701: PROVIDE THREAD IDENTITY SUPPORT FOR CONNECTORS FOR WEBSPHERE FOR Z/OS 5.0 | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Connector Thread Identity Support will not be available at GA and will be implemented with this APAR. Thread Identity Support is the capability to have the identity associated with the current thread be used as the owner of the connection when a getConnection() is issued with res-auth=Container. This capability was supported in WebSphere z/OS 4.0.1 and will be added to WebSphere z/OS 5.0 with this APAR. Until this APAR is implemented, customers will be able to associate a userid/password with each ConnectionFactory or datasource that is configured. The associated userid will then be used as the connection owner whenever a connection is requested from the configured ConnectionFactory or datasource.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Need to provide thread identity support * * for connectors under WebSphere V5.0 * * for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** In WebSphere V4.0.1 for z/OS and OS/390 when getting a connection, support was provided by Connection Management to use the userid associated with the current thread as the owner of the connection. This support was provided for IMS, CICS, and DB2 JDBC connectors. Similar support is required in WebSphere V5.0 for z/OS 5.0 for these connectors.Problem conclusion This apar fix provides the capability to use the identity of the current thread as the owner of a connection when obtaining a connection. This function is only applicable to the following connectors that support the use of thread identity when getting a connection: 5.01 CTG CICS ECI Connector, IMS 2.1 Connector, the DB2 390 Local JDBC Provider for WebSphere V5.0 for z/OS used through the Relational Resource Adapter (RRA), and the IMS JDBC Connector for WebSphere V5.0 for z/OS. In the case of the DB2 390 Local JDBC Provider, the support is initally only available for the new 5.0 datasource support used J2EE 1.3 applications. This function is also applicable to connections obtained through the WebSphere MQ JMS Provider, i.e. external MQ, (see PQ74697 for more details). APAR PQ74701 requires a change to the WebSphere V5.0 for z/OS documentation. To access the latest online documentation that discusses the Thread Identity Support, go to the Web site at: http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp The InfoCenter is updated with the following three new files: cdat_conthid rdat_conthidref tdat_conthidep Enter "thread identity" as the InfoCenter search argument to see the content in these files. The documentation describes the thread identity support function, and lists the steps required to implement this function. It also defines levels of thread identity support. APAR PQ74701 is associated with SERVICE LEVEL W500103 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: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ74701.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 #: PQ74701
IBM Group: Software Group
Modified date: Aug 8, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.