{"text_format":"2","workbook":"xls","n_sheets":1,"sheets":["report2"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":1,"defined_names":1,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900","formulas":"cached_only"}

{"sheet":"report2","index":0,"n_rows":21,"n_cols":5,"rows_kept":21,"cut":false,"hidden":false,"merged":[[0,2,0,3],[0,4,0,5],[1,2,1,3],[1,4,1,5],[2,2,2,3],[3,2,3,3],[4,2,4,3],[5,2,5,3],[6,2,6,3],[7,2,7,3],[9,2,9,3],[10,2,10,3],[14,2,14,3]],"flags":["formulas_cached_only"]}
[null,"1.","Record Nr.",null,"UNINA9910955387803321"]
[null,null,"Titolo",null,"IMS DataPropagator implementation guide / / Jouko Jantti ... [et al.]"]
[null,null,"Pubbl/distr/stampa",null,"[San Jose, Calif., : IBM, International Technical Support Organization, c2002]"]
[null,null,"Edizione",null,"[[1st ed.].]"]
[null,null,"Descrizione fisica",null,"xviii, 252 p. : ill"]
[null,null,"Collana",null,"Redbooks"]
[null,null,"Disciplina",null,"005.74"]
[null,null,"Soggetti",null,"Database management"]
[{"$nulls":4},"IMS (DL/I) (Computer system)"]
[null,null,"Lingua di pubblicazione",null,"Inglese"]
[null,null,"Formato",null,"Materiale a stampa"]
[null,null,null,"Livello bibliografico","Monografia"]
[null,null,null,"Note generali","Bibliographic Level Mode of Issuance: Monograph"]
[null,null,null,"Nota di bibliografia","Includes bibliographical references (p. 243-244) and index."]
[null,null,"Nota di contenuto",null,"Front cover -- Contents -- Figures -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Introduction -- Chapter 1. Overview -- 1.1 What are the components of data propagation -- 1.2 Types of propagation -- 1.2.1 Asynchronous, near real time, MQSeries based propagation -- 1.2.2 Asynchronous log-based propagation -- 1.2.3 Synchronous propagation -- 1.3 IMS DPROP systems types -- 1.3.1 MQ Capture setup -- 1.3.2 MQ Apply setup -- 1.3.3 LOG-ASYNC Selector setup -- 1.3.4 LOG-ASYNC Receiver setup -- 1.3.5 Synchronous setup -- 1.4 Data mapping types -- 1.4.1 Mapping Case 1 -- 1.4.2 Mapping Case 2 -- 1.4.3 Mapping Case 3 -- 1.4.4 Special mapping cases layouts -- Chapter 2. Subsystem installation setup -- 2.1 OS/390 setup -- 2.1.1 SVC information -- 2.1.2 VLF information -- 2.1.3 OS/390 subsystem name -- 2.2 IMS subsystem setup -- 2.2.1 IMS log archive changes -- 2.2.2 Updates to IMS DLIBATCH procedures -- 2.2.3 DB2 Apply as BMP -- 2.3 MQSeries setup -- 2.3.1 MQSeries subsystem setup -- 2.3.2 MQSeries IMS adapter setup -- Part 2 Installation of DPROP systems -- Chapter 3. Installing a DPROP environment -- 3.1 Starting the installation panels -- 3.2 Defining the DPROP environment name -- 3.3 Defining the DPROP environment parameters -- 3.3.1 Defining the DPROP environment elements -- 3.3.2 Defining DPROP systems data set names -- 3.3.3 Defining the system data sets Panel 2 -- 3.3.4 Defining the OS/390 copy program -- 3.3.5 Defining environment JOB parameters -- 3.3.6 Defining installation library -- 3.3.7 Defining EKYGSYS parameters -- 3.3.8 Defining the JOB card information -- 3.3.9 Defining the audit trail table "]
[{"$nulls":4},"-- 3.3.10 Defining the audit trail table information -- 3.3.11 Defining the audit trail table DB2 objects -- 3.3.12 Defining the Language Interface environment."]
[{"$nulls":4},"3.3.13 Defining the dynamic allocation exit routine -- Chapter 4. Install and customize MQ-ASYNC Capture system -- 4.1 Introduction -- 4.1.1 System parameters and job generation -- 4.1.2 Submit installation and verification jobs -- 4.1.3 Installation verification for MQ Capture -- 4.2 Creating an additional Capture system -- 4.3 Prepare your own MQ-ASYNC capture -- Chapter 5. Installing an MQ Apply system -- 5.1 IMS DPROP MQ Apply system installation panel flow -- 5.2 Specifying MQ Apply system parameters -- 5.2.1 Defining the DB2 subsystem parameters -- 5.2.2 Defining the JOB and JOBLIB statements -- 5.3 Define system installation and IVP parameters -- 5.3.1 Define the IMS DPROP generation macro -- 5.3.2 Defining the IMS DPROP directory tables -- 5.3.3 Defining the IMS DPROP MVG input tables -- 5.4 Binding the DB2 application plans -- 5.4.1 Prepare binds for the IMS DPROP and SQL update modules -- 5.4.2 Creating the privileges for the DB2 collection IDs -- 5.4.3 Prepare the binds for the SCU plan -- 5.4.4 Defining the binding plan for the MVG application -- 5.4.5 Defining the binding plan for the CCU -- 5.4.6 Defining the binding plan for MQ Apply -- 5.5 Specifying the IMS DPROP and SMF data sets -- 5.6 Define the IVP parameters -- 5.6.1 Define the IVP JOB parameters -- 5.6.2 Defining the MQSeries parameters for the IVPs -- 5.7 Generating and submitting installation jobs -- 5.7.1 DPROP environment installation job submission -- 5.7.2 Generating the IMS DPROP Stage I Job -- 5.7.3 Edit and submit IMS DPROP Stage I job -- 5.7.4 Submitting IMS DPROP system installation jobs -- 5.7.5 Submitting IVP jobs -- 5.7.6 Verifying IMS DPROP installation for the MQ Apply system -- Chapter 6. Installing a Selector and Receiver system -- 6.1 Selector and Receiver system installation panel flow -- 6.2 Working with the Specification Primary Menu panel."]
[{"$nulls":4},"6.2.1 Defining the DB2 environment, JOB, and JOBLIB statements -- 6.2.2 Defining the DB2 subsystem parameters -- 6.2.3 Defining the JOB and JOBLIB statements -- 6.3 Defining installation and IVP parameters -- 6.3.1 Defining the IMS DPROP generation macro -- 6.3.2 Defining the IMS DPROP directory tables -- 6.3.3 Defining the mapping verification and generation input tables -- 6.3.4 Binding the DB2 application plans -- 6.3.5 Prepare the binds for the IMS DPROP and SQL update modules -- 6.3.6 Creating the privileges for the DB2 collection IDs -- 6.3.7 Defining the binding plan for the status change utility -- 6.3.8 Bind plan for mapping verification and generation application -- 6.3.9 Defining the binding plan for the consistency check utility -- 6.3.10 Defining the binding plan for the PRDS registration utility -- 6.3.11 Defining the binding plan for the group unload utility -- 6.3.12 Defining the binding plan for the LOG-ASYNC Receiver -- 6.3.13 Specifying the IMS DPROP and SMF data sets -- 6.3.14 Defining the IVP parameters -- 6.3.15 Modifying the IMS DPROP system title -- 6.4 Generating and submitting installation and IVP jobs -- 6.4.1 Submitting the installation JOBs -- 6.4.2 IMS DPROP environment installation job submission -- 6.4.3 Generating the Stage I job -- 6.4.4 Submitting the system installation jobs -- 6.4.5 Submitting the IVP jobs -- 6.4.6 Verifying the installation for the LOG ASYNC Selector -- 6.4.7 Verifying the installation of the LOG ASYNC Receiver -- Part 3 Migrating from Version 2.2 -- Chapter 7. Migrating a Selector and Receiver system -- 7.1 Migration of a Selector and Receiver system -- 7.1.1 Migration process prerequisites -- 7.1.2 General migration considerations -- 7.2 Starting migration configuration -- 7.2.1 Selecting a DPROP system to migrate -- 7.2.2 Existing IMS DPROP environments."]
[{"$nulls":4},"7.3 Migrating a Selector and Receiver system -- 7.3.1 Selector and Receiver system migration panel flow -- 7.3.2 Working with the Specification Primary Menu panel -- 7.3.3 Defining the DB2 environment, JOB, and JOBLIB statements -- 7.3.4 Defining the DB2 subsystem parameters -- 7.3.5 Defining the JOB and JOBLIB statements -- 7.3.6 Defining installation and IVP parameters -- 7.3.7 Defining the IMS DPROP generation macro -- 7.3.8 Defining the IMS DPROP directory tables -- 7.3.9 Defining the IMS DPROP MVG input tables -- 7.3.10 Binding the DB2 application plans -- 7.3.11 Prepare binding -- 7.3.12 Creating the privileges for the DB2 collection IDs -- 7.3.13 Defining the binding plan for the status change utility -- 7.3.14 Bind plan for mapping verification and generation application -- Part 4 Setting up for propagation -- Chapter 8. Preparing propagation requests -- 8.1 What is a propagation request -- 8.2 Planning a propagation request -- 8.3 How to set up a propagation request -- 8.3.1 The MVG input tables -- 8.3.2 Set up a PR via MVG input tables -- 8.3.3 The mapping verification generation utility (MVGU) -- 8.3.4 The IMS DPROP directory tables -- 8.4 Sample mapping in a propagation request -- 8.4.1 Propagation request with WHERE clause -- Chapter 9. Propagation to staging tables -- 9.1 Propagation of IMS data to staging tables -- 9.2 What are staging tables -- 9.3 Consistent change data tables -- 9.4 Defining staging tables -- 9.5 CCD propagation requests -- 9.6 Restrictions to CCD table propagation -- 9.7 Propagation to other platforms -- Appendix A. Additional material -- Locating the Web material -- Using the Web material -- How to use the Web material -- Glossary -- A -- B -- C -- D -- E -- F -- G -- H -- I -- L -- M -- N -- O -- P -- R -- S -- T -- U -- V -- Abbreviations and acronyms -- Related publications -- IBM Redbooks -- Other resources."]
[{"$nulls":4},"Referenced Web sites -- How to get IBM Redbooks -- IBM Redbooks collections -- Index -- Back cover."]
[null,null,null,"Sommario/riassunto","IMS DataPropagator (IMS DPROP) is a licensed program that maintains consistency between two copies of the same data, where one copy of the data is stored in an IMS Database Manager (IMS DB) database and the other copy is stored in a DB2 database. IMS DPROP is a key component of IBM's Data Replication Solution and IBM's Business Intelligence Solution. IMS DPROP can perform asynchronous change propagation, meaning that the change is applied independently of the updating application. You can apply changes at predetermined intervals, managing replication according to your business needs. Changes are captured from IMS environment with minimal impact to transaction response time. For asynchronous propagation, the IMS DB and DB2 systems may reside on the same or different OS/390 or z/OS systems and run under either the IMS Transaction Manager or CICS. This IBM Redbooks publication was written to enhance the installation manual and provide customer assistance in the installation and migration processes. Please note that the additional material referenced in the text is not available from IBM."]