| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| mqsisetdbparms and configureable service |
« View previous topic :: View next topic » |
| Author |
Message
|
| Johan448 |
 Posted: Tue Jun 24, 2014 12:00 am Post subject: mqsisetdbparms and configureable service |
 |
|
Newbie
Joined: 27 May 2013
Posts: 5
|
Hi,
So i am using a configureable service for an FTP connection with a FileOutput Node.
i created a secId with mqsisetdbparms but now i need to change the username.
I checked the infocenter and this say that altering the mqsisetdbparms bascially just means rerun it with new paramters. I did this and i ran an mqsireload on the EG. however the change does not seem to work. Still trying with the old username.
Is there anything i am missing ? Do i need to restart the broker ? do i need to recreate the configureable service which uses the secId ?
Broker version 7.0.0.3
Thanks ! |
|
| Back to top |
|
 |
| zpat |
| Posted: Tue Jun 24, 2014 2:48 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
if nothing in the configurable service has changed - no need to re-create it (or change it).
You can check if the mqsisetdbparms has actually worked by looking in the registry directory (DSN).
mqsireload should be enough to pick up any changes.
Are you sure the configurable service is being referenced by the flow?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| adrian_ |
| Posted: Wed Jun 25, 2014 1:55 pm Post subject: |
|
|
Novice
Joined: 06 Jan 2012
Posts: 13
|
hi, to work you need to run mqsisetdbparms with broker stoped
so first stop the broker
re run mqsisetdbparms with the new parameters
start the broker
problem solved |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jun 25, 2014 10:16 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You don't need to stop the broker to run mqsisetdbparms since version 7.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| 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
|
|
|
|
