Actually I could have been clearer in my message.  I have two OS/390
Servers, one production server running ADSM 3.1 and one test Server running
TSM 4.1.  I took one of my NT clients that was linked to the ADSM server and
pointed it to the TSM server for testing, removed the Central Scheduler
Service, installed the new one for TSM 4.1, test and verified and then
removed the new Scheduler without any troubles.  The backups and restore
testing I did was to a completely separate set of TSM databases apart from
where I want to get this NT client back to.  While trying to get the client
back to the point it was at prior to my testing, while loading the Sched
Service, I get the error described below.

  Sorry for the confusion.  Thanks for the response none-the-less...


Stan Weyman     
System Administration Specialist II

Amica Insurance
25 Amica Way, Lincoln, Rhode Island 02865-1167
Telephone:      (401) 334-6000 x2679
Fax:    (401) 334-1634
Web Site:     www.amica.com
Email:      sweyman AT amica DOT com