Re: Permission Oddity
All applications will need to be able to read mqs.ini.
It contains information for each queue manager (Name, Prefix and
Directory) which is required in order to be able to find the queue manager
at all. While nearly all of us put our queue managers in the standard place
(/var/mqm/qmgrs/QMGRNAME etc) this is not required by MQSeries. The queue
managers can actually be put anywhere in your file system by changing the
mqs.ini entry for the queue manager.
Personally, when I want to move a queue manager's files onto another
location, I leave mqs.ini alone, and create symlinks to the actual location
in /var/mqm/qmgrs and /var/mqm/log. This means that I don't have to look up
mqs.ini to find out where a queue manager's files are located. I 'know'
they are always in /var/mqm/qmgrs, even if all that gives me is the symlink
to the actual location.
Note: some earlier versions of MQ had problems with symlinks in some of the
queue manager paths, but this all seems to have ben resolved in the current
release.
Regards,
Neil C.
|-+>
| | Jeff A Tressler |
| | <[EMAIL PROTECTED]|
| | >|
| | Sent by: MQSeries|
| | List |
| | <[EMAIL PROTECTED]|
| | n.AC.AT> |
| ||
| ||
| | 12/09/2003 06:05 |
| | Please respond to|
| | MQSeries List|
| ||
|-+>
>--|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: Permission Oddity
|
>--|
>Are these apps connecting using the default queue
>manager? If so, I'll bet that mqs.ini is used to
>find that queue manager's name.
>
The applications are not using a default queue manager.
I intentionally do not create a default queue manager
just to avoid some of the problems this could create.
If I were to speculate, I would believe you have the
correct idea. It is possible that when an application
attempts to connect to a queue manager, it uses the
mqs.ini file to verify the queue manager name is
valid. If the application does not have read
permissions then it fails with 2085. This is the only
way I can explain the behaviour.
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
Re: Permission Oddity
>Are these apps connecting using the default queue >manager? If so, I'll bet that mqs.ini is used to >find that queue manager's name. > The applications are not using a default queue manager. I intentionally do not create a default queue manager just to avoid some of the problems this could create. If I were to speculate, I would believe you have the correct idea. It is possible that when an application attempts to connect to a queue manager, it uses the mqs.ini file to verify the queue manager name is valid. If the application does not have read permissions then it fails with 2085. This is the only way I can explain the behaviour. 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
Re: Permission Oddity
Are these apps connecting using the default queue manager? If so, I'll bet that mqs.ini is used to find that queue manager's name. Jeff A Tressler <[EMAIL PROTECTED]To: [EMAIL PROTECTED] >cc: Sent by: MQSeries Subject: Permission Oddity List <[EMAIL PROTECTED] N.AC.AT> 09/11/2003 02:32 PM Please respond to MQSeries List On our HP-UX system, we changed the permissions on mqs.ini from 775 to 660. Applications began failing and could not connect to the queue manager. They were getting a 2058 - Queue Manager Name Error. We verified the applications were using the correct name and that the queue manager was running. We could not get the applications to connect without changing the permissions. The most restrictive we were able to get the permissions was 664. 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
Permission Oddity
On our HP-UX system, we changed the permissions on mqs.ini from 775 to 660. Applications began failing and could not connect to the queue manager. They were getting a 2058 - Queue Manager Name Error. We verified the applications were using the correct name and that the queue manager was running. We could not get the applications to connect without changing the permissions. The most restrictive we were able to get the permissions was 664. 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
