ADSM-L

Re: scratch-volumes for tape-stgpool

2002-08-24 16:26:06
Subject: Re: scratch-volumes for tape-stgpool
From: "Mark D. Rodriguez" <mark AT MDRCONSULT DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sat, 24 Aug 2002 15:27:54 -0500
Sascha Braeuning wrote:

Hi,

I found something curious on my system (OS/390, TSM 4.2.2.2): The amount of
actual scratch volumes in a storagepool named UCART3490 is 245. The amount
of maximum scratch volumes allowed for this pool is 300. But this night the
server ran out of storagepool-space because UCART3490 seems to be full
because TSM takes no new scratch-volume (scratch volumes where available in
the tape-roboter). When I raised the number of maximum scratch volumes
allowed to 325 the server took new scratch volumes and goes on.

Any idea, what happened there?

MfG
Sascha Bräuning


Sparkassen Informatik, Fellbach

OrgEinheit: 6322
Wilhelm-Pfitzer Str. 1
70736 Fellbach

Telefon:   (0711) 5722-2144
Telefax:   (0711) 5722-1630

Mailadr.:  sascha.braeuning AT sparkassen-informatik DOT de
Hi,

The "MAXSCRatch" value actually sets the number of scratch volumes that can be used (meaning private to the storage pool and holding data) by the storage pool at any given time. It seems a little confusing, but the translation is it is the number of private volumes in the storage pool that came from scratch tapes. If you do not manually add any volumes to a storage pool and therefore you are using only scratch volumes for your inventory than the MAXSCRatch value will specify the total number of volumes that are allowed in the storage pool at any given time.

And just to give you a little more info, if a tape originally was scratch and was then automatically assigned to a storage pool when that tape is reclaimed (i.e. all data removed from it) it will go into "pending" state. After the "REUsedelay" value has been satisfied it will again return to being a scratch tape. In contrast, if a volume was added to a storage pool manually thru a "def vol" command then after reclamation and "REUsedelay" are completed the tape will become an "empty" private tape within that storage pool. And now to complete the cycle, when a storage pool needs additional space and requires a new volume (i.e. no more volumes in filling or some other reasons), it will first use tape that are in the storage pool and in the "empty" state. If there are no "empty" tapes it will then attempt to get a scratch tape if it is not currently exceeding its "MAXSCRatch" limit.

I hope that helps you understand the various attributes.

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.

===============================================================================
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE
===============================================================================

<Prev in Thread] Current Thread [Next in Thread>