Title: Message
"on UNIX the authority is stored on group level
(even if assigned using -p user...)" - is
this really true?
if you assign using -p user do the
permissions then get assigned to that users primary group or all groups of which
it is a member?
-Original Message-From:
Title: Message
yep!
-Original Message-From: Wright, Tim (ANTS)
[mailto:[EMAIL PROTECTED]Sent: Wednesday, January 07, 2004
1:29 PMTo: [EMAIL PROTECTED]Subject: Re: display /
remove all authorizations
"on UNIX the authority is stored on group
level (even if assigned using -p
Title: Message
Sorry
didn't read the last words...
the
rights are assigned to the primary group, all users who have that primairy group
as their 2nd or Nth group get the rights as well..
-Original Message-From: Wright, Tim (ANTS)
[mailto:[EMAIL PROTECTED]Sent: Wednesday, January
Title: Message
They
get assigned to the user's primary group.
Unfortunately there is no way to remove authority setting once they have
been added, short of deleting and re-creating the object. Using -all with
setmqaut against a user/group does not remove the authority. It sets the
authority to
Title: Message
Primary group (IIRC) ...
Dave
Title: Message
This
is one of the things discussed in the security article at:
http://www.sjg-enterpriseintegration.com/closingmqholes.asp
-Original Message-From: MQSeries List
[mailto:[EMAIL PROTECTED]On Behalf Of
[EMAIL PROTECTED]Sent: 07 January 2004 13:00To:
[EMAIL
I will be out of the office starting January 7, 2004 and will not return
until January 19, 2004.
I'm on vacation and business trip. I'm reading mail on request only. In
case of urgency, please call me on my mobile: +386 40 456 639. If you
cannot reach me, please leave a voice mail.
Instructions
I will be out of the office from 01/07/2004 until 01/08/2004.
I will respond to your message when I return.
For PRODUCTION emergencies ONLY please contact me at:
Cell: 347-563-1085
Pager: 917-218-8938 (Numeric)
Home: 201-251-3892
For questions OTHER than PRODUCTION emergencies
please
WL MDBs are pure JMS implementations of MDBs, and do not have IBM specific
capabilities, like WAS MDBs do. If a JMS object has an IBM specific property
(like FAIL_IF_QUIESCING), it will just be ignored by the WL MDB.
A WL MDB can check to see if its cached connection to the QM is still valid
Before acting on this e-mail or opening any attachment, you are advised to read the
disclaimer at the end of this mail.
Hi,
Could someone clarify what the set/setall/setid authority options do in relation
to queue manager and queue objects?
(I put a MCA User on a channel and I had to grant the
Other than an applications use of
the MQ API and the CKTI trigger, is the CPU usage and its costs for MQ charged
back totally to the CHIN and MSTR? In revisiting our chargeback procedure, we
want to be certain that were accurately passing the correct charges to
our users. Anyone out there
Pat,
set refers to the ability to set the attributes of an object. For
example, setting a queue to TRIGGER or NOTRIGGER.
setid refers to the ability to set the Identity Context data when placing
a message onto a queue. Ordinarily, the QMgr sets the Identity Context of a
message when the
Peter,
Do unsatisfied GETs really get logged? I thought the log was driven only by
message movement and rcdmqimg.
-- T.Rob
-Original Message-
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 07, 2004 12:03 PM
To: [EMAIL PROTECTED]
Subject: Re: Message
We use MQ on a variety of systems including Solaris, AIX, Windows, and ZOS.
What clears out the SYSTEM.ADMIN.CHANNEL.EVENT queue? We have not modified
the queue. Does a reboot of the server clear out the queue?
Thank You,
John Haraburda
TPS/ITS/Database Technologies Group
MQSeries
Hi, John. Generally, a recycle of the qmgr will clear this out. Or you can
clear them out yourself by reading them or using clear qlocal. A reboot
isn't necessary, although that does, by default, recycle the qmgr.
Rebecca Bullock
Computer Sciences Corporation
MFCoE/Newark CS Team
Educational
If you dont care about those messages, just PUT_INHIBIT that queue.
From the Event Monitoring Manual:
Enabling channel events
Most channel events are enabled automatically and you cannot enable or
disable
them by command. The exceptions are the two automatic channel definition
events. However,
You might also consider turning off channel events for these qmgrs if you're
not using them anyway. They might be useful for figuring out a problem.
However, if you don't use them you might find it better to get rid of them.
Nick
-Original Message-
From: MQSeries List [mailto:[EMAIL
I've been off the MQ board for six months.. Has implementing SSL gotten
any easier with MQ 5.3.5 ?
From an MQ perspective, it is the same as when it first came out with 5.3.
-Original Message-
From: Heggie, Peter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 05, 2004 12:30 PM
To:
Nick, you cannot explicitly turn off Channel Events, but you can block their
creation by deleting ot inhibiting their event queue (same result I
guess..potaaatoe / potatoe)
Speaking of Channel Events, I think they are pretty useless as is. Who cares
when a channel goes to STOP? That only
Thanks.. I see there is a redbook on Implementing MQ security from May
2003.. Is that the latest publication on MQ and SSL?
Peter Heggie
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of
Potkay, Peter M (PLC, IT)
Sent: Wednesday, January 07, 2004 2:55 PM
To:
the redbook is here:
http://publib-b.boulder.ibm.com/Redbooks.nsf/9445fa5b416f6e32852569ae006bb65f/3effa2807d4b649e85256b750055b5f7?OpenDocument
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 01/07/2004 03:40 PM -
Heggie,
Peter,
The MQSeries Programmable System Management manual shows the reason
qualifiers for a Stopped Channel:
ReasonQualifier (MQCFIN) Identifier that qualifies the reason code
(parameter identifier: MQIACF_REASON_QUALIFIER).
The value is one of the following:
MQRQ_CHANNEL_STOPPED_OK Channel
Peter,
When referring to the WMQ manuals, be sure that you visit
http://www-306.ibm.com/software/integration/mqfamily/support/readme/cli530_r
ead_2.html for the manual updates as there is a lot of corrected information
regarding SSL.
Regards,
John Dawson
Phone: 972.281.4016
Fax:
Thanks.. That's the one
Peter Heggie
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of
earMERC Roberts
Sent: Wednesday, January 07, 2004 3:40 PM
To: [EMAIL PROTECTED]
Subject: Re: Puzzled: MQJE001, MQRC 2102 for non-mqm users
the redbook is here:
That's a very valuable reference! thanks
Peter Heggie
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of
Dawson, John
Sent: Wednesday, January 07, 2004 3:52 PM
To: [EMAIL PROTECTED]
Subject: Re: Puzzled: MQJE001, MQRC 2102 for non-mqm users
Peter,
When
Thanks Rick. I missed that retry sub-reason under the main channel stopped
event.
I was reading the Event Monitoring manual, and saw the following. I assumed
stops meant STOPPED!
Channel events are reported by channels as a result of conditions detected
during
their operation, such as when a
Title: RE: Puzzled: MQJE001, MQRC 2102 for non-mqm users
I found the following in the text for CSD 5 for V5.3 on AIX. It MIGHT help explain
why you got a 2102 and not an access error:
IY43097 - Occasionally a failure with return code 2102
(MQRC_RESOURCE_PROBLEM) occurred when trying to
27 matches
Mail list logo
