Cover image for Systems Programmer's Guide to Resource Recovery Services (RRS).
Systems Programmer's Guide to Resource Recovery Services (RRS).
Title:
Systems Programmer's Guide to Resource Recovery Services (RRS).
Author:
Redbooks, IBM.
Personal Author:
Physical Description:
1 online resource (184 pages)
Contents:
Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Resource Recovery Services (RRS) introduction and concepts -- Chapter 1. Introduction to Resource Recovery Services (RRS) -- 1.1 Transactions -- 1.2 Resource managers and protected resources -- 1.3 The role of Resource Recovery Services (RRS) -- 1.3.1 Who uses RRS -- Chapter 2. Two-phase commit and RRS -- 2.1 Introduction to two-phase commit -- 2.2 Two-phase commit as supported by legacy resource managers -- 2.2.1 CICS -- 2.2.2 IMS -- 2.2.3 DB2 -- 2.3 How RRS works -- 2.3.1 Registration services -- 2.3.2 Context services -- 2.3.3 RRS invocation -- 2.4 How two-phase commit works with RRS -- 2.5 Summary -- Chapter 3. Distributed RRS -- 3.1 Distributed two-phase commit -- 3.1.1 RRS distributed syncpoint support -- 3.1.2 Multisystem cascaded transactions -- Part 2 Implementing and managing RRS -- Chapter 4. Implementing RRS -- 4.1 RRS Implementation overview and planning -- 4.2 Define the logging environment -- 4.2.1 RRS logging group name -- 4.2.2 Log stream characteristics -- 4.2.3 RRS log stream structure sizing -- 4.2.4 Define the RRS log streams -- 4.3 Define the RRS infrastructure -- 4.3.1 WLM definitions -- 4.3.2 RRS subsystem definitions -- 4.3.3 Define RRS procedure -- 4.3.4 RRS automation -- 4.3.5 Define RRS panels to ISPF -- 4.3.6 Define RRS SAF authorization -- 4.3.7 Define RRS component trace -- Chapter 5. RRS operations -- 5.1 Starting RRS -- 5.1.1 RRS warm start -- 5.1.2 RRS cold start -- 5.2 Stopping RRS -- 5.3 Using RRS panels -- Chapter 6. RRS performance and availability -- 6.1 Availability considerations for RRS log streams -- 6.2 Performance considerations of RRS log streams -- 6.2.1 RRS performance monitoring -- Chapter 7. RRS restart and recovery -- 7.1 RRS restart.

7.1.1 RRS log takeover -- 7.2 Resource manager restart -- 7.2.1 Resource manager startup sequence -- 7.2.2 Resource Manager restart restrictions -- 7.2.3 Example of resource manager restart within the same RRS logging group -- 7.2.4 Example of resource manager restart outside the same RRS logging group -- 7.2.5 Sample DB2/MQ restart scenario with RRS -- Part 3 RRS exploiters -- Chapter 8. WebSphere Application Server for z/OS -- 8.1 Introduction -- 8.2 J2EE terminology -- 8.3 RRS exploitation -- 8.4 Connectors for JDBC, JMS and JCA -- 8.4.1 IMS connectors -- 8.4.2 CICS connectors -- 8.4.3 DB2 connector -- 8.4.4 WebSphere MQ connector -- 8.4.5 Connector summary table -- 8.4.6 RRS versus XA resource adapters -- 8.5 Restart and recovery issues with RRS -- 8.5.1 RRS failure -- 8.5.2 Failure and restart -- 8.5.3 Peer restart and recovery -- 8.6 Example scenarios -- 8.6.1 Application updating CICS and IMS using RRS connectors -- 8.6.2 Application updating CICS and IMS with RRS and XA connectors -- 8.6.3 Application backout updating CICS and IMS with RRS and XA connectors -- Chapter 9. DB2 for z/OS -- 9.1 DB2 RRS requirements -- 9.1.1 DB2 RRS Attach facility -- 9.1.2 DB2 Stored Procedures -- 9.1.3 DB2 JDBC/SQLJ driver for OS/390 -- 9.1.4 DB2 Universal JDBC/SQLJ driver -- 9.2 DB2 restart and recovery with RRS -- 9.2.1 DB2 restart if RRS is unavailable -- 9.2.2 DB2 restart on another system -- 9.3 Sample scenarios for DB2 using RRS -- 9.3.1 Normal commit processing scenario -- Chapter 10. CICS Transaction Server -- 10.1 CICS RRS requirements -- 10.1.1 Working in CICS -- 10.1.2 Connecting to CICS via EXCI -- 10.2 CICS restart and recovery with RRS -- 10.2.1 RRS failure -- 10.2.2 CICS restart -- 10.2.3 Operator commands -- 10.2.4 CICS example -- Chapter 11. IMS -- 11.1 How IMS/ESA exploits RRS -- 11.2 Connecting to IMS/ESA -- 11.2.1 ODBA -- 11.2.2 APPC/IMS.

11.2.3 OTMA -- 11.3 IMS/ESA restart and recovery with RRS -- 11.3.1 RRS failure while IMS is active -- 11.3.2 IMS restart when RRS is not available -- 11.3.3 IMS restart when RRS has been cold-started -- 11.3.4 IMS restart on a different system -- 11.4 IMS/ESA sample scenario using RRS -- Chapter 12. WebSphere MQ for z/OS -- 12.1 WebSphere MQ RRS requirements -- 12.1.1 WebSphere MQ and DB2 stored procedures -- 12.1.2 WebSphere MQ JMS interface -- 12.2 WebSphere MQ restart and recovery issue with RRS -- 12.2.1 RRS failure when MQ is running -- 12.2.2 WebSphere MQ restart if RRS is unavailable -- 12.2.3 WebSphere MQ restart on another system -- 12.3 Sample scenarios for WebSphere MQ using RRS -- 12.3.1 Normal commit processing scenario -- Chapter 13. APPC/MVS -- 13.1 APPC/MVS RRS requirements -- 13.1.1 Transaction flow using APPC/MVS protected conversations -- 13.1.2 APPC/MVS system requirements for protected conversations -- 13.1.3 Managing APPC/MVS resources for protected conversations -- 13.2 APPC/MVS application restart and recovery with RRS -- 13.2.1 RRS failure while the APPC/MVS application is active -- 13.3 APPC/MVS sample scenario with RRS -- Chapter 14. DFSMStvs -- 14.1 DFSMtvs features that exploit RRS -- 14.1.1 Resource recovery participants -- 14.1.2 Commit flow with DFSMStvs -- 14.1.3 Backout flow with DFSMStvs -- 14.1.4 Handling of undo records when in-doubt with DFSMStvs -- 14.1.5 Handling long-running units of recovery with DFSMStvs -- 14.2 TVS restart and recovery with RRS -- 14.2.1 RRS failure -- 14.2.2 DFSMStvs restart -- 14.2.3 DFSMStvs peer restart -- 14.2.4 Operator commands -- 14.3 DFSMStvs examples -- Related publications -- IBM Redbooks -- Other publications -- How to get IBM Redbooks -- Index -- Back cover.
Local Note:
Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2017. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries.
Electronic Access:
Click to View
Holds: Copies: