| Author |
Message
|
| fossil |
 Posted: Wed Mar 21, 2007 7:52 am Post subject: WMBv6 on Solaris mqsiprofile problem |
 |
|
Newbie
Joined: 21 Mar 2007
Posts: 3
|
Running Solaris 10, zones "Whole-Root"
MQ Series is installed and running
RAC 6.0 installed
DB2 installed and running
MB v6 and FP3 installed with no problem(Broker only runtime) in the default directory /opt/IBM/mqsi/6.0
logged on as mqadmin
Executed . /mqsiprofile and . ./mqsiprofile and received the same results
PATH:/opt/IBM/mqsi/6.0/jre/bin:/opt/IBM/mqsi/6.0/bin:/usr/bin:: is not an identifier
I did not execute a .profile when doing an su - mqadmin, the PATH=/usr/bin was set by O/S 
_________________
Jim |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Mar 21, 2007 8:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Are you sure someone didn't modify ./mqsiprofile?
What happens if you source /opt/IBM/mqsi/6.0/bin/mqsiprofile, instead of ./mqsiprofile?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fossil |
| Posted: Wed Mar 21, 2007 11:06 am Post subject: |
|
|
Newbie
Joined: 21 Mar 2007
Posts: 3
|
Problem was the IBM supplied mqsiprofile. It had 'export PATH=..." in a ksh. Changed statement and it worked. There are 3 of them in a row at the end of the mqsiprofile
_________________
Jim |
|
| Back to top |
|
|
| PieterV |
| Posted: Thu Mar 22, 2007 7:09 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
this should be in the profile in stead of the lines with export before it:
PATH=${MQSI_JREPATH}/bin:${PATH}
LD_LIBRARY_PATH=${MQSI_JREPATH}/lib/sparc/server:${MQSI_JREPATH}/lib/sparc:${LD_LIBRARY_PATH}
MQSI_LIBPATH64=${MQSI_JREPATH}/lib/sparcv9/server:${MQSI_JREPATH}/lib/sparcv9:${MQSI_LIBPATH64}
export PATH LD_LIBRARY_PATH MQSI_LIBPATH64 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 22, 2007 9:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you can actually show that the presupplied mqisprofile with that came with the product does not work, then you should open a PMR and let IBM support know this so they can fix it for other customers.
I suspect, however, that someone at your organization played around with this.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PieterV |
| Posted: Fri Mar 23, 2007 12:12 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
Jeff,
when i encountered the same problem i had opened a PMR with IBM and they proposed the above solution. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Mar 23, 2007 3:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Then I guess the presupplied profile is probably wrong, and hopefully this is being corrected in later FPs or RPs. 
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PieterV |
| Posted: Fri Mar 23, 2007 5:08 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
indeed.
however i think this error only occurs on solaris and when you call your mqsiprofile in a script.
(the error does not occur when you add mqsiprofile in .profile of your user)
Anyway i've ask IBM to fix it in a future release so i don't need to adapt the mqsiprofile after each fixpack.
Let's hope they've done what i've asked  |
|
| Back to top |
|
|
|
|
