Author |
Message
|
chris boehnke |
Posted: Wed Dec 10, 2008 2:59 pm Post subject: Problem executing mqsiservice, mqsicreateconfigmgr etc. |
|
|
 Partisan
Joined: 25 Jul 2006 Posts: 369
|
Hi All,
I have installed Webspeher Message Broker V6.0 on Suse Linux Enterprise Server 10. After successful completion of broker installation, i tried to type the command mqsiservice -v at the command prompt but it gave me an error stating that: bash: mqsiservice command not found. Later I went to the installed directory /opt/ibm/mqsi/6.0/bin and executed the command ./mqsiservice -v but it returned me an error message stating that: " ./mqsiservice: error while loading shared libraries : libImbCmdLib.so: cannot open shared object file: No such file or directory"
I have not installed the fix pack for message broker yet. Is this causing the problem? Could anybody tell me the reason why it is throwing such error and how to rectify it?
Any help would be appreciable. Advance thanks for the help. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Dec 10, 2008 3:04 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
did you correctly source mqsiprofile?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
chris boehnke |
Posted: Wed Dec 10, 2008 3:26 pm Post subject: |
|
|
 Partisan
Joined: 25 Jul 2006 Posts: 369
|
Hi,
Thanks for your reply. However, I could not understand what you mean by "source mqsiprofile". What exactly should I do? |
|
Back to top |
|
 |
chris boehnke |
Posted: Wed Dec 10, 2008 3:45 pm Post subject: |
|
|
 Partisan
Joined: 25 Jul 2006 Posts: 369
|
Hi,
Thanks for your reply. I searched for the info regarding sourcing mqsiprofile and I found that I have to type . ./mqsiprofile at the installed directory and I got some info like ..
MQSI 6.0.0.1
/opt/ibm/mqsi/6.0
Then I typed ./mqsiservice -v at the installed directory and it gave me the version of the installed message broker.
Thanks a lot for your help. |
|
Back to top |
|
 |
AkankshA |
Posted: Wed Dec 10, 2008 8:00 pm Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
chris boehnke wrote: |
Hi,
Thanks for your reply. I searched for the info regarding sourcing mqsiprofile and I found that I have to type . ./mqsiprofile at the installed directory and I got some info like ..
MQSI 6.0.0.1
/opt/ibm/mqsi/6.0
Then I typed ./mqsiservice -v at the installed directory and it gave me the version of the installed message broker.
Thanks a lot for your help. |
add sourcing command in .profile of login id to avoid this problem cropping again..
 _________________ Cheers |
|
Back to top |
|
 |
PeterPotkay |
Posted: Thu Dec 11, 2008 3:05 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
chris boehnke wrote: |
MQSI 6.0.0.1
/opt/ibm/mqsi/6.0
Then I typed ./mqsiservice -v at the installed directory and it gave me the version of the installed message broker.
|
mqsiprofile already gave you the version.
mqsiservice is not a documented command. Avoid using it in favor of the official commands that give you the functionality you need. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
AkankshA |
Posted: Thu Dec 11, 2008 7:50 pm Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
peter
mqsiprofile only shows me the directory of installation but as far as i know complete version info is available only with mqsiservice
Quote: |
MQSI 6.1.0.2
/MessageBroker/IBM/mqsi/6.1
$
$ mqsiservice -v
BIPv610 en US
ucnv Console CCSID 819 dft ucnv CCSID 819
ICUW ISO-8859-1 ICUA ISO-8859-1
BIP8996I: Version: 6102
BIP8997I: Product: WebSphere Message Brokers
BIP8998I: CMVC Level: S610-FP02 DH610-FP02
BIP8999I: Build Type: Production
BIP8071I: Successful command completion. |
do we have any other substitute for mqsiservice ?? _________________ Cheers |
|
Back to top |
|
 |
smdavies99 |
Posted: Thu Dec 11, 2008 10:57 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
In the example
MQSI 6.1.0.2
as displayed when you source mqsiprofile is the version & patch level of the currently installed runtime.
If you install the latest 'fixpack' then that would change to 6.1.0.3 which by some strange coincidence is the build level of the fix pack.
This information is sufficient for IBM to know your build level when raising a PMR so a bit I'm puzzled as to why you need more detailed build state data?
/S _________________ 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 |
|
 |
|