Migrating from the StorageTek T10000A or StorageTek T10000B Tape Drive to the StorageTek T10000C Tape Drive in MVS Operating Environments

Published June 2011 (updated July 2014)


This paper briefly describes how to migrate from Oracle's StorageTek T10000A and StorageTek T10000B tape drives to Oracle's StorageTek T10000C tape drive in both the native (direct attached) MVS environment and Oracle's StorageTek VSM environment.

Note: This paper discusses migration strategies for migration from StorageTek T10000A and StorageTek T10000B devices currently defined in 3590 image to a StorageTek T10000C device in 3590 image. Migration from 3490 image to 3590 image is not covered in this paper.

Contents:

Introduction

The StorageTek T10000 tape drive family provides a range of small, modular, high-performance units designed for high-capacity data storage. The tape drives are either rack mounted or used in various StorageTek libraries. There are currently three models in the StorageTek T10000 tape drive family: StorageTek T10000A, StorageTek T10000B, and StorageTek T10000C. Illustration 1 depicts a StorageTek T10000 tape drive.

The high performance of the StorageTek T10000 tape drive reduces wall-clock time of batch production and backup applications, while the increased capacity lowers the cost of storage and saves library slots. The StorageTek T10000C tape drive increases the native cartridge capacity to 5000 GB (five terabytes). This increase was achieved through several technological advances, including a new advanced media type and a new tape head design. The capacity has also been increased on the existing VolSafe (now 5 TB) and Sport (now 1 TB) tape cartridges. This increased capacity saves library slots and improves throughput by reducing mount/dismount cycles.

Figure 1

Figure 1: StorageTek T10000 Tape Drive

Note: This paper assumes that you have already defined the StorageTek T10000C tape drives in their LIBGEN and that StorageTek T10000C tape drives have been added to your tape environment. Those processes are not covered in this paper, but they must be completed prior to proceeding with the migration plan. For procedures that describe how to add, remove, and replace tape drives in MVS environments, refer to the chapter “Reconfiguring a TapePlex” in StorageTek Enterprise Library Software: Configuring HSC and VTCS for your particular ELS release level.

Legacy Read Compatibility

The StorageTek T10000C tape drive provides backward read compatibility in that it can read cartridges written on StorageTek T10000A and StorageTek T10000B tape drives to facilitate migration to the StorageTek T10000C recording format. Cartridges written on the StorageTek T10000C tape drive are automatically written at the higher recording density and are not readable by the earlier generation tape drives.

Data Cartridge Guidelines

Separate media sub-pools for StorageTek T10000 family tape drives should be created and managed when more than one tape drive type exists in the same TapePlex for native MVS tape drives. For RTD tape drives, separate MVC pools are required only if you intend to continue using mixed tape drive types. If StorageTek T10000A and/or StorageTek T10000B tape drives will be eliminated after migration to StorageTek T10000C tape drives, it is not necessary to define separate MVC pools. Guidelines for the creation and maintenance of media sub-pools are located in HSC software documentation.

The guidelines for using mixed tape drive types are as follows:

  • StorageTek T10000C tape drives can read tapes previously written by StorageTek T10000A and/or StorageTek T10000B tape drives.
  • StorageTek T10000C tape drives cannot overwrite tapes written by StorageTek T10000A and/or StorageTek T10000B tape drives.
  • StorageTek T10000C-written tapes cannot be read by StorageTek T10000A or StorageTek T10000B tape drives.
  • StorageTek T10000C-written tapes cannot be overwritten by StorageTek T10000A or StorageTek T10000B tape drives.
  • StorageTek T10000C tape drives cannot append to StorageTek T10000A-written or StorageTek T10000B-written tapes.

VolSafe Guidelines

The VolSafe guidelines are as follows:

  • StorageTek T10000C tape drives will not append to StorageTek T10000A or StorageTek T10000B VolSafe tapes.
  • StorageTek T10000C tape drives will read a StorageTek T10000A or StorageTek T10000B VolSafe tape.

Legacy Tape Drive Considerations

During the StorageTek T10000C migration, it is recommended that some StorageTek T10000A and/or StorageTek T10000B tape drives remain in the environment until all media has been converted to StorageTek T10000C format, if that is the ultimate goal.

This approach mitigates the possibility of encountering cartridges written on StorageTek T10000A or StorageTek T10000B tape drives that the StorageTek T10000C tape drives are unable to read. The probability of this occurring is extremely low. It is not anticipated that the StorageTek T10000C tape drive will encounter legacy read errors. However, it is still recommended that you keep some legacy tape drives in the environment until all data has been migrated to StorageTek T10000C format.

Host Software Levels Supporting the StorageTek T10000C Tape Drive

Table 1: Host Software Levels

Application

PTF or Patch

Additional Information

NCS/VTCS 6.2

 

 

SMC

L1A00SW

 

MVS/CSC

L1C10AZ

 

HSC/MVS

L1H15T2

 

HSC/VM

L1H15T1

 

VTCS 6.2

L1H15I4, L1H15I6

 

ELS 7.0

 

 

VTCS

L1H15I7

 

HSC/SMC

L1H15T3

 

MVS/CSC

L1C10B0

 

ELS 7.1

 

Supported in base release


Microcode Levels Supporting the StorageTek T10000C Tape Drive

It is recommended that the latest microcode levels be used when performing a migration procedure. If the latest microcode is not available, it is mandatory to use firmware update 1.37.114 or later when using both StorageTek T10000A and StorageTek T10000B tape drives in the same environment. The following levels are current as of February 1, 2011.

Table 2: Tape Drive Microcode Levels

T10000C FICON

1.51.313

T10000B FICON

1.46.209

T10000A FICON

1.46.109

VOP

1.0.17


Table 3: Library Microcode Levels

SL8500

6.04

SL3000

3.00

9310

No support

L700

No support


Table 4: VTSS Tape Drive Microcode Levels

VSM4/5

D/H02.11.18.00


StorageTek T10000 3490 Media Values

Table 5: StorageTek T10000 3490 Media Values

VOLATTR Media

Transport Model

Recording Technique

STORCLAS Media

Cartridge Type

Density

Encrypted?

T10000T1

T1A34-T10KA

T1A34

T1A000T1

StorageTek T10000 full capacity

Single

No

T1AE34-T10KA

T1AE34

T1A000E1

StorageTek T10000 full capacity for encryption

Single

Yes

T10000TS

T1A34-T10KA

T1A34

T1A000TS

StorageTek T10000 Sport

Single

No

T1AE34-T10KA

T1AE34

T1A000ES

StorageTek T10000 Sport for encryption

Single

Yes

T10000T1

T1B34-T10KB

T1B34

T1B000T1

StorageTek T10000 full capacity

Double

No

T1BE34-T10KB

T1BE34

T1B000E1

StorageTek T10000 full capacity for encryption

Double

Yes

T10000TS

T1B34-T10KB

T1B34

T1B000TS

StorageTek T10000 Sport

Double

No

T1BE34-T10KB

T1BE34

T1B000ES

StorageTek T10000 Sport for encryption

Double

Yes

T10000T2 or T2

T1C34-T10KC

T1C34

T1C000T1

StorageTek T10000 T2 full capacity

 

No

T1CE34-T10KC

T1CE34

T1C000E2

StorageTek T10000 T2 full capacity for encryption

 

Yes

T10000TT or TT

T1C34-T10KC

T1C34

T1C000T2

StorageTek T10000 Sport

 

No

T1CE34-T10KC

T1CE34

T1C000ET

StorageTek T10000 Sport for encryption

 

Yes


StorageTek T10000 3590 Media Values

Table 6: StorageTek T10000 3590 Media Values

VOLATTR Media

Transport Model

Recording Technique

STORCLAS Media

Cartridge Type

Density

Encrypted?

T10000T1

T1A35-T10KA

T1A35

T1A000T1

StorageTek T10000 full capacity

Single

No

T1AE35-T10KA

T1AE35

T1A000E1

StorageTek T10000 full capacity for encryption

Single

Yes

T10000TS

T1A35-T10KA

T1A35

T1A000TS

StorageTek T10000 Sport

Single

No

T1AE35-T10KA

T1AE35

T1A000ES

StorageTek T10000 Sport for encryption

Single

Yes

T10000T1

T1B35-T10KB

T1B35

T1B000T1

StorageTek T10000 full capacity

Double

No

T1BE35-T10KB

T1BE35

T1B000E1

StorageTek T10000 full capacity for encryption

Double

Yes

T10000TS

T1B35-T10KB

T1B35

T1B000TS

StorageTek T10000 Sport

Double

No

T1BE35-T10KB

T1BE35

T1B000ES

StorageTek T10000 Sport for encryption

Double

Yes

T10000T2

T1C35-T10KC

T1C35

T1C000T1

StorageTek T10000 T2 full capacity

 

No

T1CE354-T10KC

T1CE35

T1C000E2

StorageTek T10000 T2 full capacity for encryption

 

Yes

T10000TT

T1C35-T10KC

T1C35

T1C000T2

StorageTek T10000 Sport

 

No

T1CE35-T10KC

T1CE35

T1C000ET

StorageTek T10000 Sport for encryption

 

Yes


Use Table 5 and Table 6 as guidelines to do the following:

  • Create VOLATTR statements that segregate encrypted/non-encrypted media.

  • Specify the correct STORCLAS MEDIA values to assign the desired cartridge type and recording technique to MVCs.

  • Determine which transport models (tape drives) can write to/read from which media. A higher-capability transport (double density versus single or encryption versus non-encryption) can read from media written by a lower-capability transport but can write to that media only from the beginning of the tape. A lower-capability transport, however, cannot read from media written by a higher-capability transport but can write to that media from the beginning of the tape.

StorageTek T10000C Migration in a Native MVS Environment

This paper discusses migration strategies for migration from StorageTek T10000A and StorageTek T10000B devices currently defined in 3590 image to a StorageTek T10000C device in 3590 image. Migration from 3490 image to 3590 image is not covered in this paper.

Table 7 lists the device type and UCB type information for the StorageTek T10000 devices in 3590 image.

Table 7: UCB Type Information

Drive

Device Type

UCB Type

T10000A

3592J1A

78048083

T10000B

3592E05

78048083

T10000C

3592E06

78048083


StorageTek T10000C Recommended Migration Procedure for 3590 Image

  1. Define UNITATTRs, if necessary. It is no longer necessary to define UNITATTRs for transports located in an automated library. However, if there are standalone StorageTek T10000A, StorageTek T10000B, and/or StorageTek T10000C tape drives that exist in a native MVS environment outside an ACS, they require UNITATTRs. For example:

    UNITATTR ADDR (0600 - 060F) MODEL (T1A35) 3590 image
    UNITATTR ADDR (0800 - 080F) MODEL (T1B35) 3590 image
    UNITATTR ADDR (0A00 - 0A0F) MODEL (T1C35) 3590 image
    
  2. Define VOLATTRs for StorageTek T10000C cartridges on non-encryption enabled tape drives as follows:

    VOLATTR SERIAL(50000-50999) MEDIA(T10000T2) RECTECH (T1C35)
    
  3. Define VOLATTRs for StorageTek T10000C cartridges on encryption enabled tape drives as follows:

    VOLATTR SERIAL (50000-50999) MEDIA(T10000T2) RECTECH (T1CE35)
    
  4. Direct device allocation to StorageTek T10000C devices by defining or modifying the SMC Policy/Tapereq statement that includes a subpool parameter for each scratch request based on user-defined parameters, such as datasetname or jobname. At this point, data sets will begin writing to StorageTek T10000C media.

  5. If you are migrating data that is not managed by DFSMShsm, move existing data written on StorageTek T10000A or StorageTek T10000B tape drives to StorageTek T10000C tape drives, using one of the following two options.

    • Leave existing tape data sets on the cartridges where they currently reside and allow them to age there while you start writing new data on StorageTek T10000C.

    • Move and re-catalog non-unique data sets currently residing on cartridges written on StorageTek T10000A or StorageTek T10000B tape drives to StorageTek T10000C media, which can be accomplished by using standard copying utilities, such as IEBGENER for physical sequential data sets. Non-unique data sets are those that are independent of any software product-controlled database, such as DFSMShsm, DB2, IMS, or any MVS system data sets that may reside on tape.

  6. Direct DFSMShsm migration functions to StorageTek T10000C devices using one of the following two options:

    • Define StorageTek T10000C as the only migration device for both migration and recycle functions. This is the most straightforward option. In order to accomplish this, an esoteric must first be defined in the MVS IOGEN which contains only the StorageTek T10000C devices. For illustration purposes, the esoteric of NEWDRVC is used.

      DFSMShsm ARCCMDxx parmlib definitions are used to direct allocation for each DFSMShsm function. TAPEREQ statements are not necessary to direct allocation if you are using an esoteric containing only StorageTek T10000C devices. To direct migration output to the StorageTek T10000C, define the following:

      SETSYS TAPEMIGRATION(ML2TAPE(TAPE(NEWDRVC)))
      
      SETSYS MIGUNITNAME(NEWDRVC)

      The recycle function is an extension of migration. If the StorageTek T10000C tape drive has been defined as the only migration device, the recycle parameter definition in ARCCMDxx must be defined as follows:

      SETSYS RECYCLEOUTPUT(MIGRATION(NEWDRVC))
      
    • Define the StorageTek T10000C device as the output device for the recycle function. This option uses only the StorageTek T10000C device as the output device for the recycle function of DFSMShsm. Migration (ML2) continues to be directed to other devices as currently defined in the ARCCMDxx parameters. This option requires that all partial tapes for both migration and recycle be marked full at the end of the task. This option allows a staged migration to StorageTek T10000C media, but results in low capacity utilization for all migration and recycle volumes. TAPEREQ statements cannot be used with this option to direct allocation since the data set names of ML2 volumes and recycled ML2 volumes cannot be distinguished. To direct recycle output to StorageTek T10000C devices, the recycle parameter in ARCCMDxx must be defined as follows:

      SETSYS RECYCLEOUTPUT(MIGRATION(NEWDRVC))
      

      The following command is required to force all migration and recycle volumes to be marked full at the completion of the respective task:

      SETSYS PARTIALTAPE(MIGRATION(MARKFULL))
      
  7. Be aware of these other DFSMShsm ARCCMDxx parameter updates and considerations:

    • The USERUNITTABLE must contain all the esoteric unit names used to direct allocation within DFSMShsm. If a new esoteric has been defined in the MVS IOGEN and used in DFSMShsm ARCCMDxx parameters, it must be defined as follows, using OLDDRVA to illustrate a currently defined esoteric and NEWDRVC as the new StorageTek T10000C esoteric:

      SETSYS USERUNITTABLE(OLDDRVA:OLDDRVA,NEWDRVC:NEWDRVC)
      
    • The TAPEUTILIZATION parameter manages the amount of data written by DFSMShsm to tape media. For example, to fully utilize a StorageTek T10000C 3490E cartridge, the recommendation is to set this parameter to 50000%. The results may be unpredictable if a percentage greater than 10000% is defined. For any 3590-1 device, the recommended value is 97%.

      For 3490 image:

      SETSYS TAPEUTILIZATION(UNITTYPE(NEWDRVC)PERCENTFULL(50000))
      

      For 3590 image:

      SETSYS TAPEUTILIZATION(UNITTYPE(NEWDRVC)PERCENTFULL(97))
      
    • If you do not utilize the TAPECOPY or DUPLEX functions, you can set TAPEUTILIZATION to NOLIMIT, which allows DFSMShsm to write data to logical EOV. However, NOLIMIT will allow data sets to span volumes resulting in two volumes being mounted to satisfy a recall request.

    • Device selection for DFSMShsm recall is based on information recorded in the migration control data set (MCDS). DFSMShsm records the device type used for each migrated data set. The information stored for the device type is the hexadecimal representation of the device type from the MVS UCB, which is an entry of x’78048083’ for the 3590-1 device type. Since StorageTek T10000A and StorageTek T10000B devices are all 3590-1 device types, all would be eligible for allocation. If there is a mix of StorageTek T10000A and StorageTek T10000B devices, SMC will influence specific allocation for the recall based on the density byte recorded in the CDS for the StorageTek T10000 volser.

StorageTek T10000C Migration in a VSM Environment

In addition to the legacy tape drive considerations, it is further recommended that connectivity to multiple ACSs (for example, one StorageTek T10000A and/or one StorageTek T10000B RTD per ACS, depending on your original tape drive mixture) remain in the confVTSS until all media has been converted to StorageTek T10000C media, if that is the ultimate goal.

StorageTek T10000C Recommended Migration Procedure

  1. Ensure adequate MVCs are available for migrations. Remember the media is different, so the new StorageTek T10000 T2 carts will have to be used.

  2. Use the current MVC pool to define all MVCs in VOLATTRs with a media of T10000T2 or T2 and a recording technique of T1C34 for non-encrypted tape drives or T1CE34 for encrypted drives. For example:

    VOLATTR SER(MVC000-MVC999) MEDIA(T10000T2) RECTECH(T1C34)
    
  3. Even though all MVCs are defined with a recording technique of T10000C, review media in the Storage Class constructs to ensure that the definitions are correct for the new media setup. For example:

    STOR NAME(S1) ACS(00) MEDIA(T1C000T2) MVCPOOL(T10KC)
    
  4. At this point, new migrations will begin going to StorageTek T10000C media. Migrate the VTVs currently residing on cartridges written by StorageTek T10000A and StorageTek T10000B tape drives using one of the following two techniques.

    • Allow RECLAIM to move the data naturally when MVCs become eligible to be Reclaimed with the understanding that MVCs that do not meet RECLAIM criteria will eventually need to be drained.

    • Use MVCDRain to migrate all the MVCs, for example:

      .VT MVCDRAIN MVCid(mvc volser)
      

    Actively using MVCDRain is typically more aggressive in migrating off of old media in order to replace the remaining StorageTek T10000A and StorageTek T10000B tape drives with StorageTek T10000C tape drives to achieve a total StorageTek T10000C RTD environment.

Acronyms and Definitions

Table 8: Acronyms and Definitions

Acronym

Definition

ACS

Automated Cartridge System

ACSLS

Automated Cartridge System Library Software

CDRT

Concurrent Disaster Recovery Test

CSC

Client System Component

DFSMShsm

Data Facility Storage Management Subsystem - hierarchical storage manager

ELS

Enterprise Library Software

HSC

Host Software Component

HTTP

Hypertext Transfer Protocol

MVC

Multi-Volume Cartridges

MVS

Multiple Virtual Storage

NCS

Nearline Control Solution

PTF

Program Temporary Fix

RTD

Real Tape Drive

SMC

Storage Management Component

TAPEPLEX

A single StorageTek hardware configuration, normally represented by a single HSC Control Data Set (CDS)

UCB

Unit Control Block

VM

Virtual Machine

VOP

Virtual Operator Panel

VolSafe

Write Once Read Many Cartridge

VTCS

Virtual Tape Control System

VTSS

Virtual Tape Storage Subsystem


Related Publications

The documentation is constantly being updated to include the latest changes and additions. Please access the Current Tape Storage Documentation to obtain the latest documentation.

Revision 1.0, 06/02/2011
Revision 1.1, 07/01/2014
Added a sentence to the end of the note in the "Introduction" section.