IBM Program Directory for InfoSphere Data eplication for DB2 for z/os V10.02.01 Program Number 5655-DP for use with z/os HCHCA21 - Service Updated 31 July 2015 Document Date: October 2015 GI10-8941-02
Note Before using this information and the product it supports, be sure to read the general information under 7.0, Notices on page 35. Copyright International Business Machines Corporation 1998, 2015. US Government Users estricted ights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents 1.0 Introduction................................................... 1 1.1 InfoSphere Data eplication Description................................... 1 1.2 InfoSphere Data eplication FMIDs...................................... 4 2.0 Program Materials............................................... 5 2.1 Basic Machine-eadable Material....................................... 5 2.2 Optional Machine-eadable Material..................................... 7 2.3 Program Publications.............................................. 8 2.3.1 Optional Program Publications...................................... 8 2.4 Program Source Materials........................................... 8 2.5 Publications Useful During Installation.................................... 8 3.0 Program Support............................................... 10 3.1 Program Services............................................... 10 3.2 Preventive Service Planning......................................... 10 3.3 Statement of Support Procedures...................................... 11 4.0 Program and Service Level Information................................. 12 4.1 Program Level Information.......................................... 12 4.2 Service Level Information........................................... 12 5.0 Installation equirements and Considerations............................. 14 5.1 Driving System equirements........................................ 14 5.1.1 Machine equirements......................................... 14 5.1.2 Programming equirements...................................... 14 5.2 Target System equirements........................................ 15 5.2.1 Machine equirements......................................... 15 5.2.2 Programming equirements...................................... 15 5.2.2.1 Installation equisites....................................... 15 5.2.2.2 Operational equisites....................................... 16 5.2.2.3 Toleration/Coexistence equisites................................ 17 5.2.2.4 Incompatibility (Negative) equisites............................... 17 5.2.3 DASD Storage equirements...................................... 17 5.3 FMIDs Deleted................................................. 22 5.4 Special Considerations............................................ 22 6.0 Installation Instructions........................................... 23 6.1 Installing InfoSphere Data eplication................................... 23 6.1.1 SMP/ Considerations for Installing InfoSphere Data eplication................. 23 6.1.2 SMP/ Options Subentry Values.................................... 23 6.1.3 SMP/ CALLLIBS Processing..................................... 24 6.1.4 Sample Jobs............................................... 24 Copyright IBM Corp. 1998, 2015 iii
6.1.5 Allocate SMP/ CSI (Optional)..................................... 27 6.1.6 Initialize CSI zones (Optional)..................................... 28 6.1.7 Perform SMP/ CIV........................................ 28 6.1.8 Allocate, create and mount ZFS Files (Optional)........................... 28 6.1.9 Allocate SMP/ Target and Distribution Libraries.......................... 29 6.1.10 Allocate File system Paths....................................... 29 6.1.11 Create DDDF ntries......................................... 30 6.1.12 Perform SMP/ APPLY........................................ 30 6.1.13 Perform SMP/ ACCPT....................................... 32 6.1.14 un POT COSSZON..................................... 33 6.2 Activating the Change Data Capture feature of InfoSphere Data eplication............. 33 6.2.1 File System xecution.......................................... 33 6.3 Activating the Q and SQL eplication feature of InfoSphere Data eplication............ 33 6.3.1 File System xecution.......................................... 34 7.0 Notices..................................................... 35 7.1 Trademarks................................................... 36 eader's Comments................................................ 37 Figures 1. Program File Content for HCHCA21................................... 5 2. Program File Content for HAAWA21................................... 6 3. Program File Content for JAAWA24.................................... 6 4. Program File Content for JAAWA25.................................... 7 5. Program File Content for JAAWA26.................................... 7 6. Basic Material: Unlicensed......................................... 8 7. Publications Useful During Installation.................................. 8 8. PSP Upgrade and Subset ID........................................ 10 9. Component IDs............................................... 11 10. Driving System Software equirements................................. 15 11. Target System Mandatory Installation equisites............................ 15 12. Target System Mandatory Operational equisites........................... 16 13. Target System Conditional Operational equisites........................... 17 14. Total DASD Space equired by InfoSphere Data eplication..................... 17 15. Storage equirements for the Change Data Capture feature Target Libraries........... 19 16. Storage equirements for the Q and SQL eplication feature Target Libraries........... 20 17. Change Data Capture feature File System Paths............................ 20 18. Q and SQL eplication feature File System Paths........................... 20 19. Storage equirements for the Change Data Capture feature Distribution Libraries......... 21 20. Storage equirements for Q and SQL eplication feature Distribution Libraries.......... 22 iv InfoSphere Data eplication Program Directory
21. SMP/ Options Subentry Values..................................... 23 22. Sample Installation Jobs for the Change Data Capture feature.................... 24 23. Sample Installation Jobs for the Q and SQL eplication feature................... 25 Figures v
vi InfoSphere Data eplication Program Directory
1.0 Introduction This program directory is intended for system programmers who are responsible for program installation and maintenance. It contains information about the material and procedures associated with the installation of InfoSphere Data eplication for DB2 for z/os. This publication refers to InfoSphere Data eplication for DB2 for z/os as InfoSphere Data eplication. The Program Directory contains the following sections: 2.0, Program Materials on page 5 identifies the basic program materials and documentation for InfoSphere Data eplication. 3.0, Program Support on page 10 describes the IBM support available for InfoSphere Data eplication. 4.0, Program and Service Level Information on page 12 lists the APAs (program level) and PTFs (service level) that have been incorporated into InfoSphere Data eplication. 5.0, Installation equirements and Considerations on page 14 identifies the resources and considerations that are required for installing and using InfoSphere Data eplication. 6.0, Installation Instructions on page 23 provides detailed installation instructions for InfoSphere Data eplication. It also describes the procedures for activating the functions of InfoSphere Data eplication, or refers to appropriate publications. Before installing InfoSphere Data eplication, read the CBPDO Memo To Users and the CBPDO Memo To Users xtension that are supplied with this program in softcopy format and this Program Directory; then keep them for future reference. Section 3.2, Preventive Service Planning on page 10 tells you how to find any updates to the information and procedures in this Program Directory. InfoSphere Data eplication is supplied in a Custom-Built Product Delivery Offering (CBPDO, 5751-CS3). The Program Directory that is provided in softcopy format on the CBPDO tape is identical to the hardcopy format if one was included with your order. All service and HOLDDATA for InfoSphere Data eplication are included on the CBPDO tape. Do not use this program directory if you install InfoSphere Data eplication with a SystemPac or ServerPac. When you use one of those offerings, use the jobs and documentation supplied with the offering. The offering will point you to specific sections of this program directory as needed. 1.1 InfoSphere Data eplication Description Key capabilities available in IBM InfoSphere Data eplication for DB2 for z/os, V10.2.1 include: Change Data Capture provides heterogeneous data replication solutions for Oracle, DB2, InfoSphere DataStage, and more. Copyright IBM Corp. 1998, 2015 1
Features: High performance: InfoSphere Change Data Capture is designed to scale to high-volume replication environments with minimal performance impact on source databases. Using native log-based change data capture, it can handle increasing volumes of data to provide data integration at the pace of business. Log-based change data capture: Whether data is integrated periodically or in real time, only changed data is captured and transferred from source to target systems. Instead of performing queries directly against the database, InfoSphere Change Data Capture captures changed data directly from the database logs. Operational efficiency: InfoSphere Change Data Capture helps improve operational efficiency and save time and resources by eliminating redundant data transfer and saving network bandwidth. By accessing data from the logs, InfoSphere Change Data Capture helps reduce performance impact on mission-critical applications. Data integrity: Data delivery is accomplished by synchronizing positional information between the source and target. Transactional integrity is achieved by applying transactions on the target in the same order as on the source. ase of use: An intuitive user interface helps lower total cost of ownership by consolidating configuration and monitoring of the replication environment. Zero programming: With zero programming required, you can invest your effort in higher-value IT projects. Your company can leverage its legacy systems and integrate data across all supported platforms with few changes to the existing environment. Future changes in the computing environment can also be accommodated to protect your company's investment. Programming-free data integration: InfoSphere Change Data Capture offers out-of-the-box, programming-free data integration with DB2, Oracle, Sybase, and Informix Dynamic Server across various operating platforms. Data-enriched business events: InfoSphere Change Data Capture facilitates integration with message queues to supply data-enriched business events to business applications. nhanced data integration: InfoSphere Change Data Capture supports flat file integration to improve your ability to consolidate data across systems. New pipeline apply for DB2/Z DB2 Temporal Table support IFI filtering in DB2 for z/os, V11 Support for DB2 for z/os, V11 2 InfoSphere Data eplication Program Directory
Q eplication provides low-latency, high-throughput data replication with managed conflict detection and resolution to support business continuity, workload distribution, high availability, and active/active solutions for DB2, including those involving DB2 for z/os, V10. Features: Log-based change data capture: InfoSphere eplication Server captures changed data directly from the database logs. By accessing data from the logs, the impact on mission-critical applications is significantly reduced. High performance: Committed changes are published to WebSphere MQ message queues. A sophisticated, parallel apply engine determines transaction dependencies and replays transactions on target systems to optimize throughput and significantly reduce latency. Data integrity: Committed changes are published to WebSphere MQ message for ease of recovery during failover and switchback scenarios. Independent transactions are applied and committed in parallel, significantly reducing the chance of stranded data in high availability solutions. Workload balancing: Conflict detection and resolution algorithms allow backup systems to do productive work so application workloads can be distributed across multiple servers. Operational efficiency: With InfoSphere eplication Server, data can be filtered so only the data of interest is replicated. This can help improve operational efficiency and save time and resources by eliminating redundant data transfer and saving network bandwidth. Target loading: Automatic and high-performance load options are integrated. Because the work is "parallelized," target data can be loaded at the same time changed data is being replicated. SLA and performance monitoring: xtensive statistical data is made available for all replication activity. This helps address the needs of monitoring and service level agreements and is highly accessible through SQL and a browser-based user interface. Data verification and repair: Utilities are able to compare whole or partial source and target table contents, providing a list of differences that can be used to make modifications to either table. Scripted setup: In addition to a user interface, InfoSphere eplication Server provides a command-line processor that allows easy use of scripts to create and modify data replication configurations. IFI filtering in DB2 for z/os, V11 Support for DB2 for z/os, V11 Data vent Publishing facilitates business integration by linking changed-data events with business processes. Changed-data events are captured and published as WebSphere MQ messages that can be Introduction 3
used by other applications and tools to drive subsequent processing. Changed data can be encoded as an XML document or in delimited format such as comma-separated values. InfoSphere Data vent Publisher delivers efficient changed-data solutions for the following types of business scenarios: Application-to-application: Changes to operational customer data can be pushed to a customer relationship management (CM) application. Business process initiation: Adding a customer record can initiate new workflow that might include a welcome email, credit verification, and an update to the CM system. Critical data event monitoring: Changed-data event monitoring allows events such as low inventory levels to be used to initiate related processes such as product restocking. Data population: Data changes in operational systems can be fed to extract, transform, and load (TL) products that then populate a data warehouse, datamart, or operational data store. All InfoSphere Data vent Publisher function is also found in InfoSphere eplication Server. 1.2 InfoSphere Data eplication FMIDs InfoSphere Data eplication consists of the following FMIDs: HCHCA21 - Change Data Capture HAAWA21 - Q and SQL eplication Common Base JAAWA24 - Q Capture and P JAAWA25 - Q Apply JAAWA26 - SQL eplication The Change Data Capture feature consists of the following FMID: HCHCA21 The Q and SQL eplication feature consists of the following FMIDs: HAAWA21 JAAWA24 JAAWA25 JAAWA26 4 InfoSphere Data eplication Program Directory
2.0 Program Materials An IBM program is identified by a program number and a feature number. The program number for InfoSphere Data eplication is 5655-DP and its feature numbers are 5812, and 5801. Basic Machine-eadable Materials are materials that are supplied under the base license and feature numbers, and are required for the use of the product. The program announcement material describes the features supported by InfoSphere Data eplication. Ask your IBM representative for this information if you have not already received a copy. 2.1 Basic Machine-eadable Material The distribution medium for this program is physical media or downloadable files. This program is in SMP/ LFIL format and is installed by using SMP/. See 6.0, Installation Instructions on page 23 for more information about how to install the program. You can find information about the physical media for the basic machine-readable materials for InfoSphere Data eplication in the CBPDO Memo To Users xtension. Figure 1, Figure 2 on page 6, Figure 3 on page 6, Figure 4 on page 7, and Figure 5 on page 7 describes the program file content for InfoSphere Data eplication. You can refer to the CBPDO Memo To Users xtension to see where the files reside on the tape. Notes: 1. The data set attributes in this table must be used in the JCL of jobs that read the data sets. However, because the data sets are in IBCOPY unloaded format, their actual attributes might be different. 2. If any LFILs are identified as PDSs, ensure that SMPTLIB data sets are allocated as PDSs. Figure 1 (Page 1 of 2). Program File Content for HCHCA21 Name SMPMCS SQ FB 80 6400 IBM.HCHCA21.F1 PDS FB 80 8800 IBM.HCHCA21.F2 PDS U 0 6144 IBM.HCHCA21.F3 PDS FB 80 8800 IBM.HCHCA21.F4 PDS FB 80 8800 IBM.HCHCA21.F5 PDS FB 80 8800 O G C F M L C L BLK SIZ Copyright IBM Corp. 1998, 2015 5
Figure 1 (Page 2 of 2). Program File Content for HCHCA21 Name IBM.HCHCA21.F6 PDS FB 80 8800 IBM.HCHCA21.F7 PDS FB 80 8800 IBM.HCHCA21.F8 PDS VB 255 8800 IBM.HCHCA21.F9 PDS VB 255 8800 IBM.HCHCA21.F10 PDS FB 80 8800 IBM.HCHCA21.F11 PDS VB 255 8800 IBM.HCHCA21.F12 PDS VB 137 8800 O G C F M L C L BLK SIZ IBM.HCHCA21.F13 PDS VB 255 27998 Figure 2. Program File Content for HAAWA21 Name SMPMCS SQ FB 80 6400 IBM.HAAWA21.F1 PDS FB 80 8800 IBM.HAAWA21.F2 PDS FB 80 8800 IBM.HAAWA21.F3 PDS U 0 6144 O G C F M L C L BLK SIZ IBM.HAAWA21.F4 PDS VB 256 27920 IBM.HAAWA21.F5 PDS FB 80 8800 IBM.HAAWA21.F6 PDS FB 80 8800 IBM.HAAWA21.F7 PDS VB 256 27920 Figure 3 (Page 1 of 2). Program File Content for JAAWA24 Name SMPMCS SQ FB 80 6400 IBM.JAAWA24.F1 PDS FB 80 8800 O G C F M L C L BLK SIZ 6 InfoSphere Data eplication Program Directory
Figure 3 (Page 2 of 2). Program File Content for JAAWA24 Name IBM.JAAWA24.F2 PDS U 0 6144 O G C F M L C L BLK SIZ Figure 4. Program File Content for JAAWA25 Name SMPMCS SQ FB 80 6400 IBM.JAAWA25.F1 PDS FB 80 8800 IBM.JAAWA25.F2 PDS FB 80 8800 IBM.JAAWA25.F3 PDS U 0 6144 O G C F M L C L BLK SIZ Figure 5. Program File Content for JAAWA26 Name SMPMCS SQ FB 80 6400 IBM.JAAWA26.F1 PDS FB 80 8800 IBM.JAAWA26.F2 PDS FB 80 8800 IBM.JAAWA26.F3 PDS U 0 6144 O G C F M L C L BLK SIZ 2.2 Optional Machine-eadable Material No optional machine-readable materials are provided for InfoSphere Data eplication. Program Materials 7
2.3 Program Publications The following sections identify the basic publications for InfoSphere Data eplication. Figure 6 on page 8 identifies the basic unlicensed publications for InfoSphere Data eplication. Publications can be accessed at the IBM Publications Center website at http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss Figure 6. Basic Material: Unlicensed Publication Title InfoSphere Data eplication for DB2 for z/os License Information InfoSphere Data eplication for DB2 for z/os Program Directory InfoSphere Data eplication User's Guide eplication and vent Publishing Guide and eference SQL eplication Guide and eference eplication Installation and Customization Guide for z/os Migrating to eplication and vent Publishing Version 10.2.1 ASNCLP Program eference for eplication and vent Publishing Form Number GC19-3989 GI10-8941 LCD4-8460 SC19-3637 SC19-3638 SC19-3196 SC19-3679 SC19-3639 2.3.1 Optional Program Publications No optional publications are provided for InfoSphere Data eplication. 2.4 Program Source Materials No program source materials or viewable program listings are provided for InfoSphere Data eplication. 2.5 Publications Useful During Installation You might want to use the publications listed in Figure 7 during the installation of InfoSphere Data eplication. Figure 7 (Page 1 of 2). Publications Useful During Installation Publication Title Form Number Media Format IBM SMP/ for z/os User's Guide SA22-7773 PDF and BookManager IBM SMP/ for z/os Commands SA22-7771 PDF and BookManager 8 InfoSphere Data eplication Program Directory
Figure 7 (Page 2 of 2). Publications Useful During Installation Publication Title Form Number Media Format IBM SMP/ for z/os eference SA22-7772 PDF and BookManager IBM SMP/ for z/os Messages, Codes, and Diagnosis GA22-7770 PDF and BookManager Program Materials 9
3.0 Program Support This section describes the IBM support available for InfoSphere Data eplication. 3.1 Program Services Contact your IBM representative for specific information about available program services. 3.2 Preventive Service Planning Before you install InfoSphere Data eplication, make sure that you have reviewed the current Preventive Service Planning (PSP) information. eview the PSP Bucket for General Information, Installation Documentation, and the Cross Product Dependencies sections. For the ecommended Service section, instead of reviewing the PSP Bucket, it is recommended you use the IBM.ProductInstall-equiredService fix category in SMP/ to ensure you have all the recommended service installed. Use the FIXCAT(IBM.ProductInstall-equiredService) operand on the APPLY CHCK command. See 6.1.12, Perform SMP/ APPLY on page 30 for a sample APPLY command If you obtained InfoSphere Data eplication as part of a CBPDO, HOLDDATA is included. If the CBPDO for InfoSphere Data eplication is older than two weeks by the time you install the product materials, you can obtain the latest PSP Bucket information by going to the following website: http://www14.software.ibm.com/webapp/set2/psearch/search?domain=psp You can also use S/390 SoftwareXcel or contact the IBM Support Center to obtain the latest PSP Bucket information. For program support, access the Software Support Website at http://www-01.ibm.com/software/support/. PSP Buckets are identified by UPGADs, which specify product levels; and SUBSTs, which specify the FMIDs for a product level. The UPGAD and SUBST values for InfoSphere Data eplication are included in Figure 8 Figure 8 (Page 1 of 2). PSP Upgrade and Subset ID UPGAD SUBST Description 5655U96 HCHCA21/1531 Change Data Capture 5655IS HAAWA21 Q and SQL eplication Common Base 5655IS JAAWA24 Q-Capture for DB2 5655IS JAAWA25 Q-Apply for DB2 10 Copyright IBM Corp. 1998, 2015
Figure 8 (Page 2 of 2). PSP Upgrade and Subset ID UPGAD SUBST Description 5655IS JAAWA26 SQL-eplication for DB2 3.3 Statement of Support Procedures eport any problems which you feel might be an error in the product materials to your IBM Support Center. You may be asked to gather and submit additional diagnostics to assist the IBM Support Center in their analysis. Figure 9 identifies the component IDs (COMPID) for InfoSphere Data eplication. Figure 9. Component IDs FMID COMPID Component Name HCHCA21 5655U7600 Change Data Capture A21 HAAWA21 5655L8800 Q and SQL eplication Common Base A21 JAAWA24 5655L8800 Q-Capture for DB2 A24 JAAWA25 5655L8800 Q-Apply for DB2 A25 JAAWA26 5655L8800 SQL-eplication for DB2 A26 TAIN elease Program Support 11
4.0 Program and Service Level Information This section identifies the program and relevant service levels of InfoSphere Data eplication. The program level refers to the APA fixes that have been incorporated into the program. The service level refers to the PTFs that have been incorporated into the program. 4.1 Program Level Information The following APA fixes against previous releases of InfoSphere Data eplication have been incorporated into this release. They are listed by FMID. FMID HCHCA20 PM84163 PM86126 PM84370 PM86096 PM88648 PM88897 PM84378 PM89846 PM90789 PM93405 PM94430 PM95092 PM96087 FMID HAAWA10 PM29834 PM29835 PM31052 PM33288 PM34131 PM38951 PM43058 PM44301 PM45461 PM46474 PM49656 PM51339 PM52344 PM54183 PM55893 PM55894 PM55896 PM57439 PM58699 PM59754 PM59759 PM59830 PM60137 PM62475 PM63905 PM65382 PM65865 PM70987 PM73086 PM75117 PM75119 PM76957 PM78783 PM81928 PM82466 PM82917 PM84879 PM84946 PM88819 PM90110 PM90163 PM90165 PM90167 PM90571 PM91606 PM94614 4.2 Service Level Information PTFs containing APA fixes against this release of InfoSphere Data eplication (HCHCA21) have been incorporated into this product package. For a list of included PTFs, examine the ++V statement in the product's SMPMCS. Frequently check the InfoSphere Data eplication PSP Bucket for HIP and SPCIAL attention PTFs against all FMIDs that you must install. You can also receive the latest HOLDDATA, then ensure the FIXCAT(IBM.PODUCTINSTALL-QUIDSVIC) operand is on your APPLY CHCK command. 12 Copyright IBM Corp. 1998, 2015
This will allow you to review the recommended and critical service that should be installed with your FMIDs. Program and Service Level Information 13
5.0 Installation equirements and Considerations The following sections identify the system requirements for installing and activating InfoSphere Data eplication. The following terminology is used: Driving system: the system on which SMP/ is executed to install the program. The program might have specific operating system or product level requirements for using processes, such as binder or assembly utilities during the installation. Target system: the system on which the program is configured and run. The program might have specific product level requirements, such as needing access to the library of another product for link-edits. These requirements, either mandatory or optional, might directly affect the element during the installation or in its basic or enhanced operation. In many cases, you can use a system as both a driving system and a target system. However, you can make a separate IPL-able clone of the running system to use as a target system. The clone must include copies of all system libraries that SMP/ updates, copies of the SMP/ CSI data sets that describe the system libraries, and your PAMLIB and POCLIB. Use separate driving and target systems in the following situations: When you install a new level of a product that is already installed, the new level of the product will replace the old one. By installing the new level onto a separate target system, you can test the new level and keep the old one in production at the same time. When you install a product that shares libraries or load modules with other products, the installation can disrupt the other products. By installing the product onto a separate target system, you can assess these impacts without disrupting your production system. 5.1 Driving System equirements This section describes the environment of the driving system required to install InfoSphere Data eplication. 5.1.1 Machine equirements The driving system can run in any hardware environment that supports the required software. 5.1.2 Programming equirements 14 Copyright IBM Corp. 1998, 2015
Figure 10. Driving System Software equirements Program Number Any one of the following: Product Name Minimum VM Minimum Service Level will satisfy these APAs 5694-A01 z/os V01.13.00 N/A No 5650-ZOS z/os V02.01.00 or higher N/A No 5655-G44 IBM SMP/ for z/os V03.06.00 or higher N/A No Included in the shipped product? Note: Installation might require migration to new z/os releases to be service supported. See http://www-03.ibm.com/systems/z/os/zos/support/zos_eos_dates.html. 5.2 Target System equirements This section describes the environment of the target system required to install and use InfoSphere Data eplication. InfoSphere Data eplication installs in the DBS (P115) SL. 5.2.1 Machine equirements The target system can run in any hardware environment that supports the required software. 5.2.2 Programming equirements 5.2.2.1 Installation equisites: Installation requisites identify products that are required and must be present on the system or products that are not required but should be present on the system for the successful installation of this product. Mandatory installation requisites identify products that are required on the system for the successful installation of this product. Figure 11 (Page 1 of 2). Target System Mandatory Installation equisites Program Number Any one of the following: Product Name Minimum VM Minimum Service Level will satisfy these APAs Included in this product's shipment? Installation equirements and Considerations 15
Figure 11 (Page 2 of 2). Target System Mandatory Installation equisites Program Number Product Name Minimum VM Minimum Service Level will satisfy these APAs 5694-A01 z/os V01.13.00 N/A No 5650-ZOS z/os V02.01.00 or higher Any one of the following: 5605-DB2 DB2 for z/os V10.01.00 N/A No 5697-P31 DB2 Value Unit dition for z/os V10.01.00 N/A No 5615-DB2 DB2 for z/os V11.01.00 N/A No 5697-P43 DB2 Value Unit dition for z/os V11.01.00 N/A No N/A Included in this product's shipment? No Note: Installation might require migration to new z/os releases to be service supported. See http://www-03.ibm.com/systems/z/os/zos/support/zos_eos_dates.html. Conditional installation requisites identify products that are not required for successful installation of this product but can resolve such things as certain warning messages at installation time. InfoSphere Data eplication has no conditional installation requisites. 5.2.2.2 Operational equisites: Operational requisites are products that are required and must be present on the system or products that are not required but should be present on the system for this product to operate all or part of its functions. Mandatory operational requisites identify products that are required for this product to operate its basic functions. Figure 12. Target System Mandatory Operational equisites Program Number Product Name and Minimum VM/Service Level 5655-36 WebSphere MQ for z/os V7.1.X or higher* Any one of the following: 5605-DB2 DB2 V10.01.00 5635-P31 DB2 V10.01.00 Value Unit dition 5615-DB2 DB2 V11.01.00 5635-P43 DB2 V11.01.00 Value Unit dition 16 InfoSphere Data eplication Program Directory
*Note: A restricted use license of WebSphere MQ for z/os, V7.1.X (5655-36) is included with InfoSphere Data eplication, V10.02.01 (5655-DP). Conditional operational requisites identify products that are not required for this product to operate its basic functions but are required at run time for this product to operate specific functions. Figure 13. Target System Conditional Operational equisites Program Number Product Name and Minimum VM/Service Level Function 5655-J51 XML Toolkit for z/os For the sample job ASNQXFMT 5.2.2.3 Toleration/Coexistence equisites: Toleration/coexistence requisites identify products that must be present on sharing systems. These systems can be other systems in a multisystem environment (not necessarily sysplex), a shared DASD environment (such as test and production), or systems that reuse the same DASD environment at different time intervals. InfoSphere Data eplication has no toleration/coexistence requisites. 5.2.2.4 Incompatibility (Negative) equisites: Negative requisites identify products that must not be installed on the same system as this product. InfoSphere Data eplication has no negative requisites. 5.2.3 DASD Storage equirements InfoSphere Data eplication libraries can reside on all supported DASD types. Figure 14 lists the total space that is required for each type of library. Figure 14 (Page 1 of 2). Total DASD Space equired by InfoSphere Data eplication Library Type Target 4020 Distribution 5248 File System 1050 Total Space equired in 3390 Trks 863 for Change Data Capture feature 3159 for Q and SQL eplication feature 1641 for Change Data Capture feature 3609 for Q and SQL eplication feature 750 for Change Data Capture feature Installation equirements and Considerations 17
Figure 14 (Page 2 of 2). Total DASD Space equired by InfoSphere Data eplication Total Space equired Library Type in 3390 Trks 300 for Q and SQL eplication feature Notes: 1. For non-cfm U data sets, IBM recommends using system-determined block sizes for efficient DASD utilization. For CFM U data sets, IBM recommends using a block size of 32760, which is most efficient from the performance and DASD utilization perspective. 2. Abbreviations used for data set types are shown as follows. U S Unique data set, allocated by this product and used by only this product. This table provides all the required information to determine the correct storage for this data set. You do not need to refer to other tables or program directories for the data set size. Shared data set, allocated by this product and used by this product and other products. To determine the correct storage needed for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table. xisting shared data set, used by this product and other products. This data set is not allocated by this product. To determine the correct storage for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table. If you currently have a previous release of this product installed in these libraries, the installation of this release will delete the old release and reclaim the space that was used by the old release and any service that had been installed. You can determine whether these libraries have enough space by deleting the old release with a dummy function, compressing the libraries, and comparing the space requirements with the free space in the libraries. For more information about the names and sizes of the required data sets, see 6.1.9, Allocate SMP/ Target and Distribution Libraries on page 29. 3. Abbreviations used for the file system path type are as follows. N X P New path, created by this product. Path created by this product, but might already exist from a previous release. Previously existing path, created by another product. 4. All target and distribution libraries listed have the following attributes: The default name of the data set can be changed. The default block size of the data set can be changed. The data set can be merged with another data set that has equivalent characteristics. The data set can be either a PDS or a PDS, except SCHCLOAD and ACHCLOAD, which are required to be PDSs. 5. All target libraries listed have the following attributes: 18 InfoSphere Data eplication Program Directory
These data sets can be SMS-managed, but they are not required to be SMS-managed. These data sets are not required to reside on the IPL volume. The values in the "Member Type" column are not necessarily the actual SMP/ element types that are identified in the SMPMCS. 6. All target libraries that are listed and contain load modules have the following attributes: These data sets can be in the LPA, but they are not required to be in the LPA. These data sets can be in the LNKLST. SASNLOAD only needs to be APF authorized for Qcapture and SQL Capture. The Change Data Capture feature requires that the SMPLTS data set must be a PDS. If your existing SMPLTS is a PDS, you will need to allocate a new PDS and copy your existing SMPLTS into it and then change the SMPLTS DDDF entry to indicate the new PDS data set. The following figures describe the target and distribution libraries and file system paths required to install InfoSphere Data eplication. The storage requirements of InfoSphere Data eplication must be added to the storage required by other programs that have data in the same library or path. Note: Use the data in these tables to determine which libraries can be merged into common data sets. In addition, since some ALIAS names may not be unique, ensure that no naming conflicts will be introduced before merging libraries. Figure 15. Storage equirements for the Change Data Capture feature Target Libraries Library DDNAM Member Type Target Volume T Y P O G C F M L C L No. of 3390 Trks SCHCASM SAMP Any U PDS FB 80 3 3 SCHCC SAMP Any U PDS VB 256 7 3 SCHCCNTL SAMP Any U PDS FB 80 21 5 SCHCCOB SAMP Any U PDS FB 80 6 3 SCHCDATA DATA Any U PDS FB 80 6 3 SCHCDBM DATA Any U PDS FB 80 26 5 SCHCH SAMP Any U PDS VB 256 3 3 SCHCLOAD MOD Any U PDS U 0 776 N/A SCHCMAC SAMP Any U PDS FB 80 3 3 SCHCNOTC SAMP Any U PDS VB 137 6 1 SCHCTTL DATA Any U PDS VB 256 6 3 No. of DI Blks Installation equirements and Considerations 19
Figure 16. Storage equirements for the Q and SQL eplication feature Target Libraries Library DDNAM Member Type Target Volume T Y P O G C F M L C L No. of 3390 Trks SASNBAS Sample any U PDS FB 80 9 5 SASNDBM Macro any U PDS FB 80 75 5 SASNLOAD LMOD any U PDS U 0 3000 10 SASNSAMP Sample any U PDS FB 80 75 10 No. of DI Blks Figure 17. Change Data Capture feature File System Paths DDNAM T Y P Path Name SCHCJAVA N /usr/lpp/chc/v102m1/ibm Figure 18 (Page 1 of 2). Q and SQL eplication feature File System Paths DDNAM T Y P Path Name SASNMSGS N /usr/lpp/db2repl_10_02/ibm SASNMSGS N /usr/lpp/db2repl_10_02/bin/ibm SASNMSGS N /usr/lpp/db2repl_10_02/msg/da_dk/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/n_up/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/s_s/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/fr_f/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/it_it/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/ko_k/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/pl_pl/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/sv_s/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/zh_cn/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/de_d/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/n_us/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/fi_fi/ibm/ 20 InfoSphere Data eplication Program Directory
Figure 18 (Page 2 of 2). Q and SQL eplication feature File System Paths DDNAM T Y P Path Name SASNMSGS N /usr/lpp/db2repl_10_02/msg/ja_jp/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/no_no/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/pt_b/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/zh_tw/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/u_u/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/cs_cz/ibm/ SASNMSGS N /usr/lpp/db2repl_10_02/msg/ibm SASNCLP N /usr/lpp/db2repl_10_02/asnzclp/ibm SASNCLP N /usr/lpp/db2repl_10_02/asnzclp/classes/ibm SASNCLP N /usr/lpp/db2repl_10_02/asnzclp/bin/ibm SASNCLP N /usr/lpp/db2repl_10_02/asnzclp/ibm Figure 19. Storage equirements for the Change Data Capture feature Distribution Libraries Library DDNAM T Y P O G C F M L C L No. of 3390 Trks ACHCASM U PDS FB 80 3 3 ACHCC U PDS VB 256 7 3 ACHCCNTL U PDS FB 80 21 5 ACHCCOB U PDS FB 80 6 3 ACHCDATA U PDS FB 80 6 3 ACHCDBM U PDS FB 80 26 5 ACHCH U PDS VB 256 3 5 ACHCJAVA U PDS VB 255 541 3 ACHCLOAD U PDS U 0 1013 N/A ACHCMAC U PDS FB 80 3 3 ACHCNOTC U PDS VB 137 6 1 ACHCTTL U PDS VB 256 6 3 No. of DI Blks Installation equirements and Considerations 21
Figure 20. Storage equirements for Q and SQL eplication feature Distribution Libraries Library DDNAM T Y P O G C F M L C L No. of 3390 Trks AASNBAS U PDS FB 80 9 5 AASNCLP U PDS VB 256 300 5 AASNDBM U PDS FB 80 75 5 AASNLOAD U PDS U 0 3000 10 AASNMSGS U PDS VB 256 150 5 AASNSAMP U PDS FB 80 75 10 No. of DI Blks 5.3 FMIDs Deleted Installing InfoSphere Data eplication might result in the deletion of other FMIDs. To see which FMIDs will be deleted, examine the ++V statement in the SMPMCS of the product. If you do not want to delete these FMIDs at this time, install InfoSphere Data eplication into separate SMP/ target and distribution zones. Note: These FMIDs are not automatically deleted from the Global Zone. If you want to delete these FMIDs from the Global Zone, use the SMP/ JCT NOFMID DLTFMID command. See the SMP/ Commands book for details. 5.4 Special Considerations PDS Considerations: The Change Data Capture feauture of InfoSphere Data eplication uses the "partitioned data set extended" or PDS format for the SCHCLOAD target library. There are some operational differences between PDS and PDS data sets. The PDS format may be shared by more than one z/os system and no special precautions are necessary. However the PDS format may only be shared by z/os systems which are part of a sysplex or which are connected using Global esource Serialization (are in a GS complex). If z/os systems share use of a PDS data set outside of a sysplex or GS environment, you may experience severe problems when the data set is updated. This is due to the fact that PDS directory information is cached in storage, and when the data set is updated from one system the other system(s) have no knowledge of the update, and their cached directory information will be incorrect. You must take care not to share the SCHCLOAD data set between z/os systems unless they are in a sysplex or are connected in a GS complex. If you need to share the content of the SCHCLOAD data set, a separate copy must be created for each z/os system. 22 InfoSphere Data eplication Program Directory
6.0 Installation Instructions This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of InfoSphere Data eplication. Please note the following points: If you want to install InfoSphere Data eplication into its own SMP/ environment, consult the SMP/ manuals for instructions on creating and initializing the SMPCSI and the SMP/ control data sets. You can use the sample jobs that are provided to perform part or all of the installation tasks. The SMP/ jobs assume that all DDDF entries that are required for SMP/ execution have been defined in appropriate zones. You can use the SMP/ dialogs instead of the sample jobs to accomplish the SMP/ installation steps. 6.1 Installing InfoSphere Data eplication 6.1.1 SMP/ Considerations for Installing InfoSphere Data eplication Use the SMP/ CIV, APPLY, and ACCPT commands to install this release of InfoSphere Data eplication. 6.1.2 SMP/ Options Subentry Values The recommended values for certain SMP/ CSI subentries are shown in Figure 21. Using values lower than the recommended values can result in failures in the installation. DSSPAC is a subentry in the GLOBAL options entry. PMAX is a subentry of the GNAL entry in the GLOBAL options entry. See the SMP/ manuals for instructions on updating the global zone. Figure 21. SMP/ Options Subentry Values Subentry Value Comment DSSPAC (200,200,500) 3390 DASD tracks PMAX SMP/ Default IBM recommends using the SMP/ default for PMAX. Copyright IBM Corp. 1998, 2015 23
6.1.3 SMP/ CALLLIBS Processing The Change Data Capture feature of InfoSphere Data eplication uses the CALLLIBS function provided in SMP/ to resolve external references during installation. When InfoSphere Data eplication is installed, ensure that DDDFs exist for the following libraries: SZANT1 SZACMTX SCCPP SCLKD SCLKX CSSLIB Note: CALLLIBS uses the previous DDDFs only to resolve the link-edit for InfoSphere Data eplication. These data sets are not updated during the installation of InfoSphere Data eplication. 6.1.4 Sample Jobs The following sample installation jobs are provided as part of the product to help you install the Change Data Capture feature of InfoSphere Data eplication: Figure 22. Sample Installation Jobs for the Change Data Capture feature Job Name Job Type Description LFIL CHCALA SMP/ Sample job to allocate and initialize a new SMP/ CSI data set (Optional) CHCALB SMP/ Sample job to allocate SMP/ data sets (Optional) IBM.HCHCA21.F4 IBM.HCHCA21.F4 CHCCV CIV Sample CIV job IBM.HCHCA21.F4 CHCALLOC ALLOCAT Sample job to allocate target and distribution libraries CHCZFS ALLOMZFS Sample job to allocate new ZFS data sets (Optional) CHCISMKD MKDI Sample job to invoke the supplied CHCMKDI XC to allocate HFS or zfs paths IBM.HCHCA21.F4 IBM.HCHCA21.F4 IBM.HCHCA21.F4 CHCDDDF DDDF Sample job to define SMP/ DDDFs IBM.HCHCA21.F4 CHCAPPLY APPLY Sample APPLY job IBM.HCHCA21.F4 CHCACCP ACCPT Sample ACCPT job IBM.HCHCA21.F4 The following sample installation jobs are provided as part of the product to help you install the Q and SQL eplication feature of InfoSphere Data eplication: 24 InfoSphere Data eplication Program Directory
Figure 23. Sample Installation Jobs for the Q and SQL eplication feature Job Name Job Type Description LFIL ASNALA SMP/ Sample job to allocate and initialize a new SMP/ CSI data set (Optional) ASNALB SMP/ Sample job to allocate SMP/ data sets (Optional) IBM.HAAWA21.F6 IBM.HAAWA21.F6 ASNCV0 CIV Sample CIV job for HAAWA21 IBM.HAAWA21.F6 ASNCV1 CIV Sample CIV job for JAAWA24 IBM.HAAWA21.F6 ASNCV2 CIV Sample CIV job for JAAWA25 IBM.HAAWA21.F6 ASNCV3 CIV Sample CIV job for JAAWA26 IBM.HAAWA21.F6 ASNALLOC ALLOCAT Sample job to allocate target and distribution libraries ASNZFS ALLOMZFS Sample job to allocate new ZFS data sets (Optional) ASNISMKD MKDI Sample job to invoke the supplied ASNMKDI XC to allocate HFS paths ASNISLKM MKDI Sample job to invoke the supplied ASNLKMSG XC to create symbolic links IBM.HAAWA21.F6 IBM.HAAWA21.F6 IBM.HAAWA21.F6 IBM.HAAWA21.F6 ASNDDDF DDDF Sample job to define SMP/ DDDFs IBM.HAAWA21.F6 ASNAPPLY APPLY Sample APPLY job IBM.HAAWA21.F6 ASNACCP ACCPT Sample ACCPT job IBM.HAAWA21.F6 You can access the sample installation jobs by performing an SMP/ CIV (refer to 6.1.7, Perform SMP/ CIV on page 28) then copy the jobs from the LFILs to a work data set for editing and submission. See Figure 22 on page 24 to find the appropriate relfile data set. You can also copy the sample installation jobs from the tape or product files by submitting the following job(s). Depending on your distribution medium, use either the //TAPIN or the //FILIN DD statement and comment out or delete the other statement. Before you submit the job, add a job card and change the lowercase parameters to uppercase values to meet the requirements of your site. For the Change Data Capture feature: //STP1 XC PGM=IBCOPY //SYSPINT DD SYSOUT= // // Make the //TAPIN DD statement below active if you install // from a CBPDO tape by uncommenting the DD statement below. // // TAPIN DD DSN=IBM.HCHCA21.F4,UNIT=tunit, // VOL=S=volser,LABL=(x,SL), // DISP=(OLD,KP) // Installation Instructions 25
// Make the //TAPIN DD statement below active if you install // from a product tape received outside the CBPDO process // (using the optional SMP/ CIV job) by uncommenting // the DD statement below. // // TAPIN DD DSN=IBM.HCHCA21.F4,UNIT=tunit, // VOL=S=CHCA21,LABL=(5,SL), // DISP=(OLD,KP) // // Make the //FILIN DD statement below active for // downloaded DASD files. // // FILIN DD DSN=IBM.HCHCA21.F4,UNIT=SYSALLDA,DISP=SH, // VOL=S=filevol //OUT DD DSNAM=jcl-library-name, // DISP=(NW,CATLG,DLT), // VOL=S=dasdvol,UNIT=SYSALLDA, // SPAC=(TK,(primary,secondary,dir)) //SYSUT3 DD UNIT=SYSALLDA,SPAC=(CYL,(1,1)) //SYSIN DD COPY INDD=xxxxIN,OUTDD=OUT SLCT MMB=(CHCALA,CHCALB,CHCALLOC) SLCT MMB=(CHCDDDF,CHCCV,CHCISMKD) SLCT MMB=(CHCAPPLY,CHCACCP,CHCMKDI) SLCT MMB=(CHCZFS) / For the Q and SQL eplication feature: //STP1 XC PGM=IBCOPY //SYSPINT DD SYSOUT= // // Make the //TAPIN DD statement below active if you install // from a CBPDO tape by uncommenting the DD statement below. // // TAPIN DD DSN=IBM.HAAWA21.F6,UNIT=tunit, // VOL=S=volser,LABL=(x,SL), // DISP=(OLD,KP) // // Make the //TAPIN DD statement below active if you install // from a product tape received outside the CBPDO process // (using the optional SMP/ CIV job) by uncommenting // the DD statement below. // // TAPIN DD DSN=IBM.HAAWA21.F6,UNIT=tunit, // VOL=S=AAWA21,LABL=(7,SL), // DISP=(OLD,KP) // // Make the //FILIN DD statement below active for // downloaded DASD files. 26 InfoSphere Data eplication Program Directory
// // FILIN DD DSN=IBM.HAAWA21.F6,UNIT=SYSALLDA,DISP=SH, // VOL=S=filevol //OUT DD DSNAM=jcl-library-name, // DISP=(NW,CATLG,DLT), // VOL=S=dasdvol,UNIT=SYSALLDA, // SPAC=(TK,(primary,secondary,dir)) //SYSUT3 DD UNIT=SYSALLDA,SPAC=(CYL,(1,1)) //SYSIN DD COPY INDD=xxxxIN,OUTDD=OUT / See the following information to update the statements in the previous samples: TAPIN: tunit is the unit value that matches the product package. volser is the volume serial that matches the product package. x is the tape file number that indicates the location of the data set name on the tape. See the documentation that is provided by CBPDO for the location of IBM.HCHCA21.F4 and/or IBM.HAAWA21.F6 on the tape. FILIN: filevol is the volume serial of the DASD device where the downloaded files reside. OUT: jcl-library-name is the name of the output data set where the sample jobs are stored. dasdvol is the volume serial of the DASD device where the output data set resides. SYSIN: xxxxin is either TAPIN or FILIN depending on your input DD statement. 6.1.5 Allocate SMP/ CSI (Optional) If you are using an existing CSI, do not execute this job. If you are allocating a new SMP/ data set for this install, edit and submit sample job CHCALA to allocate the SMP/ data set for the Change Data Capture feature of InfoSphere Data eplication. Consult the instructions in the sample job for more information. If you are allocating a new SMP/ data set for this install, edit and submit sample job ASNALA to allocate the SMP/ data set for the Q and SQL eplication feature of InfoSphere Data eplication. Consult the instructions in the sample job for more information. If you are installing both features into the same SMP/ data set, you can choose to run either of the two jobs, but not both. xpected eturn Codes and Messages: You will receive a return code of 0 if this job runs correctly. Installation Instructions 27
6.1.6 Initialize CSI zones (Optional) If you are using an existing CSI, do not execute this job. dit and submit sample job CHCALB to initialize SMP/ zones for the Change Data Capture feature of InfoSphere Data eplication. Consult the instructions in the sample job for more information. dit and submit sample job ASNALB to initialize SMP/ zones for the Q and SQL eplication feature of InfoSphere Data eplication. Consult the instructions in the sample job for more information. If you are installing both features into the same SMP/ data set, you can choose to run either of the two jobs, but not both. If this is the case, remember to create SMPLTS as a PDS data set. xpected eturn Codes and Messages: You will receive a return code of 0 if this job runs correctly. 6.1.7 Perform SMP/ CIV If you have obtained InfoSphere Data eplication as part of a CBPDO, use the CVPDO job in the CBPDO IMLIB data set to receive the InfoSphere Data eplication FMIDs, service, and HOLDDATA that are included on the CBPDO package. For more information, see the documentation that is included in the CBPDO. You can also choose to edit and submit sample job CHCCV to perform the SMP/ CIV for the Change Data Capture feature of InfoSphere Data eplication. Consult the instructions in the sample job for more information. xpected eturn Codes and Messages: You will receive a return code of 0 if this job runs correctly. You can also choose to edit and submit sample jobs ASNCV0, ASNCV1, ASNCV2, and ASNCV3 to perform the SMP/ CIV for the Q and SQL eplication feature of InfoSphere Data eplication. Consult the instructions in the sample job for more information. xpected eturn Codes and Messages: You will receive a return code of 0 if these jobs run correctly. 6.1.8 Allocate, create and mount ZFS Files (Optional) dit and submit sample job CHCZFS to allocate, create a mountpoint, and mount zfs data sets for the Change Data Capture feature. dit and submit sample job ASNZFS to allocate, create a mountpoint, and mount zfs data sets for the Q and SQL eplication feature. You may receive the following message, if you try and create a directory that already exists: BPXF134 TUN COD 00000075, ASON COD 05520038. AN O OCCUD DUING TH CATION OF DICTOY pathname. 28 InfoSphere Data eplication Program Directory