A fix is available
APAR status
Closed as unreproducible in next release.
Error description
SQL Apply includes the Apply qualifier in the dataset name specified for the LOB file reference variable when processing LOB columns. However, the underscore is an invalid character for z/OS dataset name and Apply will fail with SQLCODE -452.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 1- SQL Apply users * * 2- Agricultural Bank of China * * 3- ASNCLP users * **************************************************************** * PROBLEM DESCRIPTION: 1- SQL Apply failed SQLCODE -452 when * * Apply Qualifier includes an * * 'underscore' character * * 2- Customer has the same subscription * * id under multiple consistency groups. * * Load dummy fails since they have the * * same naming format for the * * intermediate dataset created. * * 3- When DB2 for z/OS is configured to * * use a comma as the decimal point * * (DECIMAL=COMMA set to TRUE), the * * ASNCLP script to create a Q * * subscription can fail. Insert * * statements into the IBMQREP_SRC_COLS * * table in the script can have a missing * * space after a comma, causing DB2 to * * misinterpret the comma and issue a * * DSNT408I SQLCODE -104 error (illegal * * symbol). * **************************************************************** * RECOMMENDATION: * **************************************************************** 1- SQL Apply includes the Apply qualifier in the dataset name specified for the LOB file reference variable when processing LOB columns. However, the underscore is an invalid character for z/OS dataset name and Apply will fail with SQLCODE -452. 2- When Apply does loaddummy, it creates temp dataset and names it with user id and sub id, which cause duplicate dataset error in multiple consistency group scenario. 3- As a workaround, you can fix the generated script before running it by ensuring there are no missing spaces after commas, for example changing this line: ('ZZZ0001', 'ID',1, 'YNNNNNNNNN');
Problem conclusion
Temporary fix
Comments
1- Apply is changed to remove the 'underscore' before using it in the dataset name. 2- With this fix, apply will use combination of user id, ASID, sub ID and browser ID to name dataset, so that every dataset name will be unique. 3- The ASNCLP is fixed to always add a space after commas in the script.
APAR Information
APAR number
PI75005
Reported component name
WS REPLICATION
Reported component ID
5655L8800
Reported release
A21
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-01-16
Closed date
2017-02-06
Last modified date
2017-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI44451 UI44452 UI44453 UI44454
Modules/Macros
ASNAAPP ASNACMD ASNACMP ASNADMSP ASNAFET ASNAISO ASNAMAN ASNAPPLY ASNAWPN ASNCAP ASNCCMD ASNCLPAP ASNCLPCL ASNCLPCM ASNCLPCO ASNCLPMS ASNCLPQA ASNMCMD ASNMON ASNQACMD ASNQAPP ASNQCAP ASNQCCMD ASNQDEP ASNQEXRP ASNQLODZ ASNQMFMT ASNQP2PI ASNQXFMT ASNRBASE ASNTDIFF ASNTDSP ASNTRC ASN2BASE
Fix information
Fixed component name
WS REPLICATION
Fixed component ID
5655L8800
Applicable component levels
RA21 PSY UI44451
UP17/02/15 P F702
RA24 PSY UI44452
UP17/02/15 P F702
RA25 PSY UI44453
UP17/02/15 P F702
RA26 PSY UI44454
UP17/02/15 P F702
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":"SSDP5R","label":"InfoSphere Replication Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A21","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 March 2017