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. Since the 3592 Model E06 is downward write compatible with the 3592 Model E05, this same concern does not exist for EFMT2/EEFMT2; however, since the 3592 Model E06 is not downward write compatible with the EFMT1 format, customers will need to mark any partially filled tapes 'full' or 'not writable' as they migrate to the newer 3592 drive technology and no longer have any devices capable of writing EFMT1.

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

If the 3592-3E 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 EFMT3 and EEFMT3 recording technologies.
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 TS1130 (3592 Model E06) 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 the different 3592 devices to prevent allocating an inappropriate device for a volume written in the EFMT3 or EEFMT3 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.

All partially filled EFMT1 volumes belonging to a storage group with 3592-3E devices assigned need to be marked 'full' or 'not writeable' as the 3592-3E device is not downward write-compatible with the EFMT1 recording format. This will prevent a 3592-3E device from being selected to write an EFMT1 tape volume.

Coexistence and full support systems must have the new NUMPKBWO, NUMLKBWO, NUMLKBDEO, FRESPACEO and CAPACITYO columns added to the TAPEVOL table in the Optical Configuration Database (OCDB). Run the CBRSMKBO DB2 Database Migration sample JCL to add the columns. After the new columns have been added, run CBRPBIND. In an OAMplex, since the DB2 tables are shared, only one system in the OAMplex needs to run CBRSMKBO to add the new TAPEVOL table columns but all the systems in the OAMplex need to run CBRPBIND.