| Author |
Message
|
| ddm |
 Posted: Fri Nov 21, 2003 1:40 pm Post subject: AMQ8118: WebSphere MQ queue manager does not exist. |
 |
|
Apprentice
Joined: 17 Nov 2003
Posts: 40
|
I am getting this error when I run strmqm on my machine.
AMQ8118: WebSphere MQ queue manager does not exist.
I am running MQSeries 5.3 on W2K. I have my environment variable all set up for the MQ Server.
How do I define an MQ Queue Manager?
Thanks! |
|
| Back to top |
|
 |
| starfish77 |
| Posted: Fri Nov 21, 2003 2:28 pm Post subject: |
|
|
Apprentice
Joined: 07 Nov 2003
Posts: 31
Location: USA
|
haven't u created a default QM.
Refer to chapter 6 of book WebSphere MQ Clients .. |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Nov 21, 2003 3:04 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Open WebSphere MQ Explorer
Ususally Start -> Programs -> IBM WebSpehre MQ -> MQ Explorer
Expand WebSpehre MQ and you will see Queue Managers.
Right click on Queue Managers -> New Queue Manager
Alternatively:
On a command prompt
crtmqm QMGRNAME |
|
| Back to top |
|
|
| clindsey |
| Posted: Fri Nov 21, 2003 3:53 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
You could make one of your queue managers a default qmgr if you choose, otherwise you have to include a qmgr name as a parm with strmqm. Start MQ Services and expand the qmgr list. right click on the qmgr you want to be default and select properties. Near the bottom of the dialog box you will see a check box that you can select to make this the default queue manager. Then strmqm with no parms will work.
Having said that, on windows it is preferred to start the qmgr as a service either from the MQ Explorer or from the command line with amqmdain.
Charlie |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Nov 21, 2003 5:04 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| ddm |
| Posted: Mon Nov 24, 2003 10:36 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2003
Posts: 40
|
Thanks guys for all the replies. And yes I only have the client 5.3. Now, I cannot even run my test app because of the following error:
An unhandled exception of type 'System.IO.FileNotFoundException' occurred in amqmdnet.dll
Additional information: File or assembly name System.EnterpriseServices, or one of its dependencies, was not found.
Basically what i did was to install CSD05 for 5.3. I think I did this over MA7P and it just screwed everything up. I can see 2 amqmdnet.dll. One in my install directory for CSD05 is C:\Program Files\IBM\Source\WebSphere MQ CSD05 EnUs and the other is for MA7P which is in C:\Program Files\IBM\WebSphere MQ\bin. Which ever one I reference I am getting the same error.
Both of them is in the GAC.
Please help. |
|
| Back to top |
|
|
| JasonE |
| Posted: Mon Nov 24, 2003 12:18 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| As per another append, I think this is caused by running with .net framework 1.0 rather than 1.1 |
|
| Back to top |
|
|
| ddm |
| Posted: Mon Nov 24, 2003 1:33 pm Post subject: |
|
|
Apprentice
Joined: 17 Nov 2003
Posts: 40
|
| I checked the documentation that comes with CSD05 and it says one of the the pre-requesites is the .Net Framework 1.03705 (which I have) or later. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Nov 24, 2003 1:35 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The documentation for .NET support in CSD05 is, shall we say, not 100% correct all the time.
You need 1.1, despite what the read me says.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| JasonE |
| Posted: Mon Nov 24, 2003 2:12 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Yes. FYI The SOE pages (which document the supported environments) is supposed to be being updated to document that. I spoke with the main developer of this the other day and he assured me it should have been documented in the first place.
I think the prereqs may have changed when converting from a support pack to the official version, but thats a guess. I suspect that would explain why the docs were not corrected as well.  |
|
| Back to top |
|
|
| ddm |
| Posted: Mon Nov 24, 2003 2:43 pm Post subject: |
|
|
Apprentice
Joined: 17 Nov 2003
Posts: 40
|
I was able to get it to work. I did install .Net Framework 1.1
Thanks guys for all your help! |
|
| Back to top |
|
|
|
|
