2 options
DFSMShsm ABARS and Mainstar solutions / [Yolanda Cascajo Jimenez, Coleen Gordon].
- Format:
- Book
- Author/Creator:
- Cascajo Jimenez, Yolanda.
- Series:
- IBM redbooks.
- Redbooks
- Language:
- English
- Subjects (All):
- Electronic data processing--Backup processing alternatives.
- Electronic data processing.
- Data recovery (Computer science).
- Physical Description:
- 1 online resource (210 p.)
- Edition:
- 2nd ed.
- Place of Publication:
- [San Jose, Calif.] : IBM International Technical Support Organization, 2002.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Figures
- Examples
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Chapter 1. Product overview
- 1.1 Aggregate Backup and Recovery Support
- 1.1.1 Aggregate group definition
- 1.1.2 Aggregate backup
- 1.1.3 Aggregate recovery
- 1.1.4 Strengths of ABARS
- 1.2 ASAP
- 1.2.1 ASAP data set identification
- 1.2.2 ASAP data set analysis
- 1.2.3 Monitoring changes
- 1.2.4 ASAP filters and controls
- 1.3 Backup &
- Recovery Manager
- 1.3.1 Easy aggregate recovery
- 1.3.2 Online monitoring
- 1.3.3 Selective data set restore
- 1.3.4 Aggregate balancing
- 1.3.5 Online and batch reporting
- 1.3.6 Additional functionality
- Chapter 2. Business recovery concepts
- 2.1 A structured approach to disaster recovery
- 2.2 Relationships between backup and recovery
- 2.3 Solutions for reducing perceived burden of backup
- Chapter 3. Sample environment
- 3.1 Crazy Socks Corporation
- 3.2 Crazy Socks Corporation configuration
- 3.2.1 Crazy Socks business processes
- 3.2.2 Current disaster backup procedures
- 3.3 Data classification and recovery requirements
- 3.3.1 Immediately critical data, to be recovered within 8 hours
- 3.3.2 Highly critical data, to be recovered in 24 hours
- 3.3.3 Moderately critical data, to be recovered in 48 hours
- 3.3.4 Less critical data, to be recovered in 4 days
- 3.3.5 Least critical data, to be recovered in 7 days
- 3.3.6 Changes required for production cycles or a vault run
- 3.4 Recovery scenario A
- 3.4.1 Recovery objectives
- 3.4.2 Recovery solution
- 3.5 Recovery scenario B
- 3.5.1 Recovery objectives
- 3.5.2 Recovery solution
- 3.6 Our ABARS backup and recovery strategy
- Chapter 4. ABARS implementation tasks and considerations
- 4.1 ABARS implementation tasks.
- 4.1.1 Roles and responsibilities
- 4.2 Data considerations
- 4.2.1 Data supported by ABARS
- 4.2.2 Catalog considerations
- 4.2.3 Naming conventions
- 4.2.4 Vaulting cycle
- 4.3 Setting up your ABARS environment
- 4.3.1 SETSYS commands for ABARS
- 4.3.2 DEFINE ARPOOL command
- 4.3.3 Security requirements
- 4.3.4 Tape management considerations
- 4.3.5 Expiring ABR records in the BCDS
- Chapter 5. Application characteristics
- 5.1 Current recovery strategies
- 5.2 Identifying job names and run schedules
- 5.3 Synchronization points
- 5.4 Database types
- 5.5 Application data sets
- 5.6 Interfacing systems
- 5.7 Externally created data sets
- 5.8 Dynamically built JCL
- Chapter 6. Aggregate definition
- 6.1 Defining management classes
- 6.2 Defining aggregates
- 6.2.1 Aggregate group definition with ISMF
- 6.2.2 Skipping data sets
- Chapter 7. Structuring applications using ASAP
- 7.1 Data collection methods
- 7.1.1 Job collection
- 7.1.2 Batch SMF collection
- 7.1.3 Real-time selection process (RSP)
- 7.2 Defining applications to ASAP
- 7.2.1 ASAP application naming conventions
- 7.3 Steps for setting up ASAP applications using RSP
- 7.3.1 Creating the application into ASAP
- 7.3.2 Job collection
- 7.3.3 Entering job names using ISPF interface
- 7.3.4 JES3 considerations
- 7.3.5 Collecting records using RSP
- 7.3.6 Application end
- 7.3.7 Verification
- 7.3.8 Initiating verification
- 7.3.9 Filters and controls
- 7.3.10 Creating universal and global filters
- 7.3.11 Local filters
- 7.3.12 Final verification
- 7.4 Identifying overlapping data sets
- 7.5 Aggregate balancing
- Chapter 8. Using ABACKUP
- 8.1 ABARS ABACKUP command
- 8.1.1 ABARS ABACKUP parameters
- 8.2 BRM ABACKUP command
- 8.2.1 Executing BRM ABACKUP
- 8.3 Initiating ABACKUP using ISPF dialog
- 8.4 Resolving common ABARS ABACKUP errors.
- Chapter 9. Managing aggregates with Backup &
- 9.1 Interactive Backup &
- 9.1.1 Online aggregate inquiry
- 9.1.2 Aggregate Management with SMS Interface
- 9.1.3 Backup/Recovery Management
- 9.1.4 Logical Aggregate Management
- 9.1.5 Group Filter Management
- 9.1.6 Search for Dataset
- 9.1.7 Reports
- 9.1.8 ABARS Monitor
- 9.1.9 History
- 9.1.10 Incremental ABARS
- 9.1.11 Prevent BackLevel
- 9.1.12 Dynamic Data Set Backup/Reorg
- 9.1.13 Full rename
- Chapter 10. Using ARECOVER
- 10.1 ABARS ARECOVER command
- 10.1.1 ABARS ARECOVER parameters
- 10.2 BRM ARECOVER command
- 10.2.1 ARECOVER SUBMIT command
- 10.3 Executing BRM ARECOVER command
- 10.3.1 Initiating ARECOVER using BRM dialog
- 10.3.2 Restarting ARECOVER
- 10.3.3 Recovering selected data sets using BRM
- Chapter 11. Migration considerations
- 11.1 Migration and coexistence
- 11.2 Removing existing backup procedures
- Appendix A. Sample questionnaire
- A.1 Questionnaire for current recovery strategies
- A.2 Questionnaire to identify names and run schedule
- A.3 Questionnaire for synchronization points
- A.4 Questionnaire for database types
- A.5 Questionnaire for application data sets
- A.6 Questionnaire for interfacing systems
- A.7 Questionnaire for externally created data sets
- A.8 Questionnaire for dynamically built JCL
- Abbreviations and acronyms
- Glossary
- Related publications
- IBM Redbooks
- Other resources
- Referenced Web sites
- How to get IBM Redbooks
- IBM Redbooks collections
- Index
- Back cover.
- Notes:
- "August 2002."
- "SG24-5089-01."
- Includes bibliographical references (p. 181) and index.
- OCLC:
- 560311832
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.