WebSphere MQ: SYSLOG Pro-active analysis methodology

flashyfarctateInternet και Εφαρμογές Web

30 Ιουλ 2012 (πριν από 5 χρόνια και 22 μέρες)

306 εμφανίσεις

WebSphere MQ: SYSLOG Pro
-
active
analysis

methodology.

© Copyright IBM Corporation, 2008


Purpose:

To help individuals who are responsible for WebSphere MQ z/OS on going support. It should be
helpful even to experienced MQ support teams. This is a methodology for assisting with the
analysis of the SYSLOG, looking for existing problems or anomal
ies that could be advanced
warnings of potential problems.


It should be used in conjunctions with the WebSphere z/OS messages manual for your release of
WebSphere MQ. It is designed for ISPF as that is common on z/OS systems. The method uses
ISPF edit an
d the edit commands.


As usual there is a disclaimer. The tables in the figures with the edit commands provided are in
no way complete, as we go forward with more queue manager SYSLOGs additional commands
can be added.. Always review the comments associate
d with the messages in the

WebSphere MQ for z/OS Messages and Codes
Version 6.0


Available at the following URL:

http://www
-
306.ibm.com/software/integration/wmq/library/library6x.html




Details:


1.

Extract the WebSphere MQ SYSLOG to an ISPF editable dat
aset or member of a editable
PDS

2.

ISPF edit the extracted
qmgrCHIN
SYSLOG.

3.

Using the
CHIN LOG line CM
DS

worksheet of
SYSLOG
-
SPSF
-
Line
-
CMDS.

You can keep
track of the message count and investigate those that seem high and those that are of
severity 8.

4.

The

critical information messages
X
ed out during step 3
can be redisplayed by changing the
x

in the edit command to an
f

and executed. You may have to show the lines following it as
they may be associated and have additional information. To show additional l
ine type
F 3
on
the dotted line below the informational line. This will display the next 3 lines. Investigate the
occurrences and the impact these messages had on your queue manager and whether they
were resolved appropriately. I like to remove each set of

messages using
X all

before doing
the next message group.

5.

ISPF edit the extracted qmgrMSTR SYSLOG.

6.

Using the MSTR LOG line CM
DS

worksheet of
SYSLOG
-
SPSF
-
Line
-
CMDS.

You can keep
track of the message count and investigate those that seem high and those th
at are of
severity 8.

7.

The critical information messages
X
ed out during step 7 can be redisplayed by changing the
x

in the edit command to an
f

and executed. You may have to show the lines following it as
they may be associated and have additional informati
on. To show additional line type
F 3
on
the dotted line below the informational line. This will display the next 3 lines. Investigate the
occurrences and the impact these messages had on your queue manager and whether they
were resolved appropriately. I l
ike to remove each set of messages using
X all

before doing
the next message group.