IBM Support

IT02619: JMS MESSAGE SENT FORMAT FROM IBM STERLING B2B INTEGRATOR TO IBM MQ

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • IBM Sterling B2B Integrator 5.2.4.2
    MS SQL Server 2008
    Windows 2008 Server
    IBM Webshpere MQ
    
    Sending a JMS 1.1 message in the TextMessage format from IBM
    Sterling B2B Integrator to IBM
    MQ Series can result in the message being converted to
    undesirable characters set.
    
    Additionally, if you set the CCSID within IBM Sterling B2B
    Integrator it is not picked up as it should be.
    

Local fix

  • STRRTC - 425859
    JG / JG
    Circumvention: None
    

Problem summary

  • USERS AFFECTED:
    ALL
    
    PROBLEM DESCRIPTION:
    TEXTMESSAGE FORMAT SENT FROM SI TO MQ SERIES IS SOMETIMES BE
    CONVERTED TO UNDESIRABLE CHARACTER SET.
    
    PLATFORMS AFFECTED :
    ALL
    

Problem conclusion

  • RESOLUTION SUMMARY:
    THE PROBLEM HERE WAS, THE CUSTOMER DID NOT HAVE A WAY TO SET THE
    ENCODING ON THE DOCUMENT THAT WILL BE SENT AS A MESSAGE TO THE
    WSMQ SERVER.BY DEFAULT,EITHER THE ENCODING STANDARD THAT WAS
    USED TO UPLOAD THE DOCUMENT OR THE NATIVE FILE ENCODING WAS
    BEING USED TO ENCODE THE INCOMING DOCUMENT AND SENT TO THE WSMQ
    SERVER.
    HAVE RECTIFIED THIS BEHAVIOR BY ALLOWING THE USER TO SET THE
    DESIRED DOCUMENT ENCODING AND CCSID VALUE FROM WITHIN OF THE BP.
    WITH THIS CODE CHANGE, WE ARE READING THE STREAM OF BYTES USING
    THE DOCUMENT ENCODING STANDARD SPECIFIED IN THE BP.IF THIS IS
    NOT PRESENT, THEN DOCUMENT ENCODING STANDARD THAT WAS SPECIFIED
    WHILE UPLOADING THE FLLE WILL BE USED.IF THIS IS NOT AS WELL
    MENTIONED THEN NATIVE FILE ENCODING WILL BE USED.
    
    DELIVERED IN:
    5020500_1
    

Temporary fix

  • Fix is available in 5020501 fix pack.
    This fix is as well delivered as an iFix.
    

Comments

APAR Information

  • APAR number

    IT02619

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    524

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-06-18

  • Closed date

    2015-01-22

  • Last modified date

    2015-02-03

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

  • R525 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.4","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
03 February 2015