IBM Tivoli Advanced Backup and Recovery for z/OS: …publib.boulder.ibm.com/tividd/td/ITABaRfzOS/SC23-9730-00/en_US/PD… · IBM Tivoli Advanced Backup and Recovery for z/OS User's

IBM Tivoli Advanced Backup and Recovery for z/OS

User's Guide Version 2 Release 1

SC23-9730-00IBM Confidential

Note Before using this information and the product it supports, read the information in Appendix R, Notices, on page 567.

This edition applies to Version 2, Release 1, of IBM Tivoli Backup and Recovery for z/OS (product number 5698B17) and to all subsequent releases and modifications until otherwise indicated in new editions.

Copyright International Business Machines Corporation 1996, 2008. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM Confidential

Contents

Figures . . . . . . . . . . . . . . . xi

Tables . . . . . . . . . . . . . . . xiii

About this guide . . . . . . . . . . xv Intended audience for this guide . . . . . . . xv Publications . . . . . . . . . . . . . . xv

Accessing publications online . . . . . . . xvi Ordering publications . . . . . . . . . . xvi

Accessing terminology online . . . . . . . . xvi Tivoli technical training . . . . . . . . . . xvii Support information . . . . . . . . . . . xvii Conventions used in this publication . . . . . xvii

Typeface conventions . . . . . . . . . xvii

Chapter 1. Advanced Backup and Recovery for z/OS Overview . . . . . . 1 Automated Critical Data Identification . . . . . . 3

Automated Critical Data Identification features and benefits . . . . . . . . . . . . . 3 Automated Critical Data Identification components . . . . . . . . . . . . . . 5 Automated Critical Data Identification architecture and processing . . . . . . . . . . . . . 6 Application monitoring . . . . . . . . . . 8

Critical Backup Tracking and Inventory . . . . . 9 Critical Backup Tracking and Inventory features and benefits . . . . . . . . . . . . . 9 Critical Backup Tracking and Inventory components . . . . . . . . . . . . . 10 How Critical Backup Tracking and Inventory tracks backups . . . . . . . . . . . . 11 Backup utilities tracked by Critical Backup Tracking and Inventory . . . . . . . . . 11 Tracking and restoration of VSAM KSDSs with alternate indexes . . . . . . . . . . . 12

ABARS Manager overview . . . . . . . . . 12 Advanced Backup and Recovery for z/OS scenarios 14

Disaster recovery using Automated Critical Data Identification and Critical Backup Tracking and Inventory . . . . . . . . . . . . . . 14 Using Critical Backup Tracking and Inventory to centralize and inventory backups . . . . . . 15

Chapter 2. Installing Advanced Backup and Recovery for z/OS . . . . . . . . 17 Installation overview . . . . . . . . . . . 17

Advanced Backup and Recovery for z/OS data sets . . . . . . . . . . . . . . . . 17 ABARS selection data set . . . . . . . . . 19 Using the ARCSKEXT and ARCCREXT ABARS exits . . . . . . . . . . . . . . . . 20 About using the ARCBEEXT exit . . . . . . 20 APF authorization requirements . . . . . . 21

About dataspaces . . . . . . . . . . . 21 Determining the possible impact of running Advanced Backup and Recovery for z/OS with your EBCDIC code tables . . . . . . . . . 21

About the installation process . . . . . . . . 21 Step 1: Tailor Advanced Backup and Recovery for z/OS appropriately for your installation . . . . . 22 Step 2: Copy installed files to new production libraries . . . . . . . . . . . . . . . 22 Step 3: Continue the installation and configuration process . . . . . . . . . . . . . . . . 22

Chapter 3. Configuring an initial Advanced Backup and Recovery for z/OS installation . . . . . . . . . . . 23 Step 1: APF authorize the product LOAD library . . 23 Step 2: Run BKMIMERG to create a new BKMINI PARMLIB member . . . . . . . . . . . . 23 Step 3: Code the variables in the BKMINI PARMLIB member . . . . . . . . . . . . . . . 24 Step 4: Run BKMJCLBL . . . . . . . . . . 25 Step 5: Create the Automated Critical Data Identification database . . . . . . . . . . . 25 Step 6: Create the DAD database . . . . . . . 27 Step 7: Create the Advanced Backup and Recovery for z/OS Inventory Data Set (IDS) . . . . . . . 27 Step 8: Ensure adequate TSO address space region size . . . . . . . . . . . . . . . . . 27 Step 9: Verify the product installation and configuration . . . . . . . . . . . . . . 28 Step 10: Specify and display EBCDIC characters . . 28 Post-installation tasks . . . . . . . . . . . 28

Task 1: Update cross-system ENQ lists . . . . 29 Task 2: Verify that the configuration values were set in BKMINI . . . . . . . . . . . . 29 Task 3: Provide access authority . . . . . . 30 Task 4: Update the JCL librarys BKMBPROC and BKMRPROC members . . . . . . . . . . 30 Task 5: Add BKMWABAR to the TMOEDMxx file 30 Task 6: Replace the DFHSMABR procedure . . . 30 Task 7: Modify member ARCCMDxx in the DFSMShsm PARMLIB . . . . . . . . . . 31 Task 8: Update the ACF$CMD system security command table . . . . . . . . . . . . 32 Task 9: Set up ABARS Monitor . . . . . . . 32 Task 10: Set up the SDSL VOL option . . . . . 32 Task 11: Load the demonstration aggregates . . 33 Task 12: Add security for primary and line commands . . . . . . . . . . . . . . 33 Task 13: Define security class profiles for CATSCRUB . . . . . . . . . . . . . 33 Task 14: Edit the FDR_LOADLIB token in BKMINI . . . . . . . . . . . . . . 33 Task 15: Edit the ADABAS_LOADLIB token in BKMINI . . . . . . . . . . . . . . 34

IBM Confidential

Copyright IBM Corp. 1996, 2008 iii

Task 16: Define the security class profiles for the Critical Backup Tracking and Inventory started task . . . . . . . . . . . . . . . . 34 Task 17: Specify the SMF/JCL collection method 34 Task 18: Define security profiles . . . . . . 35 Task 19: Set up foreground verification . . . . 36 Task 20: Verify that the Automated Critical Data Identification selection data sets are physical sequential . . . . . . . . . . . . . . 36 Task 21: Turn off PF key function display . . . 36

Setting up the Advanced Backup and Recovery for z/OS started tasks . . . . . . . . . . . . 36

Step 1: Run BKMRSPSU to allocate and initialize the RSP data sets . . . . . . . . . . . 39 Step 2: Edit the Advanced Backup and Recovery for z/OS PARMLIB member BKMINI . . . . 40 Step 3: Allocate and initialize the BKMSTSKA data sets . . . . . . . . . . . . . . 41 Step 4: Create the BKMSTSKD log data set . . . 41 Step 5: Create the BKMSTSKD MSGQUEUE data set . . . . . . . . . . . . . . . . 42 Step 6: Modify BKMSTSKA and add it to a system PROCLIB . . . . . . . . . . . 42 Step 7: Modify BKMSTSKD and add it to a PROCLIB . . . . . . . . . . . . . . 42 Step 8: Copy BKMSTSKR to a system PROCLIB 42 Step 9: Enable the required exits in SMFPRMxx 43 Step 10: Run BKMBLDJB to build the JOBFLAT file . . . . . . . . . . . . . . . . 44 Step 11: Start the BKMSTSKA started task . . . 44 Step 12: Start the BKMSTSKD started task . . . 44 Step 13: Start the BKMSTSKR started task . . . 45 Step 14: Track critical messages . . . . . . . 46

Running BKMMODLV to validate the load module contents . . . . . . . . . . . . . . . 46 Applying maintenance . . . . . . . . . . . 48

Chapter 4. Accessing Advanced Backup and Recovery for z/OS features 49 Accessing Automated Critical Data Identification . . 49 Using the Automated Critical Data Identification Scroller . . . . . . . . . . . . . . . . 49 Accessing ABARS Manager . . . . . . . . . 49 Accessing Critical Backup Tracking and Inventory 50 Accessing CATSCRUB . . . . . . . . . . . 50 Searching for data sets . . . . . . . . . . . 51 Accessing reports . . . . . . . . . . . . 51 Accessing the ABARS Monitor feature . . . . . 52 Accessing the event history feature . . . . . . 53 Accessing online help . . . . . . . . . . . 53 Using the action bar . . . . . . . . . . . 53 Preferences . . . . . . . . . . . . . . 54

Specifying preferences for displaying data set space usage information . . . . . . . . . 54 Specifying default job card information . . . . 55

Utilities . . . . . . . . . . . . . . . . 56 Loading activity logs into the IDS . . . . . . 56 Reloading extracted data into the IDS . . . . 56 Unloading data from the IDS . . . . . . . 57 Resetting the category conflict backup options for aggregates . . . . . . . . . . . . . . 58

Accessing the DAD task monitor . . . . . . 58 Specifying backup utility equivalents . . . . . . 59 Viewing Advanced Backup and Recovery for z/OS messages . . . . . . . . . . . . . . . 59

Message identifier naming conventions . . . . 59 Determining which MESSAGES member contains a messages description . . . . . . . . . 59 Using the product interface to view messages . . 60 Browsing the Messages library . . . . . . . 60

Chapter 5. Using Automated Critical Data Identification to identify critical data . . . . . . . . . . . . . . . . 61 Identifying applications and job streams . . . . . 62 Identifying anchor jobs and tables . . . . . . . 63 Application checklist . . . . . . . . . . . 63

Chapter 6. Defining an application to Automated Critical Data Identification . 65 Specifying Application General Setup options . . . 66 Specifying Job Collection options . . . . . . . 67 Specifying Collection options . . . . . . . . 68 Specifying RSP options . . . . . . . . . . 68 Specifying JCL options . . . . . . . . . . 69 Specifying Batch SMF Scan options . . . . . . 69 Specifying Current Verification options . . . . . 70

Including or excluding data sets from the selection data set . . . . . . . . . . . 72

Specifying Verification GDG options . . . . . . 73 How generation data sets are added to the Automated Critical Data Identification Application Data Inventory . . . . . . . . 76

Specifying Backup options . . . . . . . . . 77 Specifying selection data sets options . . . . . . 77

Chapter 7. Performing a job collection 79 Understanding job elements . . . . . . . . . 79 Identifying the job elements associated with an application . . . . . . . . . . . . . . 80 Determining a starting collection point . . . . . 81 Using a job scheduling interface to perform job collection . . . . . . . . . . . . . . . 81

Performing job collection with ASG-Zeke . . . 82 Performing job collection with CONTROL-M . . 84 Performing job collection with Cybermation ESP 89 Performing job collection with TWS . . . . . 91 Performing job collection with Unicenter CA-7 92 Performing job collection with Unicenter CA-Jobtrac . . . . . . . . . . . . . . 94

Using an input data set to perform job collection . . 99 Formatting job entries for input data sets . . . 99 Defining job structure for input data sets . . . 100 Using ISPF Edit to perform job collection . . . 102 Using a pre-staged data set to perform job collection . . . . . . . . . . . . . . 103 Using a user-supplied data set to perform job collection . . . . . . . . . . . . . . 104

Modifying a job scheduling product job list or structure . . . . . . . . . . . . . . . 104 Viewing job collection results . . . . . . . . 104

IBM Confidential

iv IBM Tivoli Advanced Backup and Recovery for z/OS: User's Guide

Chapter 8. Identifying application data sets using RSP . . . . . . . . . . 105 RSP components and processing . . . . . . . 105 Creating the job table . . . . . . . . . . . 106 Updating the job table . . . . . . . . . . 107 Running the application . . . . . . . . . . 107 Running the BKMAPLEN step or job . . . . . 107

How BKMAPLEN builds the selection data set 108 Modifying the BKMAPLEN JCL . . . . . . 109 BKMAPLEN JCL parameters . . . . . . . 109 Using VDR filter lists during BKMAPLEN processing . . . . . . . . . . . . . 110

Using RSP Monitor . . . . . . . . . . . 110 Displaying RSP status . . . . . . . . . 110 Displaying RSP statistics . . . . . . . . . 111 Displaying the current job table . . . . . . 113 Displaying the current filter table . . . . . . 114 RSP commands . . . . . . . . . . . . 114

Viewing the RSP message log . . . . . . . . 115 Viewing captured SMF and JCL records . . . . 115 RSP operational considerations . . . . . . . 115

Reducing the amount of data to be processed by RSP . . . . . . . . . . . . . . . . 115 RSP cycle considerations . . . . . . . . . 115 Increasing the RSP buffer size . . . . . . . 116 RSP IPL considerations . . . . . . . . . 116 RSP and system outages . . . . . . . . . 117 RSP and the overflow data set . . . . . . . 117 RSP JCL members . . . . . . . . . . . 118

Chapter 9. Identifying application data sets using batch SMF Scan . . . . . 121 The batch SMF Scan process . . . . . . . . 121 Batch SMF Scan guidelines . . . . . . . . . 121 SMF record requirements . . . . . . . . . 122 Creating required batch SMF data sets . . . . . 123 Using SMF Scan to collect SMF data . . . . . . 123 Optional SMF Scan parameters . . . . . . . 124 Viewing the results of the SMF collection . . . . 125 Submitting the SMF Scan job . . . . . . . . 125 Viewing the results of the batch SMF Scan . . . . 125

Chapter 10. Using Verification to create a selection data set . . . . . . 127 Building the selection data set in the foreground 127 Building the selection data set in batch . . . . . 128 Verification output selection formats and data set types . . . . . . . . . . . . . . . . 128 ABARS selection data sets . . . . . . . . . 129

ABARS selection data set contents . . . . . 130 ABARS output format example . . . . . . 130

Non-ABARS selection data sets . . . . . . . 131 Non-ABARS selection data set contents . . . . 131 DSS output format example . . . . . . . 131

Adding data sets to the selection data set during Verification . . . . . . . . . . . . . . 132 Viewing the results of the Verification . . . . . 132 Scheduling application backups . . . . . . . 132 Using Verification to re-evaluate data . . . . . 133

Chapter 11. Obtaining application information . . . . . . . . . . . . 135 Displaying a list of application information . . . 135 Displaying the status of an application . . . . . 135

Displaying the current job list . . . . . . . 136 Displaying current job anchor chains . . . . 136 Displaying data set detail records . . . . . 137 Displaying current JCL and SMF DSN entries 138 Displaying current JCL and SMF DSN entries with URD information . . . . . . . . . 142 Displaying a summary of the last selection data set . . . . . . . . . . . . . . . . 143 Browsing a selection data set . . . . . . . 143

Chapter 12. Filters and controls . . . 145 Filter levels . . . . . . . . . . . . . . 145

Universal filters . . . . . . . . . . . 146 Global filters . . . . . . . . . . . . 146 Local filters . . . . . . . . . . . . . 147

Filter types . . . . . . . . . . . . . . 147 Data set Retention filters . . . . . . . . 147 Data set Evaluation filters . . . . . . . . 148 Job collection filters . . . . . . . . . . 148

Filter categories . . . . . . . . . . . . 148 Defining Universal and Global filters . . . . . 149

Data set Retention filter syntax . . . . . . 149 KEEP only or EVAL only examples . . . . . 151 Data set Evaluation filter syntax . . . . . . 152 Data set Include filters (INClude ACCOMPany, and ALLOCate keywords) . . . . . . . . 153

Defining Local filters . . . . . . . . . . . 154 Defining Local filters (Retention and Evaluation filters) . . . . . . . . . . . . . . . 154 Defining Local filters for job collection . . . . 155

How filters and controls work for GDSs and Verification GDG rules . . . . . . . . . . 157 Reviewing the results of application filtering . . . 158 Filtering guidelines . . . . . . . . . . . 158

Chapter 13. Getting started with Critical Backup Tracking and Inventory . . . . . . . . . . . . . 161 Identifying involved images; set up and start the intercept tasks . . . . . . . . . . . . . 161 Creating test scenarios . . . . . . . . . . 161 Restore scenario considerations . . . . . . . 161 BKMBLDRJ options and skeleton variations . . . 162 Relative date masking . . . . . . . . . . 163

Chapter 14. Critical Backup Tracking and Inventory setup and configuration 165 Preparing to track backup data using Critical Backup Tracking and Inventory . . . . . . . 165 Batch intercept file (BIF) filters . . . . . . . 165

Critical Backup Tracking and Inventory . . . 166 Application Backup and Restore . . . . . . 202

IBM Confidential

Contents v

Chapter 15. Setup and configuration for using Advanced Backup and Recovery for z/OS . . . . . . . . . 211 Setting up aggregate management . . . . . . 211

Using line commands to manage aggregates . . 212 Adding an aggregate to the IDS . . . . . . 213 Submitting an ABARS Manager backup of an aggregate . . . . . . . . . . . . . . 214 About concurrent copy . . . . . . . . . 215 Changing an aggregate in the IDS . . . . . 216 Deleting an aggregate from the IDS . . . . . 216 Viewing aggregate information . . . . . . 217 Browsing an aggregates instruction data set . . 218 Editing an aggregates instruction data set . . . 219 Browsing an aggregates SDSL parameters . . . 219 Converting an aggregates selection data set to SDSL parameters . . . . . . . . . . . 219 Editing an aggregates SDSL parameters . . . 220 Browsing an aggregates selection data sets . . 220 Editing an aggregates selection data set . . . 221

Setting up group filter management . . . . . . 222 Adding a group filter . . . . . . . . . . 222 Deleting a group filter . . . . . . . . . 223 Editing a group filter . . . . . . . . . . 223

Chapter 16. Managing ABARS events 225 Displaying a list of ABARS events . . . . . . 225

Viewing ABACKUP or ARECOVER data set name lists . . . . . . . . . . . . . 226 Viewing ABACKUP or ARECOVER event detail 226 Displaying space usage information for an aggregate . . . . . . . . . . . . . . 226 Viewing summary information for an ABACKUP or ARECOVER event . . . . . . 227 Viewing ABACKUP or ARECOVER event activity logs . . . . . . . . . . . . . 230 Viewing ARECOVER input conflict data sets 230 Viewing ABACKUP or ARECOVER event errors 231 Viewing ABACKUP instruction data sets . . . 232 Viewing restart data sets used as input to an ARECOVER event . . . . . . . . . . . 232 Viewing restart data sets created as output from an ARECOVER event . . . . . . . . . . 233 Viewing ABACKUP selection data sets . . . . 233 Deleting an ABARS event record . . . . . . 233 Submitting an ABACKUP for an aggregate . . 234 About concurrent copy . . . . . . . . . 234 Changing an aggregates IDS information . . . 235 Monitoring ABACKUPs and ARECOVERS as they execute . . . . . . . . . . . . . 235 Searching for ABACKUP data set overlap . . . 236 Submitting a non-incremental ARECOVER . . 236 Submitting an incremental ARECOVER . . . 237 About using the FullRename feature with ARECOVER . . . . . . . . . . . . . 238 Submitting a RECOVER of ABARS D file data using DFSMSdss . . . . . . . . . . . 246 Browsing an aggregates instruction data set . . 247 Editing an aggregates ARECOVER conflict data set . . . . . . . . . . . . . . . . 247

Browsing an aggregates SDSL parameters . . . 248 Editing an aggregates SDSL parameters . . . 248 Browsing an aggregates selection data set . . . 248 Editing an aggregates selection data set . . . 249 Browsing an aggregates cataloged ARECOVER restart data set . . . . . . . . . . . . 249 Editing an aggregates cataloged ARECOVER restart data set . . . . . . . . . . . . 249 Browsing an aggregates ARECOVER conflict data set . . . . . . . . . . . . . . 250 Editing an aggregates ARECOVER conflict data set . . . . . . . . . . . . . . . . 250

About logical aggregate management . . . . . 251 Accessing the logical aggregate management feature . . . . . . . . . . . . . . 251 Creating a logical aggregate . . . . . . . 251 Adding an aggregate to a logical aggregate . . 252 Deleting a logical aggregate . . . . . . . 252 Deleting a physical aggregate from a logical aggregate . . . . . . . . . . . . . . 253

Selection data set language (SDSL) . . . . . . 253 How does SDSL processing work? . . . . . 254 SDSL keywords . . . . . . . . . . . 255 Using SDSL . . . . . . . . . . . . . 256 Constructing SDSL instructions . . . . . . 256 Processing SDSL instructions . . . . . . . 257 About the SDSL CANDIDATES instruction . . 259 About the SDSL FILTERS instruction . . . . 261 CANDIDATES and FILTERS usage examples 268

ABARS Aggregate LoadBalancer . . . . . . . 272 Using the ABARS Aggregate LoadBalancer . . 273 DISTRIBUTE control statements . . . . . . 276 Using the sample Aggregate LoadBalancer REXX EXEC . . . . . . . . . . . . . 279 Aggregate LoadBalancer space calculations . . 279

Performing incremental backups and recoveries 279 Using ABARS Manager to run incremental backups . . . . . . . . . . . . . . 280 Backing up the IDS . . . . . . . . . . 284

Chapter 17. Using CATSCRUB to synchronize catalogs and DASD volumes . . . . . . . . . . . . . 285 Building a CATSCRUB command . . . . . . 285 About the Submit CATSCRUB panel . . . . . 286

Chapter 18. Searching for data sets 297 Searching for data sets (display all generations) 297

Search for Data Set field and command reference . . . . . . . . . . . . . . 298

Searching for data sets (quick search) . . . . . 300 Quick Search for Dataset field and command reference . . . . . . . . . . . . . . 301

Displaying data set overlaps . . . . . . . . 302 Overlap Search by Dataset field and command reference . . . . . . . . . . . . . . 303

Recovering a data set backed up by an HSM incremental using the HRECOVER command . . 303 Restoring data backed up by an unknown utility 304

IBM Confidential

vi IBM Tivoli Advanced Backup and Recovery for z/OS: User's Guide

Chapter 19. Monitoring in-progress ABARS backups and recoveries . . . 305

Chapter 20. Viewing event history . . 307 History panel field and command reference . . . 307

Chapter 21. Generating reports . . . . 311 Generating Automated Critical Data Identification reports . . . . . . . . . . . . . . . 311

Generating a data set name report . . . . . 311 Generating an overlap report . . . . . . . 312 Generating a filter report . . . . . . . . 313 Generating a DSD record count report . . . . 314 Status descriptions . . . . . . . . . . 315

Generating Critical Backup Tracking and Inventory backup reports . . . . . . . . . . . . . 316

Overlap by Data Set report . . . . . . . . 316 Overlap by Backup Event report . . . . . . 317 Overlap by Job Groups report . . . . . . . 317 Data Set List report . . . . . . . . . . 318 Data Set List by Jobname with Outputs report 320 Full Volume Dump List report . . . . . . . 320 Jobname List report . . . . . . . . . . 321 Jobnames Not Tracked by a Job Group report 323 What Isnt Backed Up report . . . . . . . 323 Critical in Automated Critical Data Identification with No Backup Record in Critical Backup Tracking and Inventory report . . . . 325 Critical in Automated Critical Data Identification with Critical Backup Tracking and Inventory Backup Record report . . . . . . 325 BKMBKEND Summary report . . . . . . . 326 Overlap by BKMBKEND Application report . . 327 TapePull report . . . . . . . . . . . . 327

Creating and viewing ABARS Manager online reports . . . . . . . . . . . . . . . 329

Creating an online Overlap by Data Set backup report . . . . . . . . . . . . . . . 330 Creating an online Overlap by Backup Event report . . . . . . . . . . . . . . . 331 Creating an online Data Set List report . . . . 332 Creating an online Event List report . . . . . 333 Creating and viewing an online Tape Pull List report . . . . . . . . . . . . . . . 334 Creating an online Disaster Recovery Space Summary report . . . . . . . . . . . 336 Creating an online Overlap by Data Set Recovery report . . . . . . . . . . . 337

Appendix A. Authority requirements 339 ABARS Manager required authorities, by data set or function . . . . . . . . . . . . . . 339 Incremental ABARS required authorities, by data set or function . . . . . . . . . . . . . 340 Incremental ABARS required authorities, by user or job . . . . . . . . . . . . . . . . . 340 Critical Backup Tracking and Inventory required authorities, by data set or function . . . . . . 341 Automated Critical Data Identification required authorities, by data set or function . . . . . . 342

Automated Critical Data Identification required authorities, by job or user . . . . . . . . . 343 Authorities required for ABARS Manager primary commands . . . . . . . . . . . . . . 344 SAF class profiles for the Critical Backup Tracking and Inventory started task . . . . . . . . . 346 SAF class profiles for controlling CATSCRUB command execution . . . . . . . . . . . 346

Appendix B. BKMINI configuration values . . . . . . . . . . . . . . 347 Coding the BKMINI keyword values . . . . . 347 Modifying data set name high order nodes . . . 347 BKMINI sections . . . . . . . . . . . . 348 :INIMERGE_VALUES keyword . . . . . . . 349 :PRODUCT_INFO section keywords . . . . . . 349 :PRODUCT_SECURITY section keywords . . . . 350 :INSTALLATION_DATASETS section keywords 350 :PRODUCT_DATASETS section keywords . . . . 351 :RESOURCE_SERIALIZATION section keywords 352 :HSM section keywords . . . . . . . . . . 352 :PROCESS_OPTIONS_ISPF section keywords . . . 353 :PROCESS_OPTIONS section keywords . . . . 355 :BACKUP_OPTIONS section keywords . . . . . 357 :ABARS_RC_OVERRIDES section keywords . . . 366 :RECOVERY_OPTIONS section keywords . . . . 368 :LOAD_ACTIVITY_LOG section keywords . . . 373 :BKMSTSKD_OPTIONS section keywords . . . . 373 :SI027_VALUES section keywords . . . . . . 375 :BKMSTSKA section keywords . . . . . . . 375 :CBTI_DUMP_BACKUP_PROCESS_OPTIONS section keywords . . . . . . . . . . . . 376 :CBTI_RESTORE_OPTIONS section keywords . . 377 :ACDI section keywords . . . . . . . . . . 380 :ACDI_RSP section keywords . . . . . . . . 394 :ACDIOPC_PARMS section keywords . . . . . 397 :CATSCRUB_OPTIONS section keywords . . . . 398 :SI040_VALUES section keywords . . . . . . 406 :JCL_PROC_PARMS section keywords . . . . . 409 :JCL_DEFAULTS section keywords . . . . . . 409

Appendix C. SMP/E configuration notes . . . . . . . . . . . . . . . 411 About the SMP/E DDDEFs . . . . . . . . . 411 Global Zone settings . . . . . . . . . . . 412

Global Zone data sets . . . . . . . . . 412 GLOBALZONE entry . . . . . . . . . . 413 Global Zone OPTIONS entry . . . . . . . 413 Global Zone UTILITY entries . . . . . . . 413 Global Zone DDDEF entries . . . . . . . 413 Product CSI Cluster . . . . . . . . . . 414

Target Zone settings . . . . . . . . . . . 414 Target Zone data sets . . . . . . . . . . 414 TARGETZONE entry . . . . . . . . . . 414 Target Zone DDDEF entries . . . . . . . 414

DLIB Zone settings . . . . . . . . . . . 415 DLIB Zone data sets . . . . . . . . . . 415 DLIBZONE entry . . . . . . . . . . . 415 DLIB Zone DDDEF entries . . . . . . . . 416

IBM Confidential

Contents vii

Appendix D. Extended ACS masking characters in filtering pattern masks . 417

Appendix E. Batch processing . . . . 419 Automated Critical Data Identification batch job submission sequence . . . . . . . . . . . 419 Critical Backup Tracking and Inventory batch processing . . . . . . . . . . . . . . 420

Batch jobs . . . . . . . . . . . . . 420 Batch reports . . . . . . . . . . . . 422 BKMBPROC syntax . . . . . . . . . . 435

Using ABARS Manager in batch mode . . . . . 439 Viewing Advanced Backup and Recovery for z/OS messages . . . . . . . . . . . . 439 Using the ABACKUP command . . . . . . 440 Using the ARECOVER command . . . . . . 446 Using native ABARS ARECOVER . . . . . 462 About the AGGMGMT command . . . . . 463 About the CONVSDSL command . . . . . . 468 About the LOADACT command . . . . . . 470 About the LOADIDS command . . . . . . 471 About the UNLOADIDS command . . . . . 473 About the REPORT command . . . . . . . 477 Batch ABARS output reporting . . . . . . 487 Checking ABACKUP and ARECOVER results 489

Appendix F. RSP operator commands 493 Starting the RSP started task . . . . . . . . 493 Stopping the RSP started task . . . . . . . . 494 RSP Monitor task commands . . . . . . . . 494 IEFU83 commands . . . . . . . . . . . 494 IEFUJI commands . . . . . . . . . . . . 495 ACDIUPDT task commands . . . . . . . . 496 Overflow task commands . . . . . . . . . 496

Appendix G. Sizing the Advanced Backup and Recovery for z/OS data sets . . . . . . . . . . . . . . . 499 Sizing suggestions for the product libraries . . . 499

Estimating the size of the IDS . . . . . . . 499 Work data set allocation . . . . . . . . . 500 Backing up, reorganizing, or resizing the IDS 500

Sizing the Automated Critical Data Identification database . . . . . . . . . . . . . . . 501

Estimating the size of your Automated Critical Data Identification database . . . . . . . 501 Preventing the database from running out of space . . . . . . . . . . . . . . . 505 Resizing the Automated Critical Data Identification database . . . . . . . . . 506

Appendix H. Inventory data set administration . . . . . . . . . . . 509 Backing up, reorganizing, and re-sizing the Advanced Backup and Recovery for z/OS Inventory Data Set . . . . . . . . . . . 509 Backing up and reorganzing the Inventory Data Set 509

About the Dynamic Data Set Backup/Reorganization utility . . . . . . . 509

Using the dynamic data set backup/reorganization utility . . . . . . . 510 Tailoring and executing the dynamic backup/reorganization utility JCL . . . . . 511 About the BKM01BRR parameters . . . . . 514

Using the IDS Health Check utility . . . . . . 515 Loading Critical Backup Tracking and Inventory data into the Advanced Backup and Recovery for z/OS Inventory Data Set . . . . . . . . . 516 Unloading Critical Backup Tracking and Inventory data from the Advanced Backup and Recovery for z/OS Inventory Data Set . . . . . . . . . 517

Appendix I. Data set activity database (DAD) administration . . . . . . . . 519 Tracking data changes in the Data Set Activity Database (DAD) . . . . . . . . . . . . 519

Using AUTOSTART to start the DAD and its sub-tasks . . . . . . . . . . . . . . 519 Using job name to start the DAD started task and its sub-tasks . . . . . . . . . . . 520 Starting the DAD started task without also starting the sub-tasks . . . . . . . . . . 520 Stopping the structure and terminating BKMSTSKD . . . . . . . . . . . . . 520 Manipulating the IEFU83 exit . . . . . . . 521 Removing obsolete entries from the DAD database . . . . . . . . . . . . . . 521

Appendix J. Critical Backup Tracking and Inventory tracking started task (BKMSMFTK) . . . . . . . . . . . 525 Critical Backup Tracking and Inventory commands 527 Starting the Critical Backup Tracking and Inventory tracking started task . . . . . . . 528 Stopping the Critical Backup Tracking and Inventory tracking started task . . . . . . . 529

Appendix K. Critical Backup Tracking and Inventory skeleton processing . . 531 Skeleton guidelines and considerations . . . . . 531 Generic skeleton commands . . . . . . . . 532 Skeleton control names . . . . . . . . . . 534 Skeleton variables . . . . . . . . . . . . 535

Generic skeleton variables . . . . . . . . 535 Skeleton source file variables . . . . . . . 537 Skeleton cluster variables . . . . . . . . 537 Skeleton path variables . . . . . . . . . 539 Non-VSAM skeleton variables . . . . . . . 540 Non-VSAM alias skeleton variables . . . . . 542 GDG base skeleton variables . . . . . . . 542

Skeleton event fields . . . . . . . . . . . 542 Skeleton index components . . . . . . . . . 544 Skeleton data components . . . . . . . . . 545

Appendix L. Automated Critical Data Identification utilities . . . . . . . . 547 Using the BKMMNT01 utility to rename an application . . . . . . . . . . . . . . 547

IBM Confidential

viii IBM Tivoli Advanced Backup and Recovery for z/OS: User's Guide

Using the BKMAPPCP utility to copy an application . . . . . . . . . . . . . . 547 Using the BKMDELAP utility to delete an application . . . . . . . . . . . . . . 548 Using the BKMFILTR utility to perform batch filter processing . . . . . . . . . . . . . . 548

FILTERS keywords . . . . . . . . . . 548

Appendix M. Sample job collection procedures . . . . . . . . . . . . 553 ASG-Zeke job collection procedure (BKMJOBZK) 553 CONTROL-M job collection procedure (BKMCM606 ) . . . . . . . . . . . . . 553 Cybermation ESP job collection procedure (BKMESPEX) . . . . . . . . . . . . . 554 TWS job collection procedure (BKMTWJOB) . . . 554 Unicenter CA-7 job collection procedure (BKMC7JOB ) . . . . . . . . . . . . . 555 Unicenter CA-Jobtrac job collection procedure (BKMJBTCV ) . . . . . . . . . . . . . 555 Pre-staged data set job collection procedure (BKMPRECV ) . . . . . . . . . . . . . 556

Appendix N. Extended ACS masking characters in filtering pattern masks . 557

Appendix O. Relative date masking 559

Appendix P. Data set naming conventions . . . . . . . . . . . . 561

Appendix Q. Support information . . . 563 Using IBM Support Assistant . . . . . . . . 563 Obtaining fixes . . . . . . . . . . . . . 563 Contacting IBM Software Support . . . . . . 564

Determining the business impact . . . . . . 565 Describing problems and gathering information 565 Submitting problems . . . . . . . . . . 565

Appendix R. Notices . . . . . . . . 567 Trademarks . . . . . . . . . . . . . . 568

Index . . . . . . . . . . . . . . . 569

IBM Confidential

Contents ix

IBM Confidential

x IBM Tivoli Advanced Backup and Recovery for z/OS: User's Guide

Figures

1. Automated Critical Data Identification architecture and process flow . . . . . . . 7

2. Continuous monitoring of application (in multi-image SYSPLEX modes) . . . . . . . 8

3. Example job collection structure . . . . . . 67 4. Job structure . . . . . . . . . . . . 80 5. Levels of filtering . . . . . . . . . . 146 6. Example Overlap by Data Set report . . . . 317 7. Example Overlap by Backup Event report 317 8. Example Overlap by Job Groups report 318 9. Example Data Set List report . . . . . . 318 10. Example Data Set List by Jobname with

Outputs report . . . . . . . . . . . 320 11. Example Full Volume Dump List report 320 12. Example Jobname List report . . . . . . 322 13. Example Jobnames Not Tracked by a Job

Group report . . . . . . . . . . . . 323

14. Example What Isnt Backed Up report 324 15. Example Critical in Automated Critical Data

Identification with Critical Backup Tracking and Inventory Backup Record report . . . . 325

16. Example Critical in Automated Critical Data Identification with Critical Backup Tracking and Inventory Backup Record report . . . . 326

17. Example BKMBKEND Summary report 327 18. Example Overlap by BKMBKEND

Application report . . . . . . . . . . 327 19. Example TapePull report . . . . . . . . 328 20. Job statement verification . . . . . . . 419 21. Job submission preferences . . . . . . . 419 22. ABACKUP batch process . . . . . . . 440 23. ARECOVER batch process . . . . . . . 446

IBM Confidential

Copyright IBM Corp. 1996, 2008 xi

IBM Confidential

xii IBM Tivoli Advanced Backup and Recovery for z/OS: User's Guide

Tables

1. Application checklist for Automated Critical Data Identification . . . . . . . . . . 63

2. Example - GDSes added from RSP JCL Capture . . . . . . . . . . . . . . 76

3. Required SMF records and descriptions 122

4. Output selection format and supported data set types . . . . . . . . . . . . . 129

5. Filter keywords and criteria . . . . . . . 263 6. Filtering pattern masks . . . . . . . . 417 7. Filtering pattern masks . . . . . . . . 557

IBM Confidential

Copyright IBM Corp. 1996, 2008 xiii

IBM Confidential

xiv IBM Tivoli Advanced Backup and Recovery for z/OS: User's Guide

About this guide

This book provides instructions for using IBM Tivoli Advanced Backup and Recovery for z/OS.

This information is designed to help storage administrators and application programmers who use, manage, and monitor application backup functions within the DFSMShsm, FDR, DFSMSdss, and Brightstor CA-Disk system releases operate Advanced Backup and Recovery for z/OS.

Intended audience for this guide This book is intended for those persons responsible for installing, configuring and using IBM Tivoli Advanced Backup and Recovery for z/OS and assumes a working knowledge of: v The z/OS operating system v The Microsoft Windows operating system

Publications The following publications are included in the Advanced Backup and Recovery for z/OS product library: v IBM Tivoli Advanced Backup and Recovery for z/OS Program Directory, GI11-8886

Provides hardware and software prerequisites and instructions for the Advanced Backup and Recovery for z/OS SMP/E installation.

v IBM Tivoli Advanced Backup and Recovery for z/OS User's Guide, SC23-9730 Provides instructions for using Advanced Backup and Recovery for z/OS.

v IBM Tivoli Advanced Backup and Recovery for z/OS Monitoring Agent Planning and Configuration Guide, SC23-9732 Provides instructions for planning, installing, and configuring Advanced Backup and Recovery for z/OS. This publication includes the following types of information: Information and worksheets to help you plan your configuration A list of prerequisite steps to complete before configuring the product Instructions for configuring the monitoring server and monitoring agent on a

z/OS system Instructions for installing and setting up the distributed components of the

product Information about using system variables and batch processing to expand a

configuration across the enterprise Security considerations and advice

v IBM Tivoli Advanced Backup and Recovery for z/OS Monitoring Agent User's Guide, SC23-9733 Provides instructions for using Advanced Backup and Recovery for z/OS to monitor z/OS system and sysplex resources, and product-specific monitoring scenarios.

v IBM Tivoli Advanced Backup and Recovery for z/OS Messages, GC23-9731 Lists and explains Advanced Backup and Recovery for z/OS messages.

IBM Confidential

Copyright IBM Corp. 1996, 2008 xv

Accessing publications online IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli Information Center Web site at http://www.ibm.com/software/tivoli/library/.

In the Tivoli Information Center window, click Tivoli product manuals. Click the letter that matches the first letter of your product name to access your product library. For example, click M to access the IBM Tivoli Monitoring library or click O to access the IBM Tivoli OMEGAMON library.

Note: If you print PDF documents on other than letter-sized paper, set the option in the File > Print window that allows Adobe Reader to print letter-sized pages on your local paper.

Reading CCR2 online IBM publishes CCR2, a useful monthly e-newsletter for the System z and zSeries software community. You can find the latest issue of CCR2 at http://www-306.ibm.com/software/tivoli/features/ccr2/info.html.

Ordering publications You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/ publications/cgibin/pbi.cgi.

You can also order by telephone by calling one of these numbers: v In the United States: 800-879-2755 v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli publications. To locate the telephone number of your local representative, perform the following steps: 1. Go to http://www.elink.ibmlink.ibm.com/public/applications/

publications/cgibin/pbi.cgi. 2. Select your country from the list and click Go. 3. Click About this site in the main panel to see an information page that

includes the telephone number of your local representative.

Accessing terminology online The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available at the following Tivoli software library Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology Web site at the following Web address:

http://www-306.ibm.com/software/globalization/terminology

IBM Confidential

xvi IBM Tivoli Advanced Backup and Recovery for z/OS: User's Guide

http://www.ibm.com/software/tivoli/library/http://www-306.ibm.com/software/tivoli/features/ccr2/info.htmlhttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htmhttp://www-306.ibm.com/software/globalization/terminology

Tivoli technical training For Tivoli technical training information, refer to the following IBM Tivoli Education Web site:

http://www.ibm.com/software/tivoli/education

Support information If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: v IBM Support Assistant: You can search across a large collection of known

problems and workarounds, Technotes, and other information at http://www.ibm.com/software/support/isa.

v Obtaining fixes: You can locate the latest fixes that are already available for your product.

v Contacting IBM Software Support: If you still cannot solve your problem, and you need to work with someone from IBM, you can use a variety of ways to contact IBM Software Support.

For more information about resolving problems, see Appendix Q, Support information, on page 563.

Conventions used in this publication

Typeface conventions This guide uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip: and Operating system considerations)

v Keywords and parameters in textItalic

v Words defined in text v Emphasis of words (words as words) v New terms in text (except in a definition list) v Variables and values you must provide

Monospace

v Examples and code examples v File names, programming keywords, and other elements that are difficult

to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options

IBM Confidential

About this guide xvii

http://www.ibm.com/software/tivoli/educationhttp://www-306.ibm.com/software/support/isa

IBM Confidential

xviii IBM Tivoli Advanced Backup and Recovery for z/OS: User's Guide

Chapter 1. Advanced Backup and Recovery for z/OS Overview

This information describes the main features and capabilities of Advanced Backup and Recovery for z/OS.

This software comprises one common install, a common inventory data set for ABARS Manager and Critical Backup Tracking/Inventory, a separate database for Automated Critical Data Identification, and common panels. Advanced Backup and Recovery for z/OS is designed to meet your companys business resiliency needs either locally, or in the event of a disaster, from the minor to the catastrophic. Advanced Backup and Recovery for z/OS offers the following products and features: v ABARS Manager:

Enhances and extends ABARS functionality Centralizes management of ABARS to make ABARS easy to use Consolidates and manages essential tracking, status, and resource information Adds functionality not included in native ABARS Provides selectable feature Incremental ABARS for true ABARS incremental

support CATSCRUB, designed for full volume restore, enables you to synchronize

quickly one or more BCS catalogs with associated DASD volumes at your disaster recovery site

Incremental ABARS enables you to perform ABARS backups on an incremental basis

v Critical Backup Tracking/Inventory Centralizes and inventories z/OS backups so you can recover anywhere,

anytime Identifies what has not been backed up at your site

v Automated Critical Data Identification Identifies critical business data as the application executes Identifies the data that needs to be backed up for business resiliency onsite or

offsite (or both) and builds the list as input to a backup utilityv Automated Critical Data Identification and Critical Backup Tracking/Inventory

working together Use the list created by Automated Critical Data Identification to compare to

what was actually backed up Provide documented evidence that critical assets have a backup Provide proof that critical business data is offsite if required Alert on critical assets that dont have a backup

Advanced Backup and Recovery for z/OS panels provide access to functionality common to all features, ABARS Manager, Critical Backup Tracking/Inventory, and Automated Critical Data Identification, and are named either Advanced Backup and Recovery for z/OS or BKM. ABARS Manager panels are named either ABARS Manager or ABM, Critical Backup Tracking/Inventory panels are named either Critical Backup Tracking/Inventory or CBTI, and Automated Critical Data Identification panels are named either Automated Critical Data Identification or ACDI.

IBM Confidential

Copyright IBM Corp. 1996, 2008 1

Why use Advanced Backup and Recovery for z/OS instead of native ABARS?

ABARS Manager provides powerful enhancements and extensions to ABARS processing and availability. ABARS Manager is specifically designed to enhance, simplify, and automate Disaster Recovery and Local processing using ABARS backup and recovery functions. ABARS Manager makes ABARS and DFSMShsm more powerful, flexible, reliable, and easier to use.

Incremental ABARS allows you to combine the Disaster Recovery Solutions provided by ABARS, with the benefits of incremental backup strategy.

CATSCRUB synchronizes catalogs and volumes for Disaster Recovery at blazing speeds. The result is catalogs that correctly reflect the data on physical volumes.

ABARS Manager provides the following benefits: v Centralized management and control information in a powerful Inventory Data

Set (IDS) with in-depth tracking features v Batch operation for routine operations and planned activities v Interactive operation for detailed analysis, error correction, research, process

restart, selective recovery, overlap analysis, and VTOC information v Tape information is automatically created for recovery execution v Extensive supplemental information held in the IDS, including selection data set

information and activity log details, as well as error status. v The following extended ABARS functionality and reliability features:

Selection Data Set Language (SDSL) is a powerful tool that expands the ABARS language to over 30 different attributes for INCLUDE or EXCLUDE of data sets. Boolean logic makes it easy to define powerful selection rules.

Prevent BackLevel ensures that an application is not back-leveled by an older copy of a data set being restored.

GDG REPLACE/NOREPLACE gives you the control to restore non-GDS using the NOREPLACE parameter for non-GDS files, and REPLACE specifically for GDS files.

Selective Data Set Restore allows you to restore specific data sets, data sets you identify using masking, or data sets independent of the backup name.

Extended Rename provides the capability to rename more than the high level qualifier.

ABARS and other utilities

Tracking and restoring ABARS backups requires ABARS Manager. Unlike other utilities, ABARS-tracked backups require initiating backups using an ABARS Manager procedure.

If you use both ABARS Manager and Critical Backup Tracking/Inventory, all backed-up data sets (that is, if backed up either by ABARS or other z/OS backups) are presented in a consolidated view.

IBM Confidential

2 IBM Tivoli Advanced Backup and Recovery for z/OS: User's Guide

Automated Critical Data Identification Automated Critical Data Identification uses information from job scheduling products, JCL libraries, and SMF records to help storage administrators easily determine which data sets should be included as part of an application backup. Automated Critical Data Identification provides storage administrators with a set of sophisticated tools to implement and manage an installations application backup strategy.

Installations often back up unnecessary data using mask filters or manual lists that are often not maintained because identifying the data to be backed up can be a time-consuming task. Automated Critical Data Identification solves this problem by automating the task of identifying the critical data to be backed up. Using information from a variety of OS/390 or z/OS sources, Automated Critical Data Identification automatically constructs a list of data sets used by an application each time the application runs. The list of critical data sets is immediately available as input to a backup, or it can be used for analysis.

Automated Critical Data Identification features and benefits Using Automated Critical Data Identification helps ensure that all critical data is included in the backup, while saving resources and reducing costs by backing up only the data required.

Automatically detects application changes

Automated Critical Data Identification automatically detects application changes that might require changes to backup selection criteria.

Support for forward and rerun recovery methods

Determining which data sets are critical can be a complex task without Automated Critical Data Identification. Detailed decisions depend largely on the planned recovery methodology. Each organization must make specific decisions about each application as to whether forward recovery (sometimes called forward resumption) or rerun recovery will be used. Automated Critical Data Identification provides automated support of rerun recovery and substantial support for forward recovery. Override and option settings are available either globally or at the application level to assist you in configuring Automated Critical Data Identification appropriately.

Job scheduler interfaces

Automated Critical Data Identification provides interfaces to these job scheduling products: v ASG-Zeke for z/OS v BMC CONTROL-M for z/OS v Cybermation ESP v Tivoli Workload Scheduler (TWS) v Unicenter CA-7 Job Management v Unicenter CA-Jobtrac Job Management

IBM Confidential

Chapter 1. Advanced Backup and Recovery for z/OS Overview 3

Mirroring support

Automated Critical Data Identification supports remote mirroring to track tape data or other data that should be mirrored. Automated Critical Data Identification mirroring support provides several benefits.

Verifies the correct data sets are being mirrored

If you have data sets (for example on volumes PROD*) that are being mirrored and you want to identify data sets for those applications that were allocated on volumes outside of the mirrored volumes, you can define all applications on the PROD* volumes to Automated Critical Data Identification and it will track the applications as they run. You can review the selection data set on a daily basis to identify those data sets not on mirrored volumes.

Identifies data sets on specific volumes By browsing the contents of the Automated Critical Data Identification selection data set, you can view the volume where each data set is located (which can alert you to potential problems). For example, if a data set should be located on a PROD* volume and it is located on a TEST volume, or another volume that is not mirrored, you can easily determine if you need to take action.

Identifies tape data sets By excluding all data on volumes other than tape, Automated Critical Data Identification will provide a list of tape data. Automated Critical Data Identification can also identify data and distinguish between migration level 1 (ML1) DASD and migration level 2 (ML2) tape data sets. For example, by excluding all data on volumes other than TAPE and MIGRA2, Automated Critical Data Identification will provide a list of data that resides on tape.

Note: Automated Critical Data Identification does not determine tape sizing it only determines whether or not the data set is on tape.

Identifies data required for point-in-time backups If you are mirroring batch data you still need a point-in-time backup. If an error occurs in batch, and it is duplicated to the mirrored DASD, you might not be able to back out of the error because it was duplicated at your remote site and there was no point-in-time backup.

Reporting

Automated Critical Data Identification provides a variety of reports that can be used to list filters, the number of Data Set Detail (DSD) records, and other relevant information for each application tracked by Automated Critical Data Identification.

Automated Critical Data Identification and Critical Backup Tracking and Inventory

Together, Automated Critical Data Identification and Critical Backup Tracking and Inventory provide these features: v The ability to compare the Automated Critical Data Identification critical data set

list against Critical Backup Tracking and Inventory discovered backups. v The ability to restore data sets for Automated Critical Data Identification

applications and specific cycles within an application.

IBM Confidential


v Reports to interrogate tape management systems (TMS) to determine the location of backup tapes.

v Provide proof that critical data is backed up. v Provide alerts for those data sets that are not backed up.

Automated Critical Data Identification components Automated Critical Data Identification consists of several components. Some components are initiated by started tasks, and others are initiated by jobs that you must customize for your environment.

Automated Critical Data Identification Application Data Inventory The Automated Critical Data Identification Application Data Inventory, a VSAM KSDS database, maintains and tracks application information. The information gathered by the job collection process is stored in the Automated Critical Data Identification Application Data Inventory.

The Automated Critical Data Identification Application Data Inventory provides a repository for user overrides, application level selection and analysis options, and details of job and data set collection and data set activity. Automated Critical Data Identification uses application information in the inventory to create selection data sets in various supported formats.

Real-time selection process (RSP) After you place an application under Automated Critical Data Identification administration, the Real-time Selection Process (RSP) continuously monitors application activity to ensure the application critical data set list is current and accurate. RSP effectively handles a variety of typical but troublesome processing modes such as applications that run overlapping cycles, and applications that create, or use, pseudo-GDG data sets (data sets whose names change in a systematic non-standard manner). RSP provides two methods you can use to collect data: RSP SMF Capture and RSP JCL Capture.

RSP SMF Capture RSP SMF Capture uses the IEFU83 SMF exit facility to collect SMF data in real-time, which it then uses to reevaluate the criticality of data sets in the application.

RSP JCL Capture RSP JCL Capture uses the IEFUJI JCL exit facility to collect interpreted JCL information in real time.

BKMAPLEN RSP uses an added job step, the application end step (BKMAPLEN), to signal that a full application cycle has been completed. This allows RSP to process any remaining SMF records, update the Automated Critical Data Identification Application Data Inventory, and rebuild the application selection data set for the next backup event. There can be one, or many, application end steps in an application job stream, depending on the complexity of job relationships.

Job table For each image, RSP builds an internal dataspace table, called the job table (or job reference table), containing the job names defined to each application. All data collection methods read the job table.

Job scheduler interfaces Automated Critical Data Identification collects information about an

IBM Confidential


applications jobs and job dependencies using multiple methods to gather information from a variety of sources. One method is to use an interface to a job scheduling product. Automated Critical Data Identification provides interfaces to a variety of job scheduling products.

Selection data set The selection data set contains the most recent critical data set entries to be backed up. Each application has a unique selection data set. You define the selection data set during the application setup process using an output format that is compatible with the backup product you are using. Automated Critical Data Identification populates the selection data set using one of the following supported output formats: v ABARS (Default format.) Uses standard INCLUDE, ALLOCATE and

ACCOMPANY type entries. v DFSMSdss Uses the logical dump data set format. v FDR/ABR Uses primary and allocate type data set entries. v Brightstor CA-Disk (DMS) Uses primary data set entries. v List Generic list format.

SMF Scan SMF Scan is intended for those installations that are not ready to implement RSP or for those installations that want a historical analysis of an application. SMF scan is a batch process that you can use to scan a user specified collection of captured SMF data. Identifying application data sets through SMF Scan is an optional step performed after job collection.

Verification During Verification processing, Automated Critical Data Identification generates backup control statements in the selected output format and places them in the selection data set. The Verification program can be used to test the creation of the selection data set and determine the critical selection data set entries for an application.

Automated Critical Data Identification architecture and processing

Through the use of various methodologies, functionality, and support capabilities, Automated Critical Data Identification provides you with the tools you need for critical data set identification in the most complex processing environments.

An overview of Automated Critical Data Identification architecture and the process flow to identify critical data are shown in Figure 1 on page 7.

IBM Confidential


Identifying Critical Application Data Sets

Application Setup Job CollectionRSP

- SMF Capture- JCL Capture

BKMAPLEN orVerification: Critical

Data Set Entries

Monitor ApplicationChanges

Forward Recovery orRerun Recovery

Job SchedulerInterface or

Manual InputReal-time

Collection ofData Sets

UpdatesSelection Data

Set

Critical Data Set

List

RSP JCL CaptureRSP SMF Capture

Critical Data Set

List

1 2 3 4 5

AutomatedCritical

Data IdentificationApplication Data

Inventory

1. During the application setup process, you define, for each application, information such as the recovery method and GDG support options. Automated Critical Data Identification uses this information to determine which data sets belong to an application and which data sets are critical for backup.

2. Automated Critical Data Identification performs the job collection process by gathering information about the jobs and job structures associated with an application from sources such as job scheduler products, job name masks, or user created lists. The information gathered by the job collection process is placed in the Automated Critical Data Identification Application Data Inventory for later use in the data gathering process.

3. RSP continuously monitors the activity of the applications to ensure the application critical data set list is current and accurate. RSP captures and analyzes SMF and JCL data for applications defined to Automated Critical Data Identification as they run and updates the Automated Critical Data Identification Application Data Inventory with the data set names used by the application.

4. BKMAPLEN or Verification is used to identify critical data and create the selection data set. When creating the selection data set, Automated Critical Data Identification combines data set detail records (DSDs), created from RSP JCL Capture, RSP SMF Capture, and SMF Scan into a single record for each data set. Data sets are evaluated for criticality. This step also inserts arbitrary data set names (external filters).

5. After the initial selection data set has been created, Automated Critical Data Identification monitors changes to an the applications data set usage and

Figure 1. Automated Critical Data Identification architecture and process flow

IBM Confidential


automatically maintains a current critical data set name list for use in backing up the application for local or disaster recovery purposes.

Application monitoring Monitoring application changes ensures that any changes made to the application are reflected in the selection data set and the Automated Critical Data Identification Application Data Inventory.

After the job collection and real-time tracking is complete for an application, and the selection data set has been created, both real-time and batch mechanisms are provided for collecting and monitoring data set changes for any application. Figure 2 shows the processes involved in monitoring and updating an application selection data set.

RSP- SMF Capture- JCL Capture

BKMAPLEN orVerification: Critical

Data Set Entries

Applications

Data SetReferences

UpdatesSelection Data

Set

Critical Data Set

List

Image - 1Image - 2

Critical Data Set

List

AutomatedCritical

Data IdentificationApplication Data

Inventory

RSP allows continuous application monitoring and collection of data set entries using RSP JCL Capture and RSP SMF Capture. RSP can monitor and track an application in both single and multi-image environments (or SYSPLEX). At the completion of an applications processing, the data set entries are updated and the selection data set list is reconstructed, ensuring that the subsequent backup contains the most current critical application data sets.

Figure 2. Continuous monitoring of application (in multi-image SYSPLEX modes)

IBM Confidential


Critical Backup Tracking and Inventory Critical Backup Tracking and Inventory provides centralized backup control for business resiliency (both locally and for disaster recovery purposes).

Critical Backup Tracking and Inventory intercepts, inventories, and centralizes z/OS backups without requiring JCL changes to existing backup utilities, giving you the ability to recover anywhere, anytime. It consolidates and manages essential backup tracking, status, and resource information for effective backup and recovery.

Critical Backup Tracking and Inventory: v Provides business resiliency for local recovery or disaster recovery, from minor

to catastrophic outages. v Tracks and records backups and data without the need for any JCL changes to

existing backup utilities. v Quickly locates any backup copy recorded in the Advanced Backup and

Recovery for z/OS Inventory Data Set and easily enables you to display backup details and restore data.

v Provides easy to use ISPF and batch interfaces. v Identifies what is not backed up at your installation to help ensure you are not

missing critical data sets. By tracking and providing an inventory of backups, you can easily find data sets not backed up by comparing them to the Advanced Backup and Recovery for z/OS Inventory Data Set, DFSMShsm, BCDS, or both.

v Identifies multiple data set backups to help reduce resources. v Automatically constructs restore JCL and utility control statements that will

reverse the copy of a backed-up data set. Construction of recovery JCL control statements can be varied through the Critical Backup Tracking and Inventory file tailoring process.

v When used with Automated Critical Data Identification, Critical Backup Tracking and Inventory: Uses the list created by Automated Critical Data Identification Application

Data Inventory to compare to what was actually backed up Provides documented evidence that critical assets have a backup Alerts on critical assets that do not have a backup Proves that critical business data is offsite if required

Critical Backup Tracking and Inventory features and benefits Critical Backup Tracking and Inventory provides these features and benefits. v Intercepts backups without JCL changes therefore making tracking backups

simple to set up. v Centralization enables you to easily determine what data is, or is not, backed up. v Quickly locates backups. By tracking z/OS backups, Critical Backup Tracking

and Inventory can locate any and all backups of the data set, regardless of the utility used, by simply specifying a data set name.

v Provides for business resiliency both locally and for disaster recovery: Locally Use Critical Backup Tracking and Inventory on site if a data set

becomes deleted or corrupted, or a backout of a batch process is required. Disaster Recovery Use Critical Backup Tracking and Inventory offsite if a

disaster strikes to easily restore and quickly get your systems up and running.

IBM Confidential


v Identifies what is not backed up at your site to help ensure you are not missing critical data sets that require a backup. Compares data sets on your volumes, or in your ICF User Catalog, or both, to

the Critical Backup Tracking and Inventory data set, and optionally to the DFSMShsm BCDS.

Critical Backup Tracking and Inventory will identify data sets that are not recorded in either and thus, have not been tracked yet, or do not have a backup.

v Tracks multiple generations of backups. Critical Backup Tracking and Inventory can optionally track multiple generations of a backup, allowing restoration of a backup other than the most current generation.

v View data sets backed up from each utility including full volume dump, and provide data set restore off full volume dumps (a rare occurrence but sometimes necessary).

v Automatically recovers JCL and control statements. It is not uncommon for backups to be placed in production with no corresponding restore JCL or control statements created and available for quick access. Critical Backup Tracking and Inventory resolves this issue by automatically constructing the restore JCL or control statements that match the utility and commands used to originally back up data sets or volumes.

v Alerts if backups fail. Processes are not always set to fail or provide an alert if a backup fails. By tracking not only which data sets or volumes are backed up, but by also recording the success or failure, Critical Backup Tracking and Inventory provides a mechanism for alerting responsible parties that backups have failed.

v Interactive operation for detailed analysis, error status, research, overlap analysis, and DSCB information.

v Identifies data sets backed up multiple times to save on tape and CPU resources v Identifies data sets that could possibly be overwritten during restore caused by:

Overlaps between full volume dumps and application backups. Overlaps that can occur when multiple applications back up the same data

set.

Critical Backup Tracking and Inventory components Critical Backup Tracking and Inventory consists of several components. Some components are initiated by a started task and others are initiated by JCL that you must customize for your environment.

Critical Backup Tracking and Inventory (BKMSMFTK) started task The started task intercepts supported in-stream backups performed during a backup and provides a method for tracking them in the Advanced Backup and Recovery for z/OS Inventory Data Set.

Step initiation exit (IEFUSI) Starts the Critical Backup Tracking and Inventory job intercepts.

Batch Intercept File (BIF) The batch intercept file contain batch intercept file entries. Batch intercept file entries identify the jobs, steps, or program names to track.

Intercept modules for supported backup utilities These modules enable you to track the backup utilities supported by Critical Backup Tracking and Inventory.

IBM Confidential


Advanced Backup and Recovery for z/OS Inventory Data Set A common Advanced Backup and Recovery for z/OS Inventory Data Set is used for both ABARS Manager and Critical Backup Tracking and Inventory.

ISPF interface Critical Backup Tracking and Inventory provides an ISPF-based user interface that enables you to easily perform backup and restore management tasks.

Batch utilities The Critical Backup Tracking and Inventory batch utilities enable you to load and unload data from the Advanced Backup and Recovery for z/OS Inventory Data Set, expire and remove backups that are no longer valid from the Advanced Backup and Recovery for z/OS Inventory Data Set and generate a variety of reports.

How Critical Backup Tracking and Inventory tracks backups To avoid requiring JCL changes to existing backup utilities, Critical Backup Tracking and Inventory identifies backups to be tracked using a seamless intercept triggered by matching job names, step names, and utility program names to a user-defined table. Although it is necessary to identify which jobs are backups, the risk and procedural difficulties associated with modifying production JCL are eliminated.

You identify backup jobs to Critical Backup Tracking and Inventory through batch intercept file entries. The batch intercept file entries identify a backup job or step and identify the expected backup utility.

To intercept backups, Critical Backup Tracking and Inventory uses a started task on each image which installs step initiation exit (IEFUSI). If a backup is to be intercepted, the execute statement is modified to run an intercept program, which in turn runs the utility.

Subtasks process the results of intercepted utilities and record the pertinent data in the Advanced Backup and Recovery for z/OS Inventory Data Set. For most types of backups, Critical Backup Tracking and Inventory captures catalog and volume metadata in synchronization with the status of the data sets at the time of the backup. This ensures that restore allocations match the status of data sets at the time they were backed up.

Backup utilities tracked by Critical Backup Tracking and Inventory

This information describes the backup utilities tracked by Critical Backup Tracking and Inventory. v ABARS backups performed through ABARS Manager v Adabas (ADARUN) v IBM Tivoli Advanced Catalog Management backups v CFCAMS (REPRO and EXPORT) v DFSMSdss (Full volume, physical dump by data set, and logical backups) v DFSMShsm ARCINBAK v DFSMShsm AUTODUMP v DFSMShsm BACKVOL

IBM Confidential


v DFSMShsm Incremental v FDR (FDR, DSF, ABRFDR) v ICEGENER v IDCAMS (REPRO and EXPORT) v IEBCOPY v IEBGENER v SORT v SYNCGENR

Note:

v DFSMShsm AUTODUMP and BACKVOL are supported through batch utilities.

v SORT is typically used to SORT data. Sorts of this type are not considered backups and should not be tracked by Critical Backup Tracking and Inventory. The function of Critical Backup Tracking and Inventory is to track data sets that have been backed up. Critical Backup Tracking and Inventory tracks SORT because some installations might have jobs that sort data to an output file that they consider a backup. These are valid backups. Make sure that discrete job names are specified in the backup tracking INCLUDE filters instead of masks for any SORT job you want to track, in order to prevent tracking sort output files that are not backups, or to prevent failures. SORT functions often use PDS members as input to the SORT, however Critical Backup Tracking and Inventory requires you to use the full partitioned data set name. Member names are not supported.

Tracking and restoration of VSAM KSDSs with alternate indexes

Some backup and restore utilities have a SPHERE option which causes the utility to back up all components and associations of a VSAM sphere. When using a utility that does not have a SPHERE option, Critical Backup Tracking and Inventory requires only that the base cluster be backed up. Backups of AIXes are ignored.

When a backup of a VSAM base cluster is tracked, all association information is saved in the Advanced Backup and Recovery for z/OS Inventory Data Set. This information is then used to define and rebuild any associated AIXes and define any associated PATHs. This feature provides the sphere backup and restore capability to utilities that do not inherently perform this function.

After verifying the AIXes and PATHs are appropriately restored, you might want to remove potential unnecessary backups of AIXes, and user procedures, to capture catalog PATH information.

ABARS Manager overview ABARS Manager provides powerful enhancements and extensions to ABARS processing and availability. Designed to enhance, simplify, and automate disaster recovery and local processing, it uses native ABARS backup and recovery functions.

You can use Incremental ABARS to combine the disaster recovery solutions provided by ABARS with the benefits of incremental backup strategy.

IBM Confidential


ABARS Managers CATSCRUB feature lets you synchronize catalogs with volumes speedily so that catalogs correctly reflect the data on physical volumes.

Benefits of using ABARS Manager

Why would you want to use ABARS Manager? v It provides centralized management and control information in the Inventory

Data Set (IDS), with in-depth tracking features. v You can use ABARS Manager in batch mode for routine operations and planned

activities. v You can use ABARS Manager in interactive mode for these purposes:

Detailed analysis Error correction Research Restarting processes Selective recovery Overlap analysis Obtaining VTOC information

v Tape information is created automatically for recovery execution. v The IDS stores extensive supplemental information, including information about

selection data sets, activity log details, and error status. v ABARS Managers Selection Data Set Language (SDSL) extends the ABARS

language to over 30 attributes for the inclusion or exclusion of data sets. Boolean logic simplifies the definition of powerful selection rules.

v The pre-processing of selection data sets reduces run-time errors by identifying and correcting common ABARS syntax errors.

v The Prevent BackLevel feature ensures that an application is not back-leveled by an older copy during a data set restoration.

v The GDG REPLACE/NOREPLACE option gives you the control to restore non-GDS using the NOREPLACE parameter for non-GDS fiels and REPLACE specifically for GDS files.

v Selective data set restoration lets your restore specific data sets. You can identify the data sets by masking or you can indicate that you want specific data sets restored, regardless of the backup name.

v You can use the Extended Rename feature to rename multiple high-level qualifiers.

About ABARS and other utilities

Tracking and restoring ABARS backups requires ABARS Manager. Unlike other utilities, ABARS-tracked backups require that you initiate backups by using an ABARS Manager procedure.

If you use both ABARS Manager and Critical Backup Tracking and Inventory, all backed-up data sets (regardless of whether they were backed up by ABARS or other z/OS backup methods) are displayed in one consolidated view.

IBM Confidential


Advanced Backup and Recovery for z/OS scenarios You can use Advanced Backup and Recovery for z/OS to meet your business resiliency needs either locally, or in the event of a disaster, from the minor to the catastrophic. These scenarios illustrate how you can use Advanced Backup and Recovery for z/OS to address typical business problems.

Disaster recovery using Automated Critical Data Identification and Critical Backup Tracking and Inventory

You manually identify data used by production batch applications, started tasks, or individual users for disaster recovery purposes and want to avoid backing up more data than you need. You are concerned that you might not be backing up critical data and might not be able to recover your data in a timely manner.

Automated Critical Data Identification and Critical Backup Tracking and Inventory enable your business to benefit from an automated, round-the-clock solution that identifies data used by each application for the purpose of protecting the data for both local and offsite recovery.

Automated Critical Data Identification

By using Automated Critical Data Identification you can provide an autonomic solution for the identification of your data.

Automated Critical Data Identification: v runs continuously, identifying data used by production batch applications,

started tasks, or individual users. v eliminates the manual, time-consuming, and error-prone task of identifying data

for backup. v identifies data as it is used, thus eliminating the need to backup data using

masking every day while reducing tape and CPU resources.

Automated Critical Data Identification eliminates the need for manual and often error-prone identification of your business data requiring backup for disaster recovery preparedness. Automated Critical Data Identification accurately identifies data to ensure successful recovery. Because Automated Critical Data Identification identifies critical data as it is used by an application, it provides a reduction in backup and recovery window

Documents

IBM Tivoli Advanced Backup and Recovery for z/OS: …publib.boulder.ibm.com/tividd/td/ITABaRfzOS/SC23-9730-00/en_US/PD… · IBM Tivoli Advanced Backup and Recovery for z/OS User's