Please

  I have a big problem with my system admnistration. My email account is almost the 
champion of receveid emails!!!! I tried unsubscribe me a lot of times but was not 
possible. Please, anybody helpme!!!!!!!!!

Thanks


Fábio de Arantes Ramos
Extensão 51651
[EMAIL PROTECTED]


-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay,
Peter M (PLC, IT)
Sent: quarta-feira, 10 de Março de 2004 14:31
To: [EMAIL PROTECTED]
Subject: Re: setmqaut and wildcarding


Thanks Hubert!

Wrapping the *.** in " " worked. I was running the command in a dir that had
lots of other files.

I also created a new dir called /var/mqm/emptydir (made sure there were no
other files in there), and tried running the command without the " " around
the *.**, and it worked that way as well.

So by running
/var/mqm/emptydir> setmqaut -m QM1 -t q -n *.** -g MyGroup +inq
or
/var/mqm/> setmqaut -m QM1 -t q -n "*.**" -g MyGroup +inq

any queues, including ones yet to be built, have inq authority for MyGroup.




-----Original Message-----
From: Kleinmanns, Hubert [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 10, 2004 7:15 AM
To: [EMAIL PROTECTED]
Subject: AW: setmqaut and wildcarding


Peter,

you wrote:

   brs17 > setmqaut -m HIGBRSD3 -t q -n *.** -p blrules +inq
   AMQ7085: Object cron.d, type q not found.

On Unix, the shell tries to expand wild cards to file names. This means, in
the example above, you have a directory or file called 'cron.d' in your
current working directory. The shell expands the term '*.**' to all file
names, which fit into this form (in your case only one 'cron.d') and passes
this list to the command (in this case 'setmqaut'). So you really called:

setmqaut -m HIGBRSD3 -t q -n cron.d -p blrules +inq

and then got the error message. Try the following:

setmqaut -m HIGBRSD3 -t q -n "*.**" -p blrules +inq

This should work, because now the shell passes the string '*.**' to the
command 'setmqaut.

Many regards
Hubert


-----Ursprungliche Nachricht-----
Von: Nick Dilauro [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 10. Marz 2004 01:49
An: [EMAIL PROTECTED]
Betreff: Re: setmqaut and wildcarding


Peter,


Thanks, I'll have to try it again. Must've done something wrong.

Nick


-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Potkay,
Peter M (PLC, IT)
Sent: Tuesday, March 09, 2004 4:33 PM
To: [EMAIL PROTECTED]
Subject: Re: setmqaut and wildcarding

Nick, I went to another server just to be sure.
ABC*.**

works for

ABC
ABCXXXXX
ABC.XXXX
ABC.X.X

and it works for new queues that I create as well.





>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Are you sure you deleted all the other entries first?  I tried ABC*.** and
it only worked for ABCMYQUEUENAME.

Nick

-----Original Message-----
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 09, 2004 6:11 PM
To: [EMAIL PROTECTED]
Subject: Re: setmqaut and wildcarding


ABC*.** solved the problem for the ABC queues. Any queue that start with ABC
gets it.

I then tried to give +inq to ALL the queue on the server with *.**. That
worked on server1, except SYSTEM.AUTH.DATA.QUEUE.  Even if I explicitly set
the allmqi command for this queue, I don't get access.

I went and tried this on server2, and it does not like *.**. It keeps
throwing me that "Object cron.d, type q not found" error. And, same problem
with giving api authority to the SYSTEM.AUTH.DATA.QUEUE.

brs17 > setmqaut -m HIGBRSD3 -t q -n *.** -p blrules +inq
AMQ7085: Object cron.d, type q not found.

brs17 > setmqaut -m HIGBRSD3 -n SOME.QUEUE.NAME -t q -p blrules +inq
The setmqaut command completed successfully.

brs17 > setmqaut -m HIGBRSD3 -n *.** -t q -p blrules +inq
AMQ7085: Object cron.d, type q not found.
brs17 > setmqaut -m HIGBRSD3 -n S*.** -t queue -p blrules +inq
The setmqaut command completed successfully.

brs17 > dspmqaut -m HIGBRSD3 -t q -n SYSTEM.AUTH.DATA.QUEUE -p blrules
Entity blrules has the following authorizations for object
SYSTEM.AUTH.DATA.QUEUE:
brs17>
brs17 > setmqaut -m HIGBRSD3 -t q -n SYSTEM.AUTH.DATA.QUEUE -p blrules +inq
The setmqaut command completed successfully.

brs17 > dspmqaut -m HIGBRSD3 -t q -n SYSTEM.AUTH.DATA.QUEUE -p blrules
Entity blrules has the following authorizations for object
SYSTEM.AUTH.DATA.QUEUE:

brs17>

-----Original Message-----
From: Adiraju, Rao [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 09, 2004 5:09 PM
To: [EMAIL PROTECTED]
Subject: Re: setmqaut and wildcarding


Try with ABC.** which should cover all but the second one. Either enforce a
naming standard or create a different profile for the second one.

Cheers

Rao

-----Original Message-----
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]
Sent: 10 March 2004 10:12 AM
To: [EMAIL PROTECTED]
Subject: setmqaut and wildcarding

I want to run just one setmqaut command so it works for all queues with the
following names:
ABC
ABCMYQUEUENAME
ABC.MYQUEUENAME
ABC.MY.QUEUENAME
ABC.MY.QUEUE.NAME

Anyway to do this?

(ABC** does not do it.)




Peter Potkay
MQSeries Specialist
The Hartford Financial Services
[EMAIL PROTECTED]
x77906
IBM MQSeries Certified




This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you are
not the intended recipient, please notify the sender immediately by return
email and delete this communication and destroy all copies.

Instructions for managing your mailing list subscription are provided in the
Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy or
retain it.
If you have received it in error please immediately notify me by return
email
and delete the emails.
Thank you.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to