1. Determine which data needs to be encrypted and set up the appropriate data class policy specifying EEFMT3 (or EEFMT2 for media interchanges). Also specify, as appropriate, the non-encryption recording formats, EFMT3 (or EFMT2 for media interchanges). If a TS1130 tape drive tape drive is allocated, the default recording format is EFMT3. Also, modify or create ACS routines to associate the tape output functions with a data class that has the appropriate recording format specified.
2. As appropriate, determine which key labels are to be used and how they will be specified, data class, the DD statement or Encryption Key Manager established defaults.
3. Determine whether you will need help from your tape management system vendor and contact them, if needed.
4. As appropriate, plan for the installation of the Encryption Key Manager (EKM) and decide which of the supported key stores to use.
5. As appropriate, plan for the key labels that will be used and the encoding mechanism (label or hash) for each and where the key labels will be specified.
6. For in-band key management (with encryption), update the IOS PARMLIB member (IECIOSxx) using the EKM command. Also create a z/OS UNIX segment for the IOS address space.
7. Upgrade 3592 Model J1A and 3592 Model E05 drive microcode to enable the drives to recognize and enable the EFMT3 and EEFMT3 formatted cartridges to be relabelled/reused. Also, ensure that VOLNSNS=YES is in the DEVSUPxx member of PARMLIB.
8. Determine which systems should have coexistence support and which systems should have full support.
9. Determine when to IPL the host machine after installing the coexistence PTFs, if needed.
10. Determine when to IPL the host machine after installing all necessary PTFs.

1. Determine which data needs to be encrypted and set up the appropriate data class policy specifying EEFMT3 (or EEFMT2 for media interchange). Also, specify as appropriate, the non-encryption recording formats, EFMT3 or EFMT2 (for media interchange). If a TS1130 tape drive is allocated, the default recording format is EFMT3. 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 3592 Model E06 is only downward read (and not write) compatible with the EFMT1 format, you must specify the read-compatible special attribute indicator (in the tape configuration database) or use LABEL=(,,,IN) on the DD statement of JCL to enable the 3592 Model E06 drive to be considered eligible for an EFMT1 request.
3. As appropriate, determine which key labels are to be used and how they will be specified, data class, the DD statement or Encryption Key Manager established defaults.
4. Determine whether you will need help from your tape management system vendor and contact them, if needed.
5. As appropriate, plan for the installation of the Encryption Key Manager (EKM) and decide which of the supported key stores to use.
6. As appropriate, plan for the key labels that will be used and the encoding mechanism (label or hash) for each and where the key labels will be specified.
7. For in-band key management (with encryption), update the IOS PARMLIB member (IECIOSxx) using the new EKM command. Also create a z/OS UNIX segment for the IOS address space.
8. Upgrade 3592 Model J1A and 3592 Model E05 drive microcode to enable the drives to recognize and enable the EFMT3 and EEFMT3 formatted cartridges to be relabelled/reused. Also, ensure that VOLNSNS=YES is in the DEVSUPxx member of PARMLIB.
9. Identify the installation exit changes that are needed.
10. Determine which systems should have coexistence support and which systems should have full support.
11. Determine when to IPL the host machine after installing the coexistence PTFs, if needed.
12. Determine when to IPL the host machine after installing all necessary PTFs.

The planning steps that you must consider in tape environments that use OAM objects vary depending upon the type of environment that is installed.

1. If you install the TS1130 tape drive devices in a stand-alone environment:
   1. Follow the system customization planning steps listed for a stand-alone environment.
   2. Determine the esoteric or generic device names that need to be added to STORAGEGROUP statements in the CBROAMxx member of PARMLIB for the object storage groups that are to use the new devices.
   3. Determine whether to use the global keyword DSNWITHSGNAME on the SETOAM statement in the CBROAMxx member of PARMLIB to append the object storage group name to the OAM object tape data set names. See Object tape data set low-level qualifier enhancement for additional information.
   4. Determine the new data classes that need to be defined in STORAGEGROUP statements in the CBROAMxx member of PARMLIB for the object storage groups that are to use the new encryption format EEFMT3 (by default, the non-encryption recording format EFMT3 is used).
2. If you install the TS1130 tape drive devices in an IBM tape library:
   1. Follow the system customization planning considerations listed for an IBM tape library environment.
   2. Determine the new data classes that need to be defined in STORAGEGROUP statements in the CBROAMxx member of PARMLIB for the object storage groups that are to use the new devices and the new encryption format EEFMT3.
3. In addition, if you install the TS1130 tape drive devices in an OAMplex:
   1. Ensure that the TS1130 tape drive devices are available to all instances of OAM where the full support software is installed.
   2. Determine whether systems exist that will require coexistence support. This situation is particularly important in an OAMplex where at least one system has the full-support software installed and enabled, and at least one system will not have all of the support installed or enabled. Coexistence support is needed if not all of the systems in the OAMplex will be at the same full-support level.
   3. To provide this coexistence support, as appropriate for the support and the release level, install the OAM full-support PTF without the enabling PTF or any separate coexistence support PTF.
   4. Determine when to IPL the host machine after installing the coexistence PTFs, if needed.
4. In an OAM Object Tape environment, any coexistence or full support systems must also have the new overflow-related columns added to the TAPEVOL table in the Optical Configuration Database (OCDB). Only one system in an OAMPlex needs to run CBRSMKBO sample JCL to add the new TAPEVOL columns, but all systems in the OAMplex need to run CBRPBIND. Adding the new TAPEVOL columns and running CBRPBIND is needed with the installation of the PTFs regardless of whether the new TS1130 tape drives are being used.

1. Determine how to setup your tape management systems pooling support to segregate rewritable (MEDIA5, MEDIA7, and MEDIA9) and WORM (MEDIA6, MEDIA8, and MEDIA10) media and also to segregate the standard, economy, and extended length cartridges, as appropriate for your job and application usage.
2. Review the usage of the DEVSUPxx PARMLIB option, ENFORCE_DC_MEDIA, (optional) to ensure that the media type mounted is the media type requested through data class. This can be used in conjunction with the tape management systems pooling support as an additional safety check.
3. Review the existing SMS data class media policies to ensure compatibility with existing tape scratch pool policies before enabling the DEVSUPxx PARMLIB option, ENFORCE_DC_MEDIA.
4. Review the existing SMS data class recording technology policies to ensure that data set policies set to EFMT2 and EEFMT2 are being appropriately used. If a TS1130 tape drive is allocated and the specified data class indicates EFMT2 or EEFMT2, the drive will record in the lower recording technology. Also, remember that the TS1130 does not record in the EFMT1 format, so also review any existing SMS data classes that specify EFMT1 for applicability.
5. Determine the data class updates that are needed to request the appropriate recording format for the TS1130 tape drives. If a TS1130 tape drive is allocated, the default recording format is EFMT3 (non-encryption).
6. Determine if media should use performance segmentation, with a fast access segment to be filled first, and a slower access segment to be filled after. If you decide to use the performance segmentation attribute (available with MEDIA5 and MEDIA9 tape cartridges only, and mutually exclusive with performance scaling), you can:
   1. Define a data class that requests performance segmentation.
   2. Modify or create ACS routines to associate the tape output functions using performance segmentation with a data class that requests performance segmentation.
7. Determine if media should be used at full capacity or scaled for optimal performance. If you decide to use the performance scaling attribute (available with MEDIA5 and MEDIA9 tape cartridges only), you can:
   1. Define a data class that requests performance scaling.
   2. Modify or create ACS routines to associate the tape output functions using performance scaling with a data class that requests performance scaling.
8. Determine how to allocate media to appropriate nonlibrary drives. Consider using the IBM manual tape library. You can also segregate the real drives from the emulating drives, use third-party tape management software, or use customer-written applications.
9. Identify any needed changes to the hardware configuration definition (HCD) to define the new devices.

1. Review the usage of the DEVSUPxx PARMLIB option, MTL_NO_DC_WORM_OK, if the WORM cartridges in the manual tape library environment will be mounted through use of the tape management systems pooling support versus a data class WORM media specification.
2. Determine the 3592 media usage of rewritable (MEDIA5, MEDIA7, and MEDIA9) and WORM (MEDIA6, MEDIA8, and MEDIA10) media and also the usage of the standard, economy, and extended length cartridges. Then make the appropriate data class definition updates to select the appropriate media type. WORM media can only be used if explicitly requested through data class.
3. Review ACS routines for changes needed in selecting tape storage groups and libraries that have the TS1130 tape drive devices.
4. Determine the data class updates that are needed to use the recording technology, media type, and performance scaling or performance segmentation data class attribute (performance scaling or segmentation available with MEDIA5 and MEDIA9 tape cartridges only).
5. Identify any needed changes to the HCD to define the new devices.
6. To define the partitioning category code for MEDIA5, MEDIA6, MEDIA7, MEDIA8, MEDIA9, and MEDIA10 tape cartridges, specify the appropriate parameter of the DEVSUPxx parmlib member.
7. Because the 3592 Model E06 is only downward read (and not write) compatible with the EFMT1 format, you must specify the read-compatible special attribute indicator (in the tape configuration database) or use LABEL=(,,,IN) on the DD statement of JCL to enable the 3592 Model E06 drive to be considered eligible for an EFMT1 request.

The planning steps that you must consider in tape environments that use OAM objects vary depending upon the type of environment that is installed.

1. If you install the TS1130 tape drive devices in a stand-alone environment, follow the storage administration planning steps listed for a stand-alone environment.
2. If you install the TS1130 tape drive devices in an IBM tape library:
   1. Follow the storage administration planning steps listed for an IBM tape library environment.
   2. Review ACS routines for STORE or CTRANS environments and make any changes needed to ensure proper class assignment.
3. If you install the TS1130 tape drive devices in an OAMplex, you must make the devices available to all instances of OAM where the full support is installed.

ISMF panels have been changed to support the two new recording formats, EFMT3 and EEFMT3. See ISMF modifications for TS1130 tape drive for information about ISMF support for the TS1130 tape drive.

• DEVSERV QTAPE
• DISPLAY SMS,VOLUME
• IDCAMS ALTER VOLUMEENTRY
• IDCAMS CREATE VOLUMEENTRY
• IDCAMS DCOLLECT
• IDCAMS LISTCAT
• LIBRARY DISPDRV

• CBRTDSI - Maps the Tape Device Selection Information
• CBRTVI - Maps the Tape Volume Information
• CBRUXCPL - Installation Exit CBRUXCUA Parameter List
• CBRUXEPL - Installation Exit CBRUXENT Parameter List
• CBRUXJPL - Installation Exit CBRUXEJC Parameter List
• CBRUXNPL - Installation Exit CBRUXVNL Parameter List
• DALINCHG - Dynamic Allocation DALINCHG Text Unit
• EDGRDEXT - DFSMSrmm Data Set Extract record
• EDGRVEXT - DFSMSrmm Volume Extract Record
• EDGRXEXT - DFSMSrmm Extended Extract record
• EDGXSF - DFSMSrmm API SFI definitions
• IECUCBCX - Maps the Tape UCB Device Class extension
• IFGTEP - Maps the installation exit main parameter list
• IEZDEB - Maps the data extent block (DEB)
• IHADFVT - Maps the data facilities vector table

• CBR0178I
• CBR0203I
• CBR0206I
• CBR0207I
• CBR0211I
• CBR1083I
• CBR1180I
• CBR1220I
• IEA435I
• IEH623E
• IEH641I
• IGF513I