Well, one way to do it is to do a "dis q(*)" in runmqsc, then examine the
output looking for a left bracket ('['). Runmqsc reports damaged objects
with the queue name followed by a reason code in brackets.
After a disk failure on a dev Unix box last month, I piped the runmqsc
output to grep, picking off the lines with brackets. Then I cut out the
queue names and did recovery on them. It's totally crude but effective
enough for development anyway..
"Benjamin F.
Zhou" To: [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
USA.COM> Subject: ms03 on MQ5.3 on Win2k problem
Sent by: MQSeries
List
<[EMAIL PROTECTED]
N.AC.AT>
12/04/2003 08:55
AM
Please respond to
MQSeries List
Hi,
when we run saveqmgr compiled for v5.3 on one of our Win2K boxes with
MQ5.3, we got the following message:
.....
Queue definitions written to qmgr.mqs
Skipping dynamic queue QMGR.REPLY.3FAC799201780120
Skipping dynamic queue SAVEQMGR.3FAC799201790120
Got bad PCF response message
Type = 2
StrucLength = 36
Version = 1
Command = 13
MsgSeqNumber = 24
Control = 0
CompCode = 2
Reason = 2101
ParameterCount = 1
The RC 2101 means OBJECT_DAMAGED. But I can't figure out which one.
Has anyone experienced this before? Is there a way to check each individual
objects within a queue manager for damage?
thanks for any idea.
Benjamin F. Zhou
Messaging & Integration
Mercedes-Benz USA
x.2474
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
