PROTECTED]
Subject: Re: Formatting production logs
Comment on 2) from development
"The MA0C broker shuts down streams by pulsing the stream queue's get
inhibited attribute. The attribute is set to MQQA_GET_INHIBITED and back to
MQQA_GET_ENABLED in 'quick' succession so I'
0:44 PM
To: [EMAIL PROTECTED]
Subject: Re: Formatting production logs
Comment on 2) from development
"The MA0C broker shuts down streams by pulsing the stream queue's get
inhibited attribute. The attribute is set to MQQA_GET_INHIBITED and back to
MQQA_GET_ENABLED in 'quick' suc
Comment on 2) from development
"The MA0C broker shuts down streams by pulsing the stream queue's get
inhibited attribute. The attribute is set to MQQA_GET_INHIBITED and back to
MQQA_GET_ENABLED in 'quick' succession so I'd expect it to be fairly rare
for a process that was polling queue's to see t
Title: Formatting production logs
Rao,
the
only commercial product that comes close to what you want in 1) is Cressida's
re-Quest.
(no I
have no connection to them, just answering a question :-)
)
There
is a way to format these logs yourself, but it takes a lot of guessing as the
form
z/OS
only though for Configuration Events.
I hope
the next version of MQ gives us this for Distributed.
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Sent: Friday, March 26, 2004
9:36 AMTo: [EMAIL PROTECTED]Subject: Re: Formatting
production logs [Deutsche
Stefan Raabe/DBS/GDB)
Subject: Re: Formatting production logs [Deutsche Boerse Systems:Virus checked]
.
in this case, what SYSTEM.ADMIN.QMGR.EVENT will record
is the incident of an MQGET call from a queue that is
GET-Inhibited. It will not record who inhibited it.
So, I don't
: Friday, March 26, 2004 9:11 AM
To: 'MQSeries List'
Subject: RE: Formatting production logs
It will give him the Application Name and Application Type, as well as
exactly when it happened, which may be enough. But yes, as Ruzi pointed out,
there will not be an actual User ID.
Event dat
next day with evidence in hand!
>
>
>
>
> -Original Message-
> From: Adiraju, Rao [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 25, 2004 5:49 PM
> To: [EMAIL PROTECTED]
> Subject: Formatting production logs
>
>
>
> Fellows
>
> I have two areas
Title: Formatting production logs
Thanks - will do.
Cheers
Rao
From: Potkay, Peter M (PLC, IT)
[mailto:[EMAIL PROTECTED] Sent: 26 March 2004 11:48
AMTo: [EMAIL PROTECTED]Subject: Re: Formatting
production logs
Turn
on Inhibit Events at the Queue Manager level.
Turn
off temporarily the
Title: Formatting production logs
Turn
on Inhibit Events at the Queue Manager level.
Turn
off temporarily the other Queue Manager Events.
Make
the SYSTEM.ADMIN.QMGR.EVENT default persistence equal to
Persistent.
Now
monitor your SYSTEM.ADMIN.QMGR.EVENT queue for a depth of
greater than 0
Title: Formatting production logs
Fellows
I have two areas, where I appreciate some help:
1) Formatting the logs -
In one of our production queue managers, something fishy is going on and I need to format the log to see who is exactly doing the changes. I know roughly what time
11 matches
Mail list logo
