Mark -

We are also using the MVS Server.  To answer your questions -

1.  We are currently using just 1 disk pool before we migrate to tape.  We do
not limit by file size - all goes to disk, and then to tape.

2.  We do not keep tapes by retention - they are marked in CA-1 as managed by
ADSM, and we let ADSM reclaim the tape when the amount of still active data
falls below 40%.  Once data has been migrated off, the tape is returned to the
scratch pool.  I would suggest using this type of management, since puting a
retention on the files would have the effect of requirng extra backups, and
also many more tapes used than actually needed.

3.  I think that the thresholds on the migration from DASD to Tape are
dependent on the size of your DASD pool, and the activity it supports.  For
example, if you have a small pool, and it is very active, 95% may indeed be
too high.  On the otherhand, if you have a very large pool (10 GB for
example), 5% of the pool would be 500MB.  If you have thresholds set at 50%
and 95%, the question that maybe should be asked is "Can I migrate 4.5GB off
before the customers can write 500MB and fill the pool??"

BTW, we have our thresholds set at 50% and 90%.

Jerry Lawson


________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Some questions about pools.
01-12-96 04:01 PM

Hello,

We are running the ADSM server on MVS/ESA.

1) How many disk pools do you use before moving the data to tape?

2) How long do you keep the tape for (5 years)?

3) What threshold have you set on the server before it starts moving
   data from one pool to the next. I would think 95% full is too high?

That's all for now,

Mark Brown
Operations Supervisor