Am Mo, den 26.04.2004 schrieb David Awerbuch um 23:44:
> An update.
>
> I disabled the OAM as Ken suggested, and that has solved the problem, so I now
> know it is security related.
>
> So this still begs the question: how on VMS do I find out what the security
> violation is?
> >
> > Gunther Jesc
: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David
Awerbuch
Sent: Monday, April 26, 2004 15:45
To: [EMAIL PROTECTED]
Subject: Fwd: Re: can not connect to queue manager
An update.
I disabled the OAM as Ken suggested, and that has solved the problem, so I
now
know it is security related.
So this
n, 26 Apr 2004 07:56:43 -0700 (PDT)
> From: David Awerbuch <[EMAIL PROTECTED]>
> Subject: Re: can not connect to queue manager
> To: Mqseries Messages <[EMAIL PROTECTED]>
>
> Roger Lacroix wrote:
> > Did you issue the 'refresh security' from runmqsc (or
Roger Lacroix wrote:
> Did you issue the 'refresh security' from runmqsc (or whatever it is called
for OpenVMS).
> Note: For earlier releases of MQ for Unix, you had to bounce to queue manager
> to pick up new security setting. (Strange but true.)
Roger, there were no security setting changes ma
On UNIX systems, you have to be a member of the group mqm to start
runmqsc.
You don't need any other authority.
Maybe it's the same on OpenVMS.
Regards,
Gunter
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.
You could try and disable the OAM and see if there are other
authorization issues like file/directory permissions. There's
only one problem - on VMS you define a logical PRIOR to creating
the queue manager which disables the OAM for the life of the queue
manager. This may be beneficial if you can
Hi David,
Did you issue the 'refresh security' from runmqsc (or whatever it is called for
OpenVMS).
Note: For earlier releases of MQ for Unix, you had to bounce to queue manager to
pick up new security setting. (Strange but true.)
Regards,
Roger Lacroix
Capitalware Inc.
http://www.capitalware.b
