JR35550: INCORRECT NUMBER OF MESSAGES RETRIEVED FROM MQ QUEUE USING MULTI-CONFIG FILE VIA MQ CONNECTOR IS 8.1

Download Fix Pack 2 for InfoSphere Information Server Version 8.1

APAR status

• Closed as program error.

Error description

• Problem when retrieving XML files from an MQ queue via the MQ
  connector where in some cases the number of messages retreived
  from the queue are greater that the number of files in the
  queue.
  
  This only happens when using multi-config file and works
  correctly using single node config
  

Local fix

• Use single node config file
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users with MQ connector to read messages longer than 64KB in
  parallel.
  ****************************************************************
  PROBLEM DESCRIPTION:
  Customers see extra rows in the output from MQ Connector stage
  when they run the job in multiple nodes configuration.
  This problem occurs when the input rows contain messages longer
  than 64KB
  The extra rows typically have unreadable/garbage characters at
  the end.
  When this problem occurs, following warning is shown in the job
  log:
  
  MQGET call executed with completion code 1  (MQCC_WARNING),
  reason code 2080  (MQRC_TRUNCATED_MSG_FAILED)
  
  This doesn't occur in single node configuration.
  
  ****************************************************************
  RECOMMENDATION:
  Apply the patch.
  ****************************************************************
  

Problem conclusion

• This is caused by the program error and fixed in the patch.
  When prepared buffer size is insufficient, MQ Connector retries
  MQGET call after extending the buffer.
  This problem occurs when the message is already read and deleted
  by the connector process while other connector process is in the
  middle of the retry.
  Subsequent message happens to longer than the extended buffer,
  MQ returns MQRC_TRUNCATED_MSG_FAILED warning.
  But due to wrong handling of the truncated message, connector
  sent it to output even the message is still on the MQ queue.
  

Temporary fix

• Run the connector on single node.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• SERVER
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R810 PSN

     UP