A fix is available
APAR status
Closed as program error.
Error description
Here is just an example to illustrate this problem. 1/ Create a table on member DB2B at location STLEC1B CREATE TABLE TEST01.TB(C1 INT); 2/ Create an alias on member DB2A at location STLEC1 CREATE ALIAS TEST01A.TB FOR STLEC1B.TEST01.TB; 3/ Create a program APPLX referenced the unqualified alias TB. For instance: INSERT INTO TB VALUES(2); 4/ BIND PACKAGE on member DB2A Because local BIND use QUALIFIER(TEST01A) as expected to resolve the unqualified alias TB internally, it will be successful. However, remote BIND use CURRENT SCHEMA to resolve the unqualified alias TB internally, it will get SQLCODE -204 issued by DSNXOTL indicating TEST01A.TB is an undefined name. BIND PACKAGE(STLEC1.TEST) MEMBER(APPLX) - QUALIFIER(TEST01A) BIND PACKAGE(STLEC1B.TEST) MEMBER(APPLX) - QUALIFIER(TEST01A) Additional keywords: SQLCODE204 SQLALIAS
Local fix
Modify the program to use qualified alias instead of unqualified alias. For example: INSERT INTO TEST01A.TB VALUES(2);
Problem summary
**************************************************************** * USERS AFFECTED: * * All Db2 12 for z/OS users * **************************************************************** * PROBLEM DESCRIPTION: * * Remote BIND PACKAGE fails with SQLCODE * * -204 when the package contains a query * * that references a local alias defined * * on a remote table. * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** Remote BIND PACKAGE fails with SQLCODE -204 when the package contains a query that references a local alias defined on a remote table. The root cause is Db2 did not process the alias for remote bind correctly. Additional Keywords: SQLCODE204 SQLALIAS
Problem conclusion
Db2 code has been changed to process the alias for remote bind correctly.
Temporary fix
Comments
APAR Information
APAR number
PH03111
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-09-21
Closed date
2018-11-16
Last modified date
2019-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI59790
Modules/Macros
DSNXENR DSNXEALS
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RC10 PSY UI59790
UP18/12/06 P F812
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":"12.0","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":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 January 2019