Definitely go thru the archives on this one...there is alot of good information out there.... Also review this email -----Original Message----- From: Louis Wiesemann [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 10, 2001 9:43 AM To: [EMAIL PROTECTED] Subject: TSM and 3590E Tapes We are running TSM 3.7.3 on OS/390 2.8. We are getting ready to upgrade our tape drives from model B's to model E's. IBM says that the upgraded drives will read the old tapes just fine, but will write them at the new density. I am unable to determine what, if anything, I need to do to configure TSM for this change. The deviceclasses only define "3590" with no model information. The capacity information for the old density tapes will not be correct when it starts writing at the new density. Is this something that TSM will adjust automatically or do I need to reset it somehow? Are there any problems I'm not thinking of that might bite us with some tapes at the old density and some at the new, once TSM starts writing tapes with the upgraded drives? Anything, else I should be looking at. Thanks for any advice. ---------------------------------------------------------------------------- ------------------------------------ Louis J. Wiesemann 502-852-8952 ---------------------------------------------------------------------------- ------------------------------------ The "Daily Word For Reflection" is a free service and a non-discussion list intended primarily to allow personal reflection on the Word of God. SUBSCRIBE/UNSUBSCRIBE at: http://www.cin.org:81/guest/RemoteListSummary/dailywordtoday ________________________________________________________
Here is the information on upgrading to 3590E drives $$ Support for IBM 3590 Model Exx Tape Drives --------------------------------------------- ADSM now supports the IBM 3590E Tape drive. The 3590E tape drive writes data in a new 256 track data tape format. 3590E drives can not write in 3590 128 track format however, they can read data from the tapes previously written in 128 track format on 3590 drives. With new 3590E drives available, the existing 3494 libraries with 3590 drives may either be completely upgraded with 3590E drives or they may have an intermix configuration (3590 and 3590E drives). ADSM administrators must follow certain rules to transition from old 3590 drives to new 3590E drives and/or maintain both kinds of drives within the same physical library. Configurations: Device Driver level: Atape.4.4.0.0 ( ftp://index.storsys.ibm.com/devdrvr/AIX) Microcode level: 3590E - EC F23200 D01C_502 NOTE: To convert a 3590E volume to 3590 must have microcode level EC D19328 D01A_2FC Tape formats for 3590E: - 3590E-B - uncompressed mode (similar to 3590B) - 3590E-C - compressed mode (similar to 3590C) - DRIVE - the most advanced available format Note: For 3590 and 3590E tape drives the most advanced formats are respectively 3590C and 3590E-C 1. All 3590 drives within physical library are upgraded with 3590E drives at the same time. Consider an example with one 3590 drive physically defined as /dev/rmt0. Assume that there were originally defined devclass, logical library, and storage pool for 3590 drive. There were also some volumes (tape cartridges) checked in the library with data written on that drive. Replaced 3590 drive with 3590E drive. Steps below will allow you to use the new 3590E drives with minimum changes to ADSM server: - Using SMIT utility or manually, remove /dev/rmt0 device example: rmdev -l 'rmt0' '-d; - Using SMIT utility or manually, define the 3590E device example: mkdev -c tape -t '3590' -s 'scsi' -p 'scsi0' -w '0,0' -l 'rmt0'; - Run ADSM server (dsmserv); - Issue ADSM command: UPDate DEVclass devclassname FORMAT=DRIVE update devclass devclass_3590 FORMAT=DRIVE; - Issue ADSM command: DELete DRive libname drivename delete drive lib_3590 drive_3590; - Issue ADSM command: DEFine DRive libname drivename DEVIce=devicename define drive lib_3590 drive_3590 device=/dev/rmt0; - Update all previously written on 3590 drive volumes to readonly mode update volume volname access=readonly; 2. Intermix of 3590 and 3590E drives in a single 3494 library environment. Consider an example of a physical library with one 3590 drive defined on /dev/rmt0 and a new 3590E drive defined on /dev/rmt1. Assume that there were originally defined devclass, logical library, and storage pool for 3590 drives. With addition of a new 3590E drive to the library that already has 3590 drives in it, new DEVCLASS, new logical LIBRARY, and new STORAGE pool MUST be defined. Defining new devclass, logical library, and storage pool for 3590E drive: DEFINE LOGICAL LIBRARY define library lib_3590E libtype=3494 device=/dev/lmcp0 scratchcategory=lib_3590_scratch privatecategory=lib_3590_scratch+3 DEFINE DEVCLASS define devclass devclass_3590E devtype=3590 format=3590E-C library=lib_3590E format=3590E-B format=DRIVE DEFINE STORAGE POOL define stgpool stg_3590E devclass_3590E other parameters Defining separate devclass for each type of drives will allow the user to specify the format for the drive and insure that 3590 volumes will not be mounted on 3590E drives and that 3590E volumes will not be mounted on 3590 drives. Defining a logical library for each type of drives will allow to define two separate storage pools of scratch volumes. It is necessary to allow write the label for the volume in the appropriate format. Moving a scratch volume from 3590 scratch pool to 3590E scratch pool: - ADSM command: CHECKOut LIBVolume libraryname volname REMove=No - ADSM command: CHECKIn LIBVolume libraryname SEARCH=Yes Note: In order to move volume from 3590 scratch pool to 3590E scratch pool issue above commands and RELABEL the volume after it has been checked in the 3590 library. IN ORDER TO READ THE VOLUME PREVIOUSLY WRITTEN IN 3590 FORMAT ON 3590E DRIVE (THE STORAGE POOL THAT OWNS THE VOLUME POINTS TO A DEVCLASS THAT USES 3590E drive): - UPDATE ACCESS MODE TO THAT VOLUME TO READONLY update volume volumename access=readonly; - CHECKOUT THE VOLUME FROM THE LOGICAL 3590 LIBRARY (THE DEVCLASS' OLD LIBRARY THAT HAD 3590 DRIVES); - CHECKIN THE VOLUME TO THE LOGICAL 3590E LIBRARY (THE DEVCLASS' NEW LIBRARY THAT CONTAINS 3590E DRIVES). Private volumes defined in private categories: The volumes defined in private category have to be marked READONLY in order to read data from them on 3590E drives. After data is expired and volume becomes empty its access type is still READONLY because this volume was directly defined in the private category. In order to reuse volumes with expired data on 3590E drives the access type of these volumes must be updated to READWRITE type. The user may update all volumes to READWRITE type with the following ADSM command: update volume volumename/ *(all of them) access=readwrite whereaccess=readonly wherestatus=empty There are also SQL scripts that will allow the user to query all volumes with above mentioned attributes. Next time the empty volume is mounted on 3590E drive for writing, it will be AUTOMATICALLY relabeled using 3590E format. This volume can be used neither for reading nor for writing on 3590 drives.
