PM89631: CORRELATION OF FIN ISNS MUST BE DISTINCT VIA THE MESSAGE GROUP ID

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When an ISN is corrected in MER, it is not possible to do a
  distinct correlation of the message, it's ACK and potential
  related SWIFT system messages.
  This needs to be solved, according to what has been agreed upon
  already:
  A SWIFT ISN, corrected in MER needs to be written to the message
  warehouse with a new message group to ensure, that the corrected
  message, it's ACK and potential related SWIFT system messages
  are handled within a seperate Message Group to allow for
  proper correlation.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: CORRELATION OF FIN ISNS MUST BE         *
  *                      DISTINCT VIA THE MESSAGE GROUP ID       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Formerly, ISN ACKs/NAKs could not be correlated to the
  originating ISN since the MessageGroup ID was missing in MQRFH2.
  

Problem conclusion

• Now, the MessageGroup is assigned to the ISN ACK/NAK messages.
  Furthermore, for routing of ISN NAK messages received with MER
  has been changed in the sample routing DNQ_K_FIN1_4 and
  DNQ_K_FIN2 accordingly,
  The original ISN NAK is sent to MER queue FIN1Ack. A copy of
  the message is routed to MER queue FIN1Edit with removed NAK
  information for further processing.
  To be able to manipulate a message during routing and preserving
  the changes without being restored from the database tables,
  API node ComIbmDnqErQueueOutput has been enhanced with node
  property 'AllowManipulation'.
  If the node property is set to 'YES', the message in the
  database table is updated with the manipulated version from MER
  routing. For all other values, the message is restored from
  the database table. This is the default.
  The value of the node property is checked case-insensitive.
  

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:

  PM89857

Modules/Macros

• DNQ00000
  

Fix information

• Fixed component name

  MESSAGE MANAGEM

• Fixed component ID

  5655FIN03

Applicable component levels

• R11M PSY UK96124

     UP13/07/26 P F307

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.