System customization: stand-alone
environment |
- Determine which data needs to be encrypted and set up the appropriate
data class policy specifying EEFMT2. Also specify, as appropriate,
the non-encryption recording formats, EFMT1 or EFMT2. If a encryption-capable
TS1120 tape drive is allocated, the default recording format is EFMT2.
Also, modify or create ACS routines to associate the tape output functions
with a data class that has the appropriate recording format specified.
- 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.
- Determine whether you will need help from your tape management
system vendor and contact them, if needed.
- Plan for the installation of the Encryption Key Manager (EKM)
and decide which of the supported key stores to use.
- 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.
- 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.
- Upgrade 3592 Model J1A and 3592 Model E05 drive microcode to
enable the drives to recognize and enable the EEFMT2 formatted cartridges
to be relabelled/reused. Also, ensure that VOLNSNS=YES is in the
DEVSUPxx member of PARMLIB.
- With availability of the new media (MEDIA9 and MEDIA10), determine
what microcode updates are needed. Prior to using the new media types
(MEDIA9 and MEDIA10), ensure that all 3592 Model E05 drives have had
their microcode upgraded in support of the new media types. Otherwise,
job failures may occur with a 3592 drive with the wrong microcode
level being allocated.
- Determine which systems should have coexistence support and which
systems should have full support.
- Determine when to IPL the host machine after installing the coexistence
PTFs, if needed.
- Determine when to IPL the host machine after installing all necessary
PTFs.
|
System customization: IBM library tape environment |
- Determine which data needs to be encrypted and set up the appropriate
data class policy specifying EEFMT2. Also, specify as appropriate,
the non-encryption recording formats, EFMT1 or EFMT2. If a encryption-capable
TS1120 tape drive is allocated, the default recording format is EFMT2.
Also, modify or create ACS routines to associate the tape output functions
with a data class that has the appropriate recording format specified.
- 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.
- Determine whether you will need help from your tape management
system vendor and contact them, if needed.
- Plan for the installation of the Encryption Key Manager (EKM)
and decide which of the supported key stores to use.
- 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.
- 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.
- Upgrade 3592 Model J1A and 3592 Model E05 microcode to enable
the library drives to recognize and enable the EEFMT2 formatted cartridges
to be relabelled/reused. Also, ensure that VOLNSNS=YES is in the
DEVSUPxx member of PARMLIB.
- With availability of the new media (MEDIA9 and MEDIA10), determine
what microcode updates are needed. Prior to using the new media types
(MEDIA9 and MEDIA10), ensure that all 3592 Model E05 drives have had
their microcode upgraded in support of the new media types. Otherwise,
job failures may occur with a 3592 drive with the wrong microcode
level being allocated.
- Identify the installation exit changes that are needed.
- Determine which systems should have coexistence support and which
systems should have full support.
- Determine when to IPL the host machine after installing the coexistence
PTFs, if needed.
- Determine when to IPL the host machine after installing all necessary
PTFs.
|
System customization: OAM object tape environment |
The planning steps that you must consider in tape
environments that use OAM objects vary depending upon the type of
environment that is installed.
- If you install the new encryption-capable TS1120 tape drive devices
in a stand-alone environment:
- Follow the system customization planning steps listed for a stand-alone
environment.
- 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.
- 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.
- 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 EEFMT2.
- If you install the new encryption-capable TS1120 tape drive devices
in an IBM tape library:
- Follow the system customization planning considerations listed
for an IBM tape library environment.
- 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
EEFMT2.
- In addition, if you install the new encryption-capable TS1120
tape drive devices in an OAMplex:
- Ensure that the new encryption-capable TS1120 tape drive devices
are available to all instances of OAM where the full support software
is installed.
- 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.
- 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.
- Determine when to IPL the host machine after installing the coexistence
PTFs, if needed.
|
System customization: DFSMShsm |
See Implementation considerations for using encryption-capable TS1120 tape drives and DFSMShsm tips. |
Storage administration: stand-alone
tape environment |
- 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 their job and application
usage.
- 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.
- 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.
- Review the existing SMS data class recording technology policies
to ensure that data set policies set to EFMT1 are being appropriately
used. If a encryption-capable TS1120 tape drive is allocated and the
specified data class indicates EFMT1, the drive will record in the
lower recording technology.
- Determine the data class updates that are needed to request the
appropriate recording format for the encryption-capable TS1120 tape
drives. If an encryption-capable TS1120 tape drive is allocated,
the default recording format is EFMT2 (non-encryption).
- 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:
- Define a data class that requests performance segmentation.
- Modify or create ACS routines to associate the tape output functions
using performance segmentation with a data class that requests performance
segmentation.
- 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:
- Define a data class that requests performance scaling.
- Modify or create ACS routines to associate the tape output functions
using performance scaling with a data class that requests performance
scaling.
- 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.
- Identify any needed changes to the hardware configuration definition
(HCD) to define the new devices.
|
Storage administration: IBM tape library
environment |
- 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.
- 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.
- Review ACS routines for changes needed in selecting tape storage
groups and libraries that have the new encryption-capable TS1120 tape
drive devices.
- 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).
- Identify any needed changes to the HCD to define the new devices.
- 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.
|
Storage administration: OAM object tape
environment |
The planning steps that you must consider in tape environments
that use OAM objects vary depending upon the type of environment that
is installed.
- If you install the new encryption-capable TS1120 tape drive devices
in a stand-alone environment, follow the storage administration planning
steps listed for a stand-alone environment.
- If you install the new encryption-capable TS1120 tape drive devices
in an IBM tape library:
- Follow the storage administration planning steps listed for an
IBM tape library environment.
- Review ACS routines for STORE or CTRANS environments and make
any changes needed to ensure proper class assignment.
- If you install the new encryption-capable TS1120 tape drive devices
in an OAMplex, you must make the devices available to all instances
of OAM where the full support is installed.
|