> -----Original Message-----
> From: Williams, Tim P {PBSG} [mailto:Tim.Williams AT PBSG DOT COM]
> Sent: Friday, March 01, 2002 2:41 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Server-side scripting: not supported?
>
> OK, a little deeper...
> we have 5 groups of stg areas, basically...
> Since TSM doesn't give you a good way to "control" (wait=yes
> is good with move data, but there's
> nothing for, say, migration) the movement from disk to tape
> we HAVE to use move data commands...

> We have over 100 disk vols.
> We simultaneously run move datas.
> If one area completes then, it goes onto the ba stg.
> ALL move datas and ba stgs have to complete (5 general areas) prior to the
db backup, etc....
> A good scheduler, will get this done with ease.
> Scripting...that would be complex.

That "good" scheduler would have to query the TSM server to get state
variables to be "non-fragile".  For example, before issuing "move data"
commands, you would want to know there were sufficient tape drives available
(maybe issuing dismounts against mounted-but-idle volumes.) Also, to be
dynamic, it would have to query TSM to get a list of volumes for each disk
storage pool as candidates.  And maybe parse the Description field from the
stgpool to get the copypool name for the Backup Stgpool command.

So why not script away, anyway?