Can you provide a little more information about the problem? For example,
what makes you say that the migration started as a result of the Admin
schedule? Does the activity log actually show the schedule being run? What
does the definition of this schedule look like (output from Q SCH F=D for
this schedule)? I would think it more likely that backups just filled the
storage pool past the high migration theshold, so migration started on its
own.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Tommy Templeton <tommy.templeton AT MMRS.STATE.MS DOT US>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/10/2003 11:23
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Admin schedules



Environment:
  Server: RS/6000-AIX5.1     TSM V4.2.1.9
  Client:  NT4-Service pack 6,
            Win2k-SP1,             TSM V4.2.1.9
            Novell - Netware 6  TSM V5.1.5.0
            SP2-AIX5.1              TSM V4.2.1.9


Hi *SM'ers ,

I have an admin schedule setup that does my disk migration to primary tape
at 8:15am every day.
I had a weird problem with that schedule starting up at 2:35am in the
middle of backups. Has anyone else had unexpected results with the TSM
admin schedules before? It usually runs fine,

Thanks,


Tommy Templeton