Systems Programmer's Guide To

Systems Programmer's Guide To

Front cover Systems Programmer’s Guide to Resource Recovery Services (RRS) Managing, optimizing, and sizing RRS environments Restart and recovery with RRS How exploiters can get the most out of RRS Paola Bari Frank Kyne Alan Murphy ibm.com/redbooks International Technical Support Organization Systems Programmer’s Guide to Resource Recovery Services (RRS) November 2004 SG24-6980-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (November 2004) This edition applies to Version 1, Release 4 of z/OS (product number 5694-A01, 5655-G52). © Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team that wrote this redbook. ix Become a published author . .x Comments welcome. .x Part 1. Resource Recovery Services (RRS) introduction and concepts . 1 Chapter 1. Introduction to Resource Recovery Services (RRS) . 3 1.1 Transactions . 4 1.2 Resource managers and protected resources . 5 1.3 The role of Resource Recovery Services (RRS). 6 1.3.1 Who uses RRS . 7 Chapter 2. Two-phase commit and RRS . 9 2.1 Introduction to two-phase commit . 10 2.2 Two-phase commit as supported by legacy resource managers . 13 2.2.1 CICS . 14 2.2.2 IMS . 15 2.2.3 DB2 . 15 2.3 How RRS works . 16 2.3.1 Registration services. 16 2.3.2 Context services . 17 2.3.3 RRS invocation . 18 2.4 How two-phase commit works with RRS. 19 2.5 Summary. 21 Chapter 3. Distributed RRS . 23 3.1 Distributed two-phase commit. 24 3.1.1 RRS distributed syncpoint support . 25 3.1.2 Multisystem cascaded transactions . 26 Part 2. Implementing and managing RRS. 29 Chapter 4. Implementing RRS . 31 4.1 RRS Implementation overview and planning . 32 4.2 Define the logging environment . 32 4.2.1 RRS logging group name . 33 4.2.2 Log stream characteristics . 34 4.2.3 RRS log stream structure sizing . 34 4.2.4 Define the RRS log streams . 35 4.3 Define the RRS infrastructure . 42 4.3.1 WLM definitions . 42 4.3.2 RRS subsystem definitions . 42 4.3.3 Define RRS procedure . 43 4.3.4 RRS automation . 43 4.3.5 Define RRS panels to ISPF . 43 4.3.6 Define RRS SAF authorization . 44 © Copyright IBM Corp. 2004. All rights reserved. iii 4.3.7 Define RRS component trace . 44 Chapter 5. RRS operations. 45 5.1 Starting RRS . 46 5.1.1 RRS warm start. 47 5.1.2 RRS cold start. 47 5.2 Stopping RRS . 48 5.3 Using RRS panels. 48 Chapter 6. RRS performance and availability. 57 6.1 Availability considerations for RRS log streams . 58 6.2 Performance considerations of RRS log streams . 59 6.2.1 RRS performance monitoring . 60 Chapter 7. RRS restart and recovery . 61 7.1 RRS restart . 62 7.1.1 RRS log takeover . 62 7.2 Resource manager restart . 63 7.2.1 Resource manager startup sequence. 63 7.2.2 Resource Manager restart restrictions . 63 7.2.3 Example of resource manager restart within the same RRS logging group . 66 7.2.4 Example of resource manager restart outside the same RRS logging group. 66 7.2.5 Sample DB2/MQ restart scenario with RRS . 66 Part 3. RRS exploiters . 71 Chapter 8. WebSphere Application Server for z/OS . 73 8.1 Introduction . 74 8.2 J2EE terminology . 74 8.3 RRS exploitation . 75 8.4 Connectors for JDBC, JMS and JCA . 76 8.4.1 IMS connectors . 76 8.4.2 CICS connectors. ..

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    184 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us