1. Implement the data class policy specifying EFMT4 or EEFMT4. Also, specify as appropriate, the interchange recording formats, EFMT3 or EEFMT3. Also, modify or create ACS routines to associate the tape output functions with a data class that has the appropriate recording format specified. If no data class is used, EFMT4 will be the recording technology.
2. As appropriate, install the encryption key manager (IBM Security Key Lifecycle Manager or TKLM) and set up the key store it will use.
3. As appropriate, create the data classes or the DD statements (or use encryption key manager defaults) to specify the key labels and their encoding mechanism (label or hash).
4. As appropriate, for in-band key management, update the IOS PARMLIB member (IECIOSxx) using the new EKM command. Also create a z/OS UNIX segment for the IOS address space.
5. Upgrade 3592 Model E05 and 3592 Model E06 microcode to enable the drives to recognize and enable the EFMT4 or EEFMT4 formatted cartridges to be relabelled/reused. Also, ensure that VOLNSNS=YES is in the DEVSUPxx member of PARMLIB.
6. Make the required installation exit changes.
7. Make any needed changes to the HCD to define the new devices.
8. If more than one recording technology is used for the same device type, create a unique esoteric for each of the recording technologies. Use the esoteric unit names in DFSMShsm to direct allocations uniquely to each group of devices.
9. If performance scaling or performance segmentation is used (available only with MEDIA9 and MEDIA11 tape cartridges), update or create ACS routines to assign a data class to tape output functions. For example, for DFSMShsm, you can filter on single file tape data set names used by DFSMShsm functions. Define the data class with the performance scaling or performance segmentation attribute.
10. Add new device esoteric unit names or generic unit names to STORAGEGROUP statements in the CBROAMxx member of PARMLIB for the object storage groups that are to use the new devices. The esoteric or generic unit name must consist of TS1140 tape drives exclusively because the EFMT4 and EEFMT4 recording technologies are not compatible with other devices.
11. Install coexistence PTFs as appropriate.
12. IPL the system.

• z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
• z/OS HCD User's Guide
• z/OS DFSMShsm Implementation and Customization Guide

1. Implement the data class policy specifying EFMT4 or EEFMT4. Also, specify as appropriate, EFMT3 or EEFMT3 (for media interchange). Also, modify or create ACS routines to associate the tape output functions with a data class that has the appropriate recording format specified.
2. Because the TS1140 is only downward read (and not write) compatible with MEDIA9 and MEDIA10 (EFMT2 and EEFMT2) and MEDIA5 through MEDIA8 (EFMT1, EFMT2, EEFMT2, EFMT3 and EEFMT3), explicit specification of the read-compatible special attribute indicator (in the tape configuration database) or usage of the LABEL=(,,,IN) on the DD statement of JCL is needed to enable the TS1140 tape drive to be considered eligible for these volume types.
3. As appropriate, install the encryption key manager (IBM Security Key Lifecycle Manager or TKLM) and set up the key store it will use.
4. As appropriate, create the data classes or the DD statements (or use encryption key manager defaults) to specify the key labels and their encoding mechanism (label or hash).
5. For in-band key management, update (as appropriate) the IOS PARMLIB member (IECIOSxx) using the EKM command. Also create a z/OS UNIX segment for the IOS address space.
6. Upgrade 3592 Model E05 and 3592 Model E06 microcode to enable the library drives to recognize and enable the EFMT4 or EEFMT4 formatted cartridges to be relabelled/reused. Also, ensure that VOLNSNS=YES is in the DEVSUPxx member of PARMLIB.
7. Make the required installation exit changes.
8. Define or alter existing data class constructs as appropriate, to specify the EFMT4 or EEFMT4 recording technology, MEDIA9, MEDIA10, MEDIA11, MEDIA12, or MEDIA13 media type, and the performance attributes (performance scaling or performance segmentation available only with MEDIA9, or MEDIA11 tape cartridges).
9. Define or alter existing storage group constructs to include libraries with the new TS1140 tape drives devices.
10. Update ACS routines to direct allocation to the TS1140 tape drives device as requested.
11. Validate and activate any new or modified SMS configuration.
12. Make any needed changes to the HCD to define the new devices.
13. To define the partitioning category code for MEDIA9, MEDIA10, MEDIA11, MEDIA12, or MEDIA13 tape cartridges, specify the appropriate parameter of the DEVSUPxx parmlib member.
14. IPL the system.

• z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries
• z/OS HCD User's Guide
• z/OS DFSMSdfp Storage Administration

The migration steps that you must take in tape environments that use OAM objects vary depending upon the type of environment that is installed:

1. If you install the new TS1140 tape drives devices in an OAMplex:
   1. Make the new TS1140 tape drives devices available to all instances of OAM where the full support software is installed.
   2. Install coexistence PTFs as appropriate.
   3. Consider setting DSNWITHSGNAME in the SETOAM statement in the CBROAMxx PARMLIB member. Review your ACS routines if appending the storage group name to OAM data set names (DSNWITHSGNAME).
2. If you install the new TS1140 tape drives devices in an IBM tape library:
   1. Follow the migration steps listed for an IBM tape library environment.
   2. Define the new data classes in STORAGEGROUP statements in the CBROAMxx member of PARMLIB for the object storage groups that are to use the new devices.
   3. Make the needed changes to ACS routines for ALLOC, STORE, or CTRANS environments.
3. If you install the new TS1140 tape drives devices in a stand-alone environment:
   1. Follow the migration steps listed for a stand-alone environment.
   2. Add new device esoteric unit names or generic unit names to STORAGEGROUP statements in the CBROAMxx member of PARMLIB for the object storage groups that are to use the new EFMT4 or EEFMT4 recording technologies. The esoteric or generic unit name must consist of TS1140 tape drives exclusively because the EFMT4 and EEFMT4 recording technologies are not compatible with the other 3592 drives.
   3. Consider setting DSNWITHSGNAME in the SETOAM statement in the CBROAMxx PARMLIB member. Review your ACS routines if appending the storage group name to OAM data set names (DSNWITHSGNAME).
   4. Make the needed changes to ACS routines for ALLOC, STORE and CTRANS environments.
   5. Define the new data classes in STORAGEGROUP statements in the CBROAMxx member of PARMLIB for the object storage groups that are to use the new EFMT4 or EEFMT4 recording technologies.

DFSMShsm allows the specification of tape unit names using either generic or esoteric names. Installations that have a mixture of non-SMS-managed 3590 devices defined under the 3590-1 generic name, need to perform these steps:

1. Define a unique esoteric for each recording technology.
2. Use the SETSYS USERUNITTABLE command to define these esoteric names to DFSMShsm. This also applies to mixed devices in the 3490 generic. Installations that use SMS-managed tape devices or have a single 3590-1 recording technology, do not need to define an esoteric for those devices.

• z/OS DFSMShsm Implementation and Customization Guide
• z/OS DFSMShsm Storage Administration

In a SMS tape environment, and optionally in a non-SMS tape environment, the SMS data class construct can be used to select WORM tapes for ABACKUP processing. The output data set prefix specified in the aggregate group definition can be used by the ACS routines to select a WORM data class. Set up the ACS routine and the output data set name to uniquely identify the ABARS output files that must go to WORM tape.

In a non-SMS tape environment, the default allows tape pooling to determine if ABARS data sets go to WORM or R/W media. Optionally, if the DEVSUPxx parameter, ENFORCE_DC_MEDIA=ALLMEDIATY or ENFORCE_DC_MEDIA=MEDIA5PLUS, is used, then the data class must request the appropriate media type for it to be successfully mounted.

• z/OS DFSMShsm Implementation and Customization Guide
• z/OS DFSMShsm Storage Administration