|
The planning steps you must consider to successfully install the
TS1140 tape drive software, vary depending upon the tape environment
you have installed. Table 1 discusses planning
considerations for stand-alone environments (including tape devices
installed in vendors' automated tape libraries) and for IBM tape
library environments.
Table 1. TS1140 tape
drive planning considerationsArea |
Planning Considerations |
---|
System customization: stand-alone
environment |
- Determine which data needs to be encrypted and set up the appropriate
data class policy specifying EEFMT4 (or EEFMT3 for media interchanges).
Also specify, as appropriate, the non-encryption recording formats,
EFMT4 (or EFMT3 for media interchanges). If a TS1140 tape drive tape
drive is allocated, the default recording format is EFMT4. EFMT4 and
EEFMT4 can be used with MEDIA9 through MEDIA13 and MEDIA9 and MEDIA10
can be used with EFMT3 and EEFMT3. Also, modify or create ACS routines
to associate the tape output functions with a data class that has
the appropriate recording format specified.
- 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.
- Determine whether you will need help from your tape management
system vendor and contact them, if needed.
- As appropriate, plan for the installation of the encryption key
manager (IBM Security Key Lifecycle Manager or TKLM) and decide which
of the supported key stores to use.
- 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.
- 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.
- Upgrade 3592 Models E05 and E06 drive microcode to enable the
drives to recognize and enable the EFMT4 and EEFMT4 formatted cartridges
to be relabelled/reused. Also, ensure that VOLNSNS=YES is in the
DEVSUPxx member of PARMLIB.
- 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 EEFMT4 (or EEFMT3 for media interchanges).
Also specify, as appropriate, the non-encryption recording formats,
EFMT4 (or EFMT3 for media interchanges). If a TS1140 tape drive is
allocated, the default recording format is EFMT4. EFMT4 and EEFMT4
can be used with MEDIA9 through MEDIA13 and MEDIA9 and MEDIA10 can
be used with EFMT3 and EEFMT3. Also, modify or create ACS routines
to associate the tape output functions with a data class that has
the appropriate recording format specified.
- Because the TS1140 is only downward read (and not
write) compatible with the EFMT1 format (on MEDIA5 through MEDIA8),
the EFMT2 and EEFMT2 formats (on MEDIA5 through MEDIA10), and the
EFMT3 and EEFMT3 formats (on MEDIA5 through MEDIA8), explicit specification
of the read-compatible special attribute indicator (in the tape configuration
database) or usage of the LABEL=(,,,IN) on the DD statement of JCL
is needed to enable the TS1140 tape drive to be considered eligible
for these volume types.
- 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.
- Determine whether you will need help from your tape management
system vendor and contact them, if needed.
- As appropriate, plan for the installation of the encryption key
manager (IBM Security Key Lifecycle Manager or TKLM) and decide which
of the supported key stores to use.
- 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.
- 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.
- Upgrade 3592 Models E05 and E06 drive microcode to enable the
drives to recognize and enable the EFMT4 and EEFMT4 formatted cartridges
to be relabelled/reused. Also, ensure that VOLNSNS=YES is in the DEVSUPxx member of PARMLIB.
- 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 TS1140 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 EEFMT4 (by default,
the non-encryption recording format EFMT4 is used).
- If you install the TS1140 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
EEFMT4.
- In addition, if you install the TS1140 tape drive devices in an
OAMplex:
- Ensure that the TS1140 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 TS1140 tape drives and DFSMShsm tips. |
Storage administration: stand-alone
tape environment |
- Determine how to setup your tape management systems pooling support
to segregate rewritable (MEDIA9, MEDIA11, and MEDIA13) and WORM (MEDIA10
and MEDIA12) media and also to segregate the extended, advanced, and
economy length cartridges, as appropriate, for your job and application
usage. The older 3592 media types (MEDIA5 through MEDIA8) are supported on the TS1140 only for read requests.
- 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 class policies set to EFMT3 and EEFMT3 are being
appropriately used. If a TS1140 tape drive is allocated and the specified
data class indicates EFMT3 or EEFMT3, the drive will record in the
lower recording technology. Also, remember that the TS1140 can only
write to MEDIA9 and MEDIA10 (EFMT3, EEFMT3, EFMT4, and EEFMT4) and
MEDIA11, MEDIA12, and MEDIA13 (EFMT4 and EEFMT4), so also review any
existing SMS data classes for applicability.
- Determine the data class updates that are needed to request the
appropriate recording format for the TS1140 tape drives. If a TS1140
tape drive is allocated, the default recording format is EFMT4 (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 only with MEDIA9 and MEDIA11 tape cartridges,
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 only with MEDIA9 and MEDIA11 tape cartridges),
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 (MEDIA9, MEDIA11,
and MEDIA13) and WORM (MEDIA10 and MEDIA12) media and also the usage
of the extended, advanced 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 TS1140 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
only with MEDIA9 and MEDIA11 tape cartridges).
- Identify any needed changes to the HCD to define the new devices.
- To define the partitioning category code for MEDIA9, MEDIA10,
MEDIA11, MEDIA12 and MEDIA13 tape cartridges, specify the appropriate
parameter of the DEVSUPxx parmlib member.
- Because the TS1140 is only downward read (and not
write) compatible with the EFMT1 format (on MEDIA5 through MEDIA8),
the EFMT2 and EEFMT2 formats (on MEDIA5 through MEDIA10), and the
EFMT3 and EEFMT3 formats (on MEDIA5 through MEDIA8), explicit specification
of the read-compatible special attribute indicator (in the tape configuration
database) or usage of the LABEL=(,,,IN) on the DD statement of JCL
is needed to enable the TS1140 tape drive to be considered eligible
for the combinations above.
|
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 TS1140 tape drive devices in a stand-alone
environment, follow the storage administration planning steps listed
for a stand-alone environment.
- If you install the TS1140 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 TS1140 tape drive devices in an OAMplex, you
must make the devices available to all instances of OAM where the
full support is installed.
|
Implementing this change could affect these areas of your processing
environment:
Area |
Considerations |
---|
Storage Administration |
The following NaviQuest CLISTs
have changed:
- ACBJBAD1 - Sample job for data class define/alter/display
- ACBJBAL1 – Sample job for tape library define/alter/display
- ACBJBAL5 – Sample job for tape library report
- ACBJBAL6 – Sample job to generate tape library list and
report
- ACBQBAC2 – Generates SMS report
- ACBQBAD1 – CLIST for define/alter/display of data class
- ACBQBAD2 – CLIST for define/alter a data class
- ACBQBAL1 – CLIST for define/alter/ display of tape library
- ACBQBAL2 – CLIST for define/alter tape library
- ACBQBAL3 – CLIST for display of tape library
- ACBQBAL5 – CLIST for report from a saved tape library list
- ACBQBAL6 – CLIST for generating a tape library list
- ACBQFLR2 - ONLINE- SMS config report from DCOLLECT
- ACBQUTR3 – Adds legend to reports for headings DS, DASD
volume & TAPE volume reports from saved table/DCOLLECT
- ACBHELP - CLIST for NaviQuest help
ISMF panels have been changed to support the two new recording
formats, EFMT4 and EEFMT4 and the three new media types MEDIA11, MEDIA12
and MEDIA13. See ISMF modifications for TS1140 tape drive for information about ISMF
support for the TS1140 tape drive.
|
Operations |
These commands have been updated
with this support:
- DEVSERV QLIB,CATS
- DEVSERV QTAPE
- DISPLAY SMS,VOLUME
- IDCAMS ALTER LIBRARYENTRY
- IDCAMS ALTER VOLUMEENTRY
- IDCAMS CREATE LIBRARYENTRY
- IDCAMS CREATE VOLUMEENTRY
- IDCAMS DCOLLECT
- IDCAMS LISTCAT
- LIBRARY DISPDRV
- LIBRARY ENTER
- LIBRARY SETCL
|
Auditing |
None. |
Application development |
The mapping
macros and installation exits listed have been changed for this function.
- 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
Tracking Data Written: An application
may track in KBs, data such as the number of logical bytes written,
the number of physical bytes written, the amount of free space remaining
on a volume, the capacity of the volume, or the number of logical
bytes deleted. With a 1+ TB tape (non-compressed), the possibility
exists with the TS1140 (as well as the TS1130) to overflow some of
the 4-byte fields that contain these values. Of particular concern
would be the logical data-related fields that (with compression) deal
with an amount of data that may be larger than the physical capacity
of the tape. Applications that use, store, and display this type of
information may need to account for and determine how best to handle
an overflow situation. For a signed (4-byte) integer X'7F FF FF
FF' (2,147,483,647 in KBs) supports 2+ TBs and for an unsigned
(4-byte) integer X'FF FF FF FF' (4294967295 in KBs) supports
4+ TBs.
|
Diagnostic procedures |
The messages listed have been changed for
this support.
- CBR0113I
- CBR0114I
- CBR0119I
- CBR1082I
- CBR1083I
- CBR1084I
- CBR1085I
- CBR1180I
- CBR1220I
- CBR1240I
- CBR3015I
- CBR3660A
- CBR3781I
- CBR4105I
- CBR6419I
- IEA435I
- IEH623E
- IEH641I
- IGF513I
|
Automation products |
None. |
General use |
For DFSMSrmm, use the RMM subcommands
ADDVOLUME, CHANGEVOLUME, and SEARCHVOLUME to specify the new media
types (MEDIA11. MEDIA12, and MEDIA13), the recording technology EFMT4
or EEFMT4, and for EEFMT4, the key labels KEYLABEL1/KEYENCODE1 and
KEYLABEL2/KEYENCODE2. |
|