MQ ... TRANSACTION HITS

lrawat · New User Joined: 02 Feb 2008 Posts: 19 Location: usa

hi friends,
i have a windows based application integrated with CICS-mainframe.
now, as soon as any message is received by mainframe through MQ (sent by windows application), a transaction gets hit in mainframe (say OP01).
Now if multiple messages are hitting at the mainframe end through MQ, multiple instances of transaction (OP01) start running simultaneously.

Is there a way I can limit number of transactions running simultaneously. For example to 5, so incase 10 messages are received at mainframe end, only 5 messages would initiate 5 instances of transactions OP01 and 5 messages would wait by the time 5 messages from before are processed.

Any idea, if it can be done?

Thanks a lot!!!

Terry Heinze · Posted: Wed Jul 30, 2008 2:22 am

Assigning the TRANSACTION ID to its own unique TCLASS would do it, since the TCLASS can be assigned a maximum value, but I'm sure there's a better way nowadays. My CICS knowledge is rusty.

dick scherrer · Posted: Wed Jul 30, 2008 2:53 am

Hello,

Talking with your CICS System Programmer(s) would be good. . .

stodolas · Posted: Wed Jul 30, 2008 5:36 am

Our CICS support people do this for our transactions that are triggered by MQ quite often. I don't know what they do though

sudhakar84 · New User Joined: 20 Jun 2008 Posts: 25 Location: chennai

There is one concept like MQ depth. Based on this we can control the no of records a Q can hold. Just a thought..

stodolas · Posted: Wed Jul 30, 2008 7:32 pm

You wouldn't want to limit the MQ depth just to limit the number of running transactions. That would ripple up to your windows app. You want to just limit how many running transactions you have. That way you can continue to put work onto the queue and let it wait until the transaction runs and it will get pulled off.

lrawat · New User Joined: 02 Feb 2008 Posts: 19 Location: usa

all, thanks for the help!!

stodolas · Posted: Thu Jul 31, 2008 7:30 pm

Something we do with a specific transaction is it gets triggered when any message gets put onto a queue. It the processes all messages on the queue. This transaction is limited to 1 but will always empty the queue processing each message as it goes along.