| System customization: stand-alone
environment |
- Determine whether you will need help from your tape management
system vendor and contact them, if needed.
- Determine the 3592 drives that will have their microcode upgraded
in support of the new media types (MEDIA6, MEDIA7, and MEDIA8) and
ensure that the drives in the same esoteric are at the same support
level. It is recommended that you upgrade all existing 3592 drives
prior to using the new media types.
- 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 whether you will need help from your tape management
system vendor and contact them, if needed.
- Determine the libraries that will be using the new media types
(MEDIA6, MEDIA7, and MEDIA8) and ensure that all 3592 library drives
are upgraded prior to using the new media types. Also, a scratch allocation
for a particular media type may have several libraries that are eligible
for the request (have 3592 drives present), so ensure that all of
the eligible 3592 library drives are upgraded for the new support.
- 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 3592 Model J 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 new 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.
- If you install the new 3592 Model J 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.
- In addition, if you install the new 3592 Model J devices in an
OAMplex:
- Ensure that the new 3592 Model J devices are available to all
instances of OAM where this 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.
- Installation of the full or coexistence support PTF for the new
media types (MEDIA6, MEDIA7, and MEDIA8) brings in support for the
new object tape data set name format. In support of this new function
(even if this function is not used), the DSNFMT column must be added
to the TAPEVOL table in the Optical Configuration Database. Only one
system in an OAMplex needs to run CBRSMPDS to add the TAPEVOL column,
but all systems in the OAMplex need to run CBRPBIND.
- 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 3592 Model J 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 and MEDIA7) and WORM (MEDIA6 and MEDIA8)
media and also to segregate the standard and economy 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.
- 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 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 and MEDIA7)
and WORM (MEDIA6 and MEDIA8) media and also the usage of the standard
and economy 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 3592 Model J devices.
- Determine the data class updates that are needed to use the recording
technology, media type, and performance scaling data class attribute
(performance scaling available with MEDIA5 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,
and MEDIA8, 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 3592 Model J devices in a stand-alone environment,
follow the storage administration planning steps listed for a stand-alone
environment.
- If you install the new 3592 Model J 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 3592 Model J devices in an OAMplex, you
must make the devices available to all instances of OAM where the
full support is installed.
|
z/OS DFSMS Software Support for IBM System Storage TS1140, TS1130, and TS1120 Tape Drives (3592)
Copyright IBM Corporation 1990, 2014