PH03151: MESSAGE STANDARDS PROBLEMS WITH FIN MT707/MT708 IN SR2018

3.0.0-FTM-SWS-ZOS-fp0008-ifix0001

APAR status

• Closed as program error.

Error description

• The SWIFT standards implementation for SR2018 has the following
  issues for MT707/MT708:
  - MT707/MT708:
  1.field 45B,46B, 47B, 49M, 49N validation does not provide
  correct error information.
  2.field 45B,46B, 47B, 49M, 49N validation in the MER user
  interface does not detect a missing codeword in line 1.
  3.the MTXML produced when MER creates a MT 707/MT708 can be
  incorrect and might result in putting the message on a MER
  backout queue.
  4. for MT707 only:  field 71N not created/validated according to
  MFVR.
  A CRLF between the first subfield Code and the second subfield
  Narrative is required.
  
  for 3., apart from the message be put to a MER backout queue,
  following symptom is seen in the Broker Joblog:
  10.45.31 STC41640  +BIP4367E (Msg 8/9) QESEBRK DNQ_MER 32 THE
  METHOD 'evaluate' IN JAVA NO  612
      612              DE 'DnqFinApplicationOutput - To
  MQ.DniStandardsProcessing.ComIbmDniSP
      612              N' HAS THROWN THE FOLLOWING EXCEPTION:
  <com.ibm.broker.plugin.MbUserEx
      612              ception
  class:com.ibm.dni.mst.broker.DniStandardsProcessingNode method
      612              :evaluate source:dnicymsg key:0013 message:
  Unable to resolve message:
      612               Source: dnicymsgKey: 0013 >.
  
  and following error indication is seem in the message on the MER
  backout queue:
  DNIY0013E: element
  '/mtmsg:Finmessage[1]/mtmsg:Block4[1]/mt:Document[1]/mt:MT707[1]
  /mt:F46a[1]/mt:F46B[1]' has child'
  
  for 4., the message will be NAK'ed by SWIFT with NAK code T33.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Message Standards Problems with         *
  *                      FIN MT707/MT708 in SR2018               *
  ****************************************************************
  The SWIFT standards implementation for SR2018 has the following
  issues for MT707/MT708:
  - MT707/MT708:
    field 45B,46B, 47B, 49M, 49N validation does not provide
    correct information.
    field 45B,46B, 47B, 49M, 49N validation in the MER user
    interface does not detect a missing codeword in line 1.
    the MTXML produced when MER creates a MT 707/MT708 can be
    incorrect and might result in putting the message on a MER
    backout queue.
  - MT707 field 71N not created/validated according to MFVR.
    A CRLF between the first subfield Code and the second
    subfield Narrative is required.
  

Problem conclusion

• Message standards implementation corrected.
  

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:

  PH03189

Modules/Macros

• DNI00000
  

Fix information

• Fixed component name

  FTM SWIFT SVCS

• Fixed component ID

  5655FTB30

Applicable component levels

• R300 PSY UI61070

     UP19/02/06 P F902

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.