MQ

Hey All, 

We have a queue : consider(ABC.AUTH)  On the mainframe queue manager, which is a shared queue , spanning  across four queue managers.

QM1: TO.ABC.AUTH (distributed QMGR)

QM2: ABC.AUTH( Mainframe QMGR) 

We are sending messages in a batch ( consider 10k messages) from QM1 TO QM2, and they will be picked up by CICS program.

the mainframe queue is like a bridge queue and is used by different programs. (one is validating the authorization of card payments) .

Question here is, is there anyway we can set the low priority to the message that are coming through the batch, such a way it allows the other Authorization transactions to go through (without getting timed out which is now set at 10 secs).

Note:  On our testing , when we sent a batch of 10k records to that mainframe queue(ABC.AUTH) and concurrently we ran the authorization messages, at first we could see the success, but eventually all got timed out, since the messages are all set to priority and are going out on  FIFO basis.

Thanks, 

vishal 

Vishal,

You can set the priority different ways.  A default priority can be set on the remote queue used on distributed. An explicit priority can be set on the destination (JMS) or an explicit priority can be set on the message (MQMD) or JMS message properties (msg.setPriority(int i) ).

Enjoy

Hey All, 

We have a queue : consider(ABC.AUTH)  On the mainframe queue manager, which is a shared queue , spanning  across four queue managers.

QM1: TO.ABC.AUTH (distributed QMGR)

QM2: ABC.AUTH( Mainframe QMGR) 

We are sending messages in a batch ( consider 10k messages) from QM1 TO QM2, and they will be picked up by CICS program.

the mainframe queue is like a bridge queue and is used by different programs. (one is validating the authorization of card payments) .

Question here is, is there anyway we can set the low priority to the message that are coming through the batch, such a way it allows the other Authorization transactions to go through (without getting timed out which is now set at 10 secs).

Note:  On our testing , when we sent a batch of 10k records to that mainframe queue(ABC.AUTH) and concurrently we ran the authorization messages, at first we could see the success, but eventually all got timed out, since the messages are all set to priority and are going out on  FIFO basis.

Thanks, 

vishal