| Author |
Message
|
| aballuff |
 Posted: Wed Nov 27, 2002 9:22 am Post subject: setmqaut Question? |
 |
|
Newbie
Joined: 21 Oct 2002
Posts: 6
|
ALL,
I'm trying to run a setmqaut command and getting this error:
setmqaut -m tst.qmgr -t qmgr -p batchcatmquser +connect
AMQ7026: A principal or group name was invalid.
The userid is a valid unix id. and the setmqaut works with other userids.
Is there a limitation on the length of a userid in OAM?
Thanks much
A |
|
| Back to top |
|
 |
| Bill57 |
| Posted: Wed Nov 27, 2002 11:09 am Post subject: |
|
|
Apprentice
Joined: 26 Jul 2002
Posts: 35
Location: Atlanta, GA
|
AMQ7026 Specificlly means the principal name does not exist at the operating system level. Doubble (or tripple) check to make sure the Id exits in UNIX, and make sure you spelled it correctly on the command line (or script if thats what your doing)
Good luck
_________________
Bill Anderson
MQSeries Developer |
|
| Back to top |
|
|
| bduncan |
| Posted: Wed Nov 27, 2002 2:35 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
It may seem redundant, but try
'su - batchcatmquser' to make sure the user truly exists.
If so, then perhaps you've created the user since you last recycled the queue manager? I believe this shouldn't be necessary, but perhaps there is some problem and the queue manager is unaware of the existence of this particular user because it was created recently. You might want to try stoping and then restarting the queue manager to see if the problem goes away...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| nimconsult |
| Posted: Wed Nov 27, 2002 11:02 pm Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
If I remember well, the userid is limited to 12 characters on non-Windows platforms.
I am not quite sure that the limit applies to setmqaut (but apparently it does). At least I am sure that the limit applies to MQSC commands.
Nicolas
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
| Bill57 |
| Posted: Thu Nov 28, 2002 5:55 am Post subject: |
|
|
Apprentice
Joined: 26 Jul 2002
Posts: 35
Location: Atlanta, GA
|
Nicolas has a good point; the UserIdentifier field in the MQMD header is a data type of MQCHAR12. When an application connects The user Id of the connecting application is used by the OAM to determine if the application is authorized to connect, and then it saves the id in the header for checking more authority type stuff during the up coming MQOPEN. Any value greater than 12 characters would have been truncated, and would no longer be valid at the OS level.
For that reason, I would bet the setmqaut utility checks the length of the principal.
Cheers, and happy turkey day!
_________________
Bill Anderson
MQSeries Developer |
|
| Back to top |
|
|
| aballuff |
| Posted: Fri Nov 29, 2002 7:33 am Post subject: |
|
|
Newbie
Joined: 21 Oct 2002
Posts: 6
|
HI ALL,
I've triple checked the id (by su - to the id ) , re-started the qmgr and still no go. I think I'm going to just shorten the id and see what happens.
Happy Shopping day:-)
AJB
| Bill57 wrote: |
Nicolas has a good point; the UserIdentifier field in the MQMD header is a data type of MQCHAR12. When an application connects The user Id of the connecting application is used by the OAM to determine if the application is authorized to connect, and then it saves the id in the header for checking more authority type stuff during the up coming MQOPEN. Any value greater than 12 characters would have been truncated, and would no longer be valid at the OS level.
For that reason, I would bet the setmqaut utility checks the length of the principal.
Cheers, and happy turkey day! |
 |
|
| Back to top |
|
|
|
|
