z/OS DFSMS Software Support for IBM System Storage TS1140, TS1130, and TS1120 Tape Drives (3592)
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Object tape migration considerations

z/OS DFSMS Software Support for IBM System Storage TS1140, TS1130, and TS1120 Tape Drives (3592)
SC23-6854-00

If you choose to encrypt your object data, any partially filled non-encrypted tape volumes associated with an object storage group that you want to encrypt, should be marked full and not writable, so they are not selected. This is important because at the volume level all of the data on the tape is either encrypted or non-encrypted, and a mix of the two cannot reside on the same tape.

In the past, when migrating to a new drive model with a new recording technology using media types that could also be used at a lower-level recording technology, you marked your partially filled volumes as full or not writable and new write requests were done at the new recording technology. When migrating from 3592-J or 3592-2 drives to 3592-2E drives, volumes written with EFMT1 or EFMT2 recording technology and not filled to capacity do not need to be marked as full or not writable. Data can be extended using the EFMT1 or EFMT2 recording technology on the encryption-capable TS1120 tape drive.

These items should be considered when planning to use 3592-2E drives:

If the 3592-2E devices are in an IBM tape library:

  1. Follow the steps listed in OAM library support for OAM Library Support.
  2. Add new data classes, specifying EEFMT2 recording technology.
  3. Review ACS routines for STORE, or CTRANS, or both environments for any changes that may be necessary to ensure proper class assignment.

If the 3592 Model E05 (encryption capable) devices are not in an IBM tape library, use device esoterics for STORAGEGROUP statements in the CBROAMxx member of PARMLIB for the Object storage groups that are to use the new devices. It is important to segregate in an esoteric or generic the 3592 Model J devices and 3592 Model E05 (not encryption capable) from 3592 Model E05 (encryption capable) devices to prevent allocating an inappropriate drive for a volume written in EEFMT2 recording technology. Add new TAPEUNITNAME with the new device esoteric to the STORAGEGROUP statements in the CBROAMxx PARMLIB member for object storage groups or object backup storage groups that use the new devices.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014