06919nam 2200661Ia 450 991081571180332120200520144314.0(CKB)1000000000243393(SSID)ssj0000278658(PQKBManifestationID)11228497(PQKBTitleCode)TC0000278658(PQKBWorkID)10259623(PQKB)11625599(Au-PeEL)EBL3306870(CaPaEBR)ebr10113031(OCoLC)137342305(CaSebORM)0738499552(MiAaPQ)EBC3306870(OCoLC)830000262(OCoLC)ocn830000262 (EXLCZ)99100000000024339320040116d2003 uy 0engurcn|||||||||txtccrDFSMStvs application migration guide June 2003 /[Nigel Morton ... et al.]1st ed.[S.l.] IBM, International Technical Support Organization2003xvi, 176 p. illIBM redbooks"June 2003.""SG24-6972-00."0-7384-9955-2 Includes bibliographical references and index.Front cover -- Contents -- Figures -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Chapter 1. Introduction to DFSMStvs -- 1.1 VSAM sharing without DFSMStvs -- 1.1.1 Basic VSAM sharing -- 1.1.2 MVS scheduler and sharing through MVS system services -- 1.1.3 Record-level sharing -- 1.2 DFSMStvs overview -- 1.2.1 Recoverable data sets and logging -- 1.2.2 Two-phase commit -- 1.3 Batch application considerations -- 1.3.1 Commit frequency -- 1.3.2 Sharing files beyond today's batch job structure -- 1.3.3 Unit of recovery -- 1.3.4 Application restart -- 1.4 Batch performance observations -- 1.4.1 Exploiting DFSMStvs with parallel batch programs -- 1.4.2 Our experiences with parallelizing batch jobs -- 1.5 Value of DFSMStvs -- 1.6 Summary -- Chapter 2. Using commit and backout -- 2.1 Unit of recovery -- 2.2 Programming changes -- 2.2.1 How to commit -- 2.2.2 How to perform a backout -- 2.2.3 How often to commit -- 2.3 Rerunning jobs -- 2.4 Summary -- Chapter 3. Transactional recovery -- 3.1 Batch application restart -- 3.1.1 Conventional batch job structure -- 3.1.2 Using DFSMStvs: unique input -- 3.1.3 Using DFSMStvs: shared input -- 3.2 Use of forward recovery log -- 3.3 CICSVR overview -- 3.4 Summary -- Chapter 4. Defining VSAM data sets for DFSMStvs -- 4.1 Recoverable data sets -- 4.2 IDCAMS definitions -- 4.2.1 IDCAMS DEFINE CLUSTER parameters -- 4.2.2 Definition for PL/I example -- 4.3 Storage management considerations -- 4.3.1 Data class use -- 4.3.2 Storage class use -- 4.3.3 Management class use -- 4.3.4 Backup while open -- 4.3.5 Reorganization -- 4.4 Summary -- Chapter 5. DFSMStvs environment -- 5.1 SMS setup -- 5.1.1 Data class considerations -- 5.1.2 Storage class considerations -- 5.2 PARMLIB members -- 5.2.1 IFAPRDxx -- 5.2.2 IGDSMSxx.5.3 Coupling facility definitions -- 5.3.1 Log stream names -- 5.3.2 Log streams and log structures -- 5.4 Summary -- Chapter 6. Migrating a COBOL program -- 6.1 The sample program -- 6.2 Changes to the program -- 6.3 Step 1: OPEN -- 6.4 Step 2: Check for deadlocks and time-outs -- 6.5 Step 3: Add commit and backout logic -- 6.6 Step 4: Add restart logic and a positioning data set -- 6.7 Step 5: Remove writes to spool -- 6.8 Summary -- Chapter 7. Migrating a PL/I program -- 7.1 The sample program -- 7.2 Changes to the program -- 7.3 Step 1: OPEN -- 7.4 Step 2: Check for deadlocks and time-outs -- 7.5 Step 3: Add commit and backout logic -- 7.6 Step 4: Add restart logic and a positioning data set -- 7.7 Summary -- Chapter 8. DFSMStvs experiences -- 8.1 Console log during normal start -- 8.2 Exceptions -- 8.2.1 Committing without DFSMStvs -- 8.2.2 DFSMStvs server not registered to RRS -- 8.2.3 Reestablish connection between SMSVSAM and RRS -- 8.3 Monitoring DFSMStvs -- 8.3.1 SMSVSAM server connected or not connected to RRS -- 8.3.2 Display jobs using DFSMStvs -- 8.3.3 Display a specific cluster and its users -- 8.3.4 Coupling facility structure utilization -- 8.3.5 VSAM RLS central locking structure full -- 8.3.6 Display forward recovery log data sets -- 8.3.7 RRS failure terminating DFSMStvs -- 8.3.8 Coupling Facility lock structure -- 8.4 IDCAMS SHCDS examples -- 8.4.1 Data set list -- 8.4.2 Subsystem summary -- 8.4.3 Data sets by subsystem -- Appendix A. CICS VSAM recovery (CICSVR) example -- Appendix B. Example source code -- Original COBOL program -- Modified COBOL program -- Original PL/I program -- Modified PL/I program -- Glossary -- Related publications -- IBM Redbooks -- Other publications -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover.This IBM Redbooks publication will help you to migrate batch VSAM applications to exploit transactional VSAM. DFSMStvs is available in a z/OS environment and offers the ability for VSAM data to be shared for both read and write operations while maintaining integrity and recoverability. DFSNStvs allows logging of changes to recoverable VSAM data sets. Batch programs can use commit and backout functions. This book assumes that you are familiar with the material in the companion book DFSMStvs Overview and Planning, SG24-6971, and refers extensively to material published in that book. We also assume some familiarity with CICS Transaction Server and z/OS. The book is intended for application developers who want to understand how to change applications to make best use of the facilities offered by DFSMStvs and to coexist well with other batch applications and with CICS systems sharing the same VSAM data sets. We assume that you are familiar with the development of batch applications and with the facilities and use of VSAM. The tasks involved in setting up DFSMStvs and the hardware and software prerequisites are not discussed in this book; they are described in DFSMStvs Overview and Planning, SG24-6971.IBM redbooks.Virtual storage (Computer science)CICS (Computer system)Electronic data processingBatch processingApplication softwareDevelopmentVirtual storage (Computer science)CICS (Computer system)Electronic data processingBatch processing.Application softwareDevelopment.005.4/3Morton Nigel1641772International Business Machines Corporation.International Technical Support Organization.MiAaPQMiAaPQMiAaPQBOOK9910815711803321DFSMStvs application migration guide4053062UNINA