| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| windows limitation when using the mqseries api? |
« View previous topic :: View next topic » |
| Author |
Message
|
| paul0al |
 Posted: Fri Jun 07, 2002 7:58 am Post subject: windows limitation when using the mqseries api? |
 |
|
Apprentice
Joined: 30 May 2002
Posts: 26
|
| We have a program that uses mqconn to connect to a mqseries server. I notice that when I am logged in Windows 2000 with a user name greater than 12 characters (ie administrator), the program fails to connect to the server. If I log into the same machine with a user name less than 12 characters (ie john), the program connects to the server and I can put messages into a queue. The server and client is running Windows 2000 server and the program connects using mqconn. Is there limitations on the mqseries api when operating in a windows 2000 environment? |
|
| Back to top |
|
 |
| dgolding |
| Posted: Sun Jun 09, 2002 11:31 pm Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
Hi,
I think you'll find that there is a 12-character limit on User IDs on NT - so "administrator" is too long. Certainly you can't install MQ iwth a user ID longer than 12 chars. It's a bit basic, a bit like only using two digits for the year 
HTH |
|
| Back to top |
|
|
| StefanSievert |
| Posted: Mon Jun 10, 2002 9:16 am Post subject: Re: windows limitation when using the mqseries api? |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
| paul0al wrote: |
| We have a program that uses mqconn to connect to a mqseries server. I notice that when I am logged in Windows 2000 with a user name greater than 12 characters (ie administrator), the program fails to connect to the server. If I log into the same machine with a user name less than 12 characters (ie john), the program connects to the server and I can put messages into a queue. The server and client is running Windows 2000 server and the program connects using mqconn. Is there limitations on the mqseries api when operating in a windows 2000 environment? |
Paul,
yes, the userId is limited by design to max. 12 characters on the distributed platforms. If you take a look at the declaration of the MQMD structure (message descriptor), you will see
MQCHAR12 UserIdentifier; /* User identifier */
However, in a pure Windows NT environment (and I would suspect W2K as well) you actually can use userId's that are longer than 12 chars. The following is taken from Chapter 44 of the MQ Planning Guide:
| Quote: |
| The maximum length of user ID that is used in these ways by all MQSeries
| products is 12 characters.
| On Windows NT, the user name can be longer than 12 characters. For example,
| the default user name for administration on Windows NT is Administrator.
| MQSeries for Windows NT Version 5.1 supports user names that are longer than
| 12 characters, while at the same time maintaining compatibility with other products
| in the MQSeries family. The Windows NT security identifier (SID) is used to
| supplement the 12-character user ID. The SID contains information that identifies
| the full user account details on the Windows NT security account manager (SAM)
| database where the user is defined.
| When a message is created on MQSeries for Windows NT, MQSeries stores the
| SID in the message descriptor. When MQSeries for Windows NT performs
| authorization checks, it uses the SID to query the full information from the SAM
| database.
| Note: The SAM database in which the user is defined must be accessible for this
| query to succeed.
| The Windows NT SID allows MQSeries to distinguish between two user names that
| are the same. For example, the user name JohnSmith can be defined on different
| Windows NT SAMs. A new option on the Windows NT authorization service
| controls whether the authority checks require both a user ID and a valid
| Windows NT SID to be available before granting access to MQSeries objects. For
| example, when this option is set, administration messages to the
| SYSTEM.ADMIN.COMMAND.QUEUE from other systems must supply a SID that is
| valid on the local system and that resolves to the user ID in the message context. |
Hope this helps,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
