PK86667: MT950 TAG 62 FAILS SWIFT VALIDATION

APAR status

• Closed as program error.

Error description

• MT950 tag 62 fails swift validation
  

Local fix

• WTX00030592
  GK
  No workaround
  

Problem summary

• The SWIFT standard specifies one field 16x followed by another
  field [//16x]^ with the "//" serving as the boundary between the
  two.
  
  Examples:
  a) 12345678901234//16x   = valid (12345678901234)   + (//16x)
  b) 123456789012345//16x  = fails (123456789012345/) + (/16x)
  c) 1234567890123456//16x = valid (1234567890123456) + (//16x)
  d) 123456789012345 //16x = valid (123456789012345 ) + (//16x)
  
  The problem is in example b when the "//" falls on characters 16
  and 17, that is, between where the line between the two fields
  would naturally fall.  The first slash becomes the last
  character of the first field 16x and the second slash becomes
  the first character of the following field, however since it no
  longer starts with a "//", this "/16x" falls down to the [34x]
  Supplementary Details and the actual supplementary details
  "VIREMENT" is seen as excess data.
  
  If the field is padded (as in example d) with a space after the
  15th character, it works.  This is a potential workaround, that
  could be implemented by the customer in the map before
  validating.
  

Problem conclusion

• Updated MT950.xml so the two reference fields 16x and [//16x]^
  are combined into one field 34x^.  This way the "//" can't fall
  on the border between the two 16x fields.
  
  Added checkTag61 function to BaseValidation to check if either
  field contains 0 characters or more than 16.  15-character
  values for Reference for the Account Owner are now supported
  

Temporary fix

Comments

APAR Information

• 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

  WSTX PK SWIFTNT

• Fixed component ID

  5724M6001

Applicable component levels

• R423 PSY

     UP