1. Make any needed changes to the HCD to define the new devices.
2. 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.
3. If performance scaling is used (available with MEDIA5 tape cartridges only), 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 attribute.
4. 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 3592 Model J drives exclusively because the EFMT1 recording technology is not compatible with other recording technologies.
5. Install coexistence PTFs as appropriate.
6. 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. Define or alter existing data class constructs as appropriate, to specify the EFMT1 recording technology, MEDIA5, MEDIA6, MEDIA7, or MEDIA8, media type, and the performance scaling attributes (performance scaling available with MEDIA5 tape cartridges only).
2. Define or alter existing storage group constructs to include libraries with the new 3592 Model J devices.
3. Update ACS routines to direct allocation to the 3592 Model J device as requested.
4. Validate and activate any new or modified SMS configuration.
5. Make any needed changes to the HCD to define the new devices.
6. To define the partitioning category code for MEDIA5 MEDIA6, MEDIA7, or MEDIA8, tape cartridges, specify the appropriate parameter of the DEVSUPxx parmlib member.
7. When systems are sharing a library with 3592 Model J devices installed, install coexistence PTFs or full-function PTFs on all involved systems.
8. 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 3592 Model J devices in an OAMplex:
   1. Make the new 3592 Model J devices available to all instances of OAM where this software is installed.
   2. Install coexistence PTFs as appropriate.
   3. Add the DSNFMT column to the TAPEVOL table in the Optical Configuration Database. Run CBRSMPDS sample JCL to add the DSNFMT column. After the column has been added, run CBRPBIND. Only one system in an OAMplex needs to run CBRSMPDS to add the TAPEVOL column, but all systems in the OAMplex must run CBRPBIND.

      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. IPL the system.
2. If you install the new 3592 Model J 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. Add the DSNFMT column to the TAPEVOL table in the Optical Configuration Database. Run CBRSMPDS sample JCL to add the DSNFMT column. After the column has been added, run CBRPBIND. 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, or CTRANS environments.
3. If you install the new 3592 Model J 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 devices. The esoteric or generic unit name must consist of 3592 Model J drives exclusively because the EFMT1 recording technology is not compatible with other recording technologies.
   3. Add the DSNFMT column to the TAPEVOL table in the Optical Configuration Database. Run CBRSMPDS sample JCL to add the DSNFMT column. After the column has been added, run CBRPBIND. 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.

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. However, if you have a mixed SMS-managed 3590 environment, please review APAR OW57282.

• 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