Author |
Message
|
mahesh4eai |
Posted: Fri Nov 20, 2015 10:33 am Post subject: is there any command to check broker is connecting which DB? |
|
|
Novice
Joined: 09 Aug 2014 Posts: 21
|
Hi All,
I am using websphere message broker 6.1 version and want to know is there any command to check the broker is connecting which database?? Recently i have changed the password for broker due to that when i entered the (mqsilist broker name) command its throwing the database error.kindly help on this.
Thanks.... |
|
Back to top |
|
 |
Vitor |
Posted: Fri Nov 20, 2015 10:44 am Post subject: Re: is there any command to check broker is connecting which |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mahesh4eai wrote: |
I am using websphere message broker 6.1 version |
Seriously? You do know that's 2 major versions out of support don't you?
mahesh4eai wrote: |
and want to know is there any command to check the broker is connecting which database?? |
Well you could try looking at the database configuration.
If you don't know where that is, you can look it up in the online Info Center.
Or could, if there was one for such an old version.
Or the local copy you've kept around as part of your plan to support this ancient, creaking version of broker long after you should have upgraded. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Nov 20, 2015 11:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You could shut down your databases one by one until the Broker complains.
This is a terrible idea. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
Vitor |
Posted: Fri Nov 20, 2015 11:19 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
You could shut down your databases one by one until the Broker complains.
This is a terrible idea. |
You could then shut down the broker and leave it closed, because it's so old that sooner or later someone will upgrade the OS and it will stop working anyway.
This is a better idea....  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Nov 20, 2015 11:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You could find a new job, and then suddenly quit the current one.
This makes the whole mess someone else's problem.
This is probably a pretty good idea. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
Vitor |
Posted: Fri Nov 20, 2015 11:31 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
You could find a new job, and then suddenly quit the current one.
This makes the whole mess someone else's problem.
This is probably a pretty good idea. |
Best so far  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
smdavies99 |
Posted: Fri Nov 20, 2015 12:21 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
I take it that...
1) You don't have the source to the message flows being used?
2) You don't have the scripts that were used to create the broker in the first place?
If not then I agree with the idea that it is time to get another job.
Do the words 'up the creek without a paddle' describe your situation? _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
|