| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Sender Channel Status "Retrying" and Receiver Inac |
« View previous topic :: View next topic » |
| Author |
Message
|
| ckrisasa |
 Posted: Sat Sep 26, 2015 7:30 am Post subject: Sender Channel Status "Retrying" and Receiver Inac |
 |
|
Newbie
Joined: 26 Sep 2015
Posts: 9
|
Hi,
I'm new to WebSphere MQ, I've gone through some redbooks and understood its usage. I figured out installation, upgrading ... and now trying to work on some examples my own.
My infrastructure:
I have two QManagers Mercury and Venus on my localhost. I tried to define local queues, remote queues, sender channels, receiver channels and listeners on both queue managers.
Mercury QM:
Local Queue: MERCURY.LOCAL
Remote Queue: MERCURY.REMOTE , Rname:VENUS.LOCAL
TRASMIT QUEUE: MERCURY.XMIT
SDR CHL: MERCURY.VENUS, PORT: 1515
RCVR CHL: VENUS.MERCURY
LISTENER: MERCURY.VENUS.LSTR
VENUS QM:
Local Queue: VENUS.LOCAL
Remote Queue: VENUS.REMOTE , Rname:MERCURY.LOCAL
TRASMIT QUEUE: VENUS.XMIT
SDR CHL: VENUS.MERCURY, PORT: 1616
RCVR CHL: MERCURY.VENUS
LISTENER: VENUS.MERCURY.LSTR
But I've channel issues as shown in the attachment. Someone please help me.
MERCURY:
| Quote: |
CRTMQM MERCURY
STRMQM
RUNMQSC
DEFINE QLOCAL(MERCURY.XMIT) USAGE(XMITQ)
DEFINE QREMOTE(MERCURY.REMOTE) RNAME(VENUS.LOCAL) RQMNAME(VENUS) XMITQ(MERCURY.XMIT)
DEFINE QLOCAL(MERCURY.LOCAL)
DEFINE CHANNEL(MERCURY.VENUS) CHLTYPE(SDR) CONNAME('LOCALHOST(1515)') XMITQ(MERCURY.XMIT) TRPTYPE(TCP)
DEFINE CHANNEL(VENUS.MERCURY) CHLTYPE(RCVR) TRPTYPE(TCP)
DEFINE LISTENER(MERCURY.VENUS.LSTR) TRPTYPE(TCP) PORT(1515)
START CHANNEL(MERCURY.VENUS)
START LISTENER(MERCURY.VENUS.LSTR)
END
|
VENUS:
| Quote: |
CRTMQM VENUS
STRMQM VENUS
RUNMQSC VENUS
DEFINE QLOCAL(VENUS.XMIT) USAGE(XMITQ)
ALTER QREMOTE(VENUS.REMOTE) RNAME(MERCURY.LOCAL) RQMNAME(MERCURY) XMITQ(VENUS.XMIT)
DEFINE QLOCAL(VENUS.LOCAL)
DEFINE CHANNEL(MERCURY.VENUS) CHLTYPE(RCVR) TRPTYPE(TCP)
ALTER CHANNEL(VENUS.MERCURY) CHLTYPE(SDR) CONNAME('LOCALHOST(1616)') XMITQ(VENUS.XMIT) TRPTYPE(TCP)
DEFINE LISTENER(VENUS.MERCURY.LSTR) TRPTYPE(TCP) PORT(1616)
START CHANNEL(VENUS.MERCURY)
START LISTENER(VENUS.MERCURY.LSTR)
END
|
What might be the issue in this case? I even tried to start channels manually. But throwing errors.
Please find screenshot in the reply. |
|
| Back to top |
|
 |
| ckrisasa |
| Posted: Sat Sep 26, 2015 7:31 am Post subject: |
|
|
Newbie
Joined: 26 Sep 2015
Posts: 9
|
|
| Back to top |
|
|
| exerk |
| Posted: Sat Sep 26, 2015 9:16 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
1. Which version of MQ?
2. What's printed in the queue manager error log, at each end?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Sep 26, 2015 1:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Review your conventions.
A listener is not specific to a connection but it is specific to a qmgr.
So you should not have a VENUS.MERCURY listener but you should have a VENUS.LISTENER on the venus qmgr and a MERCURY.LISTENER on the mercury queue manager.
You might want to look further into default routing and xmitq naming conventions.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ckrisasa |
| Posted: Sat Sep 26, 2015 6:21 pm Post subject: |
|
|
Newbie
Joined: 26 Sep 2015
Posts: 9
|
Thanks for the replies.
I'm using MQ v7.5.x and thanks for clarifying me that listener is QMGR specific but not channel specific.
But here in this case, I believe I defined unique sender and reciever channels on both the QMGRs.
The error logs:
MERCURY:
| Quote: |
9/27/2015 07:34:55 - Process(3400.3) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ6287: WebSphere MQ V7.5.0.2 (p750-002-130627).
EXPLANATION:
WebSphere MQ system information:
Host Info :- Windows 7 Professional x64 Edition, Build 7601: SP1 (MQ
Windows 32-bit)
Installation :- C:\Program Files (x86)\IBM\WebSphereMQ (WMQ1)
Version :- 7.5.0.2 (p750-002-130627)
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:55 - Process(3400.3) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'LOGGER-IO' has started.
EXPLANATION:
The critical utility task manager has started the LOGGER-IO task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:55 - Process(3400.1) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5041: The queue manager task 'LOGGER-IO' has ended.
EXPLANATION:
The queue manager task LOGGER-IO has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(7228.3) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'LOGGER-IO' has started.
EXPLANATION:
The critical utility task manager has started the LOGGER-IO task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(4672.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ7229: 4 log records accessed on queue manager 'MERCURY' during the log
replay phase.
EXPLANATION:
4 log records have been accessed so far on queue manager MERCURY during the log
replay phase in order to bring the queue manager back to a previously known
state.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(4672.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ7230: Log replay for queue manager 'MERCURY' complete.
EXPLANATION:
The log replay phase of the queue manager restart process has been completed
for queue manager MERCURY.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(4672.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ7231: 0 log records accessed on queue manager 'MERCURY' during the recovery
phase.
EXPLANATION:
0 log records have been accessed so far on queue manager MERCURY during the
recovery phase of the transactions manager state.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(4672.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ7232: Transaction manager state recovered for queue manager 'MERCURY'.
EXPLANATION:
The state of transactions at the time the queue manager ended has been
recovered for queue manager MERCURY.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(4672.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ7233: 0 out of 0 in-flight transactions resolved for queue manager
'MERCURY'.
EXPLANATION:
0 transactions out of 0 in-flight at the time queue manager MERCURY ended have
been resolved.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(7228.4) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'CHECKPOINT' has started.
EXPLANATION:
The critical utility task manager has started the CHECKPOINT task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(8568.5) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(8568.4) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 3 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(8568.6) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 2 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(8568.3) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'ERROR-LOG' has started.
EXPLANATION:
The restartable utility task manager has started the ERROR-LOG task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:34:56 - Process(8568.7) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 4 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:03 - Process(4672.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ8048: Default objects statistics : 77 created. 0 replaced. 0 failed.
EXPLANATION:
Information on the number of objects created or replaced successfully as well
as any failures that occurred while creating the default objects.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:03 - Process(4672.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ8003: WebSphere MQ queue manager 'MERCURY' started using V7.5.0.2.
EXPLANATION:
WebSphere MQ queue manager 'MERCURY' started using V7.5.0.2.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:04 - Process(8568.1) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5041: The queue manager task 'ERROR-LOG' has ended.
EXPLANATION:
The queue manager task ERROR-LOG has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:04 - Process(8568.1) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5041: The queue manager task 'APP-SIGNAL' has ended.
EXPLANATION:
The queue manager task APP-SIGNAL has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:04 - Process(7228.1) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5041: The queue manager task 'CHECKPOINT' has ended.
EXPLANATION:
The queue manager task CHECKPOINT has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:04 - Process(7228.1) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5041: The queue manager task 'LOGGER-IO' has ended.
EXPLANATION:
The queue manager task LOGGER-IO has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:04 - Process(4672.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ8004: WebSphere MQ queue manager 'MERCURY' ended.
EXPLANATION:
WebSphere MQ queue manager 'MERCURY' ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:05 - Process(4344.3) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'LOGGER-IO' has started.
EXPLANATION:
The critical utility task manager has started the LOGGER-IO task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:05 - Process(2708.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ7229: 5 log records accessed on queue manager 'MERCURY' during the log
replay phase.
EXPLANATION:
5 log records have been accessed so far on queue manager MERCURY during the log
replay phase in order to bring the queue manager back to a previously known
state.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:05 - Process(2708.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ7230: Log replay for queue manager 'MERCURY' complete.
EXPLANATION:
The log replay phase of the queue manager restart process has been completed
for queue manager MERCURY.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:05 - Process(2708.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ7231: 0 log records accessed on queue manager 'MERCURY' during the recovery
phase.
EXPLANATION:
0 log records have been accessed so far on queue manager MERCURY during the
recovery phase of the transactions manager state.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:05 - Process(2708.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ7232: Transaction manager state recovered for queue manager 'MERCURY'.
EXPLANATION:
The state of transactions at the time the queue manager ended has been
recovered for queue manager MERCURY.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:05 - Process(2708.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ7233: 0 out of 0 in-flight transactions resolved for queue manager
'MERCURY'.
EXPLANATION:
0 transactions out of 0 in-flight at the time queue manager MERCURY ended have
been resolved.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:05 - Process(4344.4) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'CHECKPOINT' has started.
EXPLANATION:
The critical utility task manager has started the CHECKPOINT task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(2708.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ8003: WebSphere MQ queue manager 'MERCURY' started using V7.5.0.2.
EXPLANATION:
WebSphere MQ queue manager 'MERCURY' started using V7.5.0.2.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(4344.15) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'ASYNCQ' has started.
EXPLANATION:
The critical utility task manager has started the ASYNCQ task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(4344.16) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'EXPIRER' has started.
EXPLANATION:
The critical utility task manager has started the EXPIRER task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(4344.17) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'DUR-SUBS-MGR' has started.
EXPLANATION:
The critical utility task manager has started the DUR-SUBS-MGR task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(7976.4) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(7976.6) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 2 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(7976. User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'STATISTICS' has started.
EXPLANATION:
The restartable utility task manager has started the STATISTICS task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(7976.3) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'ERROR-LOG' has started.
EXPLANATION:
The restartable utility task manager has started the ERROR-LOG task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(7976.5) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 3 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(7976.7) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 4 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:06 - Process(884.1) User(MUSR_MQADMIN) Program(amqrrmfa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9410: Repository manager started.
EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(4344.1 User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'TOPIC-TREE' has started.
EXPLANATION:
The critical utility task manager has started the TOPIC-TREE task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(6712.3) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5052: The queue manager task 'QPUBSUB-CTRLR' has started.
EXPLANATION:
The publish/subscribe utility task manager has started the QPUBSUB-CTRLR task.
This task has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(4344.19) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'Q-DELETION' has started.
EXPLANATION:
The critical utility task manager has started the Q-DELETION task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(6712.5) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5052: The queue manager task 'QPUBSUB-SUBPT-NLCACHE' has started.
EXPLANATION:
The publish/subscribe utility task manager has started the
QPUBSUB-SUBPT-NLCACHE task. This task has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(7976.9) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5037: The queue manager task 'MARKINTSCAN' has started.
EXPLANATION:
The restartable utility task manager has started the MARKINTSCAN task. This
task has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(4344.20) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'PRESERVED-Q' has started.
EXPLANATION:
The critical utility task manager has started the PRESERVED-Q task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(4344.21) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5051: The queue manager task 'MULTICAST' has started.
EXPLANATION:
The critical utility task manager has started the MULTICAST task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(6712.4) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5052: The queue manager task 'QPUBSUB-QUEUE-NLCACHE' has started.
EXPLANATION:
The publish/subscribe utility task manager has started the
QPUBSUB-QUEUE-NLCACHE task. This task has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(6712.6) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5052: The queue manager task 'PUBSUB-DAEMON' has started.
EXPLANATION:
The publish/subscribe utility task manager has started the PUBSUB-DAEMON task.
This task has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(6712.6) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5975: 'WebSphere MQ Distributed Pub/Sub Controller' has started.
EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Controller' has started.
ACTION:
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(6712.7) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5975: 'WebSphere MQ Distributed Pub/Sub Fan Out Task' has started.
EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Fan Out Task' has started.
ACTION:
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(6712.9) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5975: 'WebSphere MQ Distributed Pub/Sub Publish Task' has started.
EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Publish Task' has started.
ACTION:
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(6712. User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5975: 'WebSphere MQ Distributed Pub/Sub Command Task' has started.
EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Command Task' has started.
ACTION:
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(9152.1) User(MUSR_MQADMIN) Program(amqzmgr0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5022: The channel initiator has started. ProcessId(1096).
EXPLANATION:
The channel initiator process has started.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:07 - Process(9152.1) User(MUSR_MQADMIN) Program(amqzmgr0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5024: The command server has started. ProcessId(3880).
EXPLANATION:
The command server process has started.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:08 - Process(7340.1) User(MUSR_MQADMIN) Program(amqfqpub.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5806: WebSphere MQ Publish/Subscribe broker started for queue manager
MERCURY.
EXPLANATION:
WebSphere MQ Publish/Subscribe broker started for queue manager MERCURY.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:41:27 - Process(9152.1) User(MUSR_MQADMIN) Program(amqzmgr0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ5026: The listener 'MERCURY.VENUS.LSTR' has started. ProcessId(11072).
EXPLANATION:
The listener process has started.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:41:27 - Process(10520.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9002: Channel 'MERCURY.VENUS' is starting.
EXPLANATION:
Channel 'MERCURY.VENUS' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:41:28 - Process(10992.3) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'MERCURY.VENUS'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:41:28 - Process(10992.3) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9999: Channel 'MERCURY.VENUS' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 10992(2704) for channel
'MERCURY.VENUS' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:41:28 - Process(10520.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'MERCURY.VENUS' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:41:28 - Process(10520.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9999: Channel 'MERCURY.VENUS' to host 'LOCALHOST(1515)' ended abnormally.
EXPLANATION:
The channel program running under process ID 10520(8064) for channel
'MERCURY.VENUS' ended abnormally. The host name is 'LOCALHOST(1515)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:42:27 - Process(8640.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9002: Channel 'MERCURY.VENUS' is starting.
EXPLANATION:
Channel 'MERCURY.VENUS' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:42:28 - Process(10992.4) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'MERCURY.VENUS'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:42:28 - Process(10992.4) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9999: Channel 'MERCURY.VENUS' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 10992(10688) for channel
'MERCURY.VENUS' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:42:28 - Process(8640.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'MERCURY.VENUS' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:42:28 - Process(8640.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9999: Channel 'MERCURY.VENUS' to host 'LOCALHOST(1515)' ended abnormally.
EXPLANATION:
The channel program running under process ID 8640(8148) for channel
'MERCURY.VENUS' ended abnormally. The host name is 'LOCALHOST(1515)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:43:30 - Process(7000.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9002: Channel 'MERCURY.VENUS' is starting.
EXPLANATION:
Channel 'MERCURY.VENUS' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:43:31 - Process(10992.5) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'MERCURY.VENUS'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:43:31 - Process(10992.5) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9999: Channel 'MERCURY.VENUS' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 10992(9708) for channel
'MERCURY.VENUS' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:43:31 - Process(7000.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'MERCURY.VENUS' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:43:31 - Process(7000.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9999: Channel 'MERCURY.VENUS' to host 'LOCALHOST(1515)' ended abnormally.
EXPLANATION:
The channel program running under process ID 7000(6532) for channel
'MERCURY.VENUS' ended abnormally. The host name is 'LOCALHOST(1515)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:44:30 - Process(6804.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9002: Channel 'MERCURY.VENUS' is starting.
EXPLANATION:
Channel 'MERCURY.VENUS' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:44:30 - Process(10992.6) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'MERCURY.VENUS'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:44:30 - Process(10992.6) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9999: Channel 'MERCURY.VENUS' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 10992(7200) for channel
'MERCURY.VENUS' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:44:30 - Process(6804.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'MERCURY.VENUS' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:44:30 - Process(6804.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(MERCURY)
AMQ9999: Channel 'MERCURY.VENUS' to host 'LOCALHOST(1515)' ended abnormally.
EXPLANATION:
The channel program running under process ID 6804(10472) for channel
'MERCURY.VENUS' ended abnormally. The host name is 'LOCALHOST(1515)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
|
|
|
| Back to top |
|
|
| ckrisasa |
| Posted: Sat Sep 26, 2015 6:28 pm Post subject: |
|
|
Newbie
Joined: 26 Sep 2015
Posts: 9
|
Error Logs:
Venus
| Quote: |
9/27/2015 07:35:50 - Process(6040.3) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ6287: WebSphere MQ V7.5.0.2 (p750-002-130627).
EXPLANATION:
WebSphere MQ system information:
Host Info :- Windows 7 Professional x64 Edition, Build 7601: SP1 (MQ
Windows 32-bit)
Installation :- C:\Program Files (x86)\IBM\WebSphereMQ (WMQ1)
Version :- 7.5.0.2 (p750-002-130627)
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:50 - Process(6040.3) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'LOGGER-IO' has started.
EXPLANATION:
The critical utility task manager has started the LOGGER-IO task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:50 - Process(6040.1) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5041: The queue manager task 'LOGGER-IO' has ended.
EXPLANATION:
The queue manager task LOGGER-IO has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:50 - Process(6920.3) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'LOGGER-IO' has started.
EXPLANATION:
The critical utility task manager has started the LOGGER-IO task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:50 - Process(4504.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ7229: 4 log records accessed on queue manager 'VENUS' during the log replay
phase.
EXPLANATION:
4 log records have been accessed so far on queue manager VENUS during the log
replay phase in order to bring the queue manager back to a previously known
state.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:50 - Process(4504.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ7230: Log replay for queue manager 'VENUS' complete.
EXPLANATION:
The log replay phase of the queue manager restart process has been completed
for queue manager VENUS.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:50 - Process(4504.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ7231: 0 log records accessed on queue manager 'VENUS' during the recovery
phase.
EXPLANATION:
0 log records have been accessed so far on queue manager VENUS during the
recovery phase of the transactions manager state.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:50 - Process(4504.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ7232: Transaction manager state recovered for queue manager 'VENUS'.
EXPLANATION:
The state of transactions at the time the queue manager ended has been
recovered for queue manager VENUS.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:50 - Process(4504.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ7233: 0 out of 0 in-flight transactions resolved for queue manager 'VENUS'.
EXPLANATION:
0 transactions out of 0 in-flight at the time queue manager VENUS ended have
been resolved.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:50 - Process(6920.4) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'CHECKPOINT' has started.
EXPLANATION:
The critical utility task manager has started the CHECKPOINT task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:51 - Process(11088.4) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:51 - Process(11088.3) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'ERROR-LOG' has started.
EXPLANATION:
The restartable utility task manager has started the ERROR-LOG task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:51 - Process(11088.6) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 2 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:51 - Process(11088.5) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 3 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:51 - Process(11088.7) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 4 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:58 - Process(4504.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ8048: Default objects statistics : 77 created. 0 replaced. 0 failed.
EXPLANATION:
Information on the number of objects created or replaced successfully as well
as any failures that occurred while creating the default objects.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:58 - Process(4504.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ8003: WebSphere MQ queue manager 'VENUS' started using V7.5.0.2.
EXPLANATION:
WebSphere MQ queue manager 'VENUS' started using V7.5.0.2.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:58 - Process(11088.1) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5041: The queue manager task 'ERROR-LOG' has ended.
EXPLANATION:
The queue manager task ERROR-LOG has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:58 - Process(11088.1) User(krishna) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5041: The queue manager task 'APP-SIGNAL' has ended.
EXPLANATION:
The queue manager task APP-SIGNAL has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:58 - Process(6920.1) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5041: The queue manager task 'CHECKPOINT' has ended.
EXPLANATION:
The queue manager task CHECKPOINT has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:58 - Process(6920.1) User(krishna) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5041: The queue manager task 'LOGGER-IO' has ended.
EXPLANATION:
The queue manager task LOGGER-IO has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:35:58 - Process(4504.1) User(krishna) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ8004: WebSphere MQ queue manager 'VENUS' ended.
EXPLANATION:
WebSphere MQ queue manager 'VENUS' ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(8604.3) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'LOGGER-IO' has started.
EXPLANATION:
The critical utility task manager has started the LOGGER-IO task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(4008.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ7229: 5 log records accessed on queue manager 'VENUS' during the log replay
phase.
EXPLANATION:
5 log records have been accessed so far on queue manager VENUS during the log
replay phase in order to bring the queue manager back to a previously known
state.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(4008.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ7230: Log replay for queue manager 'VENUS' complete.
EXPLANATION:
The log replay phase of the queue manager restart process has been completed
for queue manager VENUS.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(4008.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ7231: 0 log records accessed on queue manager 'VENUS' during the recovery
phase.
EXPLANATION:
0 log records have been accessed so far on queue manager VENUS during the
recovery phase of the transactions manager state.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(4008.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ7232: Transaction manager state recovered for queue manager 'VENUS'.
EXPLANATION:
The state of transactions at the time the queue manager ended has been
recovered for queue manager VENUS.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(4008.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ7233: 0 out of 0 in-flight transactions resolved for queue manager 'VENUS'.
EXPLANATION:
0 transactions out of 0 in-flight at the time queue manager VENUS ended have
been resolved.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(8604.4) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'CHECKPOINT' has started.
EXPLANATION:
The critical utility task manager has started the CHECKPOINT task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(4008.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ8003: WebSphere MQ queue manager 'VENUS' started using V7.5.0.2.
EXPLANATION:
WebSphere MQ queue manager 'VENUS' started using V7.5.0.2.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(11236.4) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(11236.6) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 2 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(11236.3) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'ERROR-LOG' has started.
EXPLANATION:
The restartable utility task manager has started the ERROR-LOG task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(11236.5) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 3 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(11236.7) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 4 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(8604.16) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'EXPIRER' has started.
EXPLANATION:
The critical utility task manager has started the EXPIRER task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(11236. User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'STATISTICS' has started.
EXPLANATION:
The restartable utility task manager has started the STATISTICS task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(8604.15) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'ASYNCQ' has started.
EXPLANATION:
The critical utility task manager has started the ASYNCQ task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:14 - Process(8604.17) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'DUR-SUBS-MGR' has started.
EXPLANATION:
The critical utility task manager has started the DUR-SUBS-MGR task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(7996.1) User(MUSR_MQADMIN) Program(amqrrmfa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9410: Repository manager started.
EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(8604.1 User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'TOPIC-TREE' has started.
EXPLANATION:
The critical utility task manager has started the TOPIC-TREE task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(5884.3) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5052: The queue manager task 'QPUBSUB-CTRLR' has started.
EXPLANATION:
The publish/subscribe utility task manager has started the QPUBSUB-CTRLR task.
This task has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(5884.4) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5052: The queue manager task 'QPUBSUB-QUEUE-NLCACHE' has started.
EXPLANATION:
The publish/subscribe utility task manager has started the
QPUBSUB-QUEUE-NLCACHE task. This task has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(8604.19) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'Q-DELETION' has started.
EXPLANATION:
The critical utility task manager has started the Q-DELETION task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(11236.9) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5037: The queue manager task 'MARKINTSCAN' has started.
EXPLANATION:
The restartable utility task manager has started the MARKINTSCAN task. This
task has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(8604.20) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'PRESERVED-Q' has started.
EXPLANATION:
The critical utility task manager has started the PRESERVED-Q task. This task
has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(5884.5) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5052: The queue manager task 'QPUBSUB-SUBPT-NLCACHE' has started.
EXPLANATION:
The publish/subscribe utility task manager has started the
QPUBSUB-SUBPT-NLCACHE task. This task has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(8604.21) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5051: The queue manager task 'MULTICAST' has started.
EXPLANATION:
The critical utility task manager has started the MULTICAST task. This task has
now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(5884.6) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5052: The queue manager task 'PUBSUB-DAEMON' has started.
EXPLANATION:
The publish/subscribe utility task manager has started the PUBSUB-DAEMON task.
This task has now started 1 times.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(5884.6) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5975: 'WebSphere MQ Distributed Pub/Sub Controller' has started.
EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Controller' has started.
ACTION:
-------------------------------------------------------------------------------
9/27/2015 07:37:15 - Process(5884. User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5975: 'WebSphere MQ Distributed Pub/Sub Command Task' has started.
EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Command Task' has started.
ACTION:
-------------------------------------------------------------------------------
9/27/2015 07:37:16 - Process(5884.7) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5975: 'WebSphere MQ Distributed Pub/Sub Fan Out Task' has started.
EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Fan Out Task' has started.
ACTION:
-------------------------------------------------------------------------------
9/27/2015 07:37:16 - Process(5884.9) User(MUSR_MQADMIN) Program(amqzmuf0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5975: 'WebSphere MQ Distributed Pub/Sub Publish Task' has started.
EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Publish Task' has started.
ACTION:
-------------------------------------------------------------------------------
9/27/2015 07:37:16 - Process(5596.1) User(MUSR_MQADMIN) Program(amqzmgr0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5022: The channel initiator has started. ProcessId(8460).
EXPLANATION:
The channel initiator process has started.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:16 - Process(5596.1) User(MUSR_MQADMIN) Program(amqzmgr0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5024: The command server has started. ProcessId(6308).
EXPLANATION:
The command server process has started.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:37:17 - Process(4604.1) User(MUSR_MQADMIN) Program(amqfqpub.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5806: WebSphere MQ Publish/Subscribe broker started for queue manager VENUS.
EXPLANATION:
WebSphere MQ Publish/Subscribe broker started for queue manager VENUS.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:42:07 - Process(5596.1) User(MUSR_MQADMIN) Program(amqzmgr0.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ5026: The listener 'VENUS.MERCURY.LSTR' has started. ProcessId(5424).
EXPLANATION:
The listener process has started.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:42:07 - Process(10172.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9002: Channel 'VENUS.MERCURY' is starting.
EXPLANATION:
Channel 'VENUS.MERCURY' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:42:08 - Process(3968.3) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'VENUS.MERCURY'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:42:08 - Process(3968.3) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 3968(9352) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:42:08 - Process(10172.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'VENUS.MERCURY' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:42:08 - Process(10172.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'LOCALHOST(1616)' ended abnormally.
EXPLANATION:
The channel program running under process ID 10172(1156) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'LOCALHOST(1616)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:43:08 - Process(7360.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9002: Channel 'VENUS.MERCURY' is starting.
EXPLANATION:
Channel 'VENUS.MERCURY' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:43:10 - Process(3968.4) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'VENUS.MERCURY'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:43:10 - Process(3968.4) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 3968(6784) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:43:12 - Process(7360.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'VENUS.MERCURY' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:43:12 - Process(7360.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'LOCALHOST(1616)' ended abnormally.
EXPLANATION:
The channel program running under process ID 7360(5416) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'LOCALHOST(1616)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:44:10 - Process(3952.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9002: Channel 'VENUS.MERCURY' is starting.
EXPLANATION:
Channel 'VENUS.MERCURY' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:44:10 - Process(3968.5) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'VENUS.MERCURY'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:44:10 - Process(3968.5) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 3968(7832) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:44:11 - Process(3952.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'VENUS.MERCURY' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:44:11 - Process(3952.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'LOCALHOST(1616)' ended abnormally.
EXPLANATION:
The channel program running under process ID 3952(8388) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'LOCALHOST(1616)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:45:12 - Process(8032.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9002: Channel 'VENUS.MERCURY' is starting.
EXPLANATION:
Channel 'VENUS.MERCURY' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:45:12 - Process(3968.6) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'VENUS.MERCURY'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:45:12 - Process(3968.6) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 3968(9188) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:45:12 - Process(8032.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'VENUS.MERCURY' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:45:12 - Process(8032.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'LOCALHOST(1616)' ended abnormally.
EXPLANATION:
The channel program running under process ID 8032(1484) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'LOCALHOST(1616)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:46:12 - Process(9824.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9002: Channel 'VENUS.MERCURY' is starting.
EXPLANATION:
Channel 'VENUS.MERCURY' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:46:12 - Process(3968.7) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'VENUS.MERCURY'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:46:12 - Process(3968.7) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 3968(8788) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:46:12 - Process(9824.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'VENUS.MERCURY' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:46:12 - Process(9824.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'LOCALHOST(1616)' ended abnormally.
EXPLANATION:
The channel program running under process ID 9824(10552) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'LOCALHOST(1616)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:47:12 - Process(10712.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9002: Channel 'VENUS.MERCURY' is starting.
EXPLANATION:
Channel 'VENUS.MERCURY' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:47:12 - Process(3968. User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'VENUS.MERCURY'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:47:12 - Process(3968. User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 3968(7988) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:47:12 - Process(10712.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'VENUS.MERCURY' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:47:12 - Process(10712.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'LOCALHOST(1616)' ended abnormally.
EXPLANATION:
The channel program running under process ID 10712(8904) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'LOCALHOST(1616)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:48:12 - Process(4160.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9002: Channel 'VENUS.MERCURY' is starting.
EXPLANATION:
Channel 'VENUS.MERCURY' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:48:12 - Process(3968.9) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'VENUS.MERCURY'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:48:12 - Process(3968.9) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 3968(4844) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:48:12 - Process(4160.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'VENUS.MERCURY' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:48:12 - Process(4160.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'LOCALHOST(1616)' ended abnormally.
EXPLANATION:
The channel program running under process ID 4160(8096) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'LOCALHOST(1616)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:49:12 - Process(9824.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9002: Channel 'VENUS.MERCURY' is starting.
EXPLANATION:
Channel 'VENUS.MERCURY' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:49:12 - Process(3968.10) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'VENUS.MERCURY'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:49:12 - Process(3968.10) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 3968(7196) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:49:12 - Process(9824.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'VENUS.MERCURY' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:49:12 - Process(9824.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'LOCALHOST(1616)' ended abnormally.
EXPLANATION:
The channel program running under process ID 9824(7148) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'LOCALHOST(1616)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
9/27/2015 07:50:12 - Process(8748.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9002: Channel 'VENUS.MERCURY' is starting.
EXPLANATION:
Channel 'VENUS.MERCURY' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
9/27/2015 07:50:12 - Process(3968.11) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'VENUS.MERCURY'. Some
operations are only valid for certain channel types. This channel is a 'SENDER'
channel type. For example, you can only ping a channel from the end sending the
message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- cmqxrmsa.c : 2057 -------------------------------------------------------
9/27/2015 07:50:12 - Process(3968.11) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'ADMINIB-4PF2DGD (127.0.0.1)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 3968(7540) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'ADMINIB-4PF2DGD
(127.0.0.1)'; in some cases the host name cannot be determined and so is shown
as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
9/27/2015 07:50:12 - Process(8748.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9547: Type of remote channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed because channel 'VENUS.MERCURY' on
the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
----- cmqxrfpt.c : 526 --------------------------------------------------------
9/27/2015 07:50:12 - Process(8748.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(ADMINIB-4PF2DGD) Installation(WMQ1)
VRMF(7.5.0.2) QMgr(VENUS)
AMQ9999: Channel 'VENUS.MERCURY' to host 'LOCALHOST(1616)' ended abnormally.
EXPLANATION:
The channel program running under process ID 8748(148) for channel
'VENUS.MERCURY' ended abnormally. The host name is 'LOCALHOST(1616)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1003 -------------------------------------------------------
|
|
|
| Back to top |
|
|
| exerk |
| Posted: Sat Sep 26, 2015 7:00 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Having had a more detailed look at your definitions in your first post I see this:
| Quote: |
| ALTER CHANNEL(VENUS.MERCURY) CHLTYPE(SDR) CONNAME('LOCALHOST(1616)') XMITQ(VENUS.XMIT) TRPTYPE(TCP) |
Did you stop the channel before altering it because your screen-shot shows the listener port you defined for the MERCURY queue manager, which is hosting the channel? In effect you're telling it to connect to itself.
If that's the case, sorry, I should have spotted that earlier - all the perils and pitfalls of a 'quick look'!
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| ckrisasa |
| Posted: Sat Sep 26, 2015 10:33 pm Post subject: |
|
|
Newbie
Joined: 26 Sep 2015
Posts: 9
|
EDITED: Updated PORT NUMBERS, Now its working
Sorry,
I have the latest definitions, but still I see the same error. I deleted old QMGRs and created new ones.
The problem is I couldn't pin-point the actual problem here. It would be so relief if you can trace the error here.
Mercury:
| Quote: |
CRTMQM MERCURY
STRMQM MERCURY
RUNMQSC MERCURY
DEFINE QLOCAL(MERCURY.XMIT) USAGE(XMITQ)
DEFINE QREMOTE(MERCURY.REMOTE) RNAME(VENUS.LOCAL) RQMNAME(VENUS) XMITQ(MERCURY.XMIT)
DEFINE QLOCAL(MERCURY.LOCAL)
DEFINE CHANNEL(MERCURY.VENUS) CHLTYPE(SDR) CONNAME('LOCALHOST(1515)') XMITQ(MERCURY.XMIT) TRPTYPE(TCP)
DEFINE CHANNEL(VENUS.MERCURY) CHLTYPE(RCVR) TRPTYPE(TCP)
DEFINE LISTENER(MERCURY.VENUS.LSTR) TRPTYPE(TCP) PORT(1616)
START CHANNEL(MERCURY.VENUS)
START LISTENER(MERCURY.VENUS.LSTR)
END
|
Venus:
| Quote: |
CRTMQM VENUS
STRMQM VENUS
RUNMQSC VENUS
DEFINE QLOCAL(VENUS.XMIT) USAGE(XMITQ)
DEFINE QREMOTE(VENUS.REMOTE) RNAME(MERCURY.LOCAL) RQMNAME(MERCURY) XMITQ(VENUS.XMIT)
DEFINE QLOCAL(VENUS.LOCAL)
DEFINE CHANNEL(MERCURY.VENUS) CHLTYPE(RCVR) TRPTYPE(TCP)
DEFINE CHANNEL(VENUS.MERCURY) CHLTYPE(SDR) CONNAME('LOCALHOST(1616)') XMITQ(VENUS.XMIT) TRPTYPE(TCP)
DEFINE LISTENER(VENUS.MERCURY.LSTR) TRPTYPE(TCP) PORT(1515)
START CHANNEL(VENUS.MERCURY)
START LISTENER(VENUS.MERCURY.LSTR)
END
|
Last edited by ckrisasa on Sun Sep 27, 2015 5:12 am; edited 1 time in total |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Sun Sep 27, 2015 12:44 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
It looks to me as though you are pointing your sender channels to your own listener!
The MERCURY sender channel should specify the port of the VENUS listener and
the VENUS sender channel should specify the port of the MERCURY listener.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Sep 27, 2015 3:35 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
When asked to post from error logs, please copy/paste only one instance of the relevant error - not the entire contents of the error file.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| ckrisasa |
| Posted: Sun Sep 27, 2015 5:10 am Post subject: |
|
|
Newbie
Joined: 26 Sep 2015
Posts: 9
|
| PaulClarke wrote: |
It looks to me as though you are pointing your sender channels to your own listener!
The MERCURY sender channel should specify the port of the VENUS listener and
the VENUS sender channel should specify the port of the MERCURY listener.
Cheers,
Paul. |
Thanks Man, Finally Its resolved. 
P.S: I'm sorry posting whole log information. |
|
| Back to top |
|
|
| jcv |
| Posted: Tue Oct 06, 2015 8:54 am Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
| fjb_saper wrote: |
Review your conventions.
... you should have a VENUS.LISTENER on the venus qmgr and a MERCURY.LISTENER on the mercury queue manager.
|
I avoid incorporating redundant information into object name, like object type and name of qmgr where the object is defined. Considering the fact that choosing a meaningful name is the most important agenda of naming, I wonder what would be the use case that disputes such rules? I'm not talking about listeners only here. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Oct 06, 2015 9:35 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I name listeners LISTENER.TCP.pppp
- where pppp is the port number.
This naming standard seems self-documenting. It's a LISTENER, it's listening for TCP flows, on port pppp.
I suppose I could name the listener pppp, and leave off the redundant LISTENER.TCP., but that would seem to me to be too much abbreviation.
I've been told that keystrokes that we conserve here can be used in poorer countries, but I have my doubts.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| jcv |
| Posted: Wed Oct 07, 2015 9:56 am Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
| bruce2359 wrote: |
I name listeners LISTENER.TCP.pppp
- where pppp is the port number.
This naming standard seems self-documenting. It's a LISTENER, it's listening for TCP flows, on port pppp.
I suppose I could name the listener pppp, and leave off the redundant LISTENER.TCP., but that would seem to me to be too much abbreviation.
I've been told that keystrokes that we conserve here can be used in poorer countries, but I have my doubts. |
This is not documenting anything. That's just repeating information already present in the definition. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 07, 2015 10:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jcv wrote: |
| This is not documenting anything. That's just repeating information already present in the definition. |
I also use a port number in the listener name as a surprising number of people can see the name of a listener but appear incapable of finding the port number in the definition / finding the definition / correlating the "port number" field in the definition to the port number used by the listener.
Seriously.
I was once asked how the port number defined to a listener correlated to the port that would be opened in the network.
You can't fix stupid, but this at least duct tapes it in place.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
  |
Goto page 1, 2 Next |
Page 1 of 2 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
