Re: Performance of MQ

Those parameters (looks like the defaults) are fine. Make sure the Queue
Manager Name and Queue Name match up with what the other side expects. There
really aren't any performance related parameters on a queue definition -
you'll find some on the channel definition and a bit on the queue manager
definition. However, unless you're in an extremely fast-paced transaction
environment, you won't find yourself spending much time with MQ performance.

On 12/6/06, donna lester <donna_lester_ny@xxxxxxxxx> wrote:

I m creating an MQ and the parameters are as below:

Anyone who had experience on creating MQ , please comment on the values
for the parameters in below if anything looks odd or Any suggestions for
better performance values are welcome.

Queue manager name . . . . . . : BKMGRGSC

Queue name . . . . . . . . . . : GSC.ALERTS.INPUT

Queue type . . . . . . . . . . : *LCL

Text 'description' . . . . . . : GSC Alerts Input Local Queue

Put enabled . . . . . . . . . : *YES

Default message priority . . . : 0

Default message persistence . : *NO

Process name . . . . . . . . . :

Triggering enabled . . . . . . : *NO

Get enabled . . . . . . . . . : *YES

Sharing enabled . . . . . . . : *YES

Default share option . . . . . : *YES

Message delivery sequence . . : *PTY

Harden backout count . . . . . : *YES

Trigger type . . . . . . . . . : *FIRST

Trigger depth . . . . . . . . : 1

Trigger message priority . . . : 0

Trigger data . . . . . . . . . :

Retention Interval . . . . . . : 999999999

Maximum queue depth . . . . . : 50000

Maximum message length . . . . : 4194304

Backout threshold . . . . . . : 0

Backout requeue queue . . . .:


Thanks,

Donna.

---------------------------------
Everyone is raving about the all-new Yahoo! Mail beta.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.