IBM SG24-5360-00 manual Backing up Vsam Volumes

Page 70

Warning

This approach may not work with VSAM files that specify share options 2 or

4.The reason for the problem here is that, with SHROPTN(2), or SHROPTN(4), VSE/VSAM′s method of enqueuing the file (to protect it during a

write) uses the file ID of the VSAM catalog and the volume serial number of the volume.

Notes:

Share option 2 provides that the file may be opened by more than one request for input processing and, at the same time, by one request for output processing. This option ensures write integrity; however, the file might be modified while records are retrieved from it, so every user must ensure his or her own file′s read integrity.

Share option 4 provides that a key-sequenced or relative-record file can be opened by any number of requests (ACBs) for both input and output processing by users in the first system requesting output to the file. Once a file has been opened for output by one system, VSE/VSAM accepts only open for input requests from another system. Share option 4 for an entry-sequenced file is treated as though it were a share option 2.

If, for any reason, the file were to be opened for output processing while the target is online to the VSE/ESA system, return code x′A8′

(168)might be returned indicating that the data set is in use. This is caused by the lock with duplicate volume serial numbers. The situation can be corrected by canceling and restarting the job after taking the target offline; there is no data integrity exposure.

C.1 Backing up VSAM Volumes

There are several instances where SnapShot can be used to back up VSAM volumes for use within the same LPAR or different LPARs. In a first example, we wanted to copy a VSAM volume that contained both the user catalog (UCAT) and all of the UCAT′s files on a single volume. In this case, we would make a snap copy of the volume with the target volume having a volume serial number different from that of the source. Before we actually issue the IXFP SNAP command, any files that are open have to be closed so that the data is written to the disk. Then a utility like VSE/FASTCOPY or the VM/ESA DDR could be used to back up the volume to tape. If all that we were trying to establish was a restart copy in case there was an application failure, the tape backup is superfluous. The VSAM volume cannot be used because the VSAM catalog ′ s contents include the volume serial number of the volume on which it was created. If VSAM finds a different volume serial number, it cannot process the catalog.

In a second example, the VSAM files reside on several volumes and have a unique UCAT for these files. Here, we would use the same procedure as above to quiesce activity against the files. The volumes containing the files would then be snap copied and, optionally, backed up to tape.

In a third example, we again have one or more VSAM volumes controlled by a single UCAT. This time, we would like to carry the data from our production

60 RAMAC Virtual Array, Peer-to Peer Remote VSE/ESA

Page 69 Page 71
Image 70
Page 69 Page 71
Contents International Technical Support Organization Page International Technical Support Organization First Edition January Contents Peer-to-Peer Remote Copy Itso Redbook Evaluation Contents Vi Ramac Virtual Array, Peer-to Peer Remote VSE/ESA Preface Team That Wrote This RedbookComments Welcome Your comments are important to usOverview of RVA and the Virtual Disk Architecture What Is an IBM Ramac Virtual Array?IBM Ramac Virtual Array Log Structured FileData Compression and Compaction − Functional track tableWhat Is SnapShot? What Is IXFP/SnapShot for VSE/ESA?VSE/ESA Support for the RVA What Is IXFP? Deleted Data Space ReleaseWhat Is Peer-to-Peer Remote Copy? Reporting FunctionsRamac Virtual Array, Peer-to Peer Remote VSE/ESA RVA Simplifies Your Storage Management RVA Benefits for VSE/ESADisk Capacity Ixfp AdministrationBatch Window Improvement Ramac Virtual Array IXFP/SnapShot for VSE/ESARVA Data Availability Application DevelopmentHardware SnapShot PprcRamac Virtual Array, Peer-to Peer Remote VSE/ESA VSE/ESA Support for the RVA Prerequisites1 VSE/ESA Input/Output Configuration Program VolumesHost Connection Assgn Volume Minimal InitPartial Disk Minimal Init ExecRamac Virtual Array, Peer-to Peer Remote VSE/ESA IXFP/SnapShot for VSE/ESA System VSE/ESA User TimeDTRIATTN,PARM=′ Ixfp REPORT′ Sample Batch Job to Invoke Ixfp Report FunctionIXFP/SnapShot for VSE/ESA AR 0015 CUU DEF DetailPhys DefinedFull Volume Ixfp SnapReply ′ YES′ to Proceed VSE/VSAMRange of Cylinders Non-VSAM File Expired Files Ixfp DDSR,PATEV3 Total VolumeIxfp DDSR,PATEV30000-0999,NOPROMPT Specified File Ixfp DDSR,PATEV3DSN=′ test.data.3′ , NopromptIxfp REPORT,80E,80F Ixfp REPORT,80E Ixfp REPORT,80FIxfp Report Sample Output of Ixfp Report Command Device Detail ReportRamac Virtual Array, Peer-to Peer Remote VSE/ESA Device Summary Report Subsystem Summary ReportRamac Virtual Array, Peer-to Peer Remote VSE/ESA Peer-to-Peer Remote Copy Peer-to-Peer Remote CopyPprc and VSE/ESA Software Requirements Pprc Data FlowPprc Hardware Requirements Invoking peer-to-peer remote copyPrimary Devices of a Pprc Pair Examples of Pprcopy CommandsSnapShot Considerations Secondary Devices of a Pprc PairSetting Up Pprc Paths and Pairs Recovering from a Primary Site FailureDeleting Pprc Pairs and Paths Recovering from a Secondary Site FailurePhysical Connections to the RVA Determining the Logical Control Unit Number for RVA Determining the Channel Connection AddressRamac Virtual Array, Peer-to Peer Remote VSE/ESA Appendix A. RVA Functional Device Configuration Functional Device ConfigurationFunctional Device Configuration Screen CD23 Snap Command Appendix B. Ixfp Command ExamplesSyntax Ramac Virtual Array, Peer-to Peer Remote VSE/ESA Using SnapShot to Copy One Volume to Another NopromptDEFINED-CAPACITY AR 0015 CapacityTest Prod Overall Test Prod Using SnapShot to Copy a File from One Volume to Another Using SnapShot to Copy Files with RelocationOther Uses of SnapShot IXFP20I Snap Function Completed ATDdsr Command Syntax of Ixfp Ddsr Command DetailsUsing Ddsr to Delete a Single Data Set Using Ddsr to Delete the Contents of a VolumeReport Using Ddsr to Delete the Free Space on an RVAAR+0015 IXFP29D Ddsr for For Deletion Report Command Reporting on the Capacity of the RVA Subsystem Reporting on the Capacity of a Single VolumeReporting on the Capacity of Multiple Volumes Device Detail Report FUNC. Capacity MBJOB WCWTEST1 IXFP/SnapShot Setup Job StreamsExec DTRIATTN,PARM=′ Ixfp REPORT′ Ixfp DDSR,80E BG 0000 // JOB InitdiskBG 0000 1A86I Following Assignments are Released Ready Ixfp DDSR,80F50.83 47.86 AR 0015 1I40I Ready $$DITTO BLKFACTOR=1 EOJ$$DITTO BLKFACTOR=1 $$DITTO EOJ 726532.208 MB 117880.209 MB 57754.953 MB Appendix C. VSE/VSAM Considerations Backing up Vsam Volumes Appendix C. VSE/VSAM Considerations Ramac Virtual Array, Peer-to Peer Remote VSE/ESA Appendix D. Iocds Example Ramac Virtual Array, Peer-to Peer Remote VSE/ESA Appendix E. Special Notices Following terms are trademarks of other companies Redbooks on CD-ROMs Appendix F. Related PublicationsInternational Technical Support Organization Publications Other PublicationsRamac Virtual Array, Peer-to Peer Remote VSE/ESA How to Get Itso Redbooks ∙ E-mail OrdersIBM Redbook Fax Order Form Please send me the followingIndex See CKDPprc distance Itso Redbook Evaluation Please answer the following questionsSG24-5360-00
Top Page Image Contents