| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [Solved] Problem executing mqsichangeproperties command |
« View previous topic :: View next topic » |
| Author |
Message
|
| srikanth av |
 Posted: Thu May 22, 2008 1:34 pm Post subject: [Solved] Problem executing mqsichangeproperties command |
 |
|
Apprentice
Joined: 30 Jun 2005
Posts: 37
|
Hello All,
I am running the following command to change the properties of the broker.
C:\IBM\MQSI\6.1>mqsichangeproperties WBRK61_DEFAULT_BROKER -c ServiceRegistries -o DefaultWSRR -n endpointAddress -v http://localhost:9080/WSRRCoreSDO/services/
WSRRCoreSDOport
But I am getting the following error:
BIP8004E: Invalid argument '-c ServiceRegistries' specified.
Argument specified should be well formed.
Correct and reissue the command.
Actually I am running the WSRR Connectivity sample.
Does anyone has any idea about the error.I have seen the infocenter also.I found the same syntax.Can anybody say what could be the problem is.
Thanks in advance.
_________________
a v srikanth
Last edited by srikanth av on Fri May 23, 2008 8:06 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Fri May 23, 2008 3:05 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
That looks OK to me.
You might want to try viewing and setting this value using the CMP API Exerciser; that will show you all the possible mqsichangeproperties values the broker knows about, and will therefore allow you to check you haven't made a typo.
If you do this, remember to deploy the changed configuration to the broker afterwards. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri May 23, 2008 3:42 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
...also, have you got any v6/v5 on your machine? Make sure you're running the v6.1 version of the command  |
|
| Back to top |
|
|
| srikanth av |
| Posted: Fri May 23, 2008 8:04 am Post subject: |
|
|
Apprentice
Joined: 30 Jun 2005
Posts: 37
|
Hello All,
The problem was solved by applying the fixpack 1 to the broker 6.1. 
_________________
a v srikanth |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
