Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Implementing DFSMShsm tape environments z/OS DFSMShsm Implementation and Customization Guide SC23-6869-01 |
|
You can implement a DFSMShsm tape environment by specifying SETSYS commands and placing them in the PARMLIB member ARCCMDxx. The parameters that you select define your site’s tape processing environment. SETSYS command parameters are different for each site depending on the mix of tape devices, the pools from which these devices select output tapes, and whether the tapes are in an SMS-managed library. The tape environment, as shown in Figure 1, is defined by the way libraries, tapes, devices, and performance are managed. (The way tapes are managed determines their life cycle as they enter a scratch pool, are selected for output, are inventoried, recycled, and finally returned to a scratch pool.) The way devices are managed determines how they are selected for use, are allocated, and eventually are mounted with tapes. The way you manage performance determines the level of automation and tape utilization at your site. Figure 1. Tape Management Planning Areas
The information in the following topics can help you to understand
and then to implement DFSMShsm:
Note: The following discussions relate to SMS-managed tape
environments and non-SMS managed tape environments. SMS-managed tape
environments refer to environments that support using the SMS Automatic
Class Selection routines to direct tape drive allocations, including IBM® 3494 and IBM 3495 Tape Library Data Server, and the IBM 3494 Virtual Tape Server. Non-SMS
managed tape environments refer to environments that rely on esoteric
tape devices to determine allocation, such as stand alone tape drive
models, IBM 3494 Tape Library
Data Server models managed by Basic Tape Library Support (BTLS), and
the non-IBM tape robotic system.
|
Copyright IBM Corporation 1990, 2014
|