APAR status
Closed as program error.
Error description
EmailInput node if reading a non-ascii email ( eg: a mail with Japanese characters), may cause failure if the flow is trying to cast the email body to character.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM App Connect Enterprise V12, V11 and IBM Integration Bus V10 using the EmailInput node and receiving non-ASCII emails. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: <span style="background-color:rgb(255, 255, 255)">A message flow with an EmailInput node may fail if it tries to cast to character the body of an email message that contains non-ASCII characters, for example Japanese characters.</span> The EmailInput node's behavior is to encode the email body using the charset identified from the email header. As an example, i<span style="background-color:rgb(255, 255, 255)">n the case where an email is sent </span>with charset=iso-2022-jp and with Japanese characters in the body, it encodes the body using the iso-2022-jp encoding. However, if the message flow later uses the following ESQL to cast the email body to character, it will give incorrect results as the body is not encoded in 1208 CCSID. CAST( EmailBody AS CHARACTER CCSID 1208 ENCODING 546 )
Problem conclusion
The EmailInput node behaves as expected, using the charset encoding identified from the email header to encode the email body. Users are expected to use the same encoding, which will be available in the message tree propagated out of the EmailInput node, when converting the email body to character from BLOB. For users who would prefer the EmailInput node to avoid using the charset encoding from email headers, this APAR provides the following environment variable that can be set: export MQSI_EMAILINPUTNODE_USE_DEFAULT_CHARSET=Y With this set, the EmailInput node will use the platform default encoding to encode the message body. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.25 v11.0 11.0.0.15 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT35985
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-02-22
Closed date
2021-10-29
Last modified date
2021-10-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
INTEGRATION BUS
Fixed component ID
5724J0540
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]
Document Information
Modified date:
30 October 2021