Dianne,
        Before Version 2, I used to do this via batch.  You can do this one of
2 ways.

1) Issue the following command via batch
        F ADSM,UPD STGPOOL TAPE RECLAIM=nn
        F ADSM,UPD DEVCLASS CART3480 MOUNTL=n MOUNTR=n

2) Thru the ADSM TSO Admin client - this is documented in the ADSM
manuals

For migration processing, you're limited as to how much you can control
this, especially if your disk storage pool is less than 1/5th the size
of the data you'll be backing up daily.  However, you can raise and
lower the migration thresholds via batch  (i.e. UPD STGPOOL BACKUPPOOL
HIGHMIG=90 LOWMIG=10). It's nice if you can afford to have your disk
storagepool large enough to hold one night's worth of backups; this way
you have total control over when migration processing runs.

As far as reclamation processing, I'd recommend keeping the threshold
set to 100% at all times and lower it only when you want it to run.


Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  Dianne Sharp[SMTP:DSHARP AT CLEAR.CO DOT NZ]
>Sent:  Wednesday, September 18, 1996 5:07 PM
>To:    Multiple recipients of list ADSM-L
>Subject:       Re: Cartridge Drive Utilisation
>
>I had one response about this, but it wasn't a positive one.  What I
>guess I'm asking for is if we can change parameters (e.g. Reclamation
>Threshold, Mount Limit on DEV CLASS) via a batch job on MVS?
> ----------
>From: Dianne Sharp
>To: ADSM User Group
>Subject: Cartridge Drive Utilisation
>Date: Friday, 06 September, 1996 5:36PM
>
>We are about to implement ADSM V1 Server for MVS into our Production
>environment and I have a few questions about Cartridge Drive
>Utilisation.
>
>I know you can specify a mount limit for the storage pool.  Currently we
>have this set to 2 because we will be performing reclamation.
>
>1.  We have one backup disk pool, but it is not very large (only 2-4GB).
> We will be backing up over 20GB nightly.  Therefore, we will be
>migrating data to cartridge quite often during the night.  We only have
>6 cartridge drives and they are used regularly during the night for
>Mainframe backups and other Production processing.  Is there any way of
>controlling when migration can and can't take place based on time, or
>are there commands that we can issue, preferably through an automated
>batch job or something, that can disable and enable migration at certain
>points of the night?
>
>2.  Reclamation is another concern.  If we have reclamation turned on,
>can we control when it happens?  I'm worried that if it kicks in and
>then a migration process is scheduled, that it might hold up backups
>that are currently running.
>Would it be better to set the threshold to 100% and just change it when
>you want this to run?   This is a bit messy because you'd have to
>remember to change it back again - unless this is also something that
>can be automated somehow.
>
>I have read something about Admin commands being able to be scheduled
>with Version 2.   We will be getting version 2 in a few month's, but the
>initial implementation will be Version 1 - I won't go into the reasons
>for that.
>
>Any help would be much appreciated.
>