Author |
Message |
Topic: How to read the FDC logs |
sudhaRam
Replies: 3 Views: 3514
|
Forum: General IBM MQ Support Posted: Fri Dec 21, 2007 5:34 am Subject: How to read the FDC logs |
All,
We have MQ Series Ver 5.3 CSD 12 installed in our Windows Server. Since it is off support from IBM we are not gtting any support from IBM whenever an error occurs and we need to read the FDC f ... |
Topic: Channel not getting started |
sudhaRam
Replies: 4 Views: 4840
|
Forum: General IBM MQ Support Posted: Wed Dec 12, 2007 8:21 am Subject: Channel not getting started |
The FDC was generated and the Probe ID is AQ143000.
We are working on Upgrading the MQ version as well. Thanks for the same |
Topic: Channel not getting started |
sudhaRam
Replies: 4 Views: 4840
|
Forum: General IBM MQ Support Posted: Wed Dec 12, 2007 6:22 am Subject: Channel not getting started |
All,
We were doing a fail over task in UNIX and the package was failed over from one UNIX server to the other. We have MQ V5.3 and CSD 04 in UNIX side. The UNIX talks with the mainframe and in main ... |
Topic: Queue Manager Ended abnormally |
sudhaRam
Replies: 18 Views: 20726
|
Forum: General IBM MQ Support Posted: Fri Nov 30, 2007 9:38 am Subject: Queue Manager Ended abnormally |
Different issues have different resolution.In this case we tried all the option of starting the listener, resetting the channel sequence number. The problem here was the ping channel was a normal comp ... |
Topic: Queue Manager Ended abnormally |
sudhaRam
Replies: 18 Views: 20726
|
Forum: General IBM MQ Support Posted: Fri Nov 30, 2007 9:01 am Subject: Queue Manager Ended abnormally |
The things that i did in UNIX end,
Log in as someone in the 'mqm' group.
Record the logging parameters of the failing queue manager by checking '/var/mqm/qmgrs/OLDQMGR/qm.ini'. These parameters inc ... |
Topic: Queue Manager Ended abnormally |
sudhaRam
Replies: 18 Views: 20726
|
Forum: General IBM MQ Support Posted: Fri Nov 30, 2007 6:49 am Subject: Queue Manager Ended abnormally |
yes we also checked the Listener. Its up and running. Also the receivers are not stopped in the UNIX end. anyways we r finding out |
Topic: Queue Manager Ended abnormally |
sudhaRam
Replies: 18 Views: 20726
|
Forum: General IBM MQ Support Posted: Fri Nov 30, 2007 6:41 am Subject: Queue Manager Ended abnormally |
Thanks for ur help. The Queue Manager is running now. But now we r facing another issue here. This UNIX Queue manager communicates with mainframe. While the UNIX queue manager was ended lots of messag ... |
Topic: Queue Manager Ended abnormally |
sudhaRam
Replies: 18 Views: 20726
|
Forum: General IBM MQ Support Posted: Fri Nov 30, 2007 5:27 am Subject: Queue Manager Ended abnormally |
He has stopped psoting.
Thanks i will look into the link. Also we are wiaitng for the approval from the management to upgrade the version and CSD |
Topic: Queue Manager Ended abnormally |
sudhaRam
Replies: 18 Views: 20726
|
Forum: General IBM MQ Support Posted: Fri Nov 30, 2007 5:05 am Subject: Queue Manager Ended abnormally |
The Probe ID is ZX000001
Probe Type: MSGAMQ6118
Probe Descritption: AMQ6118: An internal Websphere MQ error has occured.(7017)
Probe Severity:2 |
Topic: Queue Manager Ended abnormally |
sudhaRam
Replies: 18 Views: 20726
|
Forum: General IBM MQ Support Posted: Fri Nov 30, 2007 4:56 am Subject: Queue Manager Ended abnormally |
Yes i work with him
Probe ID please explain im not aware.
The CSD level is CSD04 |
Topic: Queue Manager Ended abnormally |
sudhaRam
Replies: 18 Views: 20726
|
Forum: General IBM MQ Support Posted: Fri Nov 30, 2007 4:33 am Subject: Queue Manager Ended abnormally |
Error Message:
When i see the error log /var/mqm/errors it says
An error has been detected and the Websphere MQ error recording routine has been called. The failing process is 17668.
The proces ... |
Topic: Queue Manager Ended abnormally |
sudhaRam
Replies: 18 Views: 20726
|
Forum: General IBM MQ Support Posted: Fri Nov 30, 2007 4:19 am Subject: Queue Manager Ended abnormally |
Hi,
Im using MQ V5.3 in HP-UX machine. Suddenly the Queue Manager ended unexpextedly. When trying to start it its not getting started. When checking the MQ error log it says serious error has occur ... |