Can someone give suggestions on how to control the maximum number of concurrent mounts based on stgp or node or some other parameter. I want to stop one client from being able to 'hog' all of the dri
Author: Nick Cassimatis <nickpc AT US.IBM DOT COM>
Date: Wed, 12 Jan 2000 13:25:01 -0500
The only way I can think to do that would be to have a different deviceclass name for each pool. Then you can set the number of mount points through that. This is not a new device type (drive), so th
Author: "Joshua S. Bassi" <jbassi AT GLORYWORKS DOT COM>
Date: Wed, 12 Jan 2000 10:41:03 -0800
There was a new paramemeter introduced with the TSM 3.7 server. The parm is "maxnummp" and is defined on a per node basis. So if you are on this verion of *SM, you can update your nodes with a maximu
Author: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Date: Sun, 04 Oct 2015 17:35:05 -0500
Can someone give suggestions on how to control the maximum number of concurrent mounts based on stgp or node or some other parameter. I want to stop one client from being able to 'hog' all of the dri
Yes, this is the only thing I could think of as well. Could you rephrase/expand the last sentence above? How would the drives "share between the pools"? I thought that under this scenario the drives
Author: Nick Cassimatis <nickpc AT US.IBM DOT COM>
Date: Thu, 13 Jan 2000 09:47:48 -0500
What I mean is that a specific drive will not be assigned to a specific pool. The assignment doesn't have to go below the level of the deviceclass. Nick Cassimatis nickpc AT us.ibm DOT com If you do