z/os dfsms oam planning, installation, and storage ... · pdf filez/os dfsms oam planning,...

722
z/OS DFSMS Object Access Method Planning, Installation, and Storage Administration Guide for Object Support Version 2 Release 3 SC23-6866-30 IBM

Upload: vukhanh

Post on 04-Mar-2018

453 views

Category:

Documents


39 download

TRANSCRIPT

  • z/OS

    DFSMS Object Access Method Planning,Installation, and Storage AdministrationGuide for Object SupportVersion 2 Release 3

    SC23-6866-30

    IBM

  • NoteBefore using this information and the product it supports, read the information in Notices on page 655.

    This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modificationsuntil otherwise indicated in new editions.

    Last updated: July 17, 2017

    Copyright IBM Corporation 1986, 2017.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

  • Contents

    Figures . . . . . . . . . . . . . . vii

    Tables . . . . . . . . . . . . . . . ix

    About This Document . . . . . . . . xiRequired product knowledge . . . . . . . . xiz/OS information . . . . . . . . . . . . xiHow to Read Syntax Diagrams . . . . . . . . xii

    How to send your comments to IBM . . xvIf you have a technical problem . . . . . . . xv

    Summary of changes . . . . . . . . xviiSummary of changes for z/OS Version 2 Release 3 xviiSummary of changes for z/OS Version 2 Release 2 xxSummary of changes for z/OS Version 2 Release 1 xx

    z/OS Version 2 Release 1 summary of changes xxi

    Chapter 1. Understanding the ObjectAccess Method . . . . . . . . . . . 1Comparing multiple OAM and classic OAMconfigurations . . . . . . . . . . . . . . 2Collections . . . . . . . . . . . . . . . 3Application programming interface (OSREQ macro) 3System-managed storage for data and spacemanagement . . . . . . . . . . . . . . 4Moving objects throughout the hierarchy . . . . . 6Hardware and software interaction with OAM . . . 6Parallel Sysplex and OAM . . . . . . . . . . 8

    OAMplex . . . . . . . . . . . . . . 8Shipping request limitations for larger dataobjects . . . . . . . . . . . . . . . 10OAMplex restrictions . . . . . . . . . . 10OAMplex and file systems . . . . . . . . 11

    OAM components . . . . . . . . . . . . 11Protecting against inadvertent object deletion . . . 12CBROAMxx PARMLIB member statements . . . . 14

    SETDISK statement for file systems used byOAM . . . . . . . . . . . . . . . 14SETOAM statement for object tape volumes . . 14SETOPT statement for options . . . . . . . 14SETOSMC statement for OSMC processing . . . 15SETTLIB statement for tape library settings . . . 15OAMXCF statement for parallel sysplexes . . . 15ONLYIF statement for parallel sysplexes. . . . 15

    ISMF library management role within OAM . . . 16Installation storage management policy overview. . 16SMS constructs and ACS routines . . . . . . . 18

    Understanding the storage group construct . . . 19Understanding the storage class construct . . . 27Understanding the management class construct 32Understanding the data class construct . . . . 33ACS routines . . . . . . . . . . . . . 35

    OAM address space . . . . . . . . . . . 36

    MEMLIMIT for OAM . . . . . . . . . . . 37OTIS address space . . . . . . . . . . . . 38Optical storage . . . . . . . . . . . . . 38

    Optical disk cartridges. . . . . . . . . . 39Optical recording techniques . . . . . . . 39Optical volumes . . . . . . . . . . . . 41Optical media types . . . . . . . . . . 42Optical disk drives . . . . . . . . . . . 43Optical libraries . . . . . . . . . . . . 44

    Tape storage . . . . . . . . . . . . . . 48Tape capacity and compaction . . . . . . . 54Tape capacity and performance scaling . . . . 55Performance segmentation considerations . . . 55KB tracking . . . . . . . . . . . . . 56Tape encryption support . . . . . . . . . 56Tape volumes. . . . . . . . . . . . . 58Tape drives . . . . . . . . . . . . . 63Tape libraries . . . . . . . . . . . . . 66

    Object tape and optical volume management . . . 66Recycling tape and optical volumes . . . . . 67Deleting tape and optical volumes. . . . . . 67Deleting recovered tape and optical volumes . . 67

    Chapter 2. Planning for OAMinstallation . . . . . . . . . . . . . 69Setting up the planning team . . . . . . . . 69Analyzing your business environment . . . . . 70

    Grouping objects . . . . . . . . . . . 71Establishing performance objectives . . . . . 71Identifying management cycles . . . . . . . 72Concluding the business analysis phase . . . . 77

    Analyzing your processing environment. . . . . 77Hardware . . . . . . . . . . . . . . 78Software . . . . . . . . . . . . . . 79

    Estimating resource requirements . . . . . . . 80General requirements . . . . . . . . . . 81DASD storage . . . . . . . . . . . . 81Object storage on removable media . . . . . 86Concluding resource estimation . . . . . . 90

    Planning to use a file system . . . . . . . . 90Security configuration for the file system . . . 91

    Preparing the physical environment . . . . . . 93Preparing for installation and customization . . . 93Planning to program applications for OAM. . . . 94Planning to administer OAM . . . . . . . . 94Preparing to operate OAM . . . . . . . . . 94OAM planning case study . . . . . . . . . 95

    Object characterization . . . . . . . . . 95Resource estimation . . . . . . . . . . 98

    Chapter 3. Migrating, installing, andcustomizing OAM . . . . . . . . . 107Verifying hardware and software prerequisites . . 108Preparing the processing environment . . . . . 108Preparing for migration or installation . . . . . 108

    Copyright IBM Corp. 1986, 2017 iii

    |||

  • High-level installation and migration checklists 1091 Changing DB2 installation parameters . . . 1132 Changing CICS installation parameters . . 1143 Configure the z/OS Unix file system . . . 1164 Modifying the installation exit to managedeleted objects . . . . . . . . . . . . 1175 Changing system libraries . . . . . . . 1176 Creating DB2 databases for object tables anddirectories . . . . . . . . . . . . . 1717 Creating the OAM configuration database 1768 Merging object tables and OCDB for anOAMplex. . . . . . . . . . . . . . 1779 Creating and binding DB2 packages . . . 17810 OSR application plans. . . . . . . . 17911 OSMC application plans . . . . . . . 18012 LCS, ISMF, and OSR application plans . . 18113 Verifying DB2 installation . . . . . . 18214 IPL the system . . . . . . . . . . 18315 Specifying the SMS definitions andprograms used by OAM. . . . . . . . . 18416 Running the OAM Installation VerificationProgram for object support . . . . . . . . 20617 Adding new tape devices to the OAMobject tape configuration . . . . . . . . 20718 Global z/OS UNIX configuration for OAMusage . . . . . . . . . . . . . . . 207

    Specialized OAM installation procedures . . . . 207Procedures for moving OAM to another system 207Merging OAMs into an OAMplex . . . . . 208Adding OAM systems to an existing OAMplex 209

    Chapter 4. Administering OAM . . . . 211Monitoring and maintaining the OAMconfiguration using ISMF . . . . . . . . . 212

    ISMF library management . . . . . . . . 212Typical ISMF library management procedures 212

    Monitoring and maintaining optical volumes . . . 217ISMF Mountable Optical Volume Application 217Handling OAM scheduling errors . . . . . 226

    Monitoring and maintaining SMS constructdefinitions . . . . . . . . . . . . . . 227

    Changing SMS construct definitions . . . . . 227Monitoring DB2 databases . . . . . . . . . 230

    DB2 RUNSTATS utility . . . . . . . . . 230DB2 STOSPACE utility . . . . . . . . . 231SQL statements . . . . . . . . . . . . 231

    Tuning OAM . . . . . . . . . . . . . 232Tuning OAM connections to DB2. . . . . . 232Tuning the DB2 databases . . . . . . . . 232Tuning object retrieval response time . . . . 240Recalling objects to disk . . . . . . . . . 241Tuning the storage management cycle . . . . 242Balancing library usage . . . . . . . . . 245Using appropriate transport classes within XCF 245

    Measuring OAM transaction performance usingSMF . . . . . . . . . . . . . . . . 247

    OAM SMF record subtypes. . . . . . . . 248OAM SMF start and end time accuracy. . . . 249

    Establishing recovery procedures . . . . . . . 250Recovering DB2 databases . . . . . . . . 250Recovering file system directories . . . . . 250

    Recovering single objects from removable media 251Recovering an entire optical cartridge or tapevolume . . . . . . . . . . . . . . 251Accessing backup objects automatically. . . . 252

    Using the Move Volume utility . . . . . . . 253Preparation of the Move Volume utilityenvironment. . . . . . . . . . . . . 255Reusing recycled tape and optical volumes . . 262Deleting recycled tape and optical volumes fromOAM . . . . . . . . . . . . . . . 264Starting tape recycle . . . . . . . . . . 265

    Expiring tape and optical volumes . . . . . . 265Expiring tape volumes in object or objectbackup storage groups . . . . . . . . . 265Expiring optical volumes in object or objectbackup storage groups . . . . . . . . . 267Using the OAM Object Tape Volume Return toMVS Scratch exit routine . . . . . . . . 268Synchronizing OAM scratch tape . . . . . . 272

    Processing object expiration . . . . . . . . 273Destroying and deleting expired data . . . . . 274

    Diagnosing nondeletion/expiration of objectsduring OSMC processing . . . . . . . . 275Checking CBRHADUX . . . . . . . . . 275Objects not selected for expiration processing byOSMC. . . . . . . . . . . . . . . 275Diagnosing unexpected results of objectmovement during OSMC processing . . . . 277

    Invoking the OSREQ macro through the OSREQTSO/E command processor . . . . . . . . 280

    OSREQ TSO/E command syntax . . . . . . 281OSREQ TSO/E command processor returncodes . . . . . . . . . . . . . . . 289

    3995 optical service information messages . . . . 290

    Chapter 5. Operating OAM and OTISaddress spaces and OSMC functions . 293Overview of operator tasks . . . . . . . . . 293Message format conventions . . . . . . . . 294Overview of operator commands . . . . . . . 295Starting OTIS . . . . . . . . .