IBM Support

IT18527: SWIFT CATEGORY 3 AND CATEGORY 6 MESSAGES ARE FAILING FOR RULES C98 AND E43 (2016)

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

  • Issue 1 : Customer has recently migrated to 5262_2 to use the
    new SWIFT 2016 standards. After the migration all there MT 300
    and 600 messages started failing with the below errors.
    MT 300.
    In sequence E, field 15E may not be the only field, i.e. if
    field 15E is present, then at least one of the other fields of
    sequence E must be present.
    MT 305, 601.
    In sequence B, field 15B may not be the only field. In other
    words, if field 15B is present then at least one of the other
    fields of sequence B must be present.
    MT 306.
    In sequence K, field 15K may not be the only field; if field
    15K is present then at least one other field in sequence K must
    be present.
    In sequence M, field 15M may not be the only field. In other
    words, if field 15M is present then at least one of the other
    fields of sequence M must be present.
    MT 320, 330, 620.
    In sequence H, field 15H may not be the only field; if field
    15H is present then at least one other field in sequence H must
    be present.
    MT 340.
    In sequence E, field 15E may not be the only field; if field
    15E is present then at least one other field in sequence E must
    be present.
    In sequence G, field 15G may not be the only field, i.e. if
    field 15G is present, then at least one of the other fields of
    sequence G must be present.
    MT 341, 600.
    In sequence D, field 15D may not be the only field, i.e. if
    field 15D is present, then at least one of the other fields of
    sequence D must be present.
    MT 360.
    In sequence O, field 15O may not be the only field, i.e. if
    field 15O is present, then at least one of the other fields of
    sequence O must be present.
    MT 361.
    In sequence P, field 15P may not be the only field, i.e. if
    field 15P is present, then at least one of the other fields of
    sequence P must be present
    Issue 2 : Even though after applying the changes to the maps,
    the message MT300 started failing with another error as below.
    SyntaxSpecific: true Syntax: 12 Start Time Code: 939
    Info:
    10002: Block Count
    33
    10017: Map Iteration Count
    1
    10003: Block Name
    17Y
    10016: Block Signature ID Tag
    17Y
    10015: Raw Block Data
    F
    10019: Location Index
    01
    10900: SWIFT Code
    T36
    10901: SWIFT Description
    Code word error.
    

Local fix

  • Issue 1 : We found that the issue is the extended rule of the
    SWIFT_2016_3** and SWIFT_2016_6**. The problem with rule C98
    being improperly thrown is a bug that existed in 2015 but the
    customer test data is revealing it now in the 2016 maps.
    The messages affected by this issue are the following MT's:
    300, 305, 306, 320, 330, 340, 341, 360, 361, 600, 601, 620.
    Issue 2 : We have fixed this issue by applying changes to the
    properties file as below.
    1) Edit translator_swift_2016.properties file under properties
    folder of SI installation directory
    2) Look for these entries..
    swiftField.17Y.1.1.300='N','Y':T36
    swiftField.17Y.1.1.305='N','Y':T36
    swiftField.17Y.1.1.306='N','Y':T36
    swiftField.17Y.1.1.340='N','Y':T36
    swiftField.17Y.1.1.341='N','Y':T36
    swiftField.17Y.1.1.360='N','Y':T36
    swiftField.17Y.1.1.361='N','Y':T36
    swiftField.17Y.1.1.600='N','Y':T36
    swiftField.17Y.1.1.601='N','Y':T36
    swiftField.17Y.1.1.*='N','Y':T36
    3) Change them to below..
    swiftField.17Y.1.1.300='F','N':T36
    swiftField.17Y.1.1.305='F','N':T36
    swiftField.17Y.1.1.306='F','N':T36
    swiftField.17Y.1.1.340='F','N':T36
    swiftField.17Y.1.1.341='F','N':T36
    swiftField.17Y.1.1.360='F','N':T36
    swiftField.17Y.1.1.361='F','N':T36
    swiftField.17Y.1.1.600='F','N':T36
    swiftField.17Y.1.1.601='F','N':T36
    swiftField.17Y.1.1.*='F','N':T36
    4) Save this file
    5) Restart SI
    

Problem summary

  • Swift Category 3 and Category 6 messages are failing for Rules
    C98 and E43 (2016)
    

Problem conclusion

  • fix provided
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT18527

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    526

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-21

  • Closed date

    2018-04-11

  • Last modified date

    2018-04-11

  • 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

[{"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.6","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
11 April 2018