ORPP logo
Image from Google Jackets

DFSMStvs Overview and Planning Guide.

By: Material type: TextTextPublisher: Durham : I B M, 2003Copyright date: ©2003Edition: 1st edDescription: 1 online resource (258 pages)Content type:
  • text
Media type:
  • computer
Carrier type:
  • online resource
ISBN:
  • 9780738499543
Subject(s): Genre/Form: Additional physical formats: Print version:: DFSMStvs Overview and Planning GuideDDC classification:
  • 004.5
LOC classification:
  • QA76.9.V5 -- D47 2003eb
Online resources:
Contents:
Front cover -- Contents -- Figures -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Chapter 1. Introducing DFSMStvs -- 1.1 A brief history of VSAM -- 1.2 Changing business requirements -- 1.2.1 Extending CICS availability -- 1.2.2 Reducing the batch window -- 1.2.3 Web access to VSAM data -- 1.3 Some definitions -- 1.3.1 Backward recovery -- 1.3.2 Forward recovery -- 1.3.3 Atomic updates -- 1.3.4 Unit of work and unit of recovery -- 1.3.5 Two-phase commit -- 1.3.6 In-flight and in-doubt -- 1.3.7 Repeatable read -- 1.3.8 Recoverable data sets -- 1.4 CICS support for recoverable VSAM -- 1.5 VSAM record level sharing introduction -- 1.5.1 RLS new function APARs -- 1.6 DFSMStvs introduction -- 1.6.1 DFSMStvs locking -- 1.6.2 DFSMStvs logging -- 1.6.3 Recovery coordination -- 1.7 Effect on the batch window -- 1.8 Planning for DFSMStvs -- 1.9 Summary -- Chapter 2. What you need for DFSMStvs -- 2.1 Hardware -- 2.2 Software -- 2.2.1 z/OS -- 2.2.2 DFSMS -- 2.2.3 CICS Transaction Server -- 2.2.4 CICS VSAM Recovery -- 2.2.5 Global Resource Serialization -- 2.2.6 z/OS Security Server -- 2.2.7 IMS -- 2.2.8 DB2 -- 2.2.9 Language products -- 2.3 Unsupported VSAM functions -- 2.4 Summary -- Chapter 3. How DFSMStvs works -- 3.1 VSAM RLS and DFSMStvs -- 3.1.1 Sharing VSAM data -- 3.1.2 What is DFSMStvs? -- 3.1.3 What is DFSMStvs mode? -- 3.2 Resource locking -- 3.2.1 Locking concepts -- 3.2.2 Open integrity -- 3.2.3 Share locks and exclusive locks -- 3.2.4 False lock contention -- 3.2.5 Read integrity options -- 3.2.6 Deadlock -- 3.2.7 Retained locks -- 3.2.8 Recovery of lost locks -- 3.3 Resource recovery logging -- 3.3.1 Logging changed data -- 3.3.2 The system logger and DFSMStvs log streams -- 3.3.3 Logging strategy -- 3.3.4 DFSMStvs undo logging and backout.
3.3.5 DFSMStvs forward recovery logging -- 3.4 Two-phase commit and backout -- 3.4.1 Resource recovery participants -- 3.4.2 Two-phase commit protocols -- 3.4.3 Commit flow -- 3.4.4 Backout flow -- 3.4.5 Handling of undo records when in-doubt -- 3.4.6 Handling long-running units of recovery -- 3.4.7 Complex application considerations for commit and backout -- 3.4.8 Backout failure -- 3.5 DFSMStvs environment -- 3.5.1 Coupling facility use -- 3.5.2 SMSVSAM address space -- 3.5.3 Sharing control data sets -- 3.5.4 VSAM data sets -- 3.5.5 The system logger -- 3.5.6 Resource Recovery Services -- 3.5.7 CICS TS -- 3.5.8 Batch applications -- 3.6 Summary -- Chapter 4. Batch jobs as transactions -- 4.1 What is a transaction? -- 4.2 Implications of running as a transaction -- 4.3 How often should you commit? -- 4.3.1 Why doesn't DFSMStvs commit automatically? -- 4.3.2 Browsing -- 4.4 How can you avoid deadlocks? -- 4.5 Replacing batch backup steps -- 4.6 What to do when a job fails -- 4.6.1 Job rerun in case of failure -- 4.6.2 Determining the restart point -- 4.7 Unit of recovery isolation -- 4.8 Multi-tasking -- 4.9 Summary -- Chapter 5. Looking for candidates for DFSMStvs -- 5.1 What are the business needs? -- 5.2 What do you want to achieve? -- 5.2.1 Reducing the batch window -- 5.2.2 Eliminating the batch window -- 5.2.3 New applications -- 5.2.4 Vendor applications -- 5.3 What to look for in a batch job -- 5.3.1 Value of scheduling flexibility -- 5.3.2 Degree of VSAM use -- 5.3.3 Read/write profile -- 5.3.4 Pattern of access to data -- 5.3.5 Capable of parallelization -- 5.3.6 Random or sequential access -- 5.3.7 Elapsed time -- 5.3.8 Program structure -- 5.3.9 Database use -- 5.3.10 Functions not supported by DFSMStvs -- 5.3.11 Checklist -- 5.4 Examining batch jobs -- 5.4.1 CICS file resource definitions -- 5.4.2 Operational documentation.
5.4.3 JCL scans -- 5.4.4 SMF records -- 5.5 Build a migration plan -- 5.6 Summary -- Chapter 6. Batch application design with DFSMStvs -- 6.1 Application classification -- 6.1.1 DFSMStvs intolerant applications -- 6.1.2 DFSMStvs tolerant applications -- 6.1.3 DFSMStvs exploiting applications -- 6.2 Simple and advanced application models -- 6.3 Designing efficient transactional applications -- 6.3.1 Exclusive control of resources -- 6.3.2 Minimizing contention -- 6.3.3 Transactional isolation -- 6.4 Programming interfaces -- 6.4.1 High-level language considerations -- 6.4.2 Enhancements to the application programming interfaces -- 6.4.3 VSAM macros -- 6.4.4 Opening in DFSMStvs mode -- 6.4.5 Using commit and backout -- 6.4.6 Checking VSAM return codes -- 6.5 How you can avoid reapplying updates -- 6.5.1 Repositioning input files -- 6.5.2 Repositioning output files -- 6.5.3 Generalized subroutines -- 6.6 Other application considerations -- 6.6.1 Read integrity options -- 6.6.2 Applications using non-shared resources -- 6.6.3 Deleting data sets -- 6.6.4 Checkpoint/restart -- 6.6.5 Hiperbatch -- 6.7 Accessing records -- 6.7.1 Maximum record size -- 6.7.2 Browsing -- 6.7.3 Skip-sequential processing -- 6.7.4 Updating records -- 6.7.5 Deleting records -- 6.7.6 Adding records -- 6.8 VSAM restrictions -- 6.8.1 Defer processing -- 6.8.2 Load mode -- 6.8.3 Positioning -- 6.8.4 Locking -- 6.8.5 Sharing -- 6.8.6 SHAREOPTIONS -- 6.8.7 DEFINE parameters -- 6.8.8 Alternate indices -- 6.8.9 GETIX and PUTIX interfaces -- 6.8.10 VSAM exits -- 6.8.11 Request environment -- 6.9 Lock handling -- 6.9.1 Record locking for recoverable data sets -- 6.9.2 Types of locks -- 6.9.3 Lock duration -- 6.9.4 Lock granularity and ownership -- 6.9.5 Intra-unit of recovery lock contention -- 6.10 Deadlocks -- 6.10.1 Deadlock detection -- 6.10.2 Deadlock and time-out.
6.10.3 Avoiding deadlocks -- 6.11 Synchronization point processing -- 6.12 Transactional recovery -- 6.12.1 Resource recovery participants -- 6.12.2 Recovery considerations -- 6.12.3 Logging -- 6.12.4 Restrictions on retrying operations -- 6.13 Minimizing errors by design and testing -- 6.14 Summary -- Chapter 7. Planning for DFSMStvs -- 7.1 Coupling facility planning -- 7.1.1 What is a coupling facility? -- 7.1.2 What kind of coupling facility should you use? -- 7.1.3 What is in the coupling facility? -- 7.1.4 Coupling facility storage sizing -- 7.1.5 Coupling facility links -- 7.1.6 CPU planning for the coupling facility -- 7.2 Processor capacity planning -- 7.3 Software configuration planning -- 7.4 System logger planning -- 7.4.1 What is the system logger? -- 7.4.2 Log streams -- 7.4.3 Structures and log streams -- 7.4.4 DASD-only log streams -- 7.4.5 Log stream sizing -- 7.4.6 DASD staging data sets -- 7.4.7 DASD log data sets -- 7.5 VSAM operations planning -- 7.5.1 Recovery procedures -- 7.5.2 Forward recovery operation planning -- 7.5.3 Reorganization -- 7.5.4 Automatic Restart Manager planning -- 7.5.5 What is ARM? -- 7.5.6 ARM benefits -- 7.5.7 ARM exploiters -- 7.5.8 DFSMStvs and ARM -- 7.5.9 Peer recovery -- 7.6 Summary -- Chapter 8. Implementing DFSMStvs -- 8.1 Implementation overview -- 8.2 Setting up a Parallel Sysplex environment -- 8.3 Define coupling facility structures -- 8.4 Define the DFSMS environment -- 8.4.1 Define SMSplex environment -- 8.4.2 Define cache structures in the SMS base configuration -- 8.4.3 Define storage classes for VSAM files -- 8.4.4 Change ACS routines for VSAM data sets -- 8.4.5 Define SMS environment for the system logger -- 8.4.6 Modify SYS1.PARMLIB member IGDSMSxx -- 8.4.7 Modify SYS1.PARMLIB member IFAPRDxx -- 8.5 Define the Sharing Control Data Set (SHCDS) -- 8.6 Define the system logger environment.
8.6.1 Define the SMS environment for the system logger -- 8.6.2 Modify SYS1.PARMLIB member IEFSSNxx -- 8.6.3 Define list structures -- 8.6.4 DFSMStvs Define LOGR CDS -- 8.6.5 Modify SYS1.PARMLIB member COUPLExx -- 8.6.6 Define LOGR policy -- 8.7 Define the RRS environment -- 8.7.1 Define RRS log streams -- 8.7.2 Define the RRS start procedure -- 8.7.3 Modify SYS1.PARMLIB member IEFSSNxx -- 8.8 Migrate VSAM files -- 8.9 Plan for fallback -- 8.10 What are the RACF implications? -- 8.10.1 SMSVSAM access to log streams -- 8.10.2 User access to log streams -- 8.10.3 Authority to use IDCAMS SHCDS -- 8.11 Operational procedures -- 8.11.1 DFSMStvs failure -- 8.11.2 DFSMStvs restart -- 8.11.3 Renaming DFSMStvs -- 8.11.4 Data integrity considerations -- 8.12 Summary -- Chapter 9. DFSMStvs performance -- 9.1 Performance effects -- 9.2 Comparison to RLS -- 9.3 Comparison to non-RLS -- 9.4 Sequential performance -- 9.5 Logging performance -- 9.6 Monitoring performance -- 9.7 Tuning DFSMStvs -- 9.8 System-wide recommendations -- 9.9 Summary -- Appendix A. Quiesce protocols -- A.1 Quiesce types -- QUICLOSE -- QUIOPEN -- QUICOPY -- QUICEND -- QUIBWO -- QUIBEND -- QUIFRC -- QUICMP -- QUICA -- Cancelling a quiesce -- Unquiesce processing -- Authority -- Appendix B. Changed commands for DFSMStvs -- B.1 Display SMS -- B.2 VARY SMS -- B.3 SETSMS -- B.4 IDCAMS SHCDS -- Appendix C. RMF Monitor III enhancements -- C.1 Activity by storage class -- C.2 Data set activity -- C.3 LRU statistics -- C.4 Display SMS -- C.5 VARY SMS -- C.6 SETSMS -- C.7 IDCAMS SHCDS -- Glossary -- Abbreviations and acronyms -- Related publications -- IBM Redbooks -- Other publications -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover.
Tags from this library: No tags from this library for this title. Log in to add tags.
Star ratings
    Average rating: 0.0 (0 votes)
No physical items for this record

Front cover -- Contents -- Figures -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Chapter 1. Introducing DFSMStvs -- 1.1 A brief history of VSAM -- 1.2 Changing business requirements -- 1.2.1 Extending CICS availability -- 1.2.2 Reducing the batch window -- 1.2.3 Web access to VSAM data -- 1.3 Some definitions -- 1.3.1 Backward recovery -- 1.3.2 Forward recovery -- 1.3.3 Atomic updates -- 1.3.4 Unit of work and unit of recovery -- 1.3.5 Two-phase commit -- 1.3.6 In-flight and in-doubt -- 1.3.7 Repeatable read -- 1.3.8 Recoverable data sets -- 1.4 CICS support for recoverable VSAM -- 1.5 VSAM record level sharing introduction -- 1.5.1 RLS new function APARs -- 1.6 DFSMStvs introduction -- 1.6.1 DFSMStvs locking -- 1.6.2 DFSMStvs logging -- 1.6.3 Recovery coordination -- 1.7 Effect on the batch window -- 1.8 Planning for DFSMStvs -- 1.9 Summary -- Chapter 2. What you need for DFSMStvs -- 2.1 Hardware -- 2.2 Software -- 2.2.1 z/OS -- 2.2.2 DFSMS -- 2.2.3 CICS Transaction Server -- 2.2.4 CICS VSAM Recovery -- 2.2.5 Global Resource Serialization -- 2.2.6 z/OS Security Server -- 2.2.7 IMS -- 2.2.8 DB2 -- 2.2.9 Language products -- 2.3 Unsupported VSAM functions -- 2.4 Summary -- Chapter 3. How DFSMStvs works -- 3.1 VSAM RLS and DFSMStvs -- 3.1.1 Sharing VSAM data -- 3.1.2 What is DFSMStvs? -- 3.1.3 What is DFSMStvs mode? -- 3.2 Resource locking -- 3.2.1 Locking concepts -- 3.2.2 Open integrity -- 3.2.3 Share locks and exclusive locks -- 3.2.4 False lock contention -- 3.2.5 Read integrity options -- 3.2.6 Deadlock -- 3.2.7 Retained locks -- 3.2.8 Recovery of lost locks -- 3.3 Resource recovery logging -- 3.3.1 Logging changed data -- 3.3.2 The system logger and DFSMStvs log streams -- 3.3.3 Logging strategy -- 3.3.4 DFSMStvs undo logging and backout.

3.3.5 DFSMStvs forward recovery logging -- 3.4 Two-phase commit and backout -- 3.4.1 Resource recovery participants -- 3.4.2 Two-phase commit protocols -- 3.4.3 Commit flow -- 3.4.4 Backout flow -- 3.4.5 Handling of undo records when in-doubt -- 3.4.6 Handling long-running units of recovery -- 3.4.7 Complex application considerations for commit and backout -- 3.4.8 Backout failure -- 3.5 DFSMStvs environment -- 3.5.1 Coupling facility use -- 3.5.2 SMSVSAM address space -- 3.5.3 Sharing control data sets -- 3.5.4 VSAM data sets -- 3.5.5 The system logger -- 3.5.6 Resource Recovery Services -- 3.5.7 CICS TS -- 3.5.8 Batch applications -- 3.6 Summary -- Chapter 4. Batch jobs as transactions -- 4.1 What is a transaction? -- 4.2 Implications of running as a transaction -- 4.3 How often should you commit? -- 4.3.1 Why doesn't DFSMStvs commit automatically? -- 4.3.2 Browsing -- 4.4 How can you avoid deadlocks? -- 4.5 Replacing batch backup steps -- 4.6 What to do when a job fails -- 4.6.1 Job rerun in case of failure -- 4.6.2 Determining the restart point -- 4.7 Unit of recovery isolation -- 4.8 Multi-tasking -- 4.9 Summary -- Chapter 5. Looking for candidates for DFSMStvs -- 5.1 What are the business needs? -- 5.2 What do you want to achieve? -- 5.2.1 Reducing the batch window -- 5.2.2 Eliminating the batch window -- 5.2.3 New applications -- 5.2.4 Vendor applications -- 5.3 What to look for in a batch job -- 5.3.1 Value of scheduling flexibility -- 5.3.2 Degree of VSAM use -- 5.3.3 Read/write profile -- 5.3.4 Pattern of access to data -- 5.3.5 Capable of parallelization -- 5.3.6 Random or sequential access -- 5.3.7 Elapsed time -- 5.3.8 Program structure -- 5.3.9 Database use -- 5.3.10 Functions not supported by DFSMStvs -- 5.3.11 Checklist -- 5.4 Examining batch jobs -- 5.4.1 CICS file resource definitions -- 5.4.2 Operational documentation.

5.4.3 JCL scans -- 5.4.4 SMF records -- 5.5 Build a migration plan -- 5.6 Summary -- Chapter 6. Batch application design with DFSMStvs -- 6.1 Application classification -- 6.1.1 DFSMStvs intolerant applications -- 6.1.2 DFSMStvs tolerant applications -- 6.1.3 DFSMStvs exploiting applications -- 6.2 Simple and advanced application models -- 6.3 Designing efficient transactional applications -- 6.3.1 Exclusive control of resources -- 6.3.2 Minimizing contention -- 6.3.3 Transactional isolation -- 6.4 Programming interfaces -- 6.4.1 High-level language considerations -- 6.4.2 Enhancements to the application programming interfaces -- 6.4.3 VSAM macros -- 6.4.4 Opening in DFSMStvs mode -- 6.4.5 Using commit and backout -- 6.4.6 Checking VSAM return codes -- 6.5 How you can avoid reapplying updates -- 6.5.1 Repositioning input files -- 6.5.2 Repositioning output files -- 6.5.3 Generalized subroutines -- 6.6 Other application considerations -- 6.6.1 Read integrity options -- 6.6.2 Applications using non-shared resources -- 6.6.3 Deleting data sets -- 6.6.4 Checkpoint/restart -- 6.6.5 Hiperbatch -- 6.7 Accessing records -- 6.7.1 Maximum record size -- 6.7.2 Browsing -- 6.7.3 Skip-sequential processing -- 6.7.4 Updating records -- 6.7.5 Deleting records -- 6.7.6 Adding records -- 6.8 VSAM restrictions -- 6.8.1 Defer processing -- 6.8.2 Load mode -- 6.8.3 Positioning -- 6.8.4 Locking -- 6.8.5 Sharing -- 6.8.6 SHAREOPTIONS -- 6.8.7 DEFINE parameters -- 6.8.8 Alternate indices -- 6.8.9 GETIX and PUTIX interfaces -- 6.8.10 VSAM exits -- 6.8.11 Request environment -- 6.9 Lock handling -- 6.9.1 Record locking for recoverable data sets -- 6.9.2 Types of locks -- 6.9.3 Lock duration -- 6.9.4 Lock granularity and ownership -- 6.9.5 Intra-unit of recovery lock contention -- 6.10 Deadlocks -- 6.10.1 Deadlock detection -- 6.10.2 Deadlock and time-out.

6.10.3 Avoiding deadlocks -- 6.11 Synchronization point processing -- 6.12 Transactional recovery -- 6.12.1 Resource recovery participants -- 6.12.2 Recovery considerations -- 6.12.3 Logging -- 6.12.4 Restrictions on retrying operations -- 6.13 Minimizing errors by design and testing -- 6.14 Summary -- Chapter 7. Planning for DFSMStvs -- 7.1 Coupling facility planning -- 7.1.1 What is a coupling facility? -- 7.1.2 What kind of coupling facility should you use? -- 7.1.3 What is in the coupling facility? -- 7.1.4 Coupling facility storage sizing -- 7.1.5 Coupling facility links -- 7.1.6 CPU planning for the coupling facility -- 7.2 Processor capacity planning -- 7.3 Software configuration planning -- 7.4 System logger planning -- 7.4.1 What is the system logger? -- 7.4.2 Log streams -- 7.4.3 Structures and log streams -- 7.4.4 DASD-only log streams -- 7.4.5 Log stream sizing -- 7.4.6 DASD staging data sets -- 7.4.7 DASD log data sets -- 7.5 VSAM operations planning -- 7.5.1 Recovery procedures -- 7.5.2 Forward recovery operation planning -- 7.5.3 Reorganization -- 7.5.4 Automatic Restart Manager planning -- 7.5.5 What is ARM? -- 7.5.6 ARM benefits -- 7.5.7 ARM exploiters -- 7.5.8 DFSMStvs and ARM -- 7.5.9 Peer recovery -- 7.6 Summary -- Chapter 8. Implementing DFSMStvs -- 8.1 Implementation overview -- 8.2 Setting up a Parallel Sysplex environment -- 8.3 Define coupling facility structures -- 8.4 Define the DFSMS environment -- 8.4.1 Define SMSplex environment -- 8.4.2 Define cache structures in the SMS base configuration -- 8.4.3 Define storage classes for VSAM files -- 8.4.4 Change ACS routines for VSAM data sets -- 8.4.5 Define SMS environment for the system logger -- 8.4.6 Modify SYS1.PARMLIB member IGDSMSxx -- 8.4.7 Modify SYS1.PARMLIB member IFAPRDxx -- 8.5 Define the Sharing Control Data Set (SHCDS) -- 8.6 Define the system logger environment.

8.6.1 Define the SMS environment for the system logger -- 8.6.2 Modify SYS1.PARMLIB member IEFSSNxx -- 8.6.3 Define list structures -- 8.6.4 DFSMStvs Define LOGR CDS -- 8.6.5 Modify SYS1.PARMLIB member COUPLExx -- 8.6.6 Define LOGR policy -- 8.7 Define the RRS environment -- 8.7.1 Define RRS log streams -- 8.7.2 Define the RRS start procedure -- 8.7.3 Modify SYS1.PARMLIB member IEFSSNxx -- 8.8 Migrate VSAM files -- 8.9 Plan for fallback -- 8.10 What are the RACF implications? -- 8.10.1 SMSVSAM access to log streams -- 8.10.2 User access to log streams -- 8.10.3 Authority to use IDCAMS SHCDS -- 8.11 Operational procedures -- 8.11.1 DFSMStvs failure -- 8.11.2 DFSMStvs restart -- 8.11.3 Renaming DFSMStvs -- 8.11.4 Data integrity considerations -- 8.12 Summary -- Chapter 9. DFSMStvs performance -- 9.1 Performance effects -- 9.2 Comparison to RLS -- 9.3 Comparison to non-RLS -- 9.4 Sequential performance -- 9.5 Logging performance -- 9.6 Monitoring performance -- 9.7 Tuning DFSMStvs -- 9.8 System-wide recommendations -- 9.9 Summary -- Appendix A. Quiesce protocols -- A.1 Quiesce types -- QUICLOSE -- QUIOPEN -- QUICOPY -- QUICEND -- QUIBWO -- QUIBEND -- QUIFRC -- QUICMP -- QUICA -- Cancelling a quiesce -- Unquiesce processing -- Authority -- Appendix B. Changed commands for DFSMStvs -- B.1 Display SMS -- B.2 VARY SMS -- B.3 SETSMS -- B.4 IDCAMS SHCDS -- Appendix C. RMF Monitor III enhancements -- C.1 Activity by storage class -- C.2 Data set activity -- C.3 LRU statistics -- C.4 Display SMS -- C.5 VARY SMS -- C.6 SETSMS -- C.7 IDCAMS SHCDS -- Glossary -- Abbreviations and acronyms -- Related publications -- IBM Redbooks -- Other publications -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover.

Description based on publisher supplied metadata and other sources.

Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2024. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries.

There are no comments on this title.

to post a comment.

© 2024 Resource Centre. All rights reserved.