| Author |
Message
|
| kvranjan |
 Posted: Tue Sep 26, 2006 5:59 am Post subject: refresh security |
 |
|
Apprentice
Joined: 12 Jul 2006
Posts: 28
|
| when a queuemanager is added to a cluster on solaris where do we need to issue the refresh command , on the added queumanager or repository qmgr |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Sep 26, 2006 6:12 am Post subject: |
|
|
Guest
|
When you add a queue manager to a cluster, cluster software automatically shares whatever cluster definitions are necessary. If the new queue manager is a full repos, all clustered objects will be shared. If the new queue manager is a partial (not full) repos, only info about the full repos will be shared.
You do not need to use the refresh command to add a queue manager to a cluster. |
|
| Back to top |
|
|
| kvranjan |
| Posted: Tue Sep 26, 2006 6:16 am Post subject: |
|
|
Apprentice
Joined: 12 Jul 2006
Posts: 28
|
hey ,
im sorry for not being clear, since i mentioned in the topic i ommitted it out here
im not speaking about refresh cluster, iam speaking about refresh security
awaiting your reply |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 26, 2006 6:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
As bruce2359 says you shouldn't need to refresh either the cluster or the security if you're adding a new queue manager. It will pick up the existing security arrangements as a matter of course.
You should only need to refresh security if you've changed permissions or group memberships. Do a search - the exact circumstances where it's needed has been discussed in here before.
Happy Reading! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 26, 2006 6:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
And (getting back to your original question) if you do need to do it, I'd do it on one of the full repository managers.
Conflicting views may also be valid and are welcomed. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kvranjan |
| Posted: Tue Sep 26, 2006 6:32 am Post subject: |
|
|
Apprentice
Joined: 12 Jul 2006
Posts: 28
|
thanx vitor and all,
for ur valuable feedback. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Tue Sep 26, 2006 9:51 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| Vitor wrote: |
And (getting back to your original question) if you do need to do it, I'd do it on one of the full repository managers.
Conflicting views may also be valid and are welcomed. |
The command REFRESH CLUSTER drops all local stored cluster informations and sends its own (locally defined) cluster definitions again. When you do this on a full repository, then the second full repository will send the information of the cluster again to the first one but if you have only one full repository (what you should not have at any time), then you have to perform a REFRESH CLUSTER on all partial repositories too!
Where you have to perform the command REFRESH CLUSTER depends on the situation. Mostly you need not at all run this command, but when it was necessary in the past I had to run it mostly on partial repositories.
The command REFRESH SECURITY is only neccessary, when you alter the member ship of users (on distributed systems, on z/OS are some more reasons)
_________________
Regards
Hubert |
|
| Back to top |
|
|
| kvranjan |
| Posted: Thu Sep 28, 2006 3:16 am Post subject: |
|
|
Apprentice
Joined: 12 Jul 2006
Posts: 28
|
thanx hubert ,
that was useful info for me. |
|
| Back to top |
|
|
|
|
