I agree with Tim:

SAMS:disk is defined to CA-1 or whatever TMS you are using, as an
External Data Manager, so once CA-1 knows SAMS:Disk will be using
that tape, CA-1 will not control it unitl SAMS releases it from use and in
uses an exit coded in SAMS to give it back to CA-1 to reuse.  ADSM
needs to be set up the same way.  SAMS:disk will not control the tapes,
ADSM will when it is defined as an External Data Manager.   Don't forget
to code your delete exit in the server option file in ADSM.

Jane Dagostino-Snyder
University of Minnesota
Storage Administration
(612)  624-4883.

>>> Pittson, Timothy ,Corp,US <tpittson AT HIMAIL.HCC DOT COM> 05/31/96
12:10pm >>>
Not sure I understand the part about using SAMS:DISK (aka DMS) to
migrate to mainframe tape - you should be using the facilities built in to
ADSM to migrate the data from the disk buffer pool to tape and let
ADSM manage the environment - I don't think SAMS:DISK will do what
you want it to.  Also, as far as communications method, according to the
ADSM documentation, you must use TCPIP as the communications
method for
Windows NT.

Tim Pittson tpittson AT himail.hcc DOT com

>----------
>From:  William Kral[SMTP:wkral AT TNE DOT COM]
>Sent:  Friday, May 31, 1996 12:19 PM
>To:    Multiple recipients of list ADSM-L
>Subject:       Proposed ADSM Environment
>
>We are looking for any comments or feedback on a proposed ADSM
pilot
>environment we are in the process of creating.......
>
>We will be installing ADSM to backup NT Servers to an MVS Host
>Platform. We
>will have SNA clients on the NT servers as well as MVS using a 3745
as
>the
>mainframe gateway. The ADSM Administrator workstation will be OS/2
Warp
>
>Connect in a dual boot environment with Windows 3.11 (Workstation).
The
>
>initial backup will be to mainframe DASD and subsequently migrated to
>mainframe tape using SAMS:DISK (Storage Management Software)
>
>We would appreciate any comments/criticisms or advise on what we
have
>just
>described.
>
>WKral AT TNE DOT COM
>EList AT TNE DOT COM
>