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 connect
aplications to WebSphere MQ V5.3. When a large number
of applications attempted to perform a get operation
with large buffer sizes, the shared memory set was
extended, but with incorrect permissions. This meant
that applications run under a user id which did not
have mqm as its primary group could not connect to this
extent, getting EACCESS from shmat. This was returned
as a resource problem.
-----Original Message-----
From: Dawson, John [mailto:[EMAIL PROTECTED]]
Sent: 07 January 2004 10:52
To: [EMAIL PROTECTED]
Subject: Re: Puzzled: MQJE001, MQRC 2102 for non-mqm users
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 : 972.281.4904
mailto:[EMAIL PROTECTED]
-----Original Message-----
From: Heggie, Peter [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 07, 2004 2:32 PM
To: [EMAIL PROTECTED]
Subject: Re: Puzzled: MQJE001, MQRC 2102 for non-mqm users
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: [EMAIL PROTECTED]
Subject: Re: Puzzled: MQJE001, MQRC 2102 for non-mqm users
"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: [EMAIL PROTECTED]
Subject: Re: Puzzled: MQJE001, MQRC 2102 for non-mqm users
That's right.. I have heard this before. I could use the incoming userid
and incoming machine name and perform a lookup in a table and get an
assigned userid that has the correct priviledges. And that's about
halfway to the better solution of SSL and certificates. Our organization
has not implemented application level SSL and certificates so a
homegrown solution may be our only current option.
I've been off the MQ board for six months.. Has implementing SSL gotten
any easier with MQ 5.3.5 ?
Peter Heggie
-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED]] On Behalf Of
Potkay, Peter M (PLC, IT)
Sent: Monday, January 05, 2004 12:12 PM
To: [EMAIL PROTECTED]
Subject: Re: Puzzled: MQJE001, MQRC 2102 for non-mqm users
But the real user could be some loser that defines the ID "mqm" on their
machine, logs on with that ID, and then your QM has no choice but to let
him do whatever they want!
-----Original Message-----
From: Heggie, Peter [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 05, 2004 12:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Puzzled: MQJE001, MQRC 2102 for non-mqm users
I'm sorry - I took the documentation to mean that for non-Java clients,
on Windows and UNIX, the userid in the MQCD is the currently logged on
user and that the environment variables are not referencved. So if I
could verify that it was not a Java client, then I could rely on the
userid to be the real user.
Peter Heggie
This e-mail and any files transmitted with it, are confidential to
National Grid and are intended solely for the use of the individual or
entity to whom they are addressed. If you have received this e-mail in
error, please reply to this message and let the sender know.
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, 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
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
Emails
cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability
or responsibility for any interception, corruption, destruction, loss, late
arrival or incompleteness of or tampering or interference with any of the
information contained in this email or for its incorrect delivery or
non-delivery for whatsoever reason or for its effect on any electronic device of
the recipient.
If verification of this email or any attachment is required, please request a hard-copy version.