ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQSILIST Command is displaying error

Post new topic  Reply to topic
 MQSILIST Command is displaying error « View previous topic :: View next topic » 
Author Message
praveenmq
PostPosted: Sun Mar 04, 2012 11:18 pm    Post subject: MQSILIST Command is displaying error Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

Hi All,

I just issued mqsilist in my machine and it is telling mqsilist not found.

I tried to run my mqsiprofile command using ./mqsiprofile and it ran successfully. After that i tried to issue mqsilist it is still displaying the same error.

Please advise what env variable needs to be set?

Thanks,
Praveen.
Back to top
View user's profile Send private message
smdavies99
PostPosted: Sun Mar 04, 2012 11:42 pm    Post subject: Re: MQSILIST Command is displaying error Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

praveenmq wrote:
Hi All,

I just issued mqsilist in my machine and it is telling mqsilist not found.

I tried to run my mqsiprofile command using ./mqsiprofile and it ran successfully. After that i tried to issue mqsilist it is still displaying the same error.

Please advise what env variable needs to be set?

Thanks,
Praveen.


What platform?
What version of Broker?
Can you add the output from the terminal from the time that you sourced the mqsiprofile until after the output of the mqsilist completes.

Without this sort of detail it is very difficult to even start suggesting where the problem lies.
_________________
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
View user's profile Send private message
praveenmq
PostPosted: Mon Mar 05, 2012 11:39 pm    Post subject: Resolved Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

Hi Ijust found the problem.

mqsiprofile was added into user mqm.
So i should first switch user to mqm to issue broker commands.

Thanks,
Praveen.
Back to top
View user's profile Send private message
mqsiuser
PostPosted: Tue Mar 06, 2012 1:13 am    Post subject: Re: Resolved Reply with quote

Yatiri

Joined: 15 Apr 2008
Posts: 637
Location: Germany

You should use the broker user (e.g. mqsibrk) actually.

If mqm also works, then well probably ok.

What you definitivly have to do is "load the profile".
_________________
Just use REFERENCEs
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Mar 06, 2012 5:43 am    Post subject: Re: Resolved Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

mqsiuser wrote:
If mqm also works, then well probably ok.



_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Mar 06, 2012 5:44 am    Post subject: Re: Resolved Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

praveenmq wrote:
So i should first switch user to mqm to issue broker commands.


No, you should fix your setup. Any number of posts in here about running WMB with mqm.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Tue Mar 06, 2012 5:59 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

The other posts talk about Broker service Id having mqbrkrs as its primary group. Since mqm's service Id has mqm group as it's primary group, you should not use mqm service id as the id to run Broker under.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
fjb_saper
PostPosted: Tue Mar 06, 2012 6:20 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

lancelotlinc wrote:
The other posts talk about Broker service Id having mqbrkrs as its primary group. Since mqm's service Id has mqm group as it's primary group, you should not use mqm service id as the id to run Broker under.

And how do you do that when you run WMB as a service in WMQ?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
lancelotlinc
PostPosted: Tue Mar 06, 2012 6:25 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

fjb_saper wrote:
lancelotlinc wrote:
The other posts talk about Broker service Id having mqbrkrs as its primary group. Since mqm's service Id has mqm group as it's primary group, you should not use mqm service id as the id to run Broker under.

And how do you do that when you run WMB as a service in WMQ?


We've lodged several issues with the documentation. While it is possible to do what you suggest, and the legacy documentation supports it, myriad problems occur when so: mqsi commands hang, for example.

When the Ids are arranged as indicated, and the user sudo's into the Broker service Id, the mqsi commands do not hang.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
lancelotlinc
PostPosted: Tue Mar 06, 2012 7:46 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

lancelotlinc wrote:
fjb_saper wrote:
lancelotlinc wrote:
The other posts talk about Broker service Id having mqbrkrs as its primary group. Since mqm's service Id has mqm group as it's primary group, you should not use mqm service id as the id to run Broker under.

And how do you do that when you run WMB as a service in WMQ?


We've lodged several issues with the documentation. While it is possible to do what you suggest, and the legacy documentation supports it, myriad problems occur when so: mqsi commands hang, for example.

When the Ids are arranged as indicated, and the user sudo's into the Broker service Id, the mqsi commands do not hang.


We're starting to see some of the documentation get corrected for version 8:

http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fau16560_.htm

Quote:
must have a primary group of mqbrkrs


Code:
Change / Show Characteristics of a User 

   Type or select values in entry fields.
   Press Enter AFTER making all desired changes. 
   [TOP]                               [Entry Fields]
   * User NAME                         peterc
     User ID                           [202]                    #
     ADMINISTRATIVE USER?              false                    +
     Primary GROUP                     [mqbrkrs]                +
     Group SET                         [mqbrkrs,mqm,system,sys> +



Here is an explanation of why this is so:

Quote:
A semaphore is created when the first broker starts after a reboot (or after an initial installation), and only members of the primary group of the semaphore creator can access this semaphore. This problem is a consequence of the UNIX System V IPC primitives that are used by WebSphere Message Broker.

Solution: Avoid this problem by ensuring that all user IDs used to start WebSphere Message Broker have the same primary group. If this action is impractical, ensure that all user IDs are members of primary groups of all other user IDs. Contact your IBM® Support Center for further assistance.



Some z/OS specifics:

http://www-01.ibm.com/support/docview.wss?uid=swg1PM16158

Quote:

A global mutex (semaphore) is used to control access to the
broker's configuration repository, and it is created by the
broker started task. Some commands also require access to the
repository, as well as the broker and execution group tasks,
and therefore the administrator user id that is running the
command jobs must have sufficient access permissions to use
the semaphore. If the administrator user id does not have
sufficient access, the command job abends when issuing a
semctl() system call .

When the semaphore is created by the broker on startup, it
tries to set the owning group of the semaphore to "mqbrkrs" by
making a getgrnam() system call to get the GID for the
"mqbrkrs" group name. This is correct for distributed
platforms since this group has to be defined to be able to use
the Message Broker, but this is not the case on z/OS. The
result of the getgrnam() system call is not being checked and
this leads to unpredictable values being set for the semaphore
group ownership on z/OS.

_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQSILIST Command is displaying error
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.