Re: Converting from V2 w/Enhanced Server to V3

Thanks very much, Nancy.
I think the reason I could not find it before, that directory is not
available to the public, I could not get in.
So thanks for sending it!

> -----Original Message-----
> From: Nancy Young [SMTP:youngny AT US.IBM DOT COM]
> Sent: Wednesday, December 30, 1998 12:59 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Converting from V2 w/Enhanced Server to V3
>
> Wanda,
>
>     The following section is extracted from the v3r1m1f3.fixinfo.dev.html
> under the
>         /adsm/fixes/v3r1/aixsrv/3.1.1.3  directory on
> index.storsys.ibm.com
> or via our web.
>
>
> Section C: Migration from OMI solution to ADSM
>
> Migration from OMI Enhadsmserv to IBM V3 ADSM
>
> The following describes the necessary steps for migration from
> Enhadsmserv,
>  OMI Enhanced ADSM Server for StorageTek Tape Drives and Tape Libraries ,
> to
> IBM V3 ADSM in support of StorageTek ACSLS library, Timberline drive,
> Redwood drive and DLT7000 drive. Only perform those steps applicable to
> your
> configuration.
>
>    1.Prior to installing V3 ADSM
>      Stop all activities from Enhadsmserv.
>    2.QUERY LIBRARY
>      Obtain the Library Name of each library with:
>
>      LIBTYPE=SSI
>
>    3.QUERY DEVCLASS
>      Obtain the DeviceClass Name of each device class with:
>
>      DEVTYPE=STK
>      lsdev -C -s scsi
>
>      Obtain the current device special files and its SCSI associated
> information from AIX. Note, all tape drives supported by the Enhadsmserv
> device driver have
>      the device special filename of "/dev/rmt(n)" with the device
> description of "OMI AdvanTAPE - .......".
>    4.QUERY DRIVE
>      Record the SCSI configuration information and associate these device
> special files with the Enhadsmserv DRIVE definition.
>      Note: the drive name contains information about the ACS drive ID,
> i.e.
>  STK_n_n_n_n. In addition, the first "n" is the ACS_id of the library.
>    5.DELETE DRIVE libname drivename
>      Delete all drives that were defined as DEVTYPE=STK or DEVTYPE=DLT
> that
>  use OMI device driver from all libraries.
>    6.Halt
>      Halt the Enhadsmserv server, make a copy of your DB and DEVCONFIG
> file.
>    7.Use SMIT
>      Use SMIT to delete these drive configurations from AIX.
>
>      ps -ef  |  grep ssi
>
>      Determine the SSI daemon process id.
>
>      ps -ef  |  grep mini_el
>
>      Determine the Event Logger daemon process id.
>
>      kill  nnnn
>
>
>      Kill the ssi and event logger daemons that were started by the
> rc.adsmserv shell script.
>    8.Install V3 ADSM and configure ADSM device drivers
>      Install V3 ADSM server and device driver and use SMIT to re-configure
> those deleted SCSI tape devices. All newly configured devices Note: the
>      LIBTYPE and DEVTYPE for Enhadsmserv and V3 ADSM are different.
>
>      LIBTYPE=SSI   --->  LIBTYPE=ACSLS
>      DEVTYPE=STK  ---> DEVTYPE=ECART
>
>    9.Upgrade to V3 data base
>      rc.acs_ssi
>      In the /usr/adsm.devices/bin directory, you should find rc.acs_ssi,
> this is the shell script to invoke ACSLS SSI client daemon. Start the SSI
> client daemon for
>      the ACSLS support.
>
>      ./dsmserv upgradedb
>
>   10.Invoke the V3 ADSM
>      Invoke the V3 ADSM and perform the data base upgrade
>   11.QUERY LIBRARY libname
>      After the server is initialised, the previous SSI library appears as
> MANUAL library.
>   12.UPDATE LIBRARY libname LIBTYPE=ACSLS ACSID=n
>      Update all the previous SSI libraries to the new ACSLS libraries,
> UPDATE LIBRARY to change LIBTYPE is only allowed for migration from SSI to
>      ACSLS.
>   13.AUDIT LIBRARY libname
>      Audit the library to reinitialise the ACSLS library structure. All
> ADSM checked-in volumes in the libraries will be locked during the AUDIT
> process. Depends
>      on the size of the library it may take a while before the library is
> ready for operation.
>   14.QUERY LIBV libname
>      Verify all library volumes and their status.
>   15.DEFINE DRIVE libname drivename DEVICE=/dev/mtn ACSDRVID=n,n,n,n
> ONLINE=YES
>      Re-define the drives to the library. Note, the ACSDRVID n,n,n,n
> values
>  are obtained from the drive name of STK_n_n_n_n and the device
>   16.QUERY DEVCLASS classname
>      The DEVTYPE=STK of the previous DEVCLASS appeared as OMI_STK which is
> an invalid type for V3 ADSM.
>   17.UPDATE DEVCLASS classname DEVTYPE=ECART
>      Update all OMI_STK DEVCLASSes with the new DEVTYPE, UPDATE DEVCLASS
> to
>  change DEVTYPE is only allowed for migration from
>      OMI_STK typ
>
>
> Regards,
> Nancy Young
>
>
> Email: youngny AT us.ibm DOT com
>
> ###  Find the latest ADSM information at http://www.storage.ibm.com/ADSM
> ###
>
>
>
> "Prather, Wanda" <PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU> on 12/29/98 05:57:28 
> PM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:    (bcc: Nancy Young/San Jose/IBM)
> Subject:  Converting from V2 w/Enhanced Server to V3
>
>
>
>
>
> Can anybody tell me where to find any documentation/hints/suggestions on
> converting from ADSM/AIX V2 with ADSM Enhanced Server (STK 9710 support)
> to
> ADSM/AIX V3 with native ACSLS support?
>
> I thought I had seen something at one time in a README file, but I can't
> find it now.
>
> Thanks.....