Hmmmmmm..... do you have more than one TSM server? I notice that the first
connection shows these details:

Session established with server ADSM: MVS
  Server Version 4, Release 1, Level 4.0
  Data compression forced on by the server
  Server date/time: 09/05/01   11:17:26  Last access: 09/05/01   11:07:46

And the second connection shows these details:

Session established with server ADSME: MVS
  Server Version 4, Release 1, Level 4.0
  Data compression forced on by the server
  Server date/time: 09/05/01   11:20:30  Last access: 09/05/01   11:03:00

1) The "Session established with server messages" show two different
server names: ADSM and ADSME.

2) The first attempt shows the server time is 11:17:26 with a last access
time of 11:07:46. On the second attempt, I would expect the last access
time to be at *least* 11:17:26. Yet it is 11:03:00, which is actually
*prior  to* the first attempt.

You might compare the SERVERNAME stanzas on both systems sets of TSM
client options files. Both are named ADSM, but I suspect they are pointing
to two different servers. This would most likely explain the behavior you
are seeing.

Regards,

Andy

Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

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




"Hunley, Ike" <Ike.Hunley AT BCBSFL DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/06/2001 13:10
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        FW: Inability to restore ADSM data using TSM client




Has anyone out there dealt with this?

>  -----Original Message-----
> From:         Weber, Doug
> Sent: Thursday, September 06, 2001 3:17 PM
> To:   Peppers, Holly; Hunley, Ike
> Cc:   Breckenridge, Scott; Kozak, Judy; Willis, Tom
> Subject:      Inability to restore ADSM data using TSM client
>
> The attached document shows that files archived using ADSM client
version
> 3.1.0.6 cannot be restored using TSM client version 4.1.2.14.  If no
> resolution is found for this problem, this means that after the upgrades
> to TSM are complete,  none of our data archived prior to August 2001
will
> be retrievable.  Please show me the error in my logic;  I really can't
> believe that what I am seeing is true.
>
Session run on ediprodp1:

edi01@ediprodp1[VOP]: dsmc macro macro -machinename=homer -servername=adsm
-password=<pw>
Tivoli Storage Manager
Tivoli Storage Manager
*** Fixtest, Please see README file for more information ***
Command Line Backup Client Interface - Version 4, Release 1, Level 2.14
(C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved.

retrieve -filesonly -replace=yes
/gw/R20/prod/EDI/gw/data/mb/6/650912411/archive/HIST.NSR.0A16IM.000067
Node Name: HOMER
Session established with server ADSM: MVS
  Server Version 4, Release 1, Level 4.0
  Data compression forced on by the server
  Server date/time: 09/05/01   11:17:26  Last access: 09/05/01   11:07:46

Retrieve function invoked.

ANS1092E No files matching search criteria were found

Session run on ediprodc1:

edi01@ediprodc1[VOP]: dsmc macro macro -machinename=homer

ADSTAR Distributed Storage Manager
Command Line Backup Client Interface - Version 3, Release 1, Level 0.6
(C) Copyright IBM Corporation, 1990, 1998, All Rights Reserved.

retrieve -filesonly -replace=yes -servername=adsm
/gw/R20/prod/EDI/gw/data/mb/6/650912411/archive/HIST.NSR.0A16IM.000067
Retrieve function invoked.

Node Name: HOMER
Session established with server ADSME: MVS
  Server Version 4, Release 1, Level 4.0
  Data compression forced on by the server
  Server date/time: 09/05/01   11:20:30  Last access: 09/05/01   11:03:00

 ** Interrupted **
ANS1114I Waiting for mount of offline media.
Retrieving          17,505
/gw/R20/prod/EDI/gw/data/mb/6/650912411/archive/HIST.NSR.0A16IM.000067
[Done]

Retrieve processing finished.

Total number of objects retrieved:        1
Total number of objects failed:           0
Total number of bytes transferred:     6.25 KB
Data transfer time:                    0.00 sec
Network data transfer rate:        15,225.82 KB/sec
Aggregate data transfer rate:          0.07 KB/sec
Elapsed processing time:           00:01:27


>  <<ADSM problems.doc>>

Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect
the views of Blue Cross Blue Shield of Florida, Inc.




#### ADSM problems.doc has been removed from this note on September 06
2001 by Andrew Raibeck