Ignore PURG call (ignorePURGCall)

When an IMS application has multiple ISRT and PURG calls:

• If the client application uses commit mode 1 interaction, IMS sends one response message with multiple output segments.
• If the client application uses commit mode 0:
  • If the ignorePURGCall property is set to false (the default), IMS sends multiple output response messages, one for each PURG call. The client application receives the first output message, and the remaining output messages remain in the asynchronous hold queue for that client. The message can then be retrieved by using the SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT, or SYNC_RECEIVE_CALLOUT interaction.
  • If the ignorePURGCall property is set to true, the multiple PURG calls in the IMS application are ignored. The output is returned as one single message with multiple segments.

The ignorePURGCall flag is valid for the SYNC_SEND and SYNC_SEND_RECEIVE interactions for commit mode 0 interactions on shareable persistent socket connections. Multiple PURG calls are always ignored, regardless of the value of this flag for commit mode 1 interactions.

The ignorePURGCall flag is not valid for SYNC_END_CONVERSATION, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT or SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions, or for SYNC_SEND_RECEIVE interactions on dedicated persistent socket connections. An exception is thrown in these interactions.