Installation Guide




Replication Agent for DB2 UDB for OS/390
                                   12.5
                  ...
DOCUMENT ID: 34256-01-1250-01

LAST REVISED: December 2002

Copyright © 1989-2002 by Sybase, Inc. All rights reserved.
Thi...
Contents




About This Book ................................................................................................
Contents


                  Understanding DB2 database considerations................................                    ...
Contents


                                Task 1: Edit the PARMLIB library members...................................    ...
Contents


                          DateTime_conv_err...............................................................     ...
SETUP00 member contents and parameters........................ 140
                                                   PLAN...
viii   Replication Agent for DB2 UDB for OS/390
About This Book



                              Sybase provides Replication Agent™ for DB2 UDB for OS/390
               ...
About This Book


                    •   Replication Agent for DB2 UDB for OS/390 product software, product
             ...
About This Book


                            •   The Technical Library Product Manuals Web site is an HTML version of
   ...
About This Book


Style conventions           Table 1 shows some of the style conventions used in the documentation for th...
About This Book


                           Table 2: Syntax conventions
                           Symbol    Explanation ...
About This Book


                         Table 3: Information to gather for Sybase Technical Support

              Syst...
About This Book



                 System
                 component             Information                             ...
About This Book




xvi               Replication Agent for DB2 UDB for OS/390
CH A PTE R          1         Understanding Replication Agent



                              This chapter provides an ov...
Understanding basic concepts of replication systems


                            Figure 1-1: Replication system overview
...
CHAPTER 1        Understanding Replication Agent


                          DB2 logs changes to rows in DB2 tables as the...
Understanding basic concepts of replication systems


                        Tables that receive updates to variable-leng...
CHAPTER 1       Understanding Replication Agent


                          Replication Extract and LTM for MVS run simult...
Understanding basic concepts of replication systems


                             a   LTM for MVS processes the configura...
CHAPTER 1        Understanding Replication Agent


                          9   Replication Extract resumes processing at...
Understanding basic concepts of replication systems


                            Figure 1-3: LTM for MVS components
     ...
CHAPTER 1         Understanding Replication Agent


                          5      Receives transaction operations from ...
Understanding the role of Replication Agent


                         Replication Server holds the transaction operations...
CHAPTER 1      Understanding Replication Agent


                          •      Replication Agent provides a log extract...
Understanding the role of Replication Agent


Step 1: Replication Extract reads log data
                         Replicat...
CHAPTER 1        Understanding Replication Agent


                           Figure 1-6: Replication API translates infor...
Understanding connectivity in a replication system


Step 4: Replication Server replicates information
                   ...
CHAPTER 1        Understanding Replication Agent


                          •   Replication Agent-to-Replication Server c...
Replication Agent users


                             Table 1-1: User IDs associated with Replication Agent
  User ID    ...
CHAPTER 1         Understanding Replication Agent



Understanding replication in a data-sharing
environment
             ...
Understanding replication in a data-sharing environment


                             Figure 1-9: Illustration of data-sh...
CHAPTER 1         Understanding Replication Agent


                          •     The SETUP00 and PDR members in the hlq...
Replication Agent task and documentation topics overview



              Set up communications
              Includes inf...
CHAPTER 1      Understanding Replication Agent



               Troubleshoot Replication Agent
               Includes in...
What’s next




22            Replication Agent for DB2 UDB for OS/390
CH A PTE R          2         Understanding Replication Agent
                              Installation Requirements



 ...
Understanding software requirements



                        Team skill                   Skill set
                    ...
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Installation Guide
Upcoming SlideShare
Loading in...5
×

Installation Guide

770

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
770
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Installation Guide

  1. 1. Installation Guide Replication Agent for DB2 UDB for OS/390 12.5 OS/390
  2. 2. DOCUMENT ID: 34256-01-1250-01 LAST REVISED: December 2002 Copyright © 1989-2002 by Sybase, Inc. All rights reserved. This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. To order additional documents, U.S. and Canadian customers should call Customer Fulfillment at (800) 685-8225, fax (617) 229-9845. Customers in other countries with a U.S. license agreement may contact Customer Fulfillment via the above fax number. All other international customers should contact their Sybase subsidiary or local distributor. Upgrades are provided only at regularly scheduled software release dates. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc. Sybase, the Sybase logo, AccelaTrade, ADA Workbench, Adaptable Windowing Environment, Adaptive Component Architecture, Adaptive Server, Adaptive Server Anywhere, Adaptive Server Enterprise, Adaptive Server Enterprise Monitor, Adaptive Server Enterprise Replication, Adaptive Server Everywhere, Adaptive Server IQ, Adaptive Warehouse, Anywhere Studio, Application Manager, AppModeler, APT Workbench, APT-Build, APT-Edit, APT-Execute, APT-FORMS, APT-Translator, APT-Library, Backup Server, BizTracker, ClearConnect, Client-Library, Client Services, Convoy/DM, Copernicus, Data Pipeline, Data Workbench, DataArchitect, Database Analyzer, DataExpress, DataServer, DataWindow, DB-Library, dbQueue, Developers Workbench, Direct Connect Anywhere, DirectConnect, Distribution Director, e-ADK, E-Anywhere, e-Biz Integrator, E-Whatever, EC-GATEWAY, ECMAP, ECRTP, eFulfillment Accelerator, Embedded SQL, EMS, Enterprise Application Studio, Enterprise Client/Server, Enterprise Connect, Enterprise Data Studio, Enterprise Manager, Enterprise SQL Server Manager, Enterprise Work Architecture, Enterprise Work Designer, Enterprise Work Modeler, eProcurement Accelerator, EWA, Financial Fusion, Financial Fusion Server, Gateway Manager, GlobalFIX, ImpactNow, Industry Warehouse Studio, InfoMaker, Information Anywhere, Information Everywhere, InformationConnect, InternetBuilder, iScript, Jaguar CTS, jConnect for JDBC, MainframeConnect, Maintenance Express, MDI Access Server, MDI Database Gateway, media.splash, MetaWorks, MySupport, Net-Gateway, Net-Library, New Era of Networks, ObjectConnect, ObjectCycle, OmniConnect, OmniSQL Access Module, OmniSQL Toolkit, Open Biz, Open Client, Open ClientConnect, Open Client/Server, Open Client/Server Interfaces, Open Gateway, Open Server, Open ServerConnect, Open Solutions, Optima++, PB-Gen, PC APT Execute, PC Net Library, Power++, power.stop, PowerAMC, PowerBuilder, PowerBuilder Foundation Class Library, PowerDesigner, PowerDimensions, PowerDynamo, PowerJ, PowerScript, PowerSite, PowerSocket, Powersoft, PowerStage, PowerStudio, PowerTips, Powersoft Portfolio, Powersoft Professional, PowerWare Desktop, PowerWare Enterprise, ProcessAnalyst, Rapport, Report Workbench, Report-Execute, Replication Agent, Replication Driver, Replication Server, Replication Server Manager, Replication Toolkit, Resource Manager, RW-DisplayLib, S-Designor, SDF, Secure SQL Server, Secure SQL Toolset, Security Guardian, SKILS, smart.partners, smart.parts, smart.script, SQL Advantage, SQL Anywhere, SQL Anywhere Studio, SQL Code Checker, SQL Debug, SQL Edit, SQL Edit/TPU, SQL Everywhere, SQL Modeler, SQL Remote, SQL Server, SQL Server Manager, SQL SMART, SQL Toolset, SQL Server/ CFT, SQL Server/DBM, SQL Server SNMP SubAgent, SQL Station, SQLJ, STEP, SupportNow, S.W.I.F.T. Message Format Libraries, Sybase Central, Sybase Client/Server Interfaces, Sybase Financial Server, Sybase Gateways, Sybase MPP, Sybase SQL Desktop, Sybase SQL Lifecycle, Sybase SQL Workgroup, Sybase User Workbench, SybaseWare, Syber Financial, SyberAssist, SyBooks, System 10, System 11, System XI (logo), SystemTools, Tabular Data Stream, TradeForce, Transact-SQL, Translation Toolkit, UNIBOM, Unilib, Uninull, Unisep, Unistring, URK Runtime Kit for UniCode, Viewer, Visual Components, VisualSpeller, VisualWriter, VQL, WarehouseArchitect, Warehouse Control Center, Warehouse Studio, Warehouse WORKS, Watcom, Watcom SQL, Watcom SQL Server, Web Deployment Kit, Web.PB, Web.SQL, WebSights, WebViewer, WorkGroup SQL Server, XA-Library, XA-Server and XP Server are trademarks of Sybase, Inc. 07/02 Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. All other company and product names used herein may be trademarks or registered trademarks of their respective companies. Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227- 7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies. Sybase, Inc., One Sybase Drive, Dublin, CA 94568.
  3. 3. Contents About This Book ........................................................................................................................... ix CHAPTER 1 Understanding Replication Agent ................................................. 1 Understanding basic concepts of replication systems...................... 1 Primary database ...................................................................... 2 Primary database log ................................................................ 2 Replication Extract .................................................................... 4 Log Transfer Manager for MVS ................................................. 7 Replication Server ..................................................................... 9 Materialization ......................................................................... 10 Understanding the role of Replication Agent.................................. 10 Replication Agent data flow ..................................................... 11 Understanding connectivity in a replication system........................ 14 Replication Agent-to-Replication Server connectivity.............. 15 Replication Server-to-DB2 connectivity ................................... 15 Replication Agent users ................................................................. 15 Understanding replication in a data-sharing environment .............. 17 Understanding data-sharing environment characteristics ....... 17 Replicating transactions in a data-sharing environment.......... 18 Replication Agent task and documentation topics overview .......... 19 What’s next .................................................................................... 21 CHAPTER 2 Understanding Replication Agent Installation Requirements .. 23 Understanding team skill requirements .......................................... 23 Understanding software requirements ........................................... 24 Mainframe software requirements ........................................... 24 LAN software requirements ..................................................... 25 What’s next .................................................................................... 26 CHAPTER 3 Understanding Replication Agent Operational Considerations 27 Understanding Sybase server operational considerations ............. 27 Heterogeneous datatype support (HDS) ................................. 27 Replication Server-to-DB2 connectivity ................................... 28 Replication Agent for DB2 UDB for OS/390 Installation Guide iii
  4. 4. Contents Understanding DB2 database considerations................................ 28 Support for DB2 features......................................................... 29 DB2 log capacity ..................................................................... 29 DB2 table size limit in Replication Server................................ 29 DB2 utilities ............................................................................. 29 Understanding permissions requirements...................................... 30 What’s next .................................................................................... 30 CHAPTER 4 Gathering Installation Information ............................................... 31 Section 1: Recording user IDs ....................................................... 32 Section 2: Recording the LTM for MVS start-up procedure name . 33 Section 3: Recording Replication Agent installation information .... 34 Section 4: Recording Replication Extract installation information .. 34 Specifying DB2 system libraries for multi-member datasharing 35 Section 5: Recording TCP/IP configuration information ................. 36 Recording TCP/IP information for Replication Server ............. 36 Section 6: Recording TCP/IP information for Adaptive Server....... 37 Section 7: Recording required configuration information ............... 39 Replication Agent Installation Worksheet....................................... 41 1. User IDs .............................................................................. 42 2. LTM for MVS start-up procedure name............................... 43 3. Replication Agent installation .............................................. 44 4. Replication Extract installation panel information................ 45 5. TCP/IP information for Replication Server .......................... 46 6. TCP/IP information for Adaptive Server .............................. 47 7. LTM for MVS configuration information............................... 48 What’s next .................................................................................... 48 CHAPTER 5 Installing Replication Agent ......................................................... 49 Task 1: Gather installation information........................................... 50 Task 2: Start the installation program ............................................ 50 Task 3: Customize the JCL ............................................................ 51 Task 4: Transfer the data sets ....................................................... 52 Task 5: Unpack LINKLIB data sets ................................................ 53 Task 6: Perform systems programmer installation tasks ............... 54 Task 7: Create the Replication Agent system tables ..................... 54 Task 8: Grant LTMADMIN user ID permissions............................. 55 Task 9: Install the Replication Agent interface ............................... 58 Task 10: Define the LTM start-up procedure ................................. 59 What’s next .................................................................................... 60 CHAPTER 6 Configuring Replication Extract................................................... 61 iv Replication Agent for DB2 UDB for OS/390
  5. 5. Contents Task 1: Edit the PARMLIB library members................................... 61 Task 1a: Edit the PLANS00 member ...................................... 62 Task 1b: Edit the SETUP00 member ...................................... 63 Task 1c: Edit the PDR member............................................... 65 Task 2: Bind the log extract plan .................................................... 67 Example .................................................................................. 67 What’s next .................................................................................... 69 CHAPTER 7 Configuring TCP/IP for Replication Agent.................................. 71 Task 1: Verify TCP/IP connectivity................................................. 72 Understanding the SYGWHOST macro......................................... 73 Syntax ..................................................................................... 74 Contents .................................................................................. 74 Task 2: Assemble and link the SYGWXCPH module .................... 75 What’s next .................................................................................... 75 CHAPTER 8 Completing and Verifying Your Replication Agent Installation 77 Task 1: Verify the LTM for MVS configuration file.......................... 77 What you need to know ........................................................... 79 Task 2: Configure Replication Server ............................................ 80 What you need to know ........................................................... 81 Creating the RS user on Replication Server ........................... 82 Granting connect source permission....................................... 82 Creating a connection to Replication Server ........................... 83 Task 3: Test your server connections with PINGRS ...................... 85 Correcting PINGRS errors....................................................... 85 Task 4: Start Replication Agent...................................................... 86 What’s next .................................................................................... 87 AP PE ND IX A LTM for MVS Configuration Parameters..................................... 89 Understanding the LTM for MVS configuration file ........................ 89 Sample LTM for MVS configuration file................................... 89 Understanding the LTM for MVS configuration parameters........... 94 API_com_test .......................................................................... 96 API_QID_request_interval....................................................... 98 batch_ltl_cmds ........................................................................ 99 Char_conv_err_log ................................................................ 100 Codepage.............................................................................. 100 Communications_Protocol .................................................... 103 Creator .................................................................................. 103 Date_conv_default ................................................................ 104 Date_in_char ......................................................................... 105 Replication Agent for DB2 UDB for OS/390 Installation Guide v
  6. 6. Contents DateTime_conv_err............................................................... 106 LE_oper_com ........................................................................ 107 Log_extractor ........................................................................ 107 Log_identifier......................................................................... 108 Long_varchar ........................................................................ 109 Low_activity_latency ............................................................. 110 LTL_table_col_case .............................................................. 110 LTL_test_only........................................................................ 111 LTM_admin_pw..................................................................... 112 LTM_admin_user .................................................................. 112 LTM_process_maint_uid_trans ............................................. 113 Maximum_connect_retries .................................................... 114 Minimal_cols.......................................................................... 114 Minimum_year....................................................................... 115 Packet_size ........................................................................... 116 replace_null_in_char ............................................................. 117 retry ....................................................................................... 118 RS ......................................................................................... 118 RS_ccsid ............................................................................... 119 RS_source_db....................................................................... 121 RS_source_ds....................................................................... 122 RS_pw................................................................................... 123 RS_user ................................................................................ 123 RSSD_database.................................................................... 124 RSSD_pw.............................................................................. 125 RSSD_server ........................................................................ 125 RSSD_user ........................................................................... 126 Stop_on_error ....................................................................... 126 Support_DB2_comp_rec ....................................................... 128 Suppress_col_names............................................................ 129 Time_conv_default ................................................................ 130 Time_in_char......................................................................... 131 Timestamp_in_char............................................................... 132 trace=1,4 ............................................................................... 133 trace=1,11 ............................................................................. 133 trace=1,23 ............................................................................. 134 trace=1,31 ............................................................................. 135 Transaction_name................................................................. 136 Use_repdef............................................................................ 136 User_exit ............................................................................... 138 AP PE ND IX B Replication Extract Configuration Parameters ......................... 139 PARMLIB data set members........................................................ 139 Replication Extract members and parameter conventions.... 140 vi Replication Agent for DB2 UDB for OS/390
  7. 7. SETUP00 member contents and parameters........................ 140 PLANS00 member contents .................................................. 141 PDR member contents and parameters ................................ 142 A PP EN DIX C Replication Agent Data Sets ...................................................... 151 Replication Agent data sets.......................................................... 151 DBRMLIB contents ................................................................ 151 DOCS contents...................................................................... 152 ISPF contents ........................................................................ 152 JCL contents.......................................................................... 153 MACLIB contents................................................................... 154 PDR.PARMLIB contents........................................................ 155 RA.LINKLIB contents............................................................. 155 LTMLOC ................................................................................ 155 SAS.LINKLIB ......................................................................... 155 Additional data sets ............................................................... 156 A PP EN DIX D Upgrading Your Replication Agent Software ........................... 157 Migrating to Replication Agent for DB2 UDB 12.5 software ......... 157 Additional migration considerations.............................................. 160 New LTI version..................................................................... 160 FLOAT data rounding change ............................................... 160 Understanding the LTM Locator format........................................ 161 Replication Agent LTM Locator formats ................................ 161 A PP EN DIX E Running Multiple Replication Agents........................................ 163 Running multiple Log Transfer Managers .................................... 163 JCLLIB (LTMCNFG) .............................................................. 164 PDR.PARMLIB ...................................................................... 165 RA.LINKLIB ........................................................................... 165 creator.LTMOBJECTS........................................................... 166 Glossary...................................................................................................................................... 167 Index............................................................................................................................................ 185 Replication Agent for DB2 UDB for OS/390 Installation Guide vii
  8. 8. viii Replication Agent for DB2 UDB for OS/390
  9. 9. About This Book Sybase provides Replication Agent™ for DB2 UDB for OS/390 (hereafter referred to as Replication Agent) to enable you to replicate transaction operations from IBM DB2 UDB on OS/390 to replicate databases through Sybase Replication Server®. Before you begin Read the Replication Agent for DB2 UDB Release Bulletin for OS/390 version 12.5 for important information about this Sybase software release that becomes available after this guide was printed. Audience Use this document if you are responsible for any of these tasks: • Administering Replication Server systems • Administering your MVS (OS/390) system • Administering your DB2 database • Installing Replication Agent How to use this book Use this document to accomplish the following: • Understand basic replication concepts, including the relationship between replication components in a Sybase replication system • Understand Replication Agent installation requirements • Install the LTM for MVS and Replication Extract components of Replication Agent • Verify your Replication Agent installation Use this document to accomplish the following: • Understand basic replication concepts, including the relationship between replication components in a Sybase replication system. • Understand Replication Agent installation requirements. Contents of this book See “Replication Agent task and documentation topics overview” on page 19 for a list of topics and chapters in this book. The glossary contains definitions of technical terms. Contents of Replication Replication Agent includes the following components: Agent Replication Agent for DB2 UDB for OS/390 Installation Guide ix
  10. 10. About This Book • Replication Agent for DB2 UDB for OS/390 product software, product #19319-33-1250, which includes the following components: • Log Transfer Manager (LTM for MVS) • Replication Extract, the log extract component of Replication Agent • Tracing utilities, to assist with debugging and troubleshooting Replication Agent • Replication Agent for DB2 UDB for OS/390 product documentation, including: • Replication Agent for DB2 UDB Release Bulletin for OS/390, document #71014-01-1250 • Replication Agent for DB2 UDB Installation Guide for OS/390 (this document), document #34256-01-1250 • Replication Agent for DB2 UDB User’s and Troubleshooting Guide for OS/390, document #32005-01-1250 Related documents Obtain documentation for the following Sybase products from your site’s designated Sybase representative: • Replication Server • Adaptive Server Enterprise Obtain the appropriate IBM DB2 documents concerning messages and codes, commands and utilities, SQL, administration and application programming. Obtain documentation for the TCP/IP connectivity protocol as needed. Other sources of Use the Sybase Technical Library CD and the Technical Library Product information Manuals Web site to learn more about your product: • The Technical Library CD contains product manuals and is included with your software. The DynaText browser (downloadable from Product Manuals at http://www.sybase.com/detail/1,6904,1010663,00.html) allows you to access technical information about your product in an easy-to-use format. Refer to the Technical Library Installation Guide in your documentation package for instructions on installing and starting the Technical Library. x Replication Agent for DB2 UDB for OS/390
  11. 11. About This Book • The Technical Library Product Manuals Web site is an HTML version of the Technical Library CD that you can access using a standard Web browser. In addition to product manuals, you will find links to the Technical Documents Web site (formerly known as Tech Info Library), the Solved Cases page, and Sybase/Powersoft newsgroups. To access the Technical Library Product Manuals Web site, go to Product Manuals at http://www.sybase.com/support/manuals/. Sybase certifications Technical documentation at the Sybase Web site is updated frequently. on the Web ❖ For the latest information on product certifications 1 Point your Web browser to Technical Documents at http://www.sybase.com/support/techdocs/. 2 Select Products from the navigation bar on the left. 3 Select a product name from the product list. 4 Select the Certification Report filter, specify a time frame, and click Go. 5 Click a Certification Report title to display the report. ❖ For the latest information on EBFs and Updates 1 Point your Web browser to Technical Documents at http://www.sybase.com/support/techdocs/. 2 Select EBFs/Updates. Enter user name and password information, if prompted (for existing Web accounts) or create a new account (a free service). 3 Specify a time frame and click Go. 4 Select a product. 5 Click an EBF/Update title to display the report. ❖ To create a personalized view of the Sybase Web site (including support pages) Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages. 1 Point your Web browser to Technical Documents at http://www.sybase.com/support/techdocs/. 2 Click MySybase and create a MySybase profile. Replication Agent for DB2 UDB for OS/390 Installation Guide xi
  12. 12. About This Book Style conventions Table 1 shows some of the style conventions used in the documentation for this product. Table 1: Style conventions Text Explanation Example Bold • Programs create connection • Utilities • Procedures • Commands Italics • File names PDR.PARMLIB • Directory names • Properties Code • Code examples Replication Agent for DB2 • Screen text UDB for OS/390/12.5 Bold code • User input /F [job_name],C, trace=1,11 • Command line input Italics Variables (replace these with the host_name appropriate values for your site) Code Variables in code you type (replace maintenance_user_ID italics these with the appropriate values for your site) Syntax conventions The following example illustrates some of the syntax conventions used in this guide: COMMAND [object_name, [ {TRUE | FALSE} ] ] Table 2 explains the syntax conventions used in this guide. xii Replication Agent for DB2 UDB for OS/390
  13. 13. About This Book Table 2: Syntax conventions Symbol Explanation Example ( ) Include parentheses as part of the START DATABASE command. (database_name) | A vertical bar indicates that you {red|yellow|blue} can select only one of the options shown. Do not type the bar in your command. , A comma indicates that you can {rice,potatoes,beans} choose one or more of the options shown. Separate each choice by using a comma as part of the command. {} Braces indicate that you must Select only one: choose at least one of the enclosed {red|yellow|blue} options. Do not type the braces when you enter the option. Select at least one: {rice,potatoes,beans} [] Brackets indicate that you can [anchovies] choose one or more of the enclosed options, or none. Do not type the brackets when you enter the options. ... An ellipsis indicates that you can {rice,potatoes}... repeat the previous item as many times as necessary. If you need help Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you cannot resolve a problem using the manuals or online help, please have the designated person contact Sybase Technical Support or the Sybase subsidiary in your area. Gathering Sybase Technical Support may ask for some of the information in Table 3. Be information for sure to have information about the items marked with an asterisk (*). Sybase Technical Support Replication Agent for DB2 UDB for OS/390 Installation Guide xiii
  14. 14. About This Book Table 3: Information to gather for Sybase Technical Support System component Information Output type MVS MVS version and release MVS maintenance level Version and level of SAS/C run-time library DFP/SFSMS level MVS SYGWHOST macro (in XCPHPING File contents member) MVS dump Output Warning! You must not use Abend-AID for Replication Agent dumps. Since Abend-AID removes dump information necessary to properly troubleshoot Replication Extract problems, make sure your batch job or started task JCL prevents Abend-AID from affecting abend output. Record of all console messages Output DB2 Version DSNJU004 utility listing of BSDS If running in data-sharing mode: • Number of members • DSNJU004 utility listing of BSDS (for each member of data-sharing group, if running in data-sharing mode) • LISTCAT of DB2 system logs • Group attach name Replication Server *Replication Server platform *Replication Server release Target port (Replication Server port number) Replication Server machine interfaces file File contents Replication Server subscriptions and File contents replication definitions *Replication Server log Output xiv Replication Agent for DB2 UDB for OS/390
  15. 15. About This Book System component Information Output type Replication Agent *Replication Agent release number *Replication Agent configuration file File contents *Replication Agent log files Output Adaptive Server Adaptive Server platform Adaptive Server release number TCP/IP connectivity Vendor, version, and release Maintenance level Data set prefix name Address space name *TSO PING command (if run) Output *PINGRS job including JCL listing (if run) Output JES SYSLOG during the period that PINGRS Copy runs (if run) NETSTAT ALL commands Output TESTSITE command (if run) Output TRACERTE (MVS) or traceroute (UNIX) Output command TRACE ALL and MORETRACE SOCKETS Output commands Troubleshooting All troubleshooting procedures Output Replication Agent for DB2 UDB for OS/390 Installation Guide xv
  16. 16. About This Book xvi Replication Agent for DB2 UDB for OS/390
  17. 17. CH A PTE R 1 Understanding Replication Agent This chapter provides an overview of Replication Agent for DB2 UDB for OS/390 version 12.5 (hereafter referred to as Replication Agent), including the following topics: Topic Page Understanding basic concepts of replication systems 1 Understanding the role of Replication Agent 10 Understanding connectivity in a replication system 14 Replication Agent users 15 Understanding replication in a data-sharing environment 17 Replication Agent task and documentation topics overview 19 What’s next 21 If you are completely familiar with replication concepts, your MVS environment, and Replication Server, turn now to “Understanding the role of Replication Agent” on page 10. Note The material in this chapter also appears in the Replication Agent for DB2 UDB User’s and Troubleshooting Guide for OS/390. Understanding basic concepts of replication systems Transaction replication maintains data in separate databases called replicate databases. Replicate databases contain accurate, current copies or subsets of data from the primary database. Replication of data allows slower, process-intensive decision support queries to run against the same data without slowing mission-critical, on- line transaction processing (OLTP) applications. Figure 1-1 on page 2 shows a generic replication system and its components. Replication Agent for DB2 UDB for OS/390 Installation Guide 1
  18. 18. Understanding basic concepts of replication systems Figure 1-1: Replication system overview Database Primary Adaptive Replication Log Database Server Server System Database (RSSD) Replication Agent TCP/IP Connection Log LTM for Replication Replicate Extract MVS Server Database OS/390 LAN The following sections introduce the basic concepts of transaction replication and describe the following elements of a typical replication system: • Primary database • Primary database log • Replication Extract • Log Transfer Manager for MVS • Replication Server Primary database The primary database, DB2, contains your source data. Primary database log The DB2 log contains information about updates, deletes, and inserts on DB2 tables. The DB2 log contains information about additional changes and events; this additional information is not currently replicated. 2 Replication Agent for DB2 UDB for OS/390
  19. 19. CHAPTER 1 Understanding Replication Agent DB2 logs changes to rows in DB2 tables as they occur. The information written to the log includes copies of the data before and after the changes. In DB2, these records are known as “undo” and “redo” records. Control records are written for commits and aborts. These records are translated to commits and rollbacks. The DB2 log is composed of a series of data sets. Replication Extract uses these log data sets to identify DB2 data changes. The DB2 log consists of three types of data sets: • Active log data sets reside on a direct access storage device (DASD). As changes occur, they are first recorded in an active log data set. Eventually, the active log fills and DB2 copies the log to an archive log. • Archive log data sets reside on DASD or tape. • The bootstrap data set (BSDS) contains information about all of the active and archive data sets that make up the log records. Since DB2 writes change records to the active log as they occur, Replication Extract can process the log records immediately after they are entered. Typically, DB2 writes two copies of the logs for redundancy in the event of log data set corruption. See “DB2 log capacity” on page 37 for more information on the DB2 log. DB2 log changes Replication requires an entire “before” and “after” image of the row that has been changed by an update. When you mark a table for replication using the Replication Agent interface dialog panels, the table is altered with the DATA CAPTURE CHANGES clause. As the number of DB2 tables marked for replication increases, so do the DASD space requirements for the DB2 active log data sets. There are no increases in the amount of data written to the log for deletes or inserts, because for deletes and inserts, the entire “before” image and “after” image is captured in the log. Tables that receive updates to fixed-length rows write additional data to the DB2 log, specifically, the complete before image and after image of the changed row. The additional DB2 log usage can be significant if the row size is large or if the number of updates is large. Replication Agent for DB2 UDB for OS/390 Installation Guide 3
  20. 20. Understanding basic concepts of replication systems Tables that receive updates to variable-length rows write additional data in the log, specifically, the data from the beginning of the row to the point of the change. This information is not normally written to DB2 logs. The effect of this change is minimal if the number of updates is small, if the row size is small, or if the updates are normally applied near the beginning of the row. DB2 does not log transactions in which the value of an updated DB2 column is identical to the value of that column before the update. Replication Agent does not replicate transactions of this nature because the transactions do not appear in the DB2 logs. Note There are no “begin” records for DB2. “Begin” records are generated from the first record in a transaction operation. DB2 active and archive logs Be sure to protect DB2 active and archive logs against loss or corruption. To optimize Replication Agent performance, be sure that the DB2 active logs are large enough to contain the number of log entries for a 12-hour period of update activity before reusing the log data set. This allows you to resume replication using log data following network outages that might interrupt replication, without requiring the log extract to read log entries from tape. Replication Extract Log extracts read and transfer relevant database transactions recorded in the database logs to LTM for MVS. The log extract in Replication Agent is Replication Extract. A DB2 table named LTMOBJECTS is created during the installation of Replication Agent. This table contains a row corresponding to each table that is marked for replication. Replication Extract uses the LTMOBJECTS table to identify the data marked for replication. To capture DB2 data changes, Replication Extract scans the DB2 active and archive logs for inserts, updates, and deletes on tables marked for replication. Replication Extract formats the extracted changes and passes them to LTM for MVS, which then transmits the changes to Replication Server. 4 Replication Agent for DB2 UDB for OS/390
  21. 21. CHAPTER 1 Understanding Replication Agent Replication Extract and LTM for MVS run simultaneously within a single MVS address space as an LTM for MVS started task, continuously reading the DB2 logs. When data sharing is enabled in DB2 version 5 or later, you can replicate transactions from multiple members of a data-sharing group with a single Replication Agent started task. Replication Extract merges the logs from each member within a data-sharing group. In a non-data-sharing environment, replicating transactions from multiple DB2 subsystems requires one Replication Agent started task for each DB2 subsystem. Each Replication Agent started task processes the log of a single DB2 subsystem. See “Understanding replication in a data-sharing environment” on page 17 for more information on data sharing. Replication Extract processing flow The following figure shows the processing flow between DB2, Replication Extract, LTM for MVS, and Replication Server: Figure 1-2: Replication Extract processing flow DB2 DB2 Catalog Replication Agent for DB2 UDB DB2 Replication LTM for Replication Logs Extract MVS Server OS/390 The processing flow for Replication Extract includes the following actions: 1 The MVS START command, which you issue from the MVS console, starts the LTM for MVS started task. (Replication Agent can also be started as a batch job.) Replication Agent for DB2 UDB for OS/390 Installation Guide 5
  22. 22. Understanding basic concepts of replication systems a LTM for MVS processes the configuration file and retrieves information about Replication Server, Replication Extract, user exits, defaults, DB2, traces, and DB2 subsystems. b LTM for MVS opens a connection to Replication Server. If the connection to Replication Server fails, LTM for MVS retries the connection (according to the value of the retry and Maximum_connect_retries configuration parameters). 2 LTM for MVS starts the Replication Extract task using the MVS ATTACH command. 3 Replication Extract processes the hlq.PDR.PARMLIB data set allocated to the PTIPARM DD name. The hlq.PDR.PARMLIB data set contains information about DB2 subsystem load libraries, plans, defaults, and traces. The hlq.PDR.PARMLIB data set also contains parameters that you can use to control the execution of Replication Extract. For information about the PDR.PARMLIB data set, see “Task 1: Edit the PARMLIB library members” on page 79. 4 Replication Extract connects to the DB2 subsystem using the DB2 CONNECT command. The DB2 subsystem must be active for the entire time the Replication Agent started task is active. 5 Replication Extract queries the LTMOBJECTS system table to identify the tables marked for replication. 6 Replication Extract queries the DB2 catalog to retrieve the definitions of all the tables recorded in the LTMOBJECTS table. These definitions are required to format the changes described in the DB2 log. 7 Replication Extract queries LTM for MVS for the origin queue ID (QID) of the last update that was successfully received by Replication Server, and writes a copy of the QID to the hlq.TRUNCPT data set. This QID is called the LTM Locator, and is stored in the Replication Server database, in the rs_locater table. From this QID, Replication Extract derives the point within the log from which processing is to resume. If the QID that LTM for MVS passes to Replication Extract and the QID in the TRUNCPT data set contain all binary zeros, Replication Extract begins processing from the end of the active log. 8 Replication Extract allocates and reads the BSDS to determine the names of all the active and archive log data sets. 6 Replication Agent for DB2 UDB for OS/390
  23. 23. CHAPTER 1 Understanding Replication Agent 9 Replication Extract resumes processing at the point derived from the LTM Locator and begins scanning the log (or logs, if Replication Agent is running in data-sharing mode) for changes to DB2 tables. 10 Using the log records that describe inserts, updates, and deletes to primary tables, Replication Extract constructs a full-row “after” image for inserts, a full-row “before” image for deletes, and full “before” and “after” images for updates for each affected row. The individual column values are converted from DB2 internal format to their external format. Replication Extract then passes the converted transaction operation information to LTM for MVS. Log Transfer Manager for MVS Log Transfer Manager receives relevant database transactions from log extracts. LTM for MVS translates this information into Log Transfer Language (LTL), and sends these LTL statements through a connection to Replication Server. LTM for MVS contains the following interfaces: • Replication API (Replication Application Program Interface) • Log Transfer Interface (LTI) • Sybase Open ClientConnect™ routines that allow LTM for MVS to communicate with Replication Server Replication Agent for DB2 UDB for OS/390 Installation Guide 7
  24. 24. Understanding basic concepts of replication systems Figure 1-3: LTM for MVS components Replication Agent for DB2 UDB Replication Replication Log Transfer Extract API Interface Open Client LTM for MVS LTM for MVS translates the transaction information received from Replication Extract into Log Transfer Language (LTL), and sends these LTL statements to the primary Replication Server. Replication Server holds the LTL statements in a stable queue, transforms these transactions (usually into SQL, according to user instructions), and passes the transformed transaction information to the replicate Replication Servers or replicate database(s) for processing. LTM for MVS processing flow LTM for MVS processes as follows: 1 Logs in to the primary Replication Server. 2 Sends a connect source command to identify the session as a log transfer source and to specify the database log to be transferred. 3 Obtains the maintenance user ID from Replication Server. LTM for MVS uses the Replication Server maintenance user ID to filter operations executed by the maintenance user. 4 Requests the origin queue ID from Replication Server. The origin queue ID contains the LTM Locator value. Replication Extract uses the LTM Locator value to determine the point in the log at which LTM for MVS should begin transferring transaction operation records. Replication Server successfully received all log records up to this location. 8 Replication Agent for DB2 UDB for OS/390
  25. 25. CHAPTER 1 Understanding Replication Agent 5 Receives transaction operations from Replication Extract following the point in the log indicated by the LTM Locator value and formats them into LTL commands. What you need to know Maintenance user ID The Replication Server get maintenance user command returns the Replication Server maintenance user ID. Replication Server uses the maintenance user ID to update tables with replicated data in the database monitored by Replication Agent. By default, Replication Agent does not pass transactions made by the maintenance user ID to Replication Server for replication. To replicate changes made by this user, set the value of the LTM for MVS LTM_process_maint_uid_trans configuration parameter to Y to specify that Replication Agent replicate all logged changes made by the Replication Server maintenance user. LTM Locator and The Replication Server get truncation command returns a origin queue ID value called the LTM Locator, which is the origin queue ID associated with the transaction operation last saved by Replication Server. Replication Extract uses the LTM Locator value to determine the location in the log where replication should begin. Replication Server has successfully saved all transactions up to this LTM Locator value in its stable queue; Replication Agent can safely ignore all transactions before this point in the log. Replication Server Replication Server transfers database transactions to the replicate database using a connection to the replicate database. Replication Server can replicate to a single database, multiple databases, or other Replication Servers. Replication Agent for DB2 UDB for OS/390 Installation Guide 9
  26. 26. Understanding the role of Replication Agent Replication Server holds the transaction operations in a stable queue and delivers them as soon as possible to other Replication Servers (replicate Replication Servers) or replicate databases. These transactions are transformed (usually into SQL) according to the instructions you provide to Replication Server and are sent to the replicate database for processing. Replication Server guarantees transaction delivery: Every transaction successfully received from a LTM is guaranteed to be delivered to appropriately subscribing replicate databases. Replication Server systems are administered through a LAN-based interface. The System Administrator creates subscriptions for replication definitions on Replication Server. The subscriptions and replication definitions define the columns and rows that Replication Server manages at the replicate sites. The System Administrator also defines destinations and routes to manage network traffic. Materialization Materialization is the process of initially populating the replicate database with a copy of the data from the primary database. Replication Agent requires that you set up and populate each replicate database so that it is in a state consistent with that of the primary database. Replication Server then replicates incremental changes to the primary data from the primary database to the replicate database. Understanding the role of Replication Agent Replication Agent is a component of a replication system that moves primary database transactions from DB2 through Replication Server to replicate databases. Replication Agent fits into the generic replication system, illustrated in Figure 1-4, with the following differences: • With Replication Agent, the primary database is DB2, which runs as a subsystem in MVS. The database logs are DB2 logs. 10 Replication Agent for DB2 UDB for OS/390
  27. 27. CHAPTER 1 Understanding Replication Agent • Replication Agent provides a log extract, called Replication Extract, that reads the DB2 logs and retrieves the relevant DB2 active and archive log entries for tables marked for replication. • LTM for MVS receives the data marked for replication from Replication Extract and transfers this data to Replication Server using the TCP/IP communications protocol. • Replication Server then applies the changes to the replicate databases. Figure 1-4: Replication Agent data flow Replication System: Primary Side DB2 Logs DB2 Replication Agent for DB2 UDB Replication LTM for Replication Extract MVS Server See also • Replication Server Administration Guide and Replication Server Design Guide for information about additional replication system topics Replication Agent data flow The Replication Agent data flow consists of four primary steps: Step 1: Replication Extract reads log data. Step 2: Replication API translates information. Step 3: The LTI delivers information. Step 4: Replication Server replicates information. Replication Agent for DB2 UDB for OS/390 Installation Guide 11
  28. 28. Understanding the role of Replication Agent Step 1: Replication Extract reads log data Replication Extract reads the DB2 active and archive log data sets for changes to DB2 tables marked for replication. It retrieves all the relevant information and delivers it to the Replication API, a component of LTM for MVS. Figure 1-5 illustrates this process. Figure 1-5: Replication Extract reads log data DB2 Logs DB2 OS/390 Replication Agent for DB2 UDB Replication Replication Log Transfer Extract API Interface Open Client LTM for MVS Step 2: Replication API translates information The Replication API receives information from Replication Extract, translates the command structures received from the log extract into Log Transfer Language (LTL) statements, places the LTL in a buffer, and delivers the buffer to the LTI. Figure 1-6 illustrates this process. 12 Replication Agent for DB2 UDB for OS/390
  29. 29. CHAPTER 1 Understanding Replication Agent Figure 1-6: Replication API translates information Replication Agent for DB2 UDB Replication Replication Log Transfer Extract API Interface Open Client LTM for MVS Step 3: The LTI delivers information The LTI delivers the buffer to the Open ClientConnect for MVS routines embedded in LTM for MVS, as shown in Figure 1-7. Figure 1-7: LTI translates information for Open Client Replication Agent for DB2 UDB Replication Replication Log Transfer Extract API Interface Open Client LTM for MVS Replication Agent for DB2 UDB for OS/390 Installation Guide 13
  30. 30. Understanding connectivity in a replication system Step 4: Replication Server replicates information LTM for MVS delivers LTL to Replication Server over the network. Replication Server translates the LTL statements into transactions that replicate the primary database changes to the replicate databases, as shown in Figure 1- 8. Figure 1-8: Replication Server receives transactions for replication DB2 Logs DB2 OS/390 Replication Replication Log Transfer Extract API Interface LTL Open Client Replication LTM for MVS Server Replication Agent for DB2 UDB See also • “Understanding connectivity in a replication system” for information on Replication Agent-to-Replication Server connectivity • Replication Server Administration Guide and the Replication Server Design Guide for more information about Replication Server functionality Understanding connectivity in a replication system Replicating transaction operations from MVS to Replication Server requires communication between different operating systems. Each site has two sets of connectivity options: 14 Replication Agent for DB2 UDB for OS/390
  31. 31. CHAPTER 1 Understanding Replication Agent • Replication Agent-to-Replication Server connectivity • Replication Server-to-DB2 connectivity Replication Agent-to-Replication Server connectivity Replication Agent communicates with Replication Server using the MVS TCP/IP protocol. Replication Server-to-DB2 connectivity Replication from Replication Server to DB2 replicate databases can use a variety of gateways. This connectivity, however, is required only when you plan to use automatic materialization (which Replication Agent does not support). Three-tier architecture You can use Sybase DirectConnect™ for DB2 for gateway connectivity to allow Replication Server to issue selects, inserts, updates, or deletes against the tables stored in DB2. Two-tier architecture You can also set up Replication Server-to-DB2 connectivity without a DirectConnect for DB2 gateway. For details on how to accomplish this, see the Replication Server Heterogeneous Replication Guide. See also • Chapter 3, “Understanding Replication Agent operational considerations” for information about connectivity options for replication into DB2 • Chapter 3, “Preparing for Replication” in the Replication Agent for DB2 UDB User’s and Troubleshooting Guide for OS/390 for information for information on bulk materialization. Replication Agent users Several user identifiers are required for working with Replication Agent. The following table describes each one and its requirements. Replication Agent for DB2 UDB for OS/390 Installation Guide 15
  32. 32. Replication Agent users Table 1-1: User IDs associated with Replication Agent User ID Description Restrictions LTMADMIN user Sybase recommends that you create the This identifier can be a TSO user ID LTMADMIN user ID, a TSO user optionally named or a group identifier. MVS user ID LTMADMIN, to perform the following tasks: restrictions apply to this identifier • Install, start, and stop Replication Agent (eight characters maximum, all uppercase). • Manage the Replication Agent system tables on DB2 This user ID should not be identical to the Replication Server • Bind the log extract plan maintenance user ID. Replication Server The maintenance user is the Replication Server user Any updates applied to the primary maintenance in the create connection command used to create a database by the maintenance user user connection from Replication Agent to Replication are ignored for replication unless Server. the value of the LTM for MVS Any updates applied to the primary database by the LTM_process_maint_uid_trans maintenance user are ignored for replication unless configuration parameter has a value the value of the LTM_process_maint_uid_trans of Y. LTM for MVS configuration parameter has a value Because this user ID is intended to of Y. compare against a user ID that can The Replication Server get maintenance user perform updates on DB2, it must command returns the Replication Server conform to MVS user ID maintenance user ID. restrictions (eight characters maximum, all uppercase). Note To avoid cyclic replication, this user ID should not be identical to the value of the LTM for MVS RS_user configuration parameter (the RS user). RS user The RS user is the user ID specified in the value of This user ID can be a maximum of the RS_user configuration parameter. 30 characters. This is the user ID that Replication Agent uses to connect to the primary Replication Server. Note This user ID should not be identical to the Replication Server maintenance user ID. RSSD user The RSSD user is the user ID specified in the value This user ID can be a maximum of of the RSSD_user configuration parameter. 30 characters. This is the user name for the Adaptive Server user who has permissions to perform selects against the primary Replication Server’s RSSD. 16 Replication Agent for DB2 UDB for OS/390
  33. 33. CHAPTER 1 Understanding Replication Agent Understanding replication in a data-sharing environment When you are using DB2 with data sharing enabled, you can replicate transactions from one or more DB2 subsystems within a data-sharing group. This chapter contains the following tasks: • Understanding data-sharing environment characteristics • Replicating transactions in a data-sharing environment Understanding data-sharing environment characteristics DB2 installations can have multiple MVS sysplexes. Each sysplex can contain multiple DB2 data-sharing groups. A DB2 data-sharing group is an MVS Cross-system Coupling Facility (XCF) group. Each member of a DB2 data-sharing group is a DB2 subsystem, also called a member. The members within a single DB2 data-sharing group can share data. DB2 data sharing does not function across groups. The Sysplex Timer synchronizes timestamps between all DB2 subsystems in a data-sharing group. The members of a DB2 data-sharing group can reside on the same or different MVS systems. Therefore, a DB2 data-sharing group can either span several MVS systems or reside on a single MVS system. Each DB2 subsystem maintains its own recovery logs and boot-strap data set (BSDS). The BSDS for every DB2 member in a data-sharing group contains information about the other group members’ BSDSs. The shared communications area (SCA) in the coupling facility (XCF) for a given data- sharing group contains information about all BSDSs and all logs for DB2 subsystems within the group. Replication Agent for DB2 UDB for OS/390 Installation Guide 17
  34. 34. Understanding replication in a data-sharing environment Figure 1-9: Illustration of data-sharing group components OS/390 System 1 OS/390 System 2 Sysplex Shared Communications Sysplex Area Timer DB2 Subsystem DB2 DB2 Subsystem Subsystem DB2 Data-Sharing Group Each log record header contains a log record sequence number (LRSN). The LRSN is a 6-byte value derived from the Store Clock timestamp. The LRSN is equal to or greater than the timestamp value truncated to 6 bytes. This value also exists in the header page of the tablespace. In the data-sharing environment, the LRSN replaces the relative byte address (RBA), although each subsystem continues to use the RBA for its own logs and BSDS. Replicating transactions in a data-sharing environment When data sharing is enabled in DB2 version 6 or later, you can replicate transactions from multiple members of a data-sharing group with a single Replication Agent started task. Replication Extract merges the logs from each member within a data-sharing group. To replicate transactions when using DB2’s data-sharing environment, you must supply specific parameter values in the following: • The LTM for MVS Log_identifier configuration parameter 18 Replication Agent for DB2 UDB for OS/390
  35. 35. CHAPTER 1 Understanding Replication Agent • The SETUP00 and PDR members in the hlq.PDR.PARMLIB data set Note The SETUP00 member was named SETUP in previous releases. • The PDRBIND member in the hlq.JCL data set (you edit and submit the PDRBIND job when binding the log extract plan) See also • Chapter 6, “Configuring Replication Extract” for information about editing the hlq.PDR.PARMLIB data set members and binding the log extract plan • Appendix A, “LTM for MVS Configuration Parameters” for detailed information about the Log_identifier parameter Replication Agent task and documentation topics overview Table 1-2 lists the locations in the Replication Agent documentation of the tasks involved in installing, using, and troubleshooting Replication Agent. Each of the guides listed in this table includes a preface, this overview chapter, and a glossary of technical terms. Table 1-2: Where to find Replication Agent documentation topics Replication Agent for DB2 UDB Installation Guide for OS/390 Plan your Replication Agent installation Includes information about installation preparation, including software requirements, operational considerations, and filling out the Replication Agent Installation Worksheet: • Go to Chapter 2, “Understanding Replication Agent Installation Requirements” • Go to Chapter 3, “Understanding Replication Agent Operational Considerations” • Go to Chapter 4, “Gathering Installation Information” Install Replication Agent Includes instructions for installing the Replication Agent software, granting permissions, and configuring Replication Extract. • Go to Chapter 5, “Installing Replication Agent” • Go to Chapter 6, “Configuring Replication Extract” Replication Agent for DB2 UDB for OS/390 Installation Guide 19
  36. 36. Replication Agent task and documentation topics overview Set up communications Includes information about setting up TCP/IP communications between Replication Agent and Replication Server: • Go to Chapter 7, “Configuring TCP/IP for Replication Agent” Verify your installation Includes information about setting required configuration parameter values, and test connections with the PING and PINGRS utilities: • Go to Chapter 8, “Completing and Verifying Your Replication Agent Installation” Reference Information • Appendix A, “LTM for MVS Configuration Parameters” • Appendix B, “Replication Extract Configuration Parameters,” • Appendix C, “Replication Agent Data Sets” • Appendix D, “Upgrading Your Replication Agent Software” • Appendix E, “Running Multiple Replication Agents” Replication Agent for DB2 UDB User’s and Troubleshooting Guide for OS/390 Start and stop Replication Agent Includes information about starting, stopping, and troubleshooting Replication Agent using trace commands: • Chapter 2, “Managing Replication Agent” Prepare for replication Includes information about preparing your replication environment for Replication Agent operations, including Replication Server setup, materializing replicate tables, and marking source data for replication: • Chapter 3, “Preparing for replication” • Chapter 4, “Replicating source tables” Work with Replication Agent system tables Includes information about using the Replication Agent system tables on DB2 to coordinate bulk materialization and mark tables for replication: • Chapter 5, “Working with Replication Agent system tables” Work with datatype conversions Includes information about LTM for MVS datatypes, Adaptive Server datatypes, and Replication Agent datatype conversion handling: • Chapter 6, “Working with datatype conversions” 20 Replication Agent for DB2 UDB for OS/390
  37. 37. CHAPTER 1 Understanding Replication Agent Troubleshoot Replication Agent Includes information about basic troubleshooting procedures, startup problems, restrictions, and failure and recovery: • Chapter 7, “Basic troubleshooting procedures” • Chapter 8, “Troubleshooting Replication Extract problems” • Chapter 9, “Understanding known issues and restrictions” • Chapter 10, “Troubleshooting Replication Agent start-up problems” • Chapter 11, “Understanding error conditions” • Chapter 12, “Recovering from Replication System errors” Understand Replication Agent messages Includes information, error, and warning messages written to log files and to the MVS operator console, accompanied by recommendations for user responses: • Chapter 13, “Replication Extract messages” • Chapter 14, “LTM for MVS messages” • Chapter 15, “MVS console messages” Reference • Appendix A, “LTM for MVS configuration parameters” • Appendix B, “Replication Extract configuration parameters” • Appendix C, “Replication Extract commands” • Appendix D, “Creating user exits” What’s next Before installing Replication Agent, be sure your site meets the installation requirements. Go to Chapter 2, “Understanding Replication Agent Installation Requirements”. Replication Agent for DB2 UDB for OS/390 Installation Guide 21
  38. 38. What’s next 22 Replication Agent for DB2 UDB for OS/390
  39. 39. CH A PTE R 2 Understanding Replication Agent Installation Requirements Before you install Replication Agent, ensure that your site meets the requirements listed in this chapter. This chapter includes the following information: Topic Page Understanding team skill requirements 23 Understanding software requirements 24 Understanding team skill requirements You need team members with the skills described in Table 2-1 to install Replication Agent successfully. For your site, identify each person or team responsible for the skill set. Table 2-1: Team skill requirements Team skill Skill set Coordination • Effective communication skills • Understanding of the MVS operating system Communications • Understanding of connectivity products used at administration your site (SNA, VTAM, and TCP/IP) • Ability to design, establish, test, and troubleshoot remote physical communications between Replication Agent and Replication Server OS/390 systems • Knowledge of the standards and conventions at programming the installation site • Knowledge of job naming and accounting standards, data set naming conventions, and library management and authorization techniques • Ability to create started tasks Replication Agent for DB2 UDB for OS/390 Installation Guide 23
  40. 40. Understanding software requirements Team skill Skill set Data source administration • Understanding of the DB2 relational database management system (RDBMS), its authorization scheme, and its backup and recovery utilities • Understanding of active and archive logs • Ability to manage permissions Replication Server • Ability to design and administer the Replication administration Server environment • Ability to determine appropriate methods for materialization and synchronization of primary and replicate tables • Ability to administer Adaptive Server databases • Ability to manage permissions needed for replication Understanding software requirements This section describes the software requirements for Replication Agent, including the following: • Mainframe software requirements • LAN software requirements Mainframe software requirements Table 2-2 describes the mainframe software requirements for Replication Agent. Check each item when it is verified by the appropriate team member. Your Replication Agent installation can fail if you do not meet the prerequisites described in this section. 24 Replication Agent for DB2 UDB for OS/390

×