Currently, most messages received on our mainframe qmgr are destined to
CICS and are triggered 'on first' . We are in the process of putting in
a new application that will receive large volumes (50,000+) of batch
messages from a vendor. The messages will come in at different times of
the day,
To:[EMAIL PROTECTED]
cc:(bcc: Richard Jackson/DTCC)
Subject:BATCH messages advice requested
Currently, most messages received on our mainframe qmgr are destined to
CICS and are triggered 'on first' . We are in the process of putting in
a new application that will receive large volumes
.
Ò¿Ó
Bob Juch
Citigroup
MQ Mainframe Support Team
Weehawken, NJ
201-974-2147
mailto:[EMAIL PROTECTED]
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Dye,
Janet E
Sent: Thursday, November 18, 2004 12:28 PM
To: [EMAIL PROTECTED]
Subject: BATCH messages advice
]
Subject: BATCH messages advice requested
Currently, most messages received on our mainframe qmgr are destined to
CICS and are triggered 'on first' . We are in the process of putting in
a new application that will receive large volumes (50,000+) of batch
messages from a vendor. The messages will come
small but it has driven many good programmers to distraction.
Alan
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Dye,
Janet E
Sent: Thursday, November 18, 2004 11:28 AM
To: [EMAIL PROTECTED]
Subject: BATCH messages advice requested
Currently, most messages
List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: BATCH messages advice requested
Date: Thu, 18 Nov 2004 11:28:03 -0600
Currently, most messages received on our mainframe qmgr are destined to
CICS and are triggered 'on first' . We are in the process of putting in
a new application
PROTECTED]
cc:
Subject:
Re: BATCH messages advice requested
Not to get into the nuts and bolts of
triggering on depth that has been
suggested by several already, it is not immediately obvious that your
programmers MUST reset the trigger on depth before terminating each time
Build a 2nd qmgr, tune it for the batch processing,
route the messages to it from the 1st.
The isolation will make it easier to tune both
logging and psid storage requirements. You've got
plenty of bufferpools, psids if you're at v5.3.
Maybe even route the batch directly to a dedicated
Title: Message
For
queue depth I was planning on having a batch job in their job stream run that
issues the 'ALTER' command to set the trigger back on. This would be a
step that ran only if the job to read the queue was successful. If
they have an abend, they can fix there problem and run
They
want to schedule it to run every hourso I assume some hours it will run and
find nothing (that was a waste), and other hours you will be watching the queue
depth climb and climb, gritting your teeth, beads of sweat forming on your
forward, w-i-s-h-i-n-g the clock on the wall to hurry
:35 PM
Please respond to MQSeries List [EMAIL PROTECTED]
Sent by:MQSeries List [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:Re: BATCH messages advice requested
For queue depth I was planning on having a batch job in their job stream
run that issues the 'ALTER' command
11 matches
Mail list logo
