Backup and Recovery

iSeries

Backup and RecoveryVersion 5SC41-5304-05

iSeries

Backup and RecoveryVersion 5SC41-5304-05

Note Before using this information and the product it supports, be sure to read the information in Appendix I. Notices on page 893.

Sixth Edition (May 2001) This edition applies to version 5, release 1, modification 0 of IBM Operating System/400 (product number 5722-SS1) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition applies only to reduced instruction set computer (RISC) systems. This edition replaces SC41-5304-04. Copyright International Business Machines Corporation 1997, 2000, 2001. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

ContentsFigures . . . . . . . . . . . . . . xiii Tables . . . . . . . . . . . . . . . xv About Backup and Recovery, SC41-5304-05. . . . . . . . . . . . xixWho should read this book . . . . Prerequisite and related information . Operations Navigator . . . . . . Installing Operations Navigator . Operations Console . . . . . How to send your comments . . . . xix . xix . . . . . xx . . . . . xx . . . . . xxi . . . . . xxi . . . . . . . .

Chapter 2. Saving your Server

. . . . 1515 17 18 18 19 19 20 20 29 30 30 30 32 33 33

Summary of Changes to Backup and Recovery . . . . . . . . . . . . . xxiiiMoving to online media... . . . . . . . . . xxiii

Part 1. Designing Backup, Recovery, and Availability . . . . . . . . . . . 1Chapter 1. Options for Backup, Recovery, and AvailabilityOverview . . 3Save and Restore OperationsOverview . . Tape UnitsOverview . . . . . . . . Automated Tape Library SystemsOverview . Alternate Installation Device-Overview . . Optical Media SupportOverview . . . . Journal ManagementOverview . . . . . Access-Path ProtectionOverview . . . . System-Managed Access-Path Protection . Explicit Journaling of Access Paths . . . Commitment ControlOverview . . . . . Auxiliary Storage PoolsOverview . . . . Mirrored ProtectionOverview . . . . . Device Parity ProtectionOverview . . . . Comparison of Disk Protection Options . . Uninterruptible Power SupplyOverview . . Dual SystemsOverview . . . . . . . ObjectConnectOverview . . . . . . . OptiConnect for OS/400Overview . . . Backup Recovery and Media Services for iSeriesOverview . . . . . . . . . Tivoli Storage ManagerOverview . . . . Content Manager OnDemand for iSeries ServerOverview . . . . . . . . . Business Continuity and Recovery ServicesOverview . . . . . . . . . Data Migration Service OfferingsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 . 4 . 4 . 4 . 4 . 5 . 5 . 5 . 6 . 6 . 6 . 7 . 8 . 8 . 9 . 9 . 10 . 10 . 10 . 11 . 11 . 11 . 12

Saving your server with the GO SAVE command . . Overview of the GO SAVE command menu options . . . . . . . . . . . . . . . Change Save menu defaults with GO SAVE: Option 20 . . . . . . . . . . . . . . Save your whole server with GO SAVE: Option 21 . . . . . . . . . . . . . . . . Save system data with GO SAVE: Option 22 . . Save user data with GO SAVE: Option 23 . . . Saving parts of your server with other GO SAVE command menu options . . . . . . . . . Using GO SAVE: Options 21, 22, and 23 . . . . Using the ObjectConnect/400 Function . . . . . Components of ObjectConnect/400 . . . . . Setting Up Your System to Use ObjectConnect/400 . . . . . . . . . . . How the System Runs an ObjectConnect Command . . . . . . . . . . . . . . Using the ObjectConnect Commands . . . . . Investigating ObjectConnect Problems . . . . CPFAD84 Error Codes . . . . . . . . . .

Part 3. Recovering Information on Your System . . . . . . . . . . . 35Chapter 3. Restore ProceduresGeneral Information . . . . . . . . . . . . . 39The Relationship Between Save and Restore Commands . . . . . . . . . . . . . . What Happens When You Restore Objects . . . . Sequence for Restoring Related Objects . . . . . Putting Your System in a Restricted State . . . . Reclaiming Storage . . . . . . . . . . . . How to Reclaim Storage . . . . . . . . . Controlling Restoration of Security-Sensitive Objects How to Set the QMCHPOOL, QBASPOOL, and QPFRADJ System Values for a Different Processor or Memory . . . . . . . . . . . . . . Locked Objects While Restoring . . . . . . . How to Verify That Objects Are Restored Successfully . . . . . . . . . . . . . . Recovery from an Unsuccessful Restore Operation Recovering from an Error While Restoring Libraries . . . . . . . . . . . . . . Recovering from an Error While Restoring DLOs How to Perform a Normal IPL . . . . . . . . Parallel Restore Operations . . . . . . . . . Recovery Considerations for Cryptographic Access Provider . . . . . . . . . . . . . . . 41 42 45 45 46 46 50

53 53 54 56 56 57 58 59 60

| |

Part 2. Saving Information on Your System . . . . . . . . . . . . . . 13

Chapter 4. Selecting the Right Recovery Strategy . . . . . . . . . . 61Some Common Recovery Terminology . . . . . 61

Copyright IBM Corp. 1997, 2000, 2001

iii

| | | |

| | | |

Recovery Procedure for a Power Failure . . . . . 62 Recovery Procedure for a System Failure . . . . 63 Recovery Procedure for a Program Failure or Human Error . . . . . . . . . . . . . . 63 Choosing the Recovery Procedure for a Disk Failure or Disk Errors . . . . . . . . . . . . . 63 Actions for load source disk unit failureChecklist 1 . . . . . . . . . . . 65 Actions for load source disk unit failureChecklist 2 . . . . . . . . . . . 66 Actions for load source disk unit failureChecklist 3 . . . . . . . . . . . 67 Actions for load source disk unit failureChecklist 4 . . . . . . . . . . . 68 Actions for load source disk unit failureChecklist 5 . . . . . . . . . . . 72 Actions for non-load source disk unit failure or disk units in user ASP disk failureChecklist 6. . 76 Actions for non-load source disk unit failureChecklist 7 . . . . . . . . . . . 77 Actions for non-load source disk unit failureChecklist 8 . . . . . . . . . . . 78 Actions for non-load source disk unit failureChecklist 9 . . . . . . . . . . . 79 Actions for non-load source disk unit failureChecklist 10 . . . . . . . . . . . 82 Actions for a failure in a user ASP disk unitChecklist 11 . . . . . . . . . . . 86 Actions for a failure in a user ASP disk unitChecklist 12 . . . . . . . . . . . 86 Actions for a failure in a user ASP disk unitChecklist 13 . . . . . . . . . . . 88 Actions for non-load source disk unit failureChecklist 14 . . . . . . . . . . . 90 Actions for non-load source disk unit failureChecklist 15 . . . . . . . . . . . 91 Actions for non-load source disk unit failureChecklist 16 . . . . . . . . . . . 92 Actions for independent ASP disk failureChecklist 17 . . . . . . . . . . . 93 Actions for a failure in an independent ASP disk unitChecklist 18 . . . . . . . . . . . 93 Actions for a failure in an independent ASP disk unitChecklist 19 . . . . . . . . . . . 94 Recovering your entire system after a complete system lossChecklist 20 . . . . . . . . . 96 Recovering your entire system after a complete system loss including independent ASPsChecklist 21 . . . . . . . . . . . 98 Recovering your entire system after a complete system loss including independent ASPs, when Service Tools Network Interface is configuredChecklist 22 . . . . . . . . . 102 Restoring a Logical Partition to Another Logical PartitionChecklist 23 . . . . . . . . . 105 Choosing the Procedure to Recover User Information . . . . . . . . . . . . . . 107 Recovering User Information Using CommandsChecklist 24. . . . . . . . . 108 Using Option 21 from the Restore MenuChecklist 25 . . . . . . . . . . 112

Using Options 22 and 23 from the Restore MenuChecklist 26 . . . . . . . . . . 114 Recovering User Information Using Tapes from Operational Assistant BackupChecklist 27 . . 117

Chapter 5. Recovering the Licensed Internal Code . . . . . . . . . . . 121How to Prepare for Loading the Licensed Internal Code . . . . . . . . . . . . . . . . Task 1Getting Ready to Load the Licensed Internal Code . . . . . . . . . . . . Task 2Powering Down the System . . . . . Task 3aPreparing the System to Perform an IPL from an Alternate Device . . . . . . . . Task 3b-Preparing a Logical Partition to Perform an IPL from an Alternate Device . . . . . . Task 4Loading the Licensed Internal Code from Media . . . . . . . . . . . . . . . How to Load the Licensed Internal Code . . . . How to Recover Your Logical Partition Configuration . . . . . . . . . . . . . How to Recover Your Disk Configuration After Installing the Licensed Internal Code and Initializing the System . . . . . . . . . . How to Recover Your Disk Configuration Using Operations Navigator at DST . . . . . . . . How to Recover Your Disk Configuration . . . . How to Start Your System After Restoring Licensed Internal Code . . . . . . . . . . . . . Disabling and Enabling the High-Speed Feature on the 2440 Tape Unit . . . . . . . . . . . 122 122 123 124 125 125 130 134

135 138 142 145 145

| |

Chapter 6. Restoring the Operating System . . . . . . . . . . . . . . 147Choosing the Right Procedure for Restoring the Operating System . . . . . . . . . . . . How to Load the Operating System Using a Manual IPL . . . . . . . . . . . . . . How to Restore the OS/400 Licensed Program . . Task 1Starting to Restore the Operating System Task 2Selecting the Installation Options . . . Task 3Selecting IPL Options . . . . . . . Task 4Setting Major System Options . . . . Task 5Defining or Changing the System at IPL Task 6Completing the IPL . . . . . . . . Recovering from SRC A900 2000 . . . . . . . Creating a Configuration for 34xx Tape Units Creating a Configuration for Other Tape Units 148 149 149 150 154 158 160 160 162 164 165 166

Chapter 7. Starting the System After It Ends Abnormally . . . . . . . . . . 167What Happens When Your System Stops . . . Using the Disk Configuration Error Report Display . . . . . . . . . . . . . Using the Main Storage Dump Manager Occurred Display . . . . . . . . . . How to Restart Your System . . . . . . . Task 1Performing an Attended IPL . . . . Task 2Using the Edit Rebuild of Access Paths Display . . . . . . . . . . . . . . 167 . 168 . 168 . 169 . 169 . 171

iv

OS/400 Backup and Recovery V5R1

Task 3Using the Edit Check Pending Constraints Display . . . . . . . . . . 173 Task 4Recovering from Damaged Objects and Unreadable Sectors . . . . . . . . . . 174

Chapter 9. The Restore Menu . . . . 207What the Restore Menu Options Do . . . . . . 208 How to Use Restore Menu Options 21, 22, and 23 208

Chapter 8. Recovering Information in a User Auxiliary Storage Pool . . . . 181Describing the Contents of Your User Auxiliary Storage Pools . . . . . . . . . . . . . Choosing the Procedure to Recover User ASPs . . How to Recover a User ASP After Recovering the System ASP . . . . . . . . . . . . . . Task 1Reclaiming Storage . . . . . . . . Task 2Restoring User Profiles. . . . . . . Task 3Restoring the Configuration . . . . . Task 4Recovering Journals and Journal Receivers in the QRCL Library . . . . . . Task 5Restoring Libraries to the System Auxiliary Storage Pool . . . . . . . . . Task 6Restoring Document Library Objects to the System Auxiliary Storage Pool . . . . . Task 7Restoring User-Defined File Systems to the User Auxiliary Storage Pool . . . . . . Task 8Reclaiming Document Library Objects Task 9Recovering Save Files from the QRCL Library . . . . . . . . . . . . . . Task 10Associating Journal Receivers with Journals . . . . . . . . . . . . . . Task 11Restoring Object Ownership . . . . How to Recover An Overflowed User Auxiliary Storage Pool . . . . . . . . . . . . . . Resetting An Overflowed User Auxiliary Storage Pool without an IPL . . . . . . . Resetting An Overflowed User Auxiliary Storage Pool during an IPL . . . . . . . . How to Delete Overflowed Objects during Recovery . . . . . . . . . . . . . . . How to Recover a Damaged User Auxiliary Storage Pool . . . . . . . . . . . . . . Task 1Restoring User Profiles. . . . . . . Task 2Determining the Contents of the Lost Auxiliary Storage Pool . . . . . . . . . Task 3Determining Tasks to Restore Objects Task 4Restoring Libraries to the User Auxiliary Storage Pool . . . . . . . . . . . . . Task 5Restoring Journals to the User Auxiliary Storage Pool . . . . . . . . . . . . . Task 6Restoring Documents to the User Auxiliary Storage Pool . . . . . . . . . Task 7Restoring User-Defined File Systems to the User Auxiliary Storage Pool . . . . . . Task 8Restoring Journal Receivers to the User Auxiliary Storage Pool . . . . . . . . . Task 9Restore Save Files to the User Auxiliary Storage Pool . . . . . . . . . . . . . How to Remove a Failed Disk Unit from the System ASP . . . . . . . . . . . . . . Task 1Access Dedicated Service Tools . . . . Task 2Delete the Auxiliary Storage Pool Data Task 3Remove the Disk Unit from the Auxiliary Storage Pool Configuration . . . . 181 182 182 183 184 185 185 186 187 187 188 188 189 190 191 192 193 196 196 196 197 197 198 198 200 200 201 201 202 202 203 204

Chapter 10. How to Restore Specific Types of Information . . . . . . . . 213Recovering System Information . . . . . . . Sequence for Restoring Security Information . . . Restoring User Profiles . . . . . . . . . . What Happens When You Restore User Profiles What You Should Know About Restoring User Profiles . . . . . . . . . . . . . . How the System Establishes Ownership for Restored Objects . . . . . . . . . . . How the System Establishes the Authorization List for a Restored Object . . . . . . . . How the System Establishes the Primary Group for Restored Objects . . . . . . . . . . Restoring Object Authorities . . . . . . . . Overview of Restoring Authorities . . . . . Restoring Authority On a System in a Non-Restricted State . . . . . . . . . . Restoring Authority On a System in a Restricted State . . . . . . . . . . . . . . . What the System Does When You Restore Authority. . . . . . . . . . . . . . How to Restore Configuration Objects . . . . . Correcting Problems with the System Resource Management Information . . . . . . . . Recovering When You Change the Console Type Recovering the System/36 Environment Configuration . . . . . . . . . . . . Restoring Logical Partitions . . . . . . . . Restoring Libraries . . . . . . . . . . . Restoring a Library From a Previous Release Restoring Multiple Libraries . . . . . . . Considerations and Restrictions . . . . . . How to Restore All Libraries from a Single Save Operation . . . . . . . . . . . . . How to Restore All Libraries from Multiple Save Operations . . . . . . . . . . . How to Restore Objects . . . . . . . . . . Restoring Objects That Are Journaled . . . . . What Happens When You Restore Journaled Objects to a Different Library . . . . . . . Restoring Database Files. . . . . . . . . . Comparing File Attributes during a Restore Operation . . . . . . . . . . . . . How the System Matches File Members during a Restore Operation . . . . . . . . . . Restoring Members to a File . . . . . . . Restoring Logical Files . . . . . . . . . How the System Restores Access Paths . . . . How the System Restores Files with Shared Formats . . . . . . . . . . . . . . How the System Restores Files with Referential Constraints . . . . . . . . . . . . . How the System Restores Files with Triggers Steps Before Deleting a Physical File . . . . Restoring Journals and Journal Receivers . . . .Contents

213 213 214 215 216 218 218 218 219 219 220 225 225 227 228 230 230 231 231 232 232 233 233 234 234 235 235 236 238 241 241 242 242 245 245 247 248 248

| | |

v

|

Restoring Journals . . . . . . . . . . . Steps before Deleting a Journal . . . . . . Restoring Journal Receivers. . . . . . . . Steps before Deleting a Journal Receiver . . . How the System Restores Programs . . . . . . Restoring Programs to a Different Release . . . Restoring OPM Program Objects . . . . . . . Restoring Save File Data. . . . . . . . . . Restoring Spooled Output Files . . . . . . . Restoring Licensed Programs . . . . . . . . Restoring Documents and Folders . . . . . . RSTDLO Command Options . . . . . . . Using Multiple Concurrent DLO commands . . Output from the RSTDLO Command . . . . Considerations and Restrictions . . . . . . Restoring Folders . . . . . . . . . . . Renaming Documents When Restoring . . . . Restoring OfficeVision/400 Mail and Distribution Objects . . . . . . . . . . How the System Restores Descriptive Information for DLOs . . . . . . . . . How the System Restores Authority and Ownership for DLOs . . . . . . . . . . When to Run the Rename Directory (RNMDIRE) Command . . . . . . . . . When to Run the Rename Document Library Object (RNMDLO) Command . . . . . . . Recovery of Text Index Files for Text Search Services . . . . . . . . . . . . . . . Restoring Objects in Directories . . . . . . . Completing Recovery for the iSeries Integration for Windows Server Product . . . . . . . . . Recovery for save performed with Integrated xSeries Server varied off . . . . . . . . . Recovery for save performed with Integrated xSeries Server varied on . . . . . . . . . Recovering Linux in a Partition . . . . . . Recovery Steps for OS/400 Enhanced Integration for Novell NetWare . . . . . . Recovering a Domino Server. . . . . . . . Recovering an entire Domino server . . . . . Recovering Domino mail . . . . . . . . Recovering specific Domino databases . . . . Restoring changed objects to a Domino server Restoring a Windows server . . . . . . . . Restoring the NWSD and disk drives for Windows server on iSeries . . . . . . . . Recovering Windows server files . . . . . . Examples: How to address parts of Windows server . . . . . . . . . . . . . . . Restrictions When Using the Restore Command How to Restore Program Temporary Fixes. . . .

248 249 250 251 252 253 254 255 255 255 255 255 256 256 256 258 258 258 259 259 260 260 260 261 263 263 264 264 264 265 265 266 267 267 270 270 273 274 275 278

Task 3Determining Whether You Need to Apply Journaled Changes . . . . . . . . . . . Task 4Determining What Journal Receivers to Use Task 5Applying Journaled Changes for User Journals . . . . . . . . . . . . . . . Task 6Applying Journaled Changes for the QAOSDIAJRN Journal . . . . . . . . . . Task 7Restoring Changed Documents and Folders

282 282 284 286 287

Chapter 12. Mirrored Protection Recovery Actions . . . . . . . . . 289System Actions for Permanent Errors . . . . . Suspending Mirrored Units. . . . . . . . . Resuming Mirrored Units . . . . . . . . . Replacing a Mirrored Unit . . . . . . . . . Using Spare Nonconfigured Units for Replacement. . . . . . . . . . . . . Mirrored Protection Recovery Actions Performed by the Service Representative . . . Other Recovery Considerations for Mirrored Protection . . . . . . . . . . . . . Mirrored Protection Disk-Error Handling . . . Missing Disk Units . . . . . . . . . . Saving a Unit . . . . . . . . . . . . Restoring a Unit . . . . . . . . . . . Active Mirrored Load Source Failure . . . . Unknown Unit 1 Status . . . . . . . . . Display Incorrect Licensed Internal Code Install 289 290 291 292 294 296 297 297 298 299 299 299 301 302

Chapter 13. How to Restore Your System Using Operational Assistant Tapes . . . . . . . . . . . . . . . 305How to Restore Your Libraries. . . . . . . . 306 How to Restore Libraries That You Saved by Using a Backup List . . . . . . . . . . . . . 307 How to Restore Changed Objects That You Saved by Using Operational Assistant . . . . . . . 308

Chapter 14. How to Restore the System from the Save Storage Media . 311Task 1Powering Down the System and Loading the Licensed Internal Code . . . . . . . . . Task 2Restoring the Save Storage Tapes . . . . Task 3Responding to Messages . . . . . . . Task 4Completing the Restore Storage Operation Task 5Restoring Additional Information . . . . Task 6Restoring Program Temporary Fixes (PTFs) How to Resume the Restore Storage Operation . . 311 312 314 315 318 318 318

Part 4. Release-to-Release Support 321Chapter 15. Release-to-Release Support . . . . . . . . . . . . . . 323Current Release-to-Previous Release Support . Creating the Object for the Previous Release Saving the Object for the Previous Release Testing the Object on the Current Release . . . . . . . . . 323 324 325 330

Chapter 11. How to Restore Changed Objects and Apply Journaled Changes . . . . . . . . . . . . . 279Task 1Restoring Changed Objects . . . . . Restoring Changed Objects by Library . . . Restoring Changed Objects Individually . . Task 2Restoring Changed Objects in Directories . 280 . 280 . 280 281

vi


Restoring and Using the Object on the Previous Release . . . . . . . . . . . . . . Restrictions for Current Release-to-Previous Release Support . . . . . . . . . . . Previous Release-to-Current Release Support . . . Considerations when Moving System Customization Information . . . . . . . . Restoring previous release user data to a new system . . . . . . . . . . . . . . Restrictions when going from previous release to current release . . . . . . . . . . .

331 331 331 332 332

| |

|348

Chapter 16. System Synchronization-Planning and Procedures . . . . . . . . . . . . 351Synchronization Methods: Overview . . . Moving Changed Objects . . . . . . . Steps for Saving Changed Objects . . . Steps for Restoring Changed Objects . . Problems When Restoring Changed Objects Moving Entire Libraries . . . . . . . . Considerations for Moving Entire Libraries Moving Individual Objects . . . . . . . Applying Journaled Changes . . . . . . Refreshing Your new system . . . . . . Additional Synchronization Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 353 354 355 357 358 360 360 361 363 363

Part 5. Considerations for Merging Two or More Systems. . . . . . . 367Chapter 17. Tips for Merging Two RISC Systems Into a Single RISC System . . . . . . . . . . . . . . 369Guidelines for Restoring Information from the Development System . . . . . . . . . . . 369

| | |

Part 6. Journaling and Commitment Control . . . . . . . 371Chapter 18. Protecting Access Paths Using System-Managed Access-Path Protection . . . . . . . . . . . . . 375| Using SMAPP with Independent ASPs . . . . . 375Benefits of SMAPP . . . . . . . . . . How SMAPP Works with Access Path Journaling How the System Chooses Which Access Paths to Protect . . . . . . . . . . . . . . How SMAPP Affects System Performance and Auxiliary Storage Use . . . . . . . . . Working with Recovery Times for Access Paths . How SMAPP Handles Changes in the Configuration of Auxiliary Storage Pools . . . . 376 376 . 377 . 377 . 378 . 380

Commands and APIs for Journal Receivers . . Commands and APIs for Journal Entries . . . Commands and APIs for Starting and Ending Journaling of an Object . . . . . . . . . Commands and APIs for Getting Information about Journaled Objects . . . . . . . . . Commands for Recovering an Object by Using the Journaled Changes . . . . . . . . . Planning Journal Management. . . . . . . . What Objects Should You Journal? . . . . . Should You Journal Objects That the System Does Not Journal? . . . . . . . . . . . Should You Use Access Path Journaling? . . . How Should Objects Be Assigned to Journals? Should You Journal Before-Images? . . . . . Should Your Journal Receivers Be in a User ASP? . . . . . . . . . . . . . . . Journaling with the Save-While-Active Function Journaling and System Performance . . . . . . Journaling and Auxiliary Storage . . . . . . . How to Estimate the Size of a Journal Receiver Journaling Features That Increase the Journal Receiver Size . . . . . . . . . . . . Setting Up Journaling . . . . . . . . . . How Journal Receivers Are Created . . . . . How Journals Are Created . . . . . . . . Creating Journals and Journal ReceiversExamples . . . . . . . . . . Starting Journaling . . . . . . . . . . . How to Start Journaling for Physical Files . . . How to Start Journaling for DB2 Multisystem Files . . . . . . . . . . . . . . . How to Start Journaling for Access Paths . . . How to Start Journaling for IFS objects . . . . How to Start Journaling for Data Areas and Data Queues . . . . . . . . . . . . Why You Must Save Objects after Starting Journaling . . . . . . . . . . . . . Tasks for Managing Your Journaling Environment Keep Records of Journaled Objects . . . . . Evaluate How System Changes Affect Journaling . . . . . . . . . . . . . How to Manage Journals and Journal Receivers Ending Journaling . . . . . . . . . . . . How to End Journaling for DB2 Multisystem Files . . . . . . . . . . . . . . . Managing IBM-Supplied Journals. . . . . . .

386 386 387 387 388 388 389 390 391 391 392 393 394 394 395 396 397 398 399 402 409 411 411 412 412 413 414 414 415 415 416 416 423 423 424

Chapter 20. Working with Journal Entries, Journals, and Journal Receivers . . . . . . . . . . . . . 427About Journal Entries . . . . . . . . . Contents of a Journal Entry. . . . . . . Sending Your Own Journal Entries . . . . . Displaying and Printing Journal Entries . . . Output for Journal Entries Directed to a Work Station . . . . . . . . . . . . . Output for Journal Entries Directed to a Database Output File . . . . . . . . . Using the Receive Journal Entry Command . .Contents

. . . .

427 428 429 429

Chapter 19. Planning and Setting Up Journaling. . . . . . . . . . . . . 383Journal Management Commands and APIs Commands and APIs for Journals . . . . . . . 385 . 385

. 430 . 431 . 432

vii

| | | |

Exit Program for Receiving Journal Entries . . Using the Retrieve Journal Entry Command . . . Using the Retrieve Journal Entries (QjoRetrieveJournalEntries) API . . . . . . . Working With Pointers in Journal Entries . . . . Working with entries which contain minimized entry-specific data . . . . . . . . . . . . Data Area Considerations . . . . . . . . Database Physical File Considerations . . . . Using Journaling to Provide an Audit Trail . . . Comparing Journal Images . . . . . . . . . Journal Receiver Chains . . . . . . . . . . Using the Work with Journal Attributes Command Working with the Receiver Directory . . . . Inoperable Journal Receivers . . . . . . . Applying and Removing Journaled Changes . . . How Applying and Removing Journaled Changes Works with Referential Constraints . . How Applying and Removing Journaled Changes Works with Trigger Programs . . . . Applying Journaled Changes . . . . . . . Apply Journaled Changes (APYJRNCHG) Command Examples . . . . . . . . . . Removing Journaled Changes . . . . . . . Remove Journaled Changes (RMVJRNCHG) Command Examples . . . . . . . . . . Actions of the APYJRNCHG or RMVJRNCHG Command by Journal Code. . . . . . . . Work with Journal (WRKJRN) Command Options Recovery Options . . . . . . . . . . . Recovery of a Journaled Object Using Journaled Changes . . . . . . . . . . . . . . Recovery after Abnormal System End . . . . Recovering When a Journal Is Damaged . . . Recovering When a Journal Receiver Is Damaged . . . . . . . . . . . . . .

433 436 437 437 438 439 439 439 440 440 442 442 444 444 445 446 446 448 450 451 452 455 456 462 462 464 465

Auxiliary Storage Considerations . . . . . . . 494 Main Storage Considerations . . . . . . . . 494 Example Remote Journal Function Environments 494 Data Replication Environment . . . . . . . 494 Hot-Backup Environment . . . . . . . . 497 Displaying Remote Journal Function Information 499 Managing the Remote Journal Function . . . . 499 Keeping Records of Your Remote Journal Network . . . . . . . . . . . . . . 499 Evaluating How System Changes Affect Your Remote Journal Network . . . . . . . . 499 Maintaining Journal Receivers . . . . . . . 500 Save and Restore Considerations . . . . . . 500 Working with Journal Entries and the Remote Journal Function . . . . . . . . . . . . 505 Retrieving Journal Entries from a Remote Journal with Library Redirection . . . . . . 506 System Dependent Information . . . . . . 506 Retrieving Journal Entries from a Remote Journal During the Catch-up Phase . . . . . 506 Retrieving Journal Entries with Commitment Control Considerations . . . . . . . . . 507 Confirmed and Unconfirmed Journal Entries 508 IPL Considerations . . . . . . . . . . . 509 Main Storage Considerations during IPL . . . 510 Journal Receiver ASP Considerations . . . . . 511 Example: Remote Journal Function Recovery . . . 511 Example Scenario Description . . . . . . . 513

Chapter 22. Commitment Control . . . 525Commitment Control Introduction . . . . . . Terms Used with Commitment Control . . . . . Commitment Control Startup . . . . . . . . Lock-Level Parameter . . . . . . . . . Notify Object Parameter . . . . . . . . . Commit Scope Parameter . . . . . . . . Commit Text Parameter . . . . . . . . . Default Journal Parameter . . . . . . . . Omit Journal Entries Parameter . . . . . . Two-Phase CommitOverview. . . . . . . . Placing Resources Under Commitment Control . . Types of Committable Resources . . . . . . Location of Committable Resources . . . . . The Commit Protocol of a Committable Resource . . . . . . . . . . . . . . The Access Intent of a Committable Resource Files Being Journaled under Commitment Control Sequence of Journal Entries Under Commitment Control . . . . . . . . . . . . . . . Commit Cycle Identifier . . . . . . . . . . Commit and Rollback Operations . . . . . . Roles in Commit Processing . . . . . . . How the System Performs a Commit Operation How the System Performs a Rollback Operation Flow of Commit Processing . . . . . . . Errors During Commit Processing . . . . . Changing the Commitment Definition to Not Wait for Outcome . . . . . . . . . . . Changing the Commitment Definition to Not Select a Last Agent . . . . . . . . . . 525 526 527 527 530 533 539 539 540 540 541 541 543 544 544 545 545 547 547 548 549 550 551 554 554 557

Chapter 21. Remote Journal FunctionIntroduction to the Remote Journal Function . . Benefits of the Remote Journal Function . . Remote Journal Function Configuration Examples . . . . . . . . . . . . . Supported Communications Protocols . . . Release to Release Considerations . . . . Planning for the Remote Journal Function . . . Determining Which Journals are Good Candidates for Remote Journals . . . . . Determining Which Communications Protocol and Delivery Mode to Use . . . . . . . How Do the Journal Attributes Affect the Remote Journal Function? . . . . . . . Setting up the Remote Journal Function . . . Preparing to use Remote Journal Function . . Adding a Remote Journal . . . . . . . Activating and Inactivating a Remote Journal Activating and Inactivating a Local Journal . Summary of the Journal Type, Delivery Mode, and Journal State Interactions . . . . . . Removing a Remote Journal . . . . . . Troubleshooting Errors . . . . . . . . Performance Considerations . . . . . . .

467. 467 . 467 . . . . 468 470 471 472

. 472 . 472 . . . . 473 473 473 474 479 . 487 488 490 491 492

. . . .

viii


Changing the Commitment Definition to Indicate OK to Leave Out . . . . . . . . Changing the Commitment Definition to Allow Vote Read-Only . . . . . . . . . . . Vote Reliable Affect on Flow of Commit Processing . . . . . . . . . . . . . Retrieving Commitment Control Information . . . States of the Logical Unit of Work (LUW) . . . . XA Transaction Support . . . . . . . . . . Commitment Control Recovery during Initial Program Load . . . . . . . . . . . . . Making Heuristic Decisions and Cancelling Resynchronization . . . . . . . . . . . . Implicit Commit and Rollback Operations . . . . Commitment Control Status . . . . . . . . End Commitment Control (ENDCMTCTL) Command . . . . . . . . . . . . . . Commitment Control during Activation Group End Commitment Control during Normal Routing Step End . . . . . . . . . . . . . . . . Commitment Control during Abnormal System or Job End . . . . . . . . . . . . . . . Commitment Control during a Save-While-Active Operation . . . . . . . . . . . . . . Commitment Control Considerations and Restrictions . . . . . . . . . . . . . . The Size of a Transaction . . . . . . . . Record Locking. . . . . . . . . . . . Minimizing Locks . . . . . . . . . . . Commitment Control for Batch Applications . . Performance Considerations for Commitment Control . . . . . . . . . . . . . . Miscellaneous Considerations and Restrictions for Commitment Control . . . . . . . . Commitment Control Errors . . . . . . . . Error Conditions . . . . . . . . . . . Non-Error Conditions . . . . . . . . . Monitoring for Errors after a CALL Command Error Messages to Monitor for Commitment Control . . . . . . . . . . . . . . Normal Commit or Rollback Processing . . . Commit or Rollback Processing During Job End Commit or Rollback Processing During IPL . . Example of Using Commitment Control . . . . Example of Transaction Logging File . . . . . Starting Application Programs Using a Notify Object . . . . . . . . . . . . . . . . Using a Unique Notify Object for Each Program Using a Single Notify Object for All Programs Using a Standard Processing Program . . . . Commitment Control Practice Problem . . . . . Steps Associated with Logic Flow . . . . .

558 560 562 564 564 566 569 570 573 576 579 580 581 581 583 584 584 585 586 588 588 591 592 592 594 595 595 598 599 599 599 602 608 609 614 614 622 631

Install and Recovery Implications for Models 600, 620, 720, and S20 . . . . . . . . . How to Set Up an Alternate Installation Device How to Disable an Alternate Installation Device Recovering Your System Using an Alternate Installation Device. . . . . . . . . . .

635 635 638 639

Part 8. Disk Configuration and Protection Procedures . . . . . 641Chapter 24. Procedures for Configuring Disks and Disk Protection 643Choosing the Right Procedure for Configuring Disks . . . . . . . . . . . . . . . . Configuring Disks on a New SystemChecklist 1 Adding Disk Units without Device Parity ProtectionChecklist 2 . . . . . . . . . Adding Disk Units to a 9337 Disk Array SubsystemChecklist 3 . . . . . . . . . Adding a New 9337 Disk Array Subsystem and Starting Device Parity Protection on ItChecklist 4 . . . . . . . . . . . . . . . . Adding a New 9337 Disk Array Subsystem That Has Device Parity Protection Already StartedChecklist 5 . . . . . . . . . . Adding Disk Units to an Existing Input/Output ProcessorChecklist 6. . . . . . . . . . Adding a New Input/Output ProcessorChecklist 7. . . . . . . . . . Moving Disk Units Between Non-Mirrored Auxiliary Storage PoolsChecklist 8 . . . . . Moving Disk Units Between Mirrored Auxiliary Storage PoolsChecklist 9 . . . . . . . . Deleting an Auxiliary Storage PoolChecklist 10 Removing Disk Units Without Device Parity ProtectionChecklist 11 . . . . . . . . . Removing Disk Units with Device Parity Protection (9337) from an ASP Without Mirrored ProtectionChecklist 12 . . . . . . . . . Removing Disk Units That Have Device Parity Protection(9337) from an ASP with Mirrored ProtectionChecklist 13 . . . . . . . . . Removing Disk Units That Have Device Parity Protection from an ASP Without Mirrored ProtectionChecklist 14 . . . . . . . . . Removing Disk Units That Have Device Parity Protection from an ASP With Mirrored ProtectionChecklist 15 . . . . . . . . . Using System Service Tools and Dedicated Service Tools . . . . . . . . . . . . How to Display Your Disk Configuration . . . 643 644 645 646

647

648 649 650 652 653 654 655

656

657

658

659 660 663

Part 7. Alternate Installation Device . . . . . . . . . . . . . . 633Chapter 23. Using an Alternate Installation Device . . . . . . . . . 635Alternate Installation Device-Overview . . . . . 635

Chapter 25. Working with Auxiliary Storage Pools . . . . . . . . . . . 669How to Add Disk Units to an Auxiliary Storage Pool . . . . . . . . . . . . . . . How to Change the Storage Threshold for an Auxiliary Storage Pool . . . . . . . . . . 669 . 672

Contents

ix

How to Change the Storage Threshold for the System Auxiliary Storage Pool. . . . . . . . How to Move a Disk Unit to a Different Auxiliary Storage Pool . . . . . . . . . . . . . . How to Remove a Disk Unit from an Auxiliary Storage Pool . . . . . . . . . . . . . . How to Delete an Auxiliary Storage Pool . . . . How to Calculate Space Requirements for an Auxiliary Storage Pool . . . . . . . . . . Task 1Calculating the Current Storage Used Task 2Calculating Storage Needed . . . . . How to Display the Objects in a User ASP . . . Balancing an Auxiliary Storage Pool . . . . . . Capacity Balancing . . . . . . . . . . Usage Balancing . . . . . . . . . . . Hierarchical Storage Management (HSM) Balancing. . . . . . . . . . . . . . Transferring Objects between Auxiliary Storage Pools . . . . . . . . . . . . . . . . How to Move Authorities to a Different ASP How to Transfer a Library to a Different ASP How to Transfer a Folder to a Different ASP . . How to Transfer Journals and Objects to a Different ASP . . . . . . . . . . . . How to Create Objects in a Library User ASP How to Place Journal Receivers in a User ASP How to Move Journal Receivers From an Overflowed User ASP . . . . . . . . . How to Reset a Journal with a Status of Overflowed . . . . . . . . . . . . . How to Work with Nonlibrary User ASPs . . . . Creating Objects in a Nonlibrary User ASP . . Transferring an Object to a Nonlibrary User ASP Transferring a Journal to a Nonlibrary User ASP

673 676 678 680 681 682 683 684 685 685 685 685 686 686 687 687 687 688 689 690 691 692 692 693 693

What the System Does When You Start Mirrored Protection . . . . . . . . . . . . . 722 Mirrored Protection Configuration Errors . . . . 722 How to Stop Mirrored Protection . . . . . . . 723

Chapter 28. Working with Disk Compression . . . . . . . . . . . 725Introduction to Disk Compression . . . . . Restrictions and Considerations . . . . . Disk Compression and Capacity . . . . . Disk Unit Full Considerations . . . . . . How The System Responds to Disk Unit Full SRC Code A6xx 0277 . . . . . . . . . . User Action 1 . . . . . . . . . . . User Action 2 . . . . . . . . . . . User Action 3 . . . . . . . . . . . User Action 4 . . . . . . . . . . . Examples of A6xx 0277 . . . . . . . . How to Start Disk Compression . . . . . . How to Stop Disk Compression . . . . . . Procedural Sequences for Configuring Disks and Protection . . . . . . . . . . . . . Adding a New I/O Compression-Capable Storage Controller . . . . . . . . . . Adding Disk Units to an Existing Compression-Capable Storage Controller . . Moving Disk Units from the System ASP to a User ASP . . . . . . . . . . . . . Recovering from Error Codes . . . . . . . Recovering from SRC 6xxx 7051 . . . . . Recovering from SRC 6xxx 7052 . . . . . . . . . . . . . . . . . 725 725 726 728 728 729 730 731 731 731 732 732 735

. 737 . 737 . 738 . . . . 739 740 740 741

Chapter 29. Managing Auxiliary Storage Pools . . . . . . . . . . . 743Working with ASP Trace and ASP Balance. Capacity Balance . . . . . . . . Hierarchical Storage Management (HSM) Balance . . . . . . . . . . . Usage Balance . . . . . . . . . ASP Trace . . . . . . . . . . Determining adequate disk storage . . . . . . . . . . . . . . . . 743 . 744 . . . . 745 745 746 746

Chapter 26. Working with Device Parity Protection . . . . . . . . . . 695Starting Device Parity Protection . . . . . . . How to Start Device Parity Protection for a 9337 Disk Array Subsystem . . . . . . . . . How to Start Device Parity Protection for an Input/Output Processor . . . . . . . . . Stopping Device Parity Protection . . . . . . How to Stop Device Parity Protection for a 9337 Disk Array Subsystem . . . . . . . . . How to Stop Device Parity Protection on an Input/Output Processor . . . . . . . . . How to Include a Disk Unit in Device Parity Protection . . . . . . . . . . . . . . How to Exclude a Disk Unit from Device Parity Protection . . . . . . . . . . . . . . How to Display Device Parity Status . . . . . How to Enable Disk Units Attached to the MFIOP to Use Device Parity Protection . . . . . . . 695 695 699 701 701 704 705 707 708 710

Chapter 30. Creating Logical Partitions . . . . . . . . . . . . . 747Preparing for Logical Partitions . . . Hardware and Software Requirements Logical Partitions . . . . . . . Before You Partition Your System. . . Creating a Logical Partition. . . . . . . for . . . . . . . . . . . 747 . 747 . 748 . 749

Part 9. Backup and Recovery Tools and Techniques . . . . . . 757Chapter 31. Techniques and Programming Examples for Backup and Recovery . . . . . . . . . . . 759Job Recovery Considerations . Interactive Job Recovery . . . . . . . . . . . . . . . 759 . 759

Chapter 27. Working with Mirrored Protection . . . . . . . . . . . . . 719Mirrored ProtectionConfiguration Rules . How to Start Mirrored Protection. . . . . . . . . 719 . 719

x


Batch Job Recovery . . . . . . . . . Considerations for Using Save Files . . . . . Using Control Language (CL) Commands for Save Files . . . . . . . . . . . . Save File Security . . . . . . . . . . Opening a Save File . . . . . . . . . Input and Output Operations on a Save File . File-Dependent Attributes for a Save File . . Damage to a Save File . . . . . . . . Clearing a Save File . . . . . . . . . Sending Network Files . . . . . . . . Programming Examples for Backup and Recovery Retrieving the Device Name from Save Completion Messages . . . . . . . . Displaying Status Messages When Saving . . Using the Retrieve Journal Entry (RTVJRNE) Command in a Program . . . . . . . . CL Program to Handle Escape Conditions . . Writing output to save media using the receive journal entry command . . . . . . . .

. 760 . 761 . . . . . . . . 762 762 763 763 764 764 764 764 765

. 765 . 766 . 766 . 767 . 769

Calculating the Time to Add Disk Units to the System ASP . . . . . . . . . . . . Calculating the Time to Move Extents . . . Determining the Time to Synchronize the Disk 9406 Model 500 Using the 6602 Disk Unit Configuration . . . . . . . . . . . . Calculating the Time to Add Disk Units to the System . . . . . . . . . . . . . Calculating the Time to Move Extents . . . Determining the Time to Synchronize the Disk Assessment of Single-Points-of-Failure . . . . System 1 . . . . . . . . . . . . . System 2 . . . . . . . . . . . . . Full Mirrored Protection Versus Partial Mirrored Protection . . . . . . . . . . . . .

. 796 . 797 797 . 798 . 798 . 799 799 . 800 . 800 . 801 . 803

Appendix D. Journal Entry Information 805Journal Codes . . . . . . . . . . Journal Entries by Journal Code and Type . The Fixed-Length Portion of a Journal Entry Variable-Length Portion of a Journal Entry . . . . . . . . . . . . 806 807 815 821

Part 10. Appendixes . . . . . . . 773Appendix A. Licensed Internal Code Installation Error Screens . . . . . . 775 Appendix B. Example Disaster Recovery Plan . . . . . . . . . . . 783Section 1. Major Goals of a Disaster Recovery PlanExample . . . . . . . . . . . . . Section 2. PersonnelExample . . . . . . . . Organization Chart . . . . . . . . . . Section 3. Application ProfileExample . . . . . Section 4. Inventory ProfileExample . . . . . Section 5. Information Services Backup Procedures Section 6. Disaster Recovery Procedures . . . . Disaster Action Checklist . . . . . . . . Recovery Start-Up Procedures for Use after Actual Disaster . . . . . . . . . . . . Section 7. Recovery PlanMobile Site . . . . . Mobile Site Setup Plan . . . . . . . . . Communication Disaster Plan . . . . . . . Electrical Service . . . . . . . . . . . Section 8. Recovery PlanHot Site . . . . . . Hot-Site System Configuration . . . . . . Section 9. Restoring the Entire System . . . . . Section 10. Rebuilding Process. . . . . . . . Section 11. Testing the Disaster Recovery Plan . . Section 12. Disaster Site Rebuilding . . . . . . Vendors . . . . . . . . . . . . . . Floor Plan . . . . . . . . . . . . . Section 13. Record of Plan Changes . . . . . . 783 783 784 784 784 785 786 786 787 787 788 788 788 789 789 789 790 790 792 793 793 793

Appendix E. How to Create and Use Output from the Save and Restore Commands . . . . . . . . . . . . 857Format of the Output. . . . Header Information Format Command Information . . Directory Information . . Object Link Information . . Trailer Information . . . Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857 858 858 859 860 861 861

Appendix F. Procedures for Recovering the Text Index . . . . . . 867 Appendix G. Recovering your system 871

Appendix H. Using Operational Assistant to Save Information . . . . 885Summary of Operational Assistant Commands and Menu Options for Backup . . . . . . . . . Getting Started with Operational Assistant Backup Defining What Should Be Saved . . . . . . . How the System Saves Changed Objects Using Operational Assistant Backup . . . . . . . . How to Define Backup Operations . . . . . . How to Define When Backup Operations Are Run 886 887 888 889 890 891

Appendix I. Notices . . . . . . . . . 893Trademarks . . . . . . . . . . . . . . 894

Appendix C. Example of Configuration Planning for Mirrored Protection . . . 7959406 Model 500 Using the 9336 Disk Unit Configuration . . . . . . . . . . . . . 795

Bibliography . . . . . . . . . . . . 897 Index . . . . . . . . . . . . . . . 901

Contents

xi

xii


Figures1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. Operations Navigator Display . . . . . . xx Save commands and menu options . . . . 16 Save MenuFirst Display . . . . . . . . 17 ObjectConnect Job Flow . . . . . . . . 31 Restore Procedures . . . . . . . . . . 40 Save procedures and restore procedures for file systems . . . . . . . . . . . . . . 41 User ASP Configuration Before Failure 181 User ASP Configuration After Restoring Operating System . . . . . . . . . . 183 User ASP Configuration After Reclaiming Storage . . . . . . . . . . . . . 184 User ASP Configuration After Recovering Isolated Journal Receiver. . . . . . . . 186 Restore MenuFirst Display . . . . . . . 207 Sample Job Log for RSTAUT on a System in a Restricted State . . . . . . . . . . . 222 Expanded Text for Message CPF3736 222 Expanded Text for Message CPF3845 223 Sample Job Log for RSTAUT on a System in a Non-restricted State . . . . . . . . . 223 Expanded Text for Message CPF3845 224 Example: Restoring a Journaled Object to a Different Library . . . . . . . . . . 236 Example of a Database File with Two Members . . . . . . . . . . . . . 237 Restoring a Copy of a File . . . . . . . 238 Restoring Database Files with Different Creation Dates . . . . . . . . . . . 239 Restoring Database Files with Different Creation Dates . . . . . . . . . . . 240 Restoring Access Paths . . . . . . . . 244 Restoring a Referential Constraint Network 246 An Object with Hard LinksExample 262 An Object with a Symbolic LinkExample 263 Sample Recovery Time Line. . . . . . . 279 Receiver DirectorySaving Attached Receivers 283 Receiver DirectorySaving Detached Receivers . . . . . . . . . . . . . 283 How the System Is Saved with Operational Assistant Backup . . . . . . . . . . 306 Recovery steps for restoring previous release user data to a new system . . . . . . . 333 Overview of Synchronization Process 352 Edit Recovery for Access Paths Display 378 Journaling Overview . . . . . . . . . 385 First Parameter of RCVJRNE CommandSingle-Entry Mode . . . . . . 435 First Parameter of RCVJRNE CommandBlock Mode . . . . . . . . 435 Creating a Journal Receiver . . . . . . . 441 Work with Receiver Directory . . . . . . 443 Hot-Backup Environment without Remote Journal Function, and Application-Code Based Apply . . . . . . . . . . . . 468

| | | | |

| |

|

| | |

39. Hot-Backup Environment with Remote Journal Function, and Application-Code Based Apply . . . . . . . . . . . . 40. Broadcast and Cascade Remote Journal Configurations . . . . . . . . . . . 41. Typical Data Replication Environment with Remote Journal Function. . . . . . . . 42. Typical Hot-Backup Environment with Remote Journal Function. . . . . . . . 43. Journal Receiver Restore Characteristics and Remote Journal Types. . . . . . . . . 44. Example Remote Journal Environment for Hot-Backup Recovery . . . . . . . . . 45. More unconfirmed journal entries present in BJ1 than known in PJ1. . . . . . . . . 46. Switch-over processing. System S2 is now ready to allow applications to run. . . . . 47. System S2 has assumed the role of the primary, and DB is now being updated. IPL processing has completed on system S1. . . 48. State of the journals and databases just before starting to replay the changes back to the original data, DB. . . . . . . . . . . 49. Preparing to let S1 again assume the role of the primary system. . . . . . . . . . 50. Preparing to let S1 again assume the role of the primary system (continued). . . . . . 51. Overview of Commitment Control Process 52. Using multiple commitment definitions in a job . . . . . . . . . . . . . . . 53. Roles in Two-Phase Commit ProcessingSingle-Level Tree . . . . . . 54. Roles in Two-Phase Commit ProcessingMulti-Level Tree. . . . . . . 55. Flow of Commit Processing without Any Optimization. . . . . . . . . . . . 56. Flow of Commit Processing with Last Agent Optimization. . . . . . . . . . . . 57. Wait for OutcomeYes . . . . . . . . 58. Wait for OutcomeNo. . . . . . . . . 59. Flow of Commit Processing without Last Agent Optimization when agent votes OK to leave out . . . . . . . . . . . . . 60. Flow of Commit Processing without Last Agent Optimization when agent votes read only . . . . . . . . . . . . . . 61. Flow of Commit Processing with Vote Reliable optimization . . . . . . . . . 62. Routing Steps with Files under Commitment Control . . . . . . . . . . . . . 63. Journal Entries for Transfer of Funds from Savings to Checking . . . . . . . . . 64. Journal Entries for a System That Ended Abnormally . . . . . . . . . . . . 65. Journal Entries for Rollback Changes 66. DDS for Physical File PRDMSTP . . . . .

468 469 495 498 502 512 514 516

518

520 522 523 527 538 548 549 552 553 556 557

559

561 563 600 601 601 602 603


xiii

67. DDS for Physical File ISSLOGP Used by ISSLOGP . . . . . . . . . . . . 68. DDS for Logical File ISSLOGL . . . . . 69. DDS for Display File PRDISSD Used in the Program . . . . . . . . . . . . 70. Program Flow . . . . . . . . . . 71. RPG Program . . . . . . . . . . 72. CL Program Used to Call RPG Program PRDISS . . . . . . . . . . . . 73. DDS for Physical File PRDLOCP . . . . 74. DDS for Display File PRDRCTD . . . . 75. DDS for Notify Object and Externally Described Data Structure (PRDRCTP) . . 76. Program Flow . . . . . . . . . . 77. RPG Source . . . . . . . . . . . 78. Application Program Example . . . . . 79. Standard Commit Processing Program 80. Initial Program Example . . . . . . . 81. RPG Source Program for ITMPTCS . . . 82. DDS for the Display File . . . . . . . 83. Logic Flow of the Practice Problem . . .

. 603 . 603 . 604 . 605 . 607 . 607 . 609 . 610 . . . . . . . . 610 612 613 617 620 622 624 629 630

84. 85. 86. 87. 88. 89. 90. 91. 92. 93. 94. 95. 96. 97. 98. 99. 100. 101.

Display Hardware Resource Listing . . . . Sample Disk Configuration . . . . . . . Program for Save Completion Messages Program for Saving Source Files . . . . . Program for Retrieving Journal Entries Example Program Prompts for Restoring the Required Receiver For an APYJRNCHG. . . Program for writing RCVJRNE output to save media . . . . . . . . . . . . . . 9406 Model 500 Original Configuration 9406 Model 500 Mirrored Configuration 9406 Model 500 Original Configuration 9406 Model 500 Mirrored Configuration 9406 Model 500 with 9336 Disk Unit Configuration . . . . . . . . . . . System 19406 Model 500 Configuration System 29406 Model 500 Configuration Output Sequence 1SAV and RST Commands Output Sequence 2SAV and RST Commands Operational Assistant Save Options . . . . Change Monthly Backup Options Display

664 682 765 766 767 768 770 796 796 798 798 800 801 802 857 858 886 888

xiv


Tables1. Comparison of Disk Protection Options . . . 9 2. Spooled Files Created by the server . . . . 27 3. ObjectConnect/400 and Associated iSeries Save and Restore Commands . . . . . . . . 29 4. Relationship Between Save and Restore Commands. . . . . . . . . . . . . 42 5. Restoring Objects with ALWOBJDIF . . . . 43 6. Resolving Problems Detected by the RCLSTG Procedure . . . . . . . . . . . . . 48 7. Lock Type Needed for Restore Operation 54 8. Choosing the Correct Recovery Procedure for Disk Media Failure . . . . . . . . . . 64 9. Recovery Checklist for Disk FailureChecklist 1 . . . . . . . . . . . . . . . . 66 10. Recovery Checklist for Disk FailureChecklist 2 . . . . . . . . . . . . . . . . 66 11. Recovery Checklist for Disk FailureChecklist 4 . . . . . . . . . . . . . . . . 69 12. Recovery Checklist for Disk FailureChecklist 5 . . . . . . . . . . . . . . . . 73 13. Recovery Checklist for Disk FailureChecklist 6 . . . . . . . . . . . . . . . . 76 14. Recovery Checklist for Disk FailureChecklist 7 . . . . . . . . . . . . . . . . 77 15. Recovery Checklist for Disk FailureChecklist 8 . . . . . . . . . . . . . . . . 78 16. Recovery Checklist for Disk FailureChecklist 9 . . . . . . . . . . . . . . . . 79 17. Recovery Checklist for Disk FailureChecklist 10 . . . . . . . . . . . . . . . . 82 18. Recovery Checklist for Disk FailureChecklist 11 . . . . . . . . . . . . . . . . 86 19. Recovery Checklist for Disk FailureChecklist 12 . . . . . . . . . . . . . . . . 87 20. Recovery Checklist for Disk FailureChecklist 13 . . . . . . . . . . . . . . . . 89 21. Recovery Checklist for Disk FailureChecklist 14 . . . . . . . . . . . . . . . . 91 22. Recovery Checklist for Disk FailureChecklist 15 . . . . . . . . . . . . . . . . 91 23. Recovery Checklist for Disk FailureChecklist 16 . . . . . . . . . . . . . . . . 92 24. Recovery Checklist for Disk FailureChecklist 17 . . . . . . . . . . . . . . . . 93 25. Recovery Checklist for Disk FailureChecklist 18 . . . . . . . . . . . . . . . . 94 26. Recovery Checklist for Disk FailureChecklist 19 . . . . . . . . . . . . . . . . 94 27. Recovery Checklist for Complete System LossChecklist 20 . . . . . . . . . . 97 28. Recovery Checklist for Complete System LossChecklist 21 . . . . . . . . . . 99 29. Recovery Checklist for Complete System LossChecklist 22 . . . . . . . . . . 102 30. Recovery Checklist for Complete System LossChecklist 23 . . . . . . . . . . 105 Copyright IBM Corp. 1997, 2000, 2001

| |

| | | |

| |

31. Choosing the Correct Recovery Procedure for User Information . . . . . . . . . . 32. Checklist for Recovering User Information Using Commands . . . . . . . . . . 33. Checklist for Recovering User Information Using Option 21 . . . . . . . . . . 34. Checklist for Recovering User Information Using Options 22 and 23 . . . . . . . . 35. Checklist for Recovering User Information Using Operational Assistant Backup Tapes . . 36. Options from the Install the Licensed Internal Code (LIC) Menu . . . . . . . . . . 37. SRC Codes When Loading the Licensed Internal Code . . . . . . . . . . . 38. Configuring Disk While Installing the Operating System . . . . . . . . . . 39. Recovery for Damaged Objects by Object Type . . . . . . . . . . . . . . 40. Object Types That Require Special Procedures for Deleting . . . . . . . . . . . . 41. Tasks for Restoring User ASP Objects 42. Commands for Changing System Information 43. How User Profiles Are Restored . . . . . 44. Results of Restoring User Profiles . . . . . 45. Restoring an Object Linked to an Authorization List . . . . . . . . . . 46. How Configuration Objects Are Restored 47. Methods for Restoring All LibrariesSingle Save Operation . . . . . . . . . . . 48. Methods for Restoring All LibrariesMultiple Save Operations . . . . . . . . . . 49. Restoring a File Network . . . . . . . 50. Restoring Files That Have Trigger Programs 51. System Actions When Restoring Programs 52. Restoring Objects That Have Hard Links 53. Using the RST Command for QSYS.LIB Objects. . . . . . . . . . . . . . 54. New Name Options on the RST CommandExamples . . . . . . . . . 55. Restore Procedures for Changed Objects 56. Handling Messages When Restoring Storage 57. Values for TGTRLS Parameter . . . . . . 58. Language Support for the Target Release Parameter. . . . . . . . . . . . . 59. Previous-Release Support by Object Type 60. Comparison of Synchronization Methods 61. System-Generated Receiver Names . . . . 62. System-Generated Receiver Names . . . . 63. System-Created Journal Receiver Names 64. IBM-Supplied Journals . . . . . . . . 65. Methods for Working with Journal Entries 66. Actions by Journal Code and Entry Type 67. Journal Types and Associated Characteristics 68. Summary of the Journal Type, Delivery Mode and Journal State Interactions . . . . . . 69. Lock Duration by Lock-Level Parameter

107 109 112 114 117 121 127 152 175 192 197 213 214 216 218 227 233 234 244 247 252 262 276 277 280 315 323 324 326 353 399 400 400 424 427 452 476 488 528

xv

70. Specifying a Commit Identification . . . . 71. Commitment Definition Names for a Job 72. Additional Examples of Multiple Commitment Definitions in a Job . . . . . 73. Types of Committable Resources . . . . . 74. Local and Remote Committable Resources 75. Coexistence Rules for One-Phase Resources and Two-Phase Resources . . . . . . . 76. Access Intents for Resource Types. . . . . 77. Sequence of Commitment Control Journal Entries . . . . . . . . . . . . . . 78. Language Support for Commit and Rollback Operations . . . . . . . . . . . . 79. Logical Unit of Work (LUW) States . . . . 80. Commit and Rollback Operations During Job End . . . . . . . . . . . . . . . 81. Commit and Rollback Operations during Activation Group Ending . . . . . . . 82. Commit and Rollback Processing for Failures. 83. Choosing the Right Disk Procedure . . . . 84. Configuring Disks on a New SystemTasks 85. Adding Disk Units without Device Parity ProtectionTasks . . . . . . . . . . 86. Adding Disk Units to an Existing 9337 Disk Array SubsystemTasks . . . . . . . . 87. Adding a New 9337 Disk Array Subsystem That Does Not Have Device Parity Protection StartedTasks . . . . . . . . . . . 88. Adding a New 9337 Disk Array Subsystem That Has Device Parity Protection Already StartedTasks . . . . . . . . . . . 89. Adding Disk Units to an Existing Input/Output ProcessorTasks . . . . . . 90. Adding a New Input/Output ProcessorTasks 91. Moving Disk Units Between ASPsTasks 92. Moving Disk Units Between ASPs with mirrored protectionTasks . . . . . . . 93. Deleting an Auxiliary Storage PoolTasks 94. Removing Disk Units That Do Not Have Device Parity ProtectionTasks . . . . . . 95. Removing Disk Units with Device Parity Protection from an ASP without Mirrored ProtectionTasks . . . . . . . . . . 96. Removing Disk Units from a 9337 Disk Array Subsystem and a Mirrored ASPTasks . . . 97. Removing Disk Units from an IOP and a Non-Mirrored ASPTasks . . . . . . . 98. Removing Disk Units from an IOP and a Mirrored ASPTasks . . . . . . . . . 99. Worksheet for Calculating ASP Capacity 100. Calculating ASP CapacityExample 2 101. Calculating ASP CapacityExample 3 102. Word formats for SRC codes in V4R5. 103. SRC code word formats in V4R4 and previous releases. . . . . . . . . . . 104. Adding a New I/O Storage Controller and Disk Units . . . . . . . . . . . . 105. Adding Compressed Disk Units to an Existing Storage Controller . . . . . . . 106. Moving Disk Units from the System ASP to a User ASP . . . . . . . . . . . . .

531 536 539 541 543 544 544 546 547 565 574 576 598 643 644 646 647

| |

648

649 650 651 652 653 654 655

656 657 658 659 681 683 684 729 730 737 738 739

| |

107. Hardware requirements for logical partitions 108. System Resource Worksheet. . . . . . . 109. Checklist for Testing the Disaster Recovery Plan . . . . . . . . . . . . . . 110. Journal Entries by Journal Code and Type 111. Field Descriptions of the Fixed-Length Portion of a Journal Entry: *TYPE1 . . . . 112. Field Descriptions of the Fixed-Length Portion of a Journal Entry: *TYPE2 . . . . 113. Field Descriptions of the Fixed-Length Portion of a Journal Entry: *TYPE3 . . . . 114. Field Descriptions of the Fixed-Length Portion of a Journal Entry: *TYPE4 . . . . 115. APYJRNCHG (B AJ, E EQ, F AY) and RMVJRNCHG (E EX, F RC) Journal Entries . 116. Change End of Data (F CE) Journal Entry 117. CHGJRN (J NR, J PR) Journal Entries 118. COMMIT (C CM) Journal Entry . . . . . 119. Delete Access Path (R PD) Journal Entry 120. Delete Receiver (J RD, J RF) Journal Entries 121. Force Data to Auxiliary Storage (F FD) Journal Entry . . . . . . . . . . . 122. INZPFM (F IZ) Journal Entry . . . . . . 123. IPL (J IA, J IN) and In-Use (B OI, D ID, E EI, F IU, Q QI) Journal Entries . . . . . . . 124. Logical Unit of Work (C LW) Journal Entry 125. Logical Unit of Work (C LW) Journal EntryHeader Record . . . . . . . . . 126. Logical Unit of Work (C LW) Journal EntryLocal Record . . . . . . . . . 127. Logical Unit of Work (C LW) Journal EntryAPI Record . . . . . . . . . . 128. Logical Unit of Work (C LW) Journal EntryDDL Record. . . . . . . . . . 129. Logical Unit of Work (C LW) Journal EntryRMT Record . . . . . . . . . 130. Logical Unit of Work (C LW) Journal EntryDDM Record . . . . . . . . . 131. Moving and Renaming Objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, Q QM, Q QN) Journal Entries . . . . . . . 132. File OPEN (F OP) and File CLOSE (F CL) Journal Entries . . . . . . . . . . . 133. Journal Code R, All Journal Entry Types Except IL . . . . . . . . . . . . . 134. RGZPFM (F RG) Journal Entry. . . . . . 135. ROLLBACK (C RB) Journal Entry . . . . . 136. Object Restored (B FR, E EL, F MR, J RR, Q QZ) and Receiver Saved (J RS) Journal Entries 137. Object Saved (B FS, E ES, F MS, Q QY) Journal Entries . . . . . . . . . . . 138. Start of Save-While-Active (B FW, E EW, F SS, Q QX) Journal Entries. . . . . . . . . 139. Start Journal (B JT, E EG, F JM, Q QB) Journal Entries . . . . . . . . . . . . . . 140. License Key Not Valid (L LK) Journal Entry 141. Usage Limit Changed (L LL) Journal Entry 142. Usage Limit Exceeded (L LU) Journal Entries 143. Update Data Area (E EA, E EB) Journal Entries . . . . . . . . . . . . . .

748 750 790 807 815 818 819 820 822 823 823 823 823 824 824 824 824 824 825 834 835 838 841 845

847 847 848 848 849 849 850 851 852 853 853 853 853

xvi


| | | | | | | | | | |

144. Data Queue Cleared, has Key (Q QJ) Journal Entry . . . . . . . . . . . . . . 145. Send Data Queue, has Key (Q QK) Journal Entry . . . . . . . . . . . . . . 146. Received Data Queue, has Key (Q QL) Journal Entry . . . . . . . . . . . 147. Send Data Queue, No Key (Q QS) Journal Entry . . . . . . . . . . . . . . 148. Object Level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, F DM, F MC) Journal Entries . . . . 149. Heading Output InformationSAV and RST Commands . . . . . . . . . . . . 150. Command Information OutputSAV and RST Commands . . . . . . . . . . . .

854 854 854 855

855 858 858

151. Directory Information OutputSAV and RST Commands . . . . . . . . . . . 152. Object Link InformationOutput from SAV and RST Commands . . . . . . . . 153. Trailer InformationOutput from SAV and RST Commands. . . . . . . . . . 154. Recovery for Search Index Services Files 155. Type of Index Request Created when Using the Restore Document Library Object (RSTDLO) Command . . . . . . . . 156. Summary of Operational Assistant Backup Options . . . . . . . . . . . .

. 859 . 860 . 861 867

. 869 . 887

Tables

xvii

xviii


About Backup and Recovery, SC41-5304-05This book provides general information about recovery and availability options for the IBM iSeries server. It describes the options available on the system, compares and contrasts them, and tells where to find more information about them. This book release contains minimal information about how to back up your server. Look for comprehensive information about backing up your server on the iSeries Information Center at the following Web site: http://www.ibm.com/eserver/iseries/infocenter. This book provides information on the following topics: v Procedures on how to save your system with the Save menu optoins of the GO SAVE command. v Restoring to different releases of OS/400 v Selecting the right recovery strategy v Procedures for restoring information to your system | v v v v v Journal management and object recovery Commitment control Device Parity Protection procedures Mirrored protection procedures Uninterruptible power supply

v Backup and recovery programming techniques

Who should read this bookThis book is intended for someone who is assigned the responsibilities of backup and recovery planning and recovering the system after a failure. You should be familiar with the information contained in the Information Center Website before using this book. If you know how to operate the system, you should be ready to use this book.

Prerequisite and related informationUse the iSeries Information Center as your starting point for looking up iSeries technical information. You can access the Information Center from the iSeries Information Center CD-ROM (English version: SK3T-2027) or from one of this Web site:http://www.ibm.com/eserver/iseries/infocenter

The iSeries Information Center contains important topics such as logical partitioning, clustering, Java, TCP/IP, Web serving, backing up your system, and secured networks. It also contains Internet links to Web sites such as iSeriesTechnical Studio. Included in the Information Center is a link that describes at a high level the differences in information between the Information Center and the Online Library. For a list of related publications, see the Bibliography on page 897.


xix

Operations NavigatorOperations Navigator is a powerful graphical interface for Windows clients. With Operations Navigator, you can manage and administer your servers from your Windows desktop. You can use Operations Navigator to manage communications, printing, database, security, and other system operations. Operations Navigator includes Management Central for managing multiple servers centrally. Figure 1 shows an example of the Operations Navigator display:

Figure 1. Operations Navigator Display

This new interface has been designed to make you more productive and is the only user interface to new, advanced features of OS/400. Therefore, IBM recommends that you useOperations Navigator, which has online help to guide you. While this interface is being developed, you may still need to use a traditional emulator such as PC5250 to do some of your tasks.

Installing Operations NavigatorTo use Operations Navigator, you must have Client Access installed on your Windows PC. For help in connecting your Windows PC to your server consult Client Access Express for Windows - Setup, SC41-5507-02. Operations Navigator is a separately installable component of Client Access that contains many subcomponents. If you are installing for the first time and you use the Typical installation option, the following options are installed by default: v Operations Navigator base support v Basic operations (messages, printer output, and printers) To select the subcomponents that you want to install, select the Custom installation option. (After Operations Navigator has been installed, you can add subcomponents by using Client Access Selective Setup.) 1. Display the list of currently installed subcomponents in the Component Selection window of Custom installation or Selective Setup. 2. SelectOperations Navigator. 3. Select any additional subcomponents that you want to install and continue with Custom installation or Selective Setup.

xx


After you install Client Access, double-click the Operations Navigator icon on your desktop to access Operations Navigator and create a server connection.

Operations ConsoleMany of the newer iSeries and AS/400e models do not have a Twinaxial Workstation Controller, but are configured to use Operations Console instead. Operations Console allows you to use a PC to access and control the system console and the system control panel. If a system is configured to use Operations Console, and that system undergoes a backup and recovery cycle, you will have to perform the following steps: 1. Perform an initial program load (IPL) in Manual mode. 2. Use dedicated service tools (DST) to reconfigure the system so that it will detect the PC console when you perform an IPL in Normal mode. Detailed instructions on setting up Operations Console are in the document Operations Console Setup.

How to send your commentsYour feedback is important in helping to provide the most accurate and high-quality information. If you have any comments about this book or any other iSeries documentation, fill out the readers comment form at the back of this book. v If you prefer to send comments by mail, use the readers comment form with the address that is printed on the back. If you are mailing a readers comment form from a country other than the United States, you can give the form to the local IBM branch office or IBM representative for postage-paid mailing. v If you prefer to send comments by FAX, use either of the following numbers: United States and Canada: 1-800-937-3430 Other countries: 1-507-253-5192 v If you prefer to send comments electronically, use one of these e-mail addresses: Comments on books: [email protected] Comments on the iSeries Information Center: [email protected] Be sure to include the following: v The name of the book or iSeries Information Center topic. v The publication number of the book. v The page number or topic to which your comment applies.

About Backup and Recovery, SC41-5304-05

xxi

xxii


Summary of Changes to Backup and RecoveryNew and enhanced functionality that was added to the Operating System/400 licensed program for Version 5 Release 1 Modification 0. This additional function affects backup, recovery, and availability. Changes are identified by change bars to the left of the information. Changes to this publication include, but are not limited to, support for the following: v Expanded journaling that includes data areas data queues IFS objects additional journal attributes v Save and restore for digitally signed objects v Support for independent auxiliary storage pools v Support for save and restore of secondary partitions with Linux Look for performance information that was included in previous versions of this book in the Performance Capabilities Reference, SC41-0607 book. Access this book on the Internet at this uniform resource locator (URL) address:http://www.ibm.com/eserver/iseries/infocenter

| | | | | | | |

Moving to online media...| | | | The iSeries Information Center contains comprehensive information for backing up your iSeries or AS/400e server. The hardcopy book contains basic information on how to use the Save menu options with the GO SAVE command. This allows you to save all or parts of your iSeries or AS/400e system. You can download a printable Portable Document Format (PDF) version of each topic in this section. The iSeries Information Center contains the following topics for backing up your system: v Planning a backup and recovery strategy v v v v v Setting up disk protection for your data Controlling system shutdown using a power-handling program. Getting your media ready to save your system Before you save anything... Saving your system with the GO SAVE command (also in Saving your server with the GO SAVE command on page 15). v Manually saving parts of your system v Saving your system while it is active v Saving to multiple devices to reduce your save window Note: Copyright IBM Corp. 1997, 2000, 2001

| |

xxiii

Access the iSeries Information Center at the following Web site:http://www.ibm.com/eserver/iseries/infocenter

xxiv


Part 1. Designing Backup, Recovery, and AvailabilityChapter 1. Options for Backup, Recovery, and AvailabilityOverview . . . . . . . . . . Save and Restore OperationsOverview . . . . Tape UnitsOverview . . . . . . . . . . Automated Tape Library SystemsOverview . . . Alternate Installation Device-Overview . . . . Optical Media SupportOverview . . . . . . Journal ManagementOverview . . . . . . . Access-Path ProtectionOverview . . . . . . System-Managed Access-Path Protection . . . Explicit Journaling of Access Paths . . . . . Commitment ControlOverview . . . . . . . Auxiliary Storage PoolsOverview . . . . . . Mirrored ProtectionOverview . . . . . . . Device Parity ProtectionOverview . . . . . . Comparison of Disk Protection Options . . . . Uninterruptible Power SupplyOverview . . . . Dual SystemsOverview . . . . . . . . . ObjectConnectOverview . . . . . . . . . OptiConnect for OS/400Overview . . . . . Backup Recovery and Media Services for iSeriesOverview . . . . . . . . . . . Tivoli Storage ManagerOverview . . . . . . Content Manager OnDemand for iSeries ServerOverview . . . . . . . . . . . Business Continuity and Recovery ServicesOverview . . . . . . . . . . . Data Migration Service OfferingsOverview . . . 3 . 3 . 4 . 4 . 4 . 4 . 5 . 5 . 5 . 6 . 6 . 6 . 7 . 8 . 8 . 9 . 9 . 10 . 10 . 10 . 11 . 11 . 11 . 12

| |


1

2


Chapter 1. Options for Backup, Recovery, and AvailabilityOverviewToday, computer systems and the applications and information that they provide are at the heart of most businesses. Without the critical functions they supportcustomer service, sales, order processing, distribution, manufacturingbusiness quickly comes to a halt. You need to plan backup, recovery, and system availability to protect your ability to maintain crucial business functions no matter what happens. Planning can mean the difference between business success and business failure. IBM iSeries and AS/400e servers offer a wide range of recovery and availability options. Your hardware or software includes some of the options. Others are ordered separately. They are intended to help you do the following: v Make your save operations faster and more efficient. v Keep your system available for your users. v Plan and manage your backup and recovery. This chapter provides an overview of the options. The iSeries Information Center provides comparisons of the options. Use this information to decide what other options beyond the basics might be useful, affordable, and practical for your situation. The overview of each option tells you where you can find more information if that option appeals to you. The remaining parts of this book include the following topics: v Recovering your system. v Using journaling and commitment control. v Configuring disks and disk protection.

Save and Restore OperationsOverviewYour Operating System/400 (OS/400) licensed program includes menus and commands for save and restore. You can use the save operations and restore operations on the system to do the following: v Recover from a program or system failure. v Exchange information between servers. v Store infrequently used objects offline. You can use commands and menu options to save individual objects and groups of objects. You can use some save and restore operations while your system is active. Other save and restore operations require that no other activity is occurring on the system. You can save and restore objects by using diskette, magnetic tape, optical media, or a save file. You can also use communications capabilities or an optical connection to save and restore objects with another system. If your system is busy most of the time, you can use the save-while-active function to reduce the time period that the system is unavailable while you are performing save operations. Copyright IBM Corp. 1997, 2000, 2001

3

Comprehensive information about save procedures and the save-while-active functions are in the Information Center. You can read more about restore procedures in Chapter 3. Restore ProceduresGeneral Information on page 39.

Tape UnitsOverviewThe iSeries and AS/400e servers offer many different types of tape units to meet a variety of requirements for performance, capacity, and cost. In many cases, you can attach enough tape drives with sufficient media capacity to save your entire system without operator intervention. This allows a complete unattended save operation. For more information about the tape units that are available to attach to your system, call 1-800-IBM-CALL (1-800-426-2255). You can read about tape performance in the Performance Capabilities Reference, ZC410607.

Automated Tape Library SystemsOverviewAutomated tape library systems are a combination of hardware and software that store, catalog, and load large numbers of tapes without operator intervention. On iSeries and AS/400e servers, Backup Recovery and Media Services (BRMS/400) software supports the use of an automated tape library system. You can read more about using automated tape library systems with the iSeries and AS/400e servers in the Automated Tape Library Planning and Management book or point your browser to the following URL: | | |http://www.ibm.com/eserver/iseries/service/brms.htm

Alternate Installation Device-OverviewAlternate Installation Device support allows you to perform installation and recovery procedures using a combination of devices. Previously, these types of activities could only be performed using devices attached to the first system bus. Now, you can use a combination of devices that are attached on the first system bus and on additional buses. The alternate installation device is not attached to the first system bus. If you use this function, the system uses existing support (a device on the first system bus) to install or recover enough of the Licensed Internal Code required to perform an IPL with IPL-type D. Then, using the new alternate installation device support, the system continues the operation using media in the alternate installation device. This new function supports installation and recovery from tape media, such as SAVSYS tapes or distribution tapes which you created, that contains Licensed Internal Code and may contain the operating system, licensed programs, and data. Some models, typically with 3590 tape devices attached, may see a performance improvement when using an alternate installation device for save operations.

Optical Media SupportOverview| | | | | You can save your entire system, all of your system data, or all of your user data, to optical media. The DVD-RAM optical media standalone device supports all save and restore commands. It is an economical alternative to tape for save/restore operations on entry level systems. The Optical Support, (SC41-5310), book provides more information about using optical media.

4


Journal ManagementOverview| | | | | | | | You can use journal management to recover the changes to various objects that have occurred since your last complete save. You use a journal to define what objects you want to protect with journal management. This is often referred to as journaling an object. A journal receiver contains the entries (called journal entries) that the system adds when events occur that are journaled, such as changes to database files, changes to other journaled objects, or security-relevant events. See Chapter 19. Planning and Setting Up Journaling on page 383 for a list of object types that can be journaled. You can use the remote journal function to set up journals and journal receivers on a remote iSeries or AS/400eserver. These journals and journal receivers are associated with journals and journal receivers on the source system. The remote journal function allows you to replicate journal entries from the source system to the remote system. The main purpose of journal management is to assist in recovery. You can also use the information that is stored in journal receivers for other purposes, such as: | v An audit trail of activity that occurs for various objects on the system. v Assistance in testing application programs. You can use journal entries to see the changes made by a particular program. You can read more about planning and setting up journal management in Chapter 19. Planning and Setting Up Journaling on page 383. Information about the remote journal function is provided in Chapter 21. Remote Journal Function on page 467.

Access-Path ProtectionOverviewAn access path describes the order in which records in a database file are processed. A file can have multiple access paths, if different programs need to see the records in different sequences. If your system ends abnormally when access paths are in use, the system may have to rebuild the access paths before you can use the files again. This is a time-consuming process. To perform an IPL on a large, busy iSeries or AS/400e server that has ended abnormally can take many hours. You can use journal management to keep a record of changes to access paths. This greatly reduces the amount of time it takes the system to perform an IPL after it ends abnormally. Two methods of access-path protection are available: v System-managed access-path protection v Explicit journaling of access paths

System-Managed Access-Path ProtectionYou can allow the system to determine which access paths to protect. You specify target recovery times for access paths for the entire system or for auxiliary storage pools (ASPs). Your system has a default recovery time for access paths for the entire system of 90 minutes when it is shipped. You can use the Edit Recovery for Access Paths (EDTRCYAP) command to see and change the target recovery times for access paths and to see how much space the system is using for system-managed access-path protection (SMAPP).Chapter 1. Options for Backup, Recovery, and AvailabilityOverview

5

SMAPP provides a simple method to reduce your recovery time after an abnormal system end. SMAPP manages the required environment for you. You do not need to use any type of journal management to use SMAPP. You can read more about SMAPP in Chapter 18. Protecting Access Paths Using System-Managed Access-Path Protection on page 375.

Explicit Journaling of Access PathsWhen you use SMAPP, the system decides which access paths to protect, based on overall target recovery times for access paths. You may want to make sure that certain access paths are protected because they are critical to your business. You can use journal management to explicitly protect access paths on your system. You can use a combination of SMAPP and explicit journaling of access paths. The system evaluates the protected and unprotected access paths to develop its strategy for meeting your recovery targets for access paths. Chapter 19. Planning and Setting Up Journaling on page 383 describes explicit journaling of access paths.

Commitment ControlOverviewCommitment control is an extension of journal management that assists you in keeping your database files synchronized. A single transaction on your system may update more than one database file. If your system is in a network, a single transaction may update files on more than one system. Commitment control helps ensure that: v All changes within a transaction are completed for all files that are affected. v If processing is interrupted before the transaction is completed, all changes within a transaction are removed. v Changes that are made during a transaction can be removed when the user program determines that it is necessary to do so. This is called a rollback operation. Without commitment control, recovering data for a complicated program requires detailed application and program knowledge. Programs that are interrupted cannot easily be started again. To restore the data to the last completed transaction, you may need to write a user program or use data file utility (DFU) to reverse the database updates that are not complete. The commit (COMMIT) and rollback (ROLLBACK) operations are available in several iSeries or AS/400e server programming languages including ILE RPG*, ILE COBOL*, ILE C*, control language (CL), and Structured Query Language (SQL). You can read more about commitment control in Chapter 22. Commitment Control on page 525.

Auxiliary Storage PoolsOverviewYour system may have many disk units attached to it for auxiliary storage of your data. To your system, they look like a single unit of storage. The system spreads data across all disk units. You can use auxiliary storage pools to separate your disk units into logical subsets.

6


An auxiliary storage pool (ASP)is a group of units that are defined from all the disk units that make up auxiliary storage. It is a software definition of how the disk units are arranged. An ASP does not necessarily correspond to the physical arrangement of disks. ASPs allow you to isolate objects on one or more specific disk units. This may reduce the loss of data due to a disk media failure. In most cases, only data that is stored on disk units in the affected ASP is lost. However, when a disk unit fails, the entire system is unusable until the disk unit is repaired, unless the failed unit is protected by device parity protection or mirrored protection. ASPs are used to manage system performance and backup requirements: v You can create an ASP to provide dedicated resources for frequently used objects, such as journal receivers. v You can create an ASP to hold save files. Objects can be backed up to save files in a different ASP. It is unlikely that both the ASP that contains the object and the ASP that contains the save file will be lost. v You can create different ASPs for objects with different recovery and availability requirements. For example, you can put critical database files or documents in an ASP that has mirrored protection or device parity protection. v You can create an ASP to place infrequently used objects, such as large history files, on disk units with slower performance. v You can use ASPs to manage recovery times for access paths for critical and noncritical database files using system-managed access-path protection. | Three types of ASPs are available on the system: v The system creates the system ASP (ASP 1) and is always configured. It contains the Licensed Internal Code, licensed programs, system libraries, and temporary system work space. The system ASP also contains all other configured disk units that are not assigned to a user ASP. | | | | | | | | | | | | | | v Grouping together a physical set of disk units and assigning them a number (2 through 32) creates a basic user ASP. ASP 1 is always reserved as the system ASP. v ASPs 33 through 99 are independent user ASPs, also known as independent disk pools in Operations Navigator. You can use clustering software to make them switchable ASPs. When you make an independent ASP switchable, you can switch it among iSeries 400 servers or logical partitions. If you choose to switch these ASPs among iSeries 400 servers, the ASPs must consist of external disk units. If you choose to switch these ASPs among logical partitions, the ASPs can consist of internal disk units. To use independent ASPs, you must use Operations Navigator. You can find more information about independent ASPs in the Information Center web site at this URL:http://www.ibm.com/eserver/iseries/infocenter/

You can read more about ASPs in Chapter 25. Working with Auxiliary Storage Pools on page 669.

Mirrored ProtectionOverviewIf a disk failure occurs, mirrored protection is intended to prevent data from being lost. Mirrored protection is a software function that uses duplicates of disk-related hardware components to keep your system available if one of the components fails. It can be used on any model of the iSeries or AS/400e server and is a part of the Licensed Internal Code.Chapter 1. Options for Backup, Recovery, and AvailabilityOverview

7

Different levels of mirrored protection are possible, depending on what hardware is duplicated. You can duplicate: v Disk units v Disk controllers v Disk I/O processors v A bus The system remains available during the failure if a failing component and the hardware components that are attached to it are duplicated. You can read more about mirrored protection in Chapter 27. Working with Mirrored Protection on page 719.

Device Parity ProtectionOverviewDevice parity protection is intended to prevent data from being lost if a disk failure occurs. In many cases, device parity protection can also prevent your system from stopping when a disk unit fails. Device parity protection provides the following: v Technology similar to the RAID-5 (redundant array