A fix is available
APAR status
Closed as program error.
Error description
DB2DDF DDFL09 defect pk68492 dpk68942 SQLCODE843 (-843) is issued from a SET CONNECTION statement after PK61025(UK35028/UK35029) is applied. The stored procedure goes outbound to 3 different remote locations and then does a SET CONNECTION to the local site where the stored procedure is running. This SET CONNECTION statement receives the -843. ************************************** Additional keywords and symptoms: SQLCODE -843 843 SQLCODE843 SQL843N SQL0843N during SQL Set Connection SetConnection
Local fix
A bypass is to use CONNECT TO local site statement instead of the SET CONNECTION statement.
Problem summary
**************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically users of remote stored * * procedures. * **************************************************************** * PROBLEM DESCRIPTION: A remote stored procedure issuing a SET * * CONNECTION to the local DB2 server * * incorrectly receives SQLCODE -843. * **************************************************************** * RECOMMENDATION: * **************************************************************** A client application running at Site1 calls a remote stored procedure that runs at DB2 for z/OS on Site2. The stored procedure performs a SET CONNECTION to Site2, but incorrectly receives SQLCODE -843 indicating that the connection to the local DB2 server Site2 does not exist. This problem occurs after applying PK61025 / UK35028 / UK35029. PK61025 changed SET CONNECTION processing for DBATs such as remote stored procedures, to check that "connection" related control blocks exist for the target location rather than checking that "DBAT" related control blocks exist. However "connection" related blocks do not exist for the local DB2 server. Only "DBAT" related blocks exist for the local server. This causes DB2 to invalidly issue SQLCODE -843 whenever a remote stored procedure does a SET CONNECTION to its local server.
Problem conclusion
DB2 for z/OS SET CONNECTION processing has been changed to check for "DBAT" related control blocks first before using "connection" related control blocks to determine the existence of a physical connection for the target location. This method matches that of CONNECT TYPE 2 processing and hence prevents DB2 from issuing the invalid SQLCODE -843 when a remote stored procedure performs a SET CONNECTION to its local DB2 server.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PK68492
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
810
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2008-07-02
Closed date
2008-08-06
Last modified date
2008-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK38747 UK38748
Modules/Macros
DSNLQDIS DSNLXRCN
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 September 2008