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: [EMAIL PROTECTED]
-----Original Message-----
From: Bernhard Unold [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 22, 2001 6:34 AM
To: [EMAIL PROTECTED]
Subject: Re: DSMCUTIL
Its not possible to go back to an older client version. Once you have
made a backup with the new client version, formats in the server for
client data are changed, and cannot retrieved with the older version.
See Tsm documentation.
"WEYMAN, STANLEY J" schrieb:
>
> In testing a new version of the TSM 4.1 client I removed the ADSM
Central
> Scheduler Service from an NT machine and installed the new version. When
> testing was complete I removed the TSM Service and then attempted to
> reinstall the old Service. When I attempt to run the DSMCUTIL to install
> the service I get an error. The command I am executing is as follows:
>
> This is done from within the baclient directory for ADSM v3.1
> DSMCUTIL INSTALL /NAME:'ADSM Central Scheduler Service' /NODE:ECOMMDEV02
> /PASSWORD:ECOMMDEV02 /AUTOSTART:YES
/CLIENTDIR:d:\progra~1\ibm\adsm\baclient
>
> What I get in return is
>
> "The ADSM Message Repository is corrupt"
> "Password Authentification Failed"
> "The Registry Password was not updated"
>
> I then tried
>
> DSMCUTIL UPDATEPW /NODE:ECOMMDEV02 /PASSWORD:GARBAGE5 /VALIDATE:YES
> /UPDATEONSERVER:YES /OLDPASSWORD:ECOMMDEV02
>
> I received pretty much the same error. This is preventing me from
> reinstalling scheduling services for this node to allow automated backups
to
> run in the middle of the night. Does anyone have any idea of how I can
fix
> this ?
>
> thanks ahead of time for your help and patience
>
> Stan
>
> 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: [EMAIL PROTECTED]
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the sender and [EMAIL PROTECTED]
> **********************************************************************
--
Mit freundlichen Grüßen
Bernhard Unold
