Stand-alone tape environment - 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 3592 Model E05 drives
exclusively because the EFMT2 recording technology is not compatible
with other recording technologies.
- Install coexistence PTFs as appropriate.
- IPL the system.
|
Required |
|
IBM tape library
environment - Define or alter existing data class
constructs as appropriate, to specify the EFMT1 or EFMT2 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 3592 Model E05 devices.
- Update ACS routines to direct allocation to the 3592 Model E05
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 J devices 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
3592 Model E05 devices in an OAMplex:
- Make the new 3592 Model E05 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).
- IPL the system.
- If you install the new 3592 Model E05 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 3592 Model E05 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 3592 Model E05 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.
|
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 |
|