IBM DB2 RepliData for z/os. Installation. Version 3 Release1 ISRD-INST-03

Transcription

1 IBM DB2 RepliData for z/os Installation Version 3 Release1 ISRD-INST-03

2

3 IBM DB2 RepliData for z/os Installation Version 3 Release1 ISRD-INST-03

4 Note! Before using this information and the product it supports, read the general information in Appendix F, Notices, on page 107. Fourth Edition (April 2003) This edition applies to Version 3 Release 1 of IBM DB2 RepliData for z/os (Program Number 5799-GKW) and to all subsequent releases until otherwise indicated in new editions. This edition replaces ISRD-INST-02. Copyright International Business Machines Corporation 1993, All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures vii About this book ix Who should read this book ix Conventions used in this book ix Service updates and support information ix Where to find information x How to send your comments x Summary of changes xi Chapter Before you start Chapter Step 1. Prepare your system a. Verify the system environment b. Check your existing libraries c. Set the CICS runtime options for LE d. Set the CICS SIT parameters e. Decide on naming conventions Chapter Step 2. Install the RepliData tape a. Obtain the RepliData tape b. Extract the sample install jobs c. Allocate SMP/E libraries d. Receive the RepliData software e. Apply the RepliData software f. Accept the RepliData software g. Allocate the staging libraries (recommended) h. Customize your environment Chapter Step 3. Customize the install libraries a. Copy the distribution libraries b. Create files needed for CICS set-up c. Prepare the concatenation CLIST d. Run the concatenation CLIST e. Define the environment and dataset names f. Build the customized JCL Chapter Step 4. Select the processing options Chapter Step 5. Update the CICS PLT start-up and shut-down lists Chapter Step 6. Update the CSD file Chapter Step 7. Allocate and initialize data sets Copyright IBM Corp. 1993, 2003 iii

6 7a. Allocate the DIABMSG data set b. Allocate the PARMDRVR data set c. Allocate the SDDLCOM data set d. Allocate the SDDLJCL data set e. Allocate the SDDLSTAT data set f. Allocate the SDDLMSG data set g. Initialize the data sets Chapter Step 8. Add entries to the file control table Examples for adding entries manually Chapter Step 9. Create the system node table Chapter Step 10. Allocate the data sets for the generated DAPs Chapter Step 11. Generate the DAPs Chapter Step 12. Initialize the SDDLJCL data set a. Prepare the VSAM file b. Define an APF-authorized load library c. Copy load module SDDREAD into APF-authorized library d. Bind the plan for SDDREAD e. Grant authority to the log read process Chapter Step 13. Modify the PARMDRVR data set Chapter Step 14. Install the databases a. Estimate how much DASD you need b. Prepare for installation c. Execute the jobs to install the database d. Complete the database installation Chapter Step 15. Customize CICS a. Start CICS b. Define the MVS internal reader to CICS c. Verify the CICS journal definition d. Identify the load module libraries to CICS e. Identify programs and transactions to CICS f. Define RDO groups to CICS g. Define transaction for the log read program h. Define VSAM files to CICS Chapter Step 16. Define MQSeries queues and processes a. Define parallel paths for sending systems b. Define the parallel paths for receiving systems c. Define queues to process compressed and archived log data d. Define the permanent dynamic queue iv Installation

7 16e. Define the queue for the currency status checking function Chapter Step 17. Verify the install a. Verify the CICS definitions b. Verify the SDD installation c. Verify that RMF has been installed d. Verify the Change Capture installation Chapter Step 18. Finish installation on source system Chapter Step 19. Identify the tables to replicate Appendix A. RepliData component list Installation components Administration components Initialization and Termination components Change Capture components Change Transmit components Change Receive and Apply components Service Module components Utility components Global Definitions (cross-component) objects Appendix B. Migrating from V2.3.1 to V Migration procedure Timestamp arbitration Appendix C. Migrating to V Migration procedure Timestamp arbitration Appendix D. Removed RepliData Components CICS transactions: CICS programs and maps: Batch programs: Transient data queues (TDQs): Resource control table entries (RCTs): DB2 DBRMs: DB2 plans (member CRDDJFRE contains FREE PLAN statements): DB2 tables, views and tablespaces (member CRDDTDRP contains DROP statements): VSAM files: Appendix E. Initializing the SDDLJCL data set with SDDLOGW Appendix F. Notices Trademarks Bibliography RepliData publications CICS publications Contents v

8 DB2 publications MQSeries publications SMP/E publications Index vi Installation

9 Figures 1. Sample JCL for extracting sample install jobs RepliData Installation Main Panel RepliData Environment Definition Panel RepliData MVS Environment Definition Panel RepliData Replication Links Definition Panel RepliData CICS Environment Definition Panel RepliData DB2 Environment Definition Panel RepliData Parameter Definition Panel RepliData Environment Table Panel SYSNODTB sample from REPLI.SAMPLE.SOURCE RepliData Installation Test panel Copyright IBM Corp. 1993, 2003 vii

10 viii Installation

11 About this book Who should read this book This book is a guide to installing RepliData on your systems and performing the initial configuration work.. Always check the Data Management Library page for the most current version of this publication: The technical changes for this edition are summarized under Summary of changes on page xi. This book is intended for anyone who is responsible for installing RepliData for z/os. Conventions used in this book This book uses the following highlighting conventions: v Boldface type indicates commands or user interface controls such as names of fields, folders, icons, or menu choices. v Monospace type indicates examples of text that you enter exactly as shown. v Italic type indicates variables that you should replace with a value. It is also used to indicate book titles and to emphasize significant words. The following labels identify significant elements that might be found within this book: v Definiton: v v v v v Example: is used to identify example code or scenarios. In this chapter: is used to identify the significant subsections within each chapter. Recommendation: is used to provide guidance when more than one option is available. Related Reading: is used to refer you to other publications that contain relevant information. Restriction: is used to identify a restriction or limitation with this product or an associated procedure. Service updates and support information To find service updates and support information, including software FixPaks, PTFs, Frequently Asked Question (FAQs), technical notes, troubleshooting information, and downloads, refer to the following Web page: Copyright IBM Corp. 1993, 2003 ix

12 Where to find information How to send your comments The Data Management Tools Library Web page provides current product documentation that you can view, print, and download. To locate publications with the most up-to-date information, refer to the following Web page: IBM Redbooks that cover Data Management Tools are available from the following Web page: Your feedback is important in helping to provide the most accurate and high-quality information. If you have any comments about this book or any other RepliData for z/os documentation: v v v Use the online reader comment form located at Send your comments by to dmtinfo@us.ibm.com. Be sure to include the name of the book, the part number of the book, the version of RepliData for z/os and, if applicable, the specific location of the text you are commenting on (for example, a page number or table number). Print and fill out the reader comment form located at the back of this book. You can use the following methods to return the form: Give it to your local IBM branch office or IBM representative. Send it to the address printed on the reader comment form. For customers in the U.S. and Canada, fax it to x Installation

13 Summary of changes Changes to this document are identified by revision bars to the left of the changes. These changes include the following: ISRD INST 03 v The procdure has changed for defining the queue for the currency status checking function. See v The description of how currency tracking works has been updated. See v Two new Change Capture statements have been added to the PARMDRVR file: If you are operating more than one instance of the Change Capture process, you can use the STARTBAT statement to indicate whether a particular CICS region should start the RepliData batch log read program. You can use CAPTNODE statement to specify the node to which SDDREAD will send log records. Use more than one CAPTNODE statement to send more than one node. For details, see An appendix has been added to explain how Change Capture works when more than one instance is running. See The description of the GMTO parameter has been clarified. This parameter specifies the differences between Greenwich Mean Time and the local system clock. See The description of the SCR parameter has been clarified. This parameter can be used to generate DAPs. For details, see A warning has been added to A page has been added to explain how to improve RepliData s performance by making your temporary storage queues memory resident. See The recommended value for NUMLOGK statement has been corrected. See All references to the TXBVIEW tool have been removed. The TXBVIEW tool is no longer supported for generating DAPs. In addition, the procedure for generating DAPs has changed. See You can now specify the SDDRTRY1T parameter as a number of seconds. In addition, the possible values for SDDRTRY2T have been clarified. See Copyright IBM Corp. 1993, 2003 xi

14 xii Installation

15 Chapter 1. Before you start This guide explains how to install Version 3.1 of RepliData for z/os. v If you are migrating from RepliData V2.3.1 to V3.0, follow the procedure in Appendix B, Migrating from V2.3.1 to V3.0, on page 93. v If you are migrating from RepliData V3.0 to V3.1, follow the procedure in Appendix C, Migrating to V3.1, on page 97. Because RepliData is a CICS DB2 application, you will need the appropriate CICS, DB2, MQSeries and MVS authority to: v Install CICS table definitions in a CICS address space. v Allocate and initialize files. v Define DB2 databases. v v Initialize parameters, generate JCL for batch jobs, and define objects for MQSeries Queue Manager. Verify that RepliData is installed correctly. Use this guide to install RepliData in each CICS source and target system. Both systems will have the same RepliData CICS definitions, files, DB2 databases, and load modules. Note: This guide and the installation package do not address the access authority for the files, transactions, and databases. Follow the standards at your location. Copyright IBM Corp. 1993,

16 2 Installation

17 Chapter 2. Step 1. Prepare your system 1a. Verify the system environment 1. Make sure that these applications are installed: v CICS/ESA Release 4.1 or higher or CICS Transaction Server Version 1 Release 1 or higher v MQSeries for MVS/ESA Version 2.1 or higher v DB2 Version 4 Release 1 or higher v The OS PL/I Compiler Version 2.3, or the PL/I for MVS and VM Compiler Version 1.1 v The compiler-related run-time environment or Language Environment Version 1.5 or higher, with CICS PL/I support specified in the System Initialization Table (SIT) v OS/390 SMP/E or System Modification Program/Extended ( ) Release 8 or higher 2. Make sure the maintenance for the DB2, CICS and MQSeries applications is up to date. 3. Make sure the MQ CICS Adapter and DB2 Attachment interfaces are installed in each RepliData CICS region. 4. Make sure you have at least 50 cylinders of 3390 DASD for the DB2 tables. (When you get to Step 14. Install the databases on page 47, you ll determine whether you need more DASD for your tables.) 1b. Check your existing libraries When you install RepliData, several non-replidata modules are expected to be in the appropriate libraries. 1. Make sure the CICS library SDFHLOAD contains modules DSNCLI and DFHEAI. APARs and PTFs may exist to correct any anomalies in this requirement. If you need help, call the help desk for the appropriate product. 2. Make sure the PL/I library PLIBASE contains module DFHPL10I and that the PL/I library SIBMBASE contains module IBMBINT. If these modules are missing, you probably don t have the OS PL/I Compiler Version 2.3 or the PL/I for MVS and VM Compiler Version 1.1. In this case, the PLIBASE and SIBMBASE libraries are not available for SMP/E link edit. Use the LE versions of PLIBASE and SIBMBASE (probably SYS1.SCEELKED) and install the appropriate CICS SYSMOD to supply the missing modules. 3. Make sure the MQ library SCSQLOAD contains modules CSQBSTUB and CSQCSTUB. 4. Make sure the DB2 library SDSNLOAD contains module DSNELI. 1c. Set the CICS runtime options for LE370 If you are using LE370, make sure the following is specified in your CICS runtime options: STORAGE=((00,NONE,00,0K),OVR) Copyright IBM Corp. 1993,

18 1d. Set the CICS SIT parameters Check your CICS System Initialization Table (SIT) parameters: v v STGPROT=YES, RENTPGM=PROTECT, and INTTR=OFF are tolerated by RepliData V3.1. Make sure the following parameter is specified for RepliData: TRANISO=NO 1e. Decide on naming conventions 1. Decide whether you want to accept RepliData s defaults for these objects: v The CICS transaction ID under which the log read program (SDDLOGJ) executes. The default name is SDL1. v The name of the CICS Transient Data Queue into which the RepliData components write error messages. The default name is SDMN. v The CICS file names of the VSAM files used by Change Capture during execution. The default names are SDDLCOM and SDDLJCL. If anything in your environment conflicts with any of the default names, you can save time by deciding now on the names you are going to use for these objects. 2. Decide on the name to be used for each system on which RepliData will be installed. There will be one installation-defined name for each CICS system on which the RepliData Log Read program or Change Apply programs will be executing. 3. Decide on the ID of each system on which RepliData will be installed. System IDs are the 4-character CICS SYSIDs on which the RepliData Log Read program will be executing. There will be a one-to-one correspondence between the system IDs and the installation-defined names for each system. 4 Installation

19 Chapter 3. Step 2. Install the RepliData tape 2a. Obtain the RepliData tape Obtain the RepliData install tape from the RepliData support group. The tape contains these files: File name File number Description CRD.F25P310.SMPMCS 1 SMP/E MCS statements for function F25P310 CRD.F25P310.F1 2 JCLIN CRD.F25P310.F2 3 ACRDOBJ (object code) CRD.F25P310.F3 4 ACRDDBRM (DBRM library) CRD.F25P310.F4 5 ACRDMAC (macros) CRD.F25P310.F5 6 ACRDISPF (TSO panels, etc.) CRD.F25P310.F6 7 ACRDSAMP (JCL procedures, samples, etc.) CRD.F25P310.F7 8 ACRDCMAP (CICS maps) Also, be sure to obtain all required maintenance for RepliData. 2b. Extract the sample install jobs 1. From the RepliData install tape, extract the sample JCL file, CRD.F25P310.F6, using JCL similar to this: //*jobname job //* //*Deletes (if it exists) and recreates dataset: CRD.BOOTSTRP //*Unload the sample JCL for RepliData from the install tape www //* //DELBOOT EXEC PGM=IEFBR14 //BOOTSTRP DD DSN=CRD.BOOTSTRP,DISP=(MOD,DELETE), // SPACE=(TRK,1),UNIT=SYSDA //* Figure 1. Sample JCL for extracting sample install jobs (Part 1 of 3) //* Extract only Installation-related jobs from SCRDSAMP //COPYBOOT EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //SYSUT2 DD DSN=CRD.BOOTSTRP,DISP=(,CATLG), // SPACE=(CYL,(5,1,40),RLSE),UNIT=SYSDA //SYSUT1 DD DSN=CRD.F25P310.F6, // DISP=OLD,UNIT=TAPE,LABEL=(7,SL), // VOL=SER=WWW //SYSIN DD * Figure 1. Sample JCL for extracting sample install jobs (Part 2 of 3) Copyright IBM Corp. 1993,

20 COPY INDD=SYSUT1,OUTDD=SYSUT2 S M=CRDNQACC S M=CRDNQAL1 S M=CRDNQAL2 S M=CRDNQAL3 S M=CRDNQAPP S M=CRDNQCSI S M=CRDNQRCV S M=CRDNQTS1 S M=CRDNQUC1 S M=CRDNQUC2 /* // 2c. Allocate SMP/E libraries Figure 1. Sample JCL for extracting sample install jobs (Part 3 of 3) The bootstrap JCL file contains these members: CRDNQTS1 TSO RECEIVE datasets containing initial load information for RepliData files. CRDNQAL1 Allocate SMP/E datasets. These datasets are needed only for a stand-alone SMP/E install. CRDNQAL2 Allocate RepliData SMP/E datasets. CRDNQAL3 Create RepliData SMP/E target libraries for execution libraries. CRDNQCSI Allocate and initialize SMP CSI. This is needed only for a stand-alone SMP/E install. CRDNQUC1 UCLIN CSI with SMP/E-required RepliData information. CRDNQUC2 UCLIN CSI with DDDEFs for CICS, PLI, DB2 and MQ load libraries. This is required for CALLLIBS linkedits. CRDNQRCV SMP/E Receive function. CRDNQAPP SMP/E Apply function. CRDNQACC SMP/E Accept function. 2. Determine whether the high-level qualifier CRD exists. This is the default for all jobs, and the documentation expects this qualifier. By default, the SMP/E jobs create and populate datasets CRD.ACRDxxxx and CRD.SCRDxxxx. If the high-level qualifier CRD does not exist, create it before you run these jobs. To use another qualifier, make the appropriate changes in all jobs and documentation. 1. Review the comments in the individual jobs to customize the jobs to meet your standards. Make changes as needed to meet your installation standards. 6 Installation

21 If you choose a high-level qualifier other than CRD, adjust job CRDNQCSI to force SMP/E to create SMPTLIB datasets with the correct high-level qualifier. To use a name other than F25P310.xx, change the SMPTLIB DDDEF DSPREFIX parameter, which is set in the CRDNQCSI job to CRD.SMPTLIB : ADD DDDEF(SMPTLIB) DSPREFIX(CRD.SMPTLIB) CYLINDERS DIR(250) SPACE(5,5) UNIT(SYSDA) Change this in the CRDNQCSI job to the correct high-level qualifier. Make sure the SMPTLIB dataset names do not have the same name as the tape RELFILE names. (That s why SMPTLIB is included as part of the DSPREFIX default parameter in the sample.) 2. Run these jobs from the bootstrap JCL library to allocate and format the SMP/E required datasets: CRDNQAL1 (see the note below) CRDNQAL2 CRDNQCSI (see the note below) CRDNQUC1 CRDNQUC2 When these jobs are completed, you have a viable set of install libraries to perform the SMP/E-based installation. 2d. Receive the RepliData software Note: It is recommended that you install this RepliData in its own SMP/E zones. If you want to do the SMP/E work with an existing GLOBAL, target or distribution zone, change the SMP/E commands to agree with the existing zones. (The GLOBAL zone must contain SREL P115.) If an existing zone is used, you usually don t need to run the CRDNQAL1 and CRDNQCSI jobs. If you skip these jobs, make sure that your zones have a DDDEF for SMPLTS defined (required for CALLLIBS support). All other jobs must be run. 1. Make changes as needed to meet your installation standards. 2. Run the RECEIVE job, CRDNQRCV, from the bootstrap JCL library. During the RECEIVE, SMP/E (among other things) reads the install tape and creates SMPTLIB datasets on DASD for subsequent use by APPLY and ACCEPT processing. Expect the RECEIVE to complete with a return code of 0. 2e. Apply the RepliData software 1. The SMP/E feature GIMDTS is used to apply maintenance. This requires extra storage because of the IEBCOPY operation involved. To prevent problems from occurring, use REGION=0M on the JOB/EXEC statement. 2. Make changes as needed to meet your installation standards. 3. Run the APPLY CHECK job, CRDNQAPP, from the bootstrap JCL library. During APPLY CHECK, SMP/E checks that the environment is set up correctly but does not install any software. Expect the APPLY CHECK to complete with a return code of Modify the CRDNQAPP job by removing the CHECK parameter from the APPLY command. This causes SMP/E to install the software from the SMPTLIB datasets into the target libraries, CRD.SCRDxxxx. Chapter 3. 7

22 2f. Accept the RepliData software Expect APPLY to complete with a return code of 0. Investigate all linkedit warnings and error messages. 1. The SMP/E feature GIMDTS is used to ACCEPT maintenance. This requires extra storage because of the IEBCOPY operation involved. To prevent problems from occurring, use REGION=0M on the JOB/EXEC statement. 2. Make changes as needed to meet your installation standards. 3. Run the ACCEPT CHECK job, CRDNQACC, from the bootstrap JCL library. During ACCEPT CHECK, SMP/E checks that the environment is set up correctly but does not accept any software. Expect the ACCEPT CHECK to complete with a return code of Modify the CRDNQACC job by removing the CHECK parameter from the ACCEPT command. This causes SMP/E to install the software from the SMPTLIB datasets into the distribution libraries, CRD.ACRDxxxx. Expect ACCEPT to complete with a return code of Check with the RepliData support group for required, preventive maintenance to be applied during the install process. Follow these guidelines: v v v v No specific SMP/E jobs are supplied to receive or apply maintenance. As maintenance is received, apply it using jobs similar to the APPLY and RECEIVE of the base F25P310 (CRDNQRCV and CRDNQAPP). Modify these jobs to refer to the PTF or APAR SYSMOD-ID instead of the base function, F25P310. Before applying any maintenance, ACCEPT the base function F25P310. Do not change SMP/E-controlled libraries or load modules outside of SMP/E. If you do, you will likely cause errors such as message IEW2611, and may invalidate the SMP/E maintenance of your RepliData installation. For example, SDDLOAD might be copied to SCRDCLNK using TSO SPF 3.3. If you see this message, delete the offending load module and reapply the SYSMOD. If binds are required as part of maintenance, run these after the maintenance is installed. 2g. Allocate the staging libraries (recommended) You may want to keep the SMP/E datasets separate from the datasets used by ongoing jobs and for other install tasks. To do this, you need to allocate staging libraries for the day-to-day execution of RepliData. 1. CRD.BOOTSTRP(CRDNQAL3) creates the staging libraries for the SMP/E installed libraries. If necessary, change the job parameters to reflect your SMP/E high-level qualifier and the high-level qualifier for the desired user staging library. Do not modify the SMP/E data sets outside of SMP/E. These staging libraries insulate the SMP/E install and maintenance from the test/production environment. 2. Submit the job to create the libraries. The staging library (SCRDCLNK) contains the executable CICS RepliData code. 2h. Customize your environment 8 Installation 1. Run the bootstrap job CRDNQTS1 to unload supplied files, to permit initial loading of various RepliData support files. 2. Rerun CRDNQTS1 if you applied maintenance that affects the sample files.

23 This member... CRDSTCMD CRDSTPND CRDSTMSD CRDSTELD CRDSTPED CRDSTPKD CRDDLDCT CRDDLFCT CRDDLGRP CRDDLRCT CRDATCTD CRDATDSD CRDATLVD CRDATLED CRDATPVD Creates this file... CRD.CRDSTCMD.LOAD CRD.CRDSTPND.LOAD CRD.CRDSTMSD.LOAD CRD.CRDSTELD.LOAD CRD.CRDSTPED.LOAD CRD.CRDSTPKD.LOAD CRD.SAMPLE.CICS.CSDFILE(CRDDLDCT) CRD.SAMPLE.CICS.CSDFILE(CRDDLFCT) CRD.SAMPLE.CICS.CSDFILE(CRDDLGRP) CRD.SAMPLE.CICS.CSDFILE(CRDDLRCT) CRD.CRDATCTD.LOAD CRD.CRDATDSD.LOAD CRD.CRDATLVD.LOAD CRD.CRDATLED.LOAD CRD.CRDATPVD.LOAD The installation of RepliData is complete. Chapter 3. 9

24 10 Installation

25 Chapter 4. Step 3. Customize the install libraries 3a. Copy the distribution libraries 1. Copy the distribution libraries to use target libraries, including the CICS execution libraries. 2. Modify the job CRD.BOOTSTRP(CRDNQAL3) to reflect your installation, and run it. This will copy the SMP/E install target libraries to user libraries. This copy of the SCRDCLNK library is the CICS execution library for RepliData. 3. Add this user library to the CICS execution libraries for RepliData. 3b. Create files needed for CICS set-up Run the job CRD.BOOTSTRP(CRDNQTS1) to create the files that will be required later to load tables and perform the CICS set-up of RepliData. 3c. Prepare the concatenation CLIST The RepliData installation CLIST produces customized JCL to be used later to install RepliData into a CICS/DB2 environment. No sample JCL is provided unless specifically noted. Many sample source members for binds, DDLs and other items are found in CRD.SCRDSAMP and referred to in later steps. To run the RepliData installation CLIST, you must make the RepliData ISPF libraries available by concatenating them with your site-specific ISPF libraries. To do this: 1. Determine whether your site has the CONCATD command in the ISPF link-list libraries: v If you do, execute ALOCINST with the correct parameters to reconcatenate your ISPF libraries to include the RepliData required datasets: ALOCINST p1 p2 where: p1 The high-level qualifier of copied datasets. The default is CRD.TEST. p2 An optional high-level qualifier in ISPPROF file p2.ispprof. The default is the current TSO user ID appended with.. v For example, execute ALOCINST CRD.TEST. HCM.PRIVATE if the defaults are unacceptable, the ISPF distribution library was copied to CRD.TEST.SCRDISPF, and the user s ISPPRFO is HCM.PRIVATE.ISPPRFO. If your site doesn t have CONCATD: a. Use a REXX exec or CLIST that uses the ALLOCATE command. The ALLOCATE command needs the library names containing your site s ISPF panels (ISPPLIB), skeletons (ISPSLIB), messages (ISPMLIB), CLISTs (SYSPROC), and tables (ISPTLIB). These items are site-dependent. b. To concatenate existing libraries, put the library names in the list of names in parentheses after DSN. The RepliData library, SCRDISPF, must be the first name in the DSN list. Copyright IBM Corp. 1993,

26 In the ALLOCATE sample shown below, the PROFILE command is used to show all error messages. In the sample, change CRD to the prefix that was used to copy the RepliData distribution files to user files in job CRDNXAL3. Change Profile to the user ID of the installer to link the ISPPROF profile library to the table input library ISPTLIB. The library list at your site may be different from the sample. Sample: /* REXX EXEC 3d. Run the concatenation CLIST "PROFILE WTP MSGID" "ALLOCATE DDNAME(ISPPLIB) DSN( CRD.SCRDISPF, SYS1.SISPPENU, SYS1.SISFPLIB, SYS1.SGIMPENU, SYS1.SBPXPENU ) SHR REUSE"; "ALLOCATE DDNAME(ISPMLIB) DSN( CRD.SCRDISPF, SYS1.SISPMENU, SYS1.SISFMLIB, SYS1.SGIMMENU, SYS1.SBPXMENU ) SHR REUSE"; "ALLOCATE DDNAME(ISPSLIB) DSN( CRD.SCRDISPF, SYS1.SISPSENU SYS1.SISPSLIB, SYS1.DGTSLIB, SYS1.SGIMSENU ) SHR REUSE"; "ALLOCATE DDNAME(ISPTLIB) DSN( Profile.ISPPROF, SYS1.SISPTENU, SYS1.SISFTLIB, SYS1.SGIMTENU, SYS1.OTABLES ) SHR REUSE"; 1. Do one of the following: v Copy the ALOCINST member into the CLIST library of the installer. For example, if the installer s TSO user id is XYZ123, copy CRD.SCRDISPF(ALOCINST) into XYZ123.CLIST(ALOCINST). v If you used the ALLOCATE method, copy the new ALOCINST member into the installer s CLIST library. 2. Log on to TSO as the installer. 3. At the READY prompt, execute the concatenation job ALOCINST: EXEC (ALOCINST) 3e. Define the environment and dataset names 1. Invoke ISPF. 2. Select the Command option from the ISPF Primary Option Menu. 3. Enter RINSTALL prefix to start the CLIST. prefix is the high-level qualifier that was used to copy the RepliData distribution tape. To do this, you ust be authorized to create datasets with the prefix high-level qualifier. You see the RepliData Installation Main Panel: 12 Installation

27 RepliData Installation Main Panel Option ===> Type one of the entries below on the OPTION line and press Enter. 1 Define RepliData Environment 2 Build Customized JCL 3 Exit F1=Help F3=Exit F12=Cancel Figure 2. RepliData Installation Main Panel 4. Enter 1. You see the RepliData Environment Definition panel: RepliData Environment Definition Option ===> Type one of the entries below on the OPTION line and press Enter. 1 Define MVS Environment 2 Define Replication Links 3 Define CICS Environment 4 Define DB2 Environment 5 Define RepliData Parameters 6 Exit F1=Help F3=Exit F12=Cancel Figure 3. RepliData Environment Definition Panel 5. On the Option line, enter 1 to define the MVS environment. You see the RepliData MVS Environment Definition panel: Chapter 4. 13

28 RepliData MVS Environment Definition Command ===> Job Card => => => => RepliData Distribution Prefix RepliData Prefix for Temp Datasets MVS Macro Library CICS System Library Prefix PL/I System Library Prefix CICS RepliData Prefix CICS CSD File CICS VSAM Prefix DB2 System Library Prefix MQSeries Library Prefix ===> ===> ===> SYS1.MACLIB ===> ===> SYS1.PLI ===> ===> ===> ===> ===> Log Analysis Parameters: DELAYINT =>00001 MSGQNAM =>SDMN SDDTRAN =>SDL1 OWNERID =>XXXX COMFNAM =>SDDLCOM JCLFNAM =>SDDLJCL DATE=>U F1=Help F3=Exit F12=Cancel Figure 4. RepliData MVS Environment Definition Panel 6. Fill in every field: Job Card The Standard Job Card information. Line 1 is required. There can be up to 4 lines of Job Card information. The first 2 characters of each line must be //. Also, lines 2-4must contain a space after the //. For example, for a two-line job card: //job_name JOB (account_number,account_info),class=x, // NOTIFY=user_id RepliData Distribution Prefix The high-level qualifier assigned to the data sets that were unloaded from the RepliData Distribution tape. RepliData Prefix for Temp Datasets The high-level qualifier to be used for temporary data sets generated during the installation. This name can be the same as RepliData Distribution prefix MVS Macro Library The name of the system assembler macro library. The default is SYS1.MACLIB. CICS System Library Prefix The library name used for CICS compile and link-edit routines such as SDFHLOAD. PL/I System Library Prefix The name of the PL/I system library. The default is SYS1.PLI. CICS RepliData Prefix The high-level qualifier that identifies the specific CICS system on which RepliData will be installed. This is the library into which 14 Installation

29 system-specific modules will be linked (SDDLGT3 and SYSNODTB). It is also the recommended DFHRPL library for the user DAP programs. CICS CSD File The data set name used for the CICS CSD file. CICS VSAM Prefix The high-level qualifier to be used upon generation of the RepliData VSAM files. DB2 System Library Prefix The system library name for DB2. MQSeries Library Prefix The system library name for MQSeries. Log Analysis Parameters DELAYINT The number of seconds for the Change Capture program to wait. The default is MSGQNAM The name of the TDQ that error messages are written to. The default is SDMN. SDDTRAN The transaction invoked during CICS PLT PT processing. The default is SDL1. OWNERID The owner ID that is passed to the instrumentation facility. The default is XXXX. COMFNAM The name of the VSAM file that is used to: v Contain an image of state memory as of the last SYNCPOINT. v Communicate between the CICS and log analysis programs. The default is SDDLCOM. JCLFNAM The VSAM file used by the Change Capture program to start SDDLOGW. The default is SDDLJCL. DATE The date format, either E for Europe (dd/mm/yyyy), or U for USA (mm/dd/yyyy). The default is U. 7. Press PF3 to save your changes. You see the RepliData Environment Definition panel again (Figure 3 on page 13). 8. Enter 2 to define the replication links. You see the RepliData Replication Links Definition panel: Chapter 4. 15

30 RepliData Replication Links Definition Command ===> CICS CICS SYSID Node Name DB2 Name SYSID Node Name DB2 Name F1=Help F3=Exit F12=Cancel Figure 5. RepliData Replication Links Definition Panel 9. Fill in each field: CICS SYSID The 4-character name to identify a specific CICS system on which RepliData is being installed. Node Name A user-friendly name given for each location. The name may contain up to 8 characters. DB2 Name An 8-character name to identify a physical database share group. Notes: a. There must be at least two replication links defined. b. Both the Node Name and the CICS SYSID are used when searching this table. Therefore, both should be unique. 10. Press PF3 to save your changes. You see the RepliData Environment Definition panel again (Figure 3 on page 13). 11. Enter 3 to define the CICS environment. You see the RepliData Environment Table panel (Figure 9 on page 21), which lists the CICS environments that have already been defined. At this point, however, the table should be empty. 12. On the Command line, type S newid, where newid is a unique 4-character name to identify the CICS system. 13. Press Enter. You see the CICS Environment Definition panel: 16 Installation

31 RepliData CICS Environment Definition Command ===> CICS SYSID Related DB2 Subsystem Related MQSeries Subsystem ===> ===> ===> CICS RepliData Loadlib ===> CICS System Definition (CSD) ===> CICS VSAM Library Prefix ===> CICS BDAM Library Prefix ===> Prefix for Apply Program Generation ===> Volume for Index dataset allocation Volume for Data dataset allocation ===> ===> F1=Help F3=Exit F12=Cancel Figure 6. RepliData CICS Environment Definition Panel 14. Fill in every field: CICS SYSID A 4-character name to identify a specific CICS system on which RepliData is being installed. Related DB2 Subsystem The DB2 subsystem attached to this CICS system. Related MQSeries Subsystem The MQ Manager attached to this CICS system. CICS RepliData Loadlib The library name for RepliData specific code and apply programs in the CICS DFHRPL. CICS System Definition (CSD) The data set name used for the CICS CSD file. CICS VSAM Library Prefix This is the high-level qualifier used for generation of the RepliData VSAM files. CICS BDAM Library Prefix This is the high-level qualifier used for generation of the RepliData BDAM files. Prefix for Apply Program Generation The high-level qualifier used for generation of SOURCE, MACLIB, DBRMLIB, and LOADLIB. Volume for Index dataset allocation The volume where the generated VSAM files will reside. Volume for Data dataset allocation The volume where the generated VSAM files will reside. 15. Press PF3 to save your changes. You see the RepliData Environment Definition panel again (Figure 3 on page 13). 16. Do one of the following: v To define another CICS environment: a. Enter 3. You see the RepliData Environment Table panel again (Figure 9 on page 21). The environment that you just defined should be listed. Chapter 4. 17

32 b. On the Command line, type S newid, where newid is a unique 4-character name to identify the next CICS system you want to define. (To copy an existing environment, type C in the LINE CMD field. To delete an environment, enter D in the LINE CMD field.) c. Press Enter. You see the RepliData CICS Environment Definition panel again (Figure 6 on page 17). Fill in the fields for the next CICS environment and press PF3 to save your changes. d. Repeat this part of the process until all CICS environments are defined. v Otherwise, go to the next step. 17. Enter 4 to define the DB2 environment. You see the RepliData Environment Table panel (Figure 9 on page 21), which lists the DB2 environments that have already been defined. At this point, however, the table should be empty. 18. On the Command line, type S newid, where newid is a unique 4-character name to identify the DB2 system. 19. Press Enter. You see the RepliData DB2 Environment Definition panel: RepliData DB2 Environment Definition Command ===> DB2 Subsystem DB2 Data Sharing Group Name DB2 System Library DB2 Bootstrap Dataset ==> ==> ==> ==> SQLID for DB2 Grant ==> REPLI Storage Group: REPLISTG Volume(s) ==> VCAT ==> ==> Are any of the replicated tables compressed? ==> N APF-Authorized Library ==> F1=Help F3=Exit F12=Cancel Figure 7. RepliData DB2 Environment Definition Panel 20. Fill in each field: DB2 Subsystem A 4-character name to identify a specific DB2 on which RepliData is being installed. DB2 Data Sharing Group Name The 4-character name of the DB2 data sharing group. DB2 System Library The high-level qualifier for the DB2 system load library (SDSNLOAD). DB2 Bootstrap Dataset The name of the bootstrap data set associated with this DB2 subsystem. SQLID for DB2 Grant The primary authorization id. Storage Group REPLISTG parameters: 18 Installation

33 Volume If SMS is used, enter * in this field. Otherwise, enter the volume(s) for the storage group. VCAT The VSAM catalog name. Are any of the replicated tables compressed? If DB2 decompression is used, enter the value Y. APF-Authorized Library The library used for the RepliData DB2 decompression program SDDREAD. This library is only referenced when DB2 decompression is used. 21. Press PF3 to save your changes. You see the RepliData Environment Definition panel again (Figure 3 on page 13). 22. Do one of the following: v To define another DB2 environment: a. Enter 4. You see the RepliData Environment Table panel (Figure 9 on page 21), which lists the DB2 environments that have already been defined. b. On the Command line, type S newid, where newid is a unique 4-character name to identify the DB2 system. (To copy an existing environment, type C in the LINE CMD field. To delete an environment, enter D in the LINE CMD field.) c. Press Enter. You see the RepliData DB2 Environment Definition panel again (Figure 7 on page 18). Fill in the fields for the next DB2 environment and press PF3 to save your changes. d. Repeat this part of the process until all DB2 environments are defined. v Otherwise, go to the next step. 23. Enter 5 to enter values for parameters in the PARMDRVR dataset. You see the RepliData Parameter Definition panel: Chapter 4. 19

34 3f. Build the customized JCL RepliData Parameter Definition Command ==> SDD entries SDDTYPE ===>M DB2SSNM ===> EXCLUDEPL ===> GMTO ===>000 GMTTO ===>_ LOGPLAN ===>CRDDPLAN MQMGR ===> NUMLOGK ===>010 NUMXMITQ ===>001 RCVRALTSY ===> RCVRDELAY ===>001 RCVRRCRDR ===>N RCVRFREQU ===>025 RCVRLIMIT ===>001 RCVRMAXDE ===>001 RCVRSHUTC ===>001 RCVRTHRES ===>025 SDDRTRY1C ===>04 SDDRTRY1T ===>0015 SDDRTRY2C ===>04 SDDRTRY2T ===>0200 URLISTMAX ===>1000 URLISTSIZ ===>1000 WL-TDQ-AC ===>_ WL-TDQ-FI ===> WL-TDQ-NA ===> WL-TDQ-RU ===> SDD visibility entries SDDHEART ===>_ SDDMSGS ===>_ Status Monitor and Statistics Writer entries LOGLATENC ===> MONEMSGTY ===>_ MONIMSGTY ===>_ MONINTERV ===> MONPRISYS ===> RECEIVEPK ===> SDLUINTV ===> SDLUTRAN ===> STATINTRV ===> TRANSMITP ===> F1=Help F3=Exit F12=Cancel Figure 8. RepliData Parameter Definition Panel This panel lists a minimal set of parameters with their defaults (If a value is not provided for a parameter, it is not implemented in PARMDRVR.) 24. Check the value for the SDDTYPE parameter, and correct it if necessary to indicate the correct system configuration type: Valid values are: M For primary location updates only (the default) P For peer-to-peer updates T For tabel-level peer-to-peer updates 25. Check the values for the other parameters, if you want. (You ll have another chance later to change the PARMDRVR dataset.) For a detailed description of the PARMDRVR dataset, see the RepliData Administration book. 26. Press PF3 to save your changes. You see the RepliData Environment Definition panel again (Figure 3 on page 13). 27. Press PF3 again. You see the RepliData Installation Main Panel again (Figure 2 on page 13). 28. Go to the next step to build the customized JCL. 1. Make sure you are viewing the RepliData Installation Main Panel. (See the beginning of the previous step if you are not.) 2. Enter 2. You see the RepliData Environment Table panel (Figure 9 on page 21): 20 Installation

35 RepliData Environment Table Command ===>, LINE CMD CICS Related DB2 Related MQ. wxyz db01 mq01 ******************************* Bottom of data ******************************* F1=Help F3=Exit F12=Cancel Figure 9. RepliData Environment Table Panel 3. Type S next to the CICS system ID for which you want to build the customized JCL. Then press Enter. 4. As the customization process starts, you see this message: BEGINNING EDITED DATA SET OUTPUT As each member is processed, you see this message: CLIST EDITING MEMBER membername When all JCL has been processed, you see this message: ALL MEMBERS HAVE BEEN PROCESSED The CLIST produces the customized JCL for each member based on the values entered on the environment definition panels. The customization process creates: v A new member for each installation job in the data set prefix.cicsxxxx.jcl v Members in a source data set called prefix.cicsxxxx.source. v Member REPLILGC in data set prefix.cicsxxxx.proclib. (Where prefix is the distribution high-level qualifier and xxxx is the CICS system ID that was selected for customization processing.) 5. Repeat this process for each CICS environment. Chapter 4. 21

36 22 Installation

37 Chapter 5. Step 4. Select the processing options 1. Review the default settings related to Change Capture, as shown in Table 1 and Table 2. Table 1. Change Capture default settings Change Capture Setting Transaction ID Error message TDQ FCT names Default SDL1 SDMN SDDLJCL SDDLCOM SDDLDATA Table 2. Change Capture parameters Parameter Default Value Description DELAYINT AL2(00001) The number of seconds for the Change Capture program to wait after it has processed all VSAM control intervals (CIs) in the DB2 active log. The program then restarts and processes the CIs that were created during the interval. OWNERID CL4 XXXX The owner ID that is passed to the instrumentation facility in the IFCA control block. MSGQNAM CL4 SDMN The name of the TDQ to which error messages are written. RepliData error messages go to the SDMN TDQ. If you want Change Capture-specific error messages to go to another TDQ, you can change this parameter. COMFNAM CL8 SDDLCOM The name of the VSAM file that is used to: v Contain the restart RBA as of the last SYNCPOINT taken by the Change Capture programs. v Communicate between the CICS application and the batch program when the Change Capture programs need to invoke the batch program that retrieves DB2 archive log data. DATAFNAM CL8 SDDLDATA The name of the VSAM file used by the batch program that processes the archive log to pass back, to CICS, the requested blocks of log data from the archive. Copyright IBM Corp. 1993,

38 Table 2. Change Capture parameters (continued) Parameter Default Value Description JCLFNAM CL8 SDDLJCL The name of the VSAM file used by the Change Capture programs to read JCL that starts the SDDLOGW or SDDREAD program. The Change Capture programs read the JCL from this file and schedule the job by writing the JCL to the Internal Reader. SDDTRAN CL4 SDL1 The name of the CICS transaction that is invoked during CICS PLT PT processing to start SDD distribution. DATESTYL CL1 U The style used for reporting dates: E indicates Europe (dd/mm/yyyy), U indicates USA (mm/dd/yyyy). IGNERROR CL1 Y A flag used by Change Capture to determine whether or not errors are to be ignored. If set to N, Change Capture terminates after finding an inconsistency in the log data. If this flag is set to Y, then inconsistencies are reported but Change Capture processing continues. DO_SQL CL1 N Used by RepliData to determine whether tokenized SQL should be produced. Tokenized SQL is produced if set to Y. No tokenized SQL is created if any other value is used. This value must be changed prior to initializing RepliData. RepliData Log Read should be quiesced before changing this value. Changing it after RepliData has been initialized will have no effect on Change Capture operation. SHADOWN CL1 Flag used to determine the owner of the shadow tables: v v If the parameter is set to R, the owner is assumed to be REPLI. If it is set to any other value, the owner is assumed to be the same as the owner of the table to which the shadow table is related. 2. Decide whether you want to change any of the defaults: v If you don t, execute the JCL job ASMLGT3. This memeber is generated by the installation CLIST into library prefix.cicsxxxx.jcl. Then go to Step 5. Update the CICS PLT start-up and shut-down lists on page 27. v If you do want to change one or more of the defaults, go to the next step. 3. Make your changes in SDDLGT3, sample source code that was generated in the RepliData ISPF install utility. It can be found in prefix.cicsxxxx.source(sddlgt3). Attention: Do not delete any of parameters. 4. Assemble and link-edit the object This generated member ASMLGT3 into prefix.cicsxxxx.jcl. 24 Installation

39 5. If you move the SDDLGT3 member to a different source library, change ASMLGT3 to point to the correct SDDLGT3 member. 6. Execute the JCL job ASMLGT3. 7. If you changed a default in Table 1 on page 23, remember to use your own value as you go through the rest of the installation process, Chapter 5. 25

40 26 Installation

41 Chapter 6. Step 5. Update the CICS PLT start-up and shut-down lists 1. Add RepliData entries to the CICS Program Load Table (PLT) start-up list. Sample entries are provided in CRD.SCRDSAMP. Member CRDDLPPI contains PLTPI table entries. The following PLT entries are for RepliData initialization. The entries are in the required order. Note: These entries should be placed after the entry in your current PLTPI list that specifies PROGRAM=DFHDELIM. That is, these programs should be executed during the third stage of initialization. DFHPLT TYPE=ENTRY, PROGRAM=SYSPLTP2 /* ITI Program Loading */ DFHPLT TYPE=ENTRY, PROGRAM=SYSITII /* ITI Table Initialization */ DFHPLT TYPE=ENTRY, PROGRAM=SDDPLT /* SDD PLT Initialization */ DFHPLT TYPE=ENTRY, PROGRAM=SYSEPLT /* ELF PLT Module */ DFHPLT TYPE=ENTRY, PROGRAM=DIAPLTPI /* DIALOG Table */ /* Initialization and */ /* Program Loading */ DFHPLT TYPE=ENTRY, PROGRAM=SDDLSTR /* ANALOG Start */ 2. Add RepliData entries to the CICS PLT shutdown list. Sample entries are provided in CRD.SCRDSAMP. Member CRDDLPSD contains PLTSD table entries. These entries should be placed before the entry in your current PLTSD list that specifies PROGRAM=DFHDELIM. That is, these programs should be executed during the first quiesce stage of shutdown. These entries should also be placed before the entry for DB2 Attach shutdown. DFHPLT TYPE=ENTRY, /* ANALOG auditing to */ PROGRAM=SDDLSTP /* stop for CICS */ /* shutdown processing */ 3. Assemble the lists. Copyright IBM Corp. 1993,