A fix is available
APAR status
Closed as program error.
Error description
SQL Apply failed -918 when deleting from remote LUW target
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 1- all SQL Apply users * * 2- Customers those who are using asnmon for * * mail encryption on Z/OS * * 3- SQL Apply users * * 4- All Capture users * **************************************************************** * PROBLEM DESCRIPTION: 1- SQL Apply does not show in sqlcode * * column in ibmsnap_applytrail for -904 * * 2- In ASNMON running on z/OS, an issue * * was identified with the log formatting * * of the email_server field. The field, * * which is expected to be a string, was * * mistakenly formatted using %d instead * * of %s. Since %d is intended for * * integers, this resulted in incorrect * * log entries and confused the customer. * * To resolve this, the formatting should * * be corrected to %s, ensuring proper * * handling of the email_server value in * * log messages. * * 3- SQL Apply failed -918 when deleting * * from remote target * * 4- The subsystem name in capture trace * * is incorrect. * **************************************************************** 1- SQLCODE column in IBMSNAP_APPLYTRAIL is not being updated for sqlcode -904 (sqlstate 57011). 2- The email_server field, which is a string, was incorrectly formatted using %d instead of %s. Since %d is meant for integers, this resulted in improper log output. 3- Running SQL Apply on zos and the target table is on LUW. If Apply deletes from target table using TRUNCATE and fails-904. then Apply deletes from the target using DELETE and will fail -918. The same TRUNCATE/DELETE processing works if the target is on zos 4- The line for 'subsy name = ' in the trace is the capture_server parameter, not subsystem name.
Problem conclusion
1- Apply is changed to always update the APPLYTRAIL table for sqlstate 57011. 2- The log formatting issue in ASNMON on z/OS was caused by incorrectly using %d instead of %s for the email_server field, which is a string. This led to incorrect log entries and potential readability issues for customers. By correcting the format specifier to %s, the problem can be resolved, ensuring accurate logging and proper handling of the email_server field. 3- Apply will be changed not to use TRUNCATE to delete from the target table if running on zos. 4- Add code to display subsystem name after each connect. ASNCLP was not updated. Function Level: 1140.103
Temporary fix
Comments
APAR Information
APAR number
PH65715
Reported component name
WS REPLICATION
Reported component ID
5655L8800
Reported release
B33
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2025-03-18
Closed date
2025-04-29
Last modified date
2025-05-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO02988 UO02989 UO02990 UO02991
Modules/Macros
ASN2BASE ASN2DBCN ASN2ZOSC ASNAAPP ASNACMD ASNADMSP ASNAPPLY ASNAPRS ASNCAP ASNCATM ASNCCMD ASNDBCON ASNMCMD ASNMON ASNMUPDT ASNQACMD ASNQAPP ASNQCAP ASNQCCMD ASNQDEP ASNQEXRP ASNQMFMT ASNQXFMT ASNRBASE ASNTDIFF ASNTDSP ASNTRC ASNZOSCN
Fix information
Fixed component name
WS REPLICATION
Fixed component ID
5655L8800
Applicable component levels
RB33 PSY UO03409
UP25/05/31 I 1000
RB34 PSY UO02989
UP25/05/02 I 1000
RB35 PSY UO02990
UP25/05/01 I 1000
RB36 PSY UO02991
UP25/05/01 I 1000
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":"BU029","label":"Software"},"Product":{"code":"SSDP5R","label":"InfoSphere Replication Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B33"}]
Document Information
Modified date:
31 May 2025