Stand-alone tape environment - Implement the data class policy specifying EEFMT2. Also, specify
as appropriate, the non-encryption recording formats, EFMT1 or EFMT2.
Also, modify or create ACS routines to associate the tape output functions with a data class that has the appropriate recording format
specified.
- Install the Encryption Key Manager (EKM) and set up the key store
it will use.
- 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).
- 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 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.
- Ensure that the required microcode updates for the new media (MEDIA9
and MEDIA10) have been made. 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.
- Make the required installation exit changes.
- Make any needed changes to the HCD to define the new devices.
- 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.
- If performance scaling or performance segmentation is used (available
with MEDIA5 and MEDIA9 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 or performance segmentation attribute.
- 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 encryption-capable TS1120
tape drive drives exclusively because the EEFMT2 recording technology
is not compatible with other recording technologies.
- Install coexistence PTFs as appropriate.
- IPL the system.
|
Required |
|
IBM tape library environment - Implement the data class
policy specifying EEFMT2. Also, specify as appropriate, the non-encryption
recording formats, EFMT1 or EFMT2. Also, modify or create ACS routines
to associate the tape output functions with a data class that has
the appropriate recording format specified.
- Install the Encryption Key Manager (EKM) and set up the key store
it will use.
- 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).
- 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.
- Ensure that the required microcode updates for the new media (MEDIA9
and MEDIA10) have been made. 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.
- Make the required installation exit changes.
- Define or alter existing data class constructs as appropriate,
to specify the EEFMT2 recording technology, MEDIA5, MEDIA6, MEDIA7,
or MEDIA8, MEDIA9, or MEDIA10 media type, and the performance attributes
(performance scaling or performance segmentation available with MEDIA5
and MEDIA9 tape cartridges only).
- Define or alter existing storage group constructs to include libraries
with the new encryption-capable TS1120 tape drive devices.
- Update ACS routines to direct allocation to the encryption-capable
TS1120 tape drive device as requested.
- Validate and activate any new or modified SMS configuration.
- Make any needed changes to the HCD to define the new devices.
- To define the partitioning category code for MEDIA5 MEDIA6, MEDIA7,
or MEDIA8, MEDIA9, or MEDIA10 tape cartridges, specify the appropriate
parameter of the DEVSUPxx parmlib member.
- When systems are sharing a library with 3592 Model E05 (encryption-capable)
installed, install coexistence PTFs as appropriate.
- IPL the system.
|
Required |
|
OAM object tape environment The
migration steps that you must take 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 an OAMplex:
- Make the new encryption-capable TS1120 tape drive devices available
to all instances of OAM where the full support software is installed.
- Install coexistence PTFs as appropriate.
- 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).
- If you install the new encryption-capable TS1120 tape drive devices
in an IBM tape library:
- Follow the migration steps listed for an IBM tape library environment.
- 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.
- Make the needed changes to ACS routines for ALLOC, STORE, or CTRANS
environments.
- If you install the new encryption-capable TS1120 tape drive devices
in a stand-alone environment:
- Follow the migration steps listed for a stand-alone environment.
- 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 encryption-capable TS1120
tape drive drives exclusively because the EFMT2 recording technology
is not compatible with other recording technologies.
- 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).
- Make the needed changes to ACS routines for ALLOC, STORE and CTRANS
environments.
- 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 encryption format EEFMT2.
|
Required |
z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support |
DFSMShsm tape environment 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:
- Define a unique
esoteric for each recording technology.
- 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.
|
Required |
|
Setting up DFSMShsm to use WORM output
tapes for ABACKUP 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.
|
Required |
|