Re: anyboby writes to one tape(solved?)
Hello together, I post node this to prevent others from loosing one day. Collocation is on and I have got enough scratch tapes in my library but I forgot the 'Maximum Scratch Volumes allowed' value. So the storagepool runs out of space. joachim schwabe Richard Sims [EMAIL PROTECTED] on 01.03.2001 13:35:55 Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Schwabe Gorbit/GE-Europe/3M/US) Subject: Re: anyboby writes to one tape does anyboby has an idea how to handle the situation that 2 migation processes and 4 client sessions want to write to only one tape? Collocation? Your posting did not say whether you are employing it. If you don't use collocation, TSM will do its darndest to maximize tape usage, and so you can end up with sessions and processes waiting their turn to write to the current Filling tape. Richard Sims, BU
anyboby writes to one tape
hallo together, does anyboby has an idea how to handle the situation that 2 migation processes and 4 client sessions want to write to only one tape? the tabe is mounted the tape isn't full access is readwrite and now - there is no real write action on this tape! setting the tape unavailable or readonly has no effect, accept the migations disappear. thanks for any help joachim
Re: anyboby writes to one tape
does anyboby has an idea how to handle the situation that 2 migation processes and 4 client sessions want to write to only one tape? Collocation? Your posting did not say whether you are employing it. If you don't use collocation, TSM will do its darndest to maximize tape usage, and so you can end up with sessions and processes waiting their turn to write to the current Filling tape. Richard Sims, BU
