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,
Has anyone come across a sample program to read/create report on SYSTEM.ADMIN.*.EVENT
msgs. With
Websphere MQ 5.3 for Z/OS, there is a new event queue called
SYSTEM.ADMIN.CONFIG.EVENT where
events are written whenever you make any change to a MQ object. I would like to
create a report
from
...),
;-) Stefan
From: Dye, Janet E [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: MQGET with wait in CICS
Date: Mon, 24 Jun 2002 16:24:00 -0500
We have noticed that when a CICS program does a MQGET with wait, that
during
the time interval that the task
We have noticed that when a CICS program does a MQGET with wait, that during
the time interval that the task is waiting, that it is using a lot of CPU
resources. When I do a MQGET with wait
in a batch environment, it does not appear to be using any resources during
the wait. Has anyone
else
