A fix is available
APAR status
Closed as program error.
Error description
DB2IDAA defect pi38336 dpi38336 SQLCODE950 is returned from DSNXEPM when a query is offloading to the acclerator even though the accelerator where the query tries to routed to is correctly defined in the CDB (Communication Database) and the SYSACCELERATORS table. The accelerator block has the list of the accelerator name and the location name sorted by the accelerator name. If the accelerator where the query is routed to happens to be listed after the other accelerator whose location name should come after in ascending order, DSNX8API fails to find the correct location name, then ended up in SQLCODE -950. For example, the accelerator block has the following list; 1) Accelerator name DB2AIDAA, location name LOC1DB2A 2) Accelerator name DB2BIDAA, location name DB2BIDAA When a query is offloading to DB2BIDAA, the find function seaches the location name from the list, but it fails to detect DB2BIDAA since it won't go back to search the location name in descending order once it reaches to LOC1DB2A. ************************************************************** Additional Symptoms and Keywords: IDAA IDAAV2R1/K IDAAV3R1/K IDAAV4R1/K SQLCODE -4742 SQLCODE4742 SQL4742n SQL04742n SQLCODE -950SQLCODE950 SQL950n SQL00950n
Local fix
Re-define the accelerator using the location name that matches to the accelerator name.
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who * * use IBM DB2 Analytics Accelerator. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may incorrectly detect an SQLCODE * * -4742 or -950 condition when work is * * being off-loaded to an accelerator. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 was not able to find the accelerator based on the Location name if the Location name is different than the Accelerator name. DB2 was also not able to find the accelerator if an Accelerator Only Table (AOT) is used and the Accelerator name is not the actual accelerator name reflected in the DDL statement.
Problem conclusion
DB2 has been changed to find the accelerator based on the Location name.
Temporary fix
Comments
APAR Information
APAR number
PI38336
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-04-06
Closed date
2015-05-22
Last modified date
2015-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI27882 UI27883
Modules/Macros
DSNX8API
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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
15 October 2021