IBM® InfoSphereTM Change Data Capture for z/OS® uses log-based change data capture technology to provide low impact capture and rapid delivery of changes to and from DB2® z/OS in heterogeneous environments without impacting source systems. Customers get the up-to-date information they need to make actionable, trusted business decisions while optimizing MIPS costs. Change Data Capture can also be used to synchronize data in real time between multiple data environments to support active data warehousing, live reporting, operational business intelligence, application consolidations and migrations, master data management, and to deliver data to SOA environments. This IBM RedpaperTM document describes InfoSphere Change Data Capture, how to install and configure it, and how to migrate to the latest release.

To make better informed business decisions, better serve clients, and increase operational efficiencies, you must be aware of changes to key data as they occur. In addition, you must enable the immediate delivery of this information to the people and processes that need to act upon it. This ability to sense and respond to data changes is fundamental to dynamic warehousing, master data management, and many other key initiatives. A major challenge in providing this type of environment is determining how to tie all the independent systems together and process the immense data flow requirements. IBM® InfoSphere® Change Data Capture (InfoSphere CDC) can respond to that challenge, providing programming-free data integration, and eliminating redundant data transfer, to minimize the impact on production systems. In this IBM Redbooks® publication, we show you examples of how InfoSphere CDC can be used to implement integrated systems, to keep those systems updated immediately as changes occur, and to use your existing infrastructure and scale up as your workload grows. InfoSphere CDC can also enhance your investment in other software, such as IBM DataStage® and IBM QualityStage®, IBM InfoSphere Warehouse, and IBM InfoSphere Master Data Management Server, enabling real-time and event-driven processes. Enable the integration of your critical data and make it immediately available as your business needs it.

This IBM® Redbooks® publication will help you install, configure, and use IBM InfoSphere® OptimTM Workload Replay (InfoSphere Workload Replay), a web-based tool that lets you capture real production SQL workload data and then replay the workload data in a pre-production environment. With InfoSphere Workload Replay, you can set up and run realistic tests for enterprise database changes without the need to create a complex client and application infrastructure to mimic your production environment. The publication goes through the steps to install and configure the InfoSphere Workload Replay appliance and related database components for IBM DB2® for Linux, UNIX, and Windows and for DB2 for IBM z/OS®. The capture, replay, and reporting process, including user ID and roles management, is described in detail to quickly get you up and running. Ongoing operations, such as appliance health monitoring, starting and stopping the product, and backup and restore in your day-to-day management of the product, extensive troubleshooting information, and information about how to integrate InfoSphere Workload Replay with other InfoSphere products are covered in separate chapters.

Design, implement, and monitor a successful Q replication and Event Publishing project with IBM InfoSphere Replication Server and Data Event Publisher using this book and eBook.

This IBM® Redbooks® publication will help you install, configure, and use IBM InfoSphere® Optim Workload Replay (InfoSphere Workload Replay), a web-based tool that lets you capture real production SQL workload data and then replay the workload data in a pre-production environment. With InfoSphere Workload Replay, you can set up and run realistic tests for enterprise database changes without the need to create a complex client and application infrastructure to mimic your production environment. The publication goes through the steps to install and configure the InfoSphere Workload Replay appliance and related database components for IBM DB2® for Linux, UNIX, and Windows and for DB2 for IBM z/OS®. The capture, replay, and reporting process, including user ID and roles management, is described in detail to quickly get you up and running. Ongoing operations, such as appliance health monitoring, starting and stopping the product, and backup and restore in your day-to-day management of the product, extensive troubleshooting information, and information about how to integrate InfoSphere Workload Replay with other InfoSphere products are covered in separate chapters.

As business cycles speed up, many customers gain significant competitive advantage from quicker and more accurate business decision-making by using real data. For many customers, choosing the path to co-locate their transactional and analytical workloads on System z® better leverages their existing investment in hardware, software, and skills. We created a project to address a number of best practice questions on how to manage these newer, analytical type workloads, especially when co-located with traditional transactional workloads. The goal of this IBM® Redbooks® publication is to provide technical guidance and performance trade-offs associated with resource management and potentially DB2® data-sharing in a variety of mixed transactional / data warehouse System z topologies. The term co-location used here and in the rest of the book is specifically defined as the practice of housing both transactional (OLTP) and data warehouse (analytical) workloads within the same System z configuration. We also assumed that key portions of the transactional and data warehouse databases would reside on DB2 for z/OS®. The databases may or may not reside in a DB2 data-sharing environment; we discuss those pros and cons in this book. The intended audience includes DB2 data warehouse architects and practitioners who are facing choices in resource management and system topologies in the data warehouse arena. This specifically includes Business Intelligence (BI) administrators, DB2 database administrators (DBAs) and z/OS performance administrators / systems programmers. In addition, decision makers and architects can utilize this book to assist in making platform and database topology decisions. The book is divided into four parts. Part I, "Introducing the co-location project" covers the System z value proposition and why one should consider System z as the central platform for their data warehousing / business analytics needs. Some topics are risk avoidance via data consolidation, continuous availability, simplified disaster recovery, IBM Smart Analytics Optimizer, reduced network bandwidth requirements, and the unique virtualization and resource management capabilities of System z LPAR, z/VM® and WLM. Part I also provides some of the common System z co-location topologies along with an explanation of the general pros and cons of each. This would be useful input for an architect to understand where a customer is today and where they might consider moving to. Part II, "Project environment" covers the environment, products, workloads, workload drivers, and data models implemented for this study. The environment consisted of a logically partitioned z10TM 32way, running z/VM, Linux®, and z/OS operating system instances. On those instances we ran products such as z/OS DB2 V9, IBM Cognos® Business Intelligence Version 8.4 for Linux on System z, InfoSphereTM Warehouse for System z, InfoSphere Change Data Capture, z/OS WebSphere® V7, Tivoli® Omegamon for DB2 Performance expert. Utilizing these products we created transactional (OLTP), data warehouse query, and data warehouse refresh workloads. All the workloads were based on an existing web-based transactional Bookstore workload, that's currently utilized for internal testing within the System p® and z labs. While some IBM Cognos BI and ISWz product usage and experiences information is covered in this book, we do not go into the depth typically found in IBM Redbooks publications, since there's another book focused specifically on that

As IBM® continues to enhance the functionality, performance, and availability of IBM Db2®, the utilities have made significant strides towards self-management. IBM Db2 for z/OS utilities is leading the trend towards autonomics. During the last couple of versions of Db2 for z/OS, and through the maintenance stream, new features and enhancements have been delivered to further improve the performance and functionality of the Db2 utilities. The intent of this IBM RedpaperTM publication is to help Db2 Database Administrators, Db2 System Programmers, and anyone who runs Db2 for z/OS utilities implement best practices. The intent of this paper is not to replicate the Db2 for z/OS Utilities Reference Guide or the Db2 for z/OS Installation Guide. This paper describes and informs you how to apply real-life practical preferred practices for the IBM Db2 for z/OS Utilities Suite. The paper concentrates on the enhancements provided by Db2 utilities, regardless of the version, albeit some functions and features are available only in Db2 12 for IBM z/OS®.

Today's computing environment is subject to increasing regulatory pressures and potentially malicious attacks. Regulatory compliance, security, and audit are in the daily headlines and growing more prominent.The security of the information to which you have been entrusted has never been more critical. The reality of compliance is too complex. Compliance demands that you work carefully to set up a strong, comprehensive set of policies and controls. That means controls that consider operational data, financial data, unstructured data, spreadsheets, e-mail, and business intelligence data. We have a responsibility to secure all business data and especially sensitive customer data. Security can be difficult to manage. IBM DB2 for z/OS already resides on one of the most secure platforms in the industry. IBM System z servers are routinely used by enterprises around the world to support their mission-critical applications. The mainframe's strengths in security stem in part from its history of supporting sensitive data for large enterprises, resulting in security features being built into its design for many decades. It also benefits from a system-wide approach with security capabilities built into the hardware, operating systems, databases, key middleware and more. Its highly evolved layers and security management components give it a fundamental advantage over other systems.

Time to market, flexibility, and cost reduction are among the top concerns common to all IT executives. If significant resource investments are placed in mature systems, IT organizations need to balance old and new technology. Older technology, such as non-IBM pre-relational databases, is costly, inflexible, and non-standard. Users store their information on the mainframe and thus preserve the skills and qualities of service their business needs. But users also benefit from standards-based modernization by migrating to IBM® DB2® for z/OS®. With this migration, users deliver new application features quickly and respond to changing business requirements more effectively. When migrating, the main decision is choosing between conversion and re-engineering. Although the rewards associated with rebuilding mature applications are high, so are the risks and customers that are embarking on a migration need that migration done quickly. In this IBM Redbooks® publication, we examine how to best approach the migration process by evaluating the environment, assessing the application as a conversion candidate, and identifying suitable tools. This publication is intended for IT decision makers and database administrators who are considering migrating their information to a modern database management system.