A fix is available
APAR status
Closed as program error.
Error description
Customer is implementing FMT features of FTM and we received the above messages after putting a message on the MQ queue DNI.DNF_PF_IS. Customer use DECIMAL = COMMA, in the DSNHDECP module. This seems the root of the problem, probably the query should be modified to accept this parameter. OUMO DNF_PF_CMD SQL error on table 'FTM30.DNF_IAMS'; SQL code='-1'; SQL state='37000'; SQL error text='{DB2 FOR OS/390}{ODBC DRIVER} {DSN11015} DSNT408I SQLCODE = -104, ERROR: ILLEGAL SYMBOL ",47". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: ??( [ CONCAT || / MICROSECONDS MICROSECOND SECONDS SECOND DSNT418I SQLSTATE = 42601 SQLSTATE RETURN CODE DSNT415I SQLERRP = DSNHPARS SQL PROCEDURE DETECTING ERROR DSNT416I SQLERRD = 3 0 0 -1 36 502 SQL DIAGNOSTIC INFORMATION DSNT416I SQLERRD = X'00000003' X'00000000' X'00000000' X'FFFFFFFF' X'00000024' X'000001F6' SQL DIAGNOSTIC INFORMATION ERRLOC=5:10:1'; SQL native error='-104'; SQL statement='SELECT DISTINCT SUBSTR(IAMS.PAYLOAD,47,9) AS SENDLT FROM FTM30.DNF_IAMS AS IAMS LEFT JOIN FTM30.DNFP_FRSS AS FRSS ON IAMS.MSGID=FRSS.IAM_MSGID WHERE (LTNAME=? OR LTNAME=?) AND FMTSTATE =' ' AND FMTGRP IS NOT NULL AND FRSS.PFR_DNOTR='T' AND SSN > ? FETCH FIRST 30 ROWS ONLY'
Local fix
all of the SQL have to add a blank before the comma, this would need FTM for SWIFT L3 to revise that.
Problem summary
**************************************************************** * USERS AFFECTED: All users * **************************************************************** * PROBLEM DESCRIPTION: SQL=-104 during execution of FMTSTART * **************************************************************** * RECOMMENDATION: * **************************************************************** Formerly, if in DB2 a comma is configured as the decimal point, and an fmtstart command is issued and FIN messages are processed in the FMT FIN services, then it was possible that an DB2 SQL error message with code -104 was issued that reports an illegal character in an SQL statement.
Problem conclusion
Now this problem has been fixed and FIN messages are processed successfully in the FMT FIN services.
Temporary fix
Comments
APAR Information
APAR number
PI83183
Reported component name
FTM SWIFT SVCS
Reported component ID
5655FTB30
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-19
Closed date
2017-08-25
Last modified date
2017-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
DNI00000
Fix information
Fixed component name
FTM SWIFT SVCS
Fixed component ID
5655FTB30
Applicable component levels
R300 PSY UI49816
UP17/08/30 P F708
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"300","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAKKL","label":"IBM Financial Transaction Manager for SWIFT Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"300","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
14 August 2020