DSXchange

Interesting. Learn something new every day.

Thanks for help,

I can make the job run endlessly till a message arrives.

But I wanted job to run 24/ 7 and when the message arrive in the queue read the message and write to staging file and again continue running state for the next message. It goes on in loop 24 /7.

What are configuration need for MQ Stage to achieve this?

Rgds,
Chakradhar.

Do you want the Job to terminate after each message? ie...receive a row, write to a flat file, terminate, and then re-start again? If you were receiving very few messages, you could do this simply by having a limit of one row before termination in the stage. After one row is received and then written somewhere, the job will terminate...... use an after job subroutine or other technique to just launch it again. But why terminate the job? Is it just so that you can get access to the flat file? Perhaps you can consider using an rdbms table instead, and make your commit equal to 1 --- then you'll have complete access to the transformed data immediately after it is written.

Ernie

No , I don't want to terminate the job. I want to read message from queue and write message to DB Table. job should continue to be in running state.

Rgds,
Chakradhar.

Then an always-running job that does exactly that would seem to me to be exactly what you require.

To conclude

Setting at MQ Series Stage
Wait Time : -1
Message Limit : 99999989
End of Data Message : 0

This settings will read the messages for ever and job will be in running state and waiting for the message to arrive.

Use a Database Stage, so that message will be written in the DB as soon as it is delivered and have commit rate as 1.

this is best settings for the quick turnaround.

Thanks for the all the input and it is resolved.

rgds,
Chakradhar.