Author |
Message
|
dlwood |
Posted: Mon Mar 11, 2002 12:34 pm Post subject: |
|
|
Newbie
Joined: 17 May 2001 Posts: 9 Location: Aegon USA
|
I get the above error on my Win2k installation of MQ 5.2.1, while trying to manipulate my channel definitions via the MMC. If I attempt to use the DOS shell under runmqsc, I get file I/O errors when displaying my list of channels. All of my channels show up in the display channel(*), with the file I/O error at the end of the list. If I attempt to display individual channels, I get the file I/O error, also.
I've been able to reset/start the channel under runmqsc, but I don't seem to get predictable results in displaying the channel status. This all sounds like a corrupt installation, so I completely uninstalled, and verified that there were no folders left or any remaining references to MQ in the register. I then reinstalled to a different directory path, but encountered the same problems.
We have a number of NT/win2k servers running MQ5.2.1, and this is the only one that we've seen this problem on. Does anyone have any ideas or suggestions?
Thanks,
Dan Wood
|
|
Back to top |
|
 |
peterli |
Posted: Mon Mar 11, 2002 2:31 pm Post subject: |
|
|
Apprentice
Joined: 17 Oct 2001 Posts: 29 Location: Melbourne, Australia
|
Is there any error messages in the AMQERR01.LOG file? I had a similiar problem on MQ5.1 CSD05. It was because the amqclchl.tab file was on a network shared drive, this was setup through the environment variables. Maybe this will help.
Cheers
Pete |
|
Back to top |
|
 |
mqonnet |
Posted: Tue Mar 12, 2002 8:35 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Check to see if your CHAD is enabled or your CHADEV is enabled. Try disabling both of them on a Newly created QM. Think this should do it.
Cheers.
Kumar
_________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
dlwood |
Posted: Tue Mar 12, 2002 8:51 am Post subject: |
|
|
Newbie
Joined: 17 May 2001 Posts: 9 Location: Aegon USA
|
The error message that shows up in the log is:
03/12/2002 11:36:41
AMQ6120: An internal MQSeries error has occurred.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
I did some checking and there is no amqclchl.tab for that queue manager. I tried creating a queue manager of the same name on a different sever, then copied that amqclchl.tab file to the problem server, but that didn't work either. Is there a circumstance that would prevent the amqclchl.tab from being created? Is there a way to create one manually that the queue manager will recognize?
Thanks for any help,
Dan |
|
Back to top |
|
 |
mrlinux |
Posted: Tue Mar 12, 2002 9:24 am Post subject: |
|
|
 Grand Master
Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA
|
I had a similar error only with queues,
Heres how I was able to find it
1) Enable Tracing strmqtrc
2) Do your failing runmqsc command
3) Disable Tracing endmqtrc
4) Search through the trace files until you find the one for the runmqsc
and see if it this gives you some useful info, or post it here and I will
look at it if you want.
_________________ Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
Back to top |
|
 |
Richard V |
Posted: Tue Mar 12, 2002 11:30 am Post subject: |
|
|
Newbie
Joined: 11 Mar 2002 Posts: 1
|
The only thing that comes to mind is that your using a client and a server on the same box. Take out all mqchltab and mqchllib references from your environment variables. THen run crtmqm with the "recreate objects" switch. Try it and let me know. Also, copy the amqclchl.tab file from the @system of your qmgr and paste it at the root Mqseries subdirector ex. d:mqseries . THe client variables is what caused this to happen. |
|
Back to top |
|
 |
neocruz |
Posted: Thu Sep 15, 2005 10:49 am Post subject: Update |
|
|
Acolyte
Joined: 13 Jun 2004 Posts: 54
|
Just to update this, the command is:
STRMQM -c <QmgrName>
This is rebuild the default system objects. |
|
Back to top |
|
 |
|