Originally posted by: gunturi

Hi We are using a burst mode in launcher with the following mq adapter options. we intende the launcher to become active every 1 min and read only n(fetch unit) no.of msgs at a time and then pass them to a diff map. but instead the burst  is reading all the messages in the first run and passing only 2 messages to the next map.

<ExecutionLog   burstreturn="21" ElapsedSec="0.023">

<inputstatus    card="1"   bytes="2511"   adapterreturn="0"   contentreturn="0"/>
<outputstatus   card="1"   bytes="2511"   adapterreturn="0"   contentreturn="0"/>

</ExecutionLog>

</Burst>

<Burst count="2">

<ExecutionLog   burstreturn="0" ElapsedSec="0.000">

<inputstatus    card="1"   bytes="0"   adapterreturn="0"   contentreturn="0"/>
<outputstatus   card="1"   bytes="0"   adapterreturn="0"   contentreturn="0"/>

</ExecutionLog>

</Burst>

<ExecutionSummary MapStatus="Warning" mapreturn="21" ElapsedSec="0.031" BurstRestartCount="0">
   <Message>Input valid but unknown data found</Message>

please see the image for the card settings.

Originally posted by: paul.brett

I recommend that you do not use Burst mode for this.  Use the adapter commands -QTY 8 and -LSN 0 instead.  This means read 8 messages, and don't wait any additional time for 8, if there are less than 8 available on the queue.

This of course assumes that your input Typetree is setup to read multiple input messages all concatenated one after the other.

Thank you.

Paul

Follow me on Twitter

Originally posted by: gunturi

Thanks Paul for the answer, May I know why a burst mode wont be appropriate here, I will mark this answer for my future similar cases while designing the solution

Originally posted by: paul.brett

Burst mode is for getting a quantity of messages, but then mapping those in 'bursts' to avoid having to map all the data in one go, usually to save memory usage.

I'm not a day-to-day mapper, and this is the best explanation I can come up with.

More detail here.

Thank you.

Paul

Follow me on Twitter