JR51773: IN MQ CONNECTOR, A WAIT TIME OF 0 SECONDS IS NOT BEING HONORED CORRECTLY WHILE READING MESSAGES FROM THE QUEUE.

APAR status

• Closed as program error.

Error description

• While using MQ Connector in the read context with a wait time
  set to 0 seconds and messages are trickling into the queue at
  regular intervals (few messages every second), the connector
  job is continuing to read the messages till the inflow of the
  messages stops. When the wait time is set to 0 seconds in the
  read context, the expectation is, the job should stop reading
  the messages as soon as it processes the existing messages and
  any other messages that are written to the queue while
  processing the existing messages. However, the job continues to
  process all the messages as long as there is continuous flow of
  messages into the queue.
  

Local fix

Problem summary

• While using MQ Connector in the read context with a wait time
  set to 0 seconds and messages are trickling into the queue at
  regular intervals (few messages every second), the connector job
  is continuing to read the messages till the inflow of the
  messages stops. When the wait time is set to 0 seconds in the
  read context, the expectation is, the job should stop reading
  the messages as soon as it processes the existing messages and
  any other messages that are written to the queue while
  processing the existing messages. However, the job continues to
  process all the messages as long as there is continuous flow of
  messages into the queue.
  

Problem conclusion

• It was found that the connector is setting  a wait interval of 1
  second in the MQ Structure which would make the MQGET call to
  block for a second when there are no messages in the queue.
  
  Since this would break the case where the wait interval is set
  to 0 seconds in the connector, the code has been modified to set
  the wait interval in the MQ structure to 0 seconds when the
  wait time is set to 0 seconds in the WaitTime option in the
  Connector.
  

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

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R870 PSY

     UP

• R910 PSY

     UP

• R912 PSY

     UP