DB2® packages were introduced with DB2 V2.3 in 1993. During the 15 years that have elapsed, a lot has changed. In particular, there is a more widespread use of distributed computing, JavaTM language, new tools, and upgrades in the platform software and hardware. The best practices back then just might not be optimal today. In this IBM® Redbooks® publication, we take a fresh look at bringing packages into the 21st century. We begin with an overview of packages and explain the advantages of using packages. Because database request module (DBRM) based plans have been deprecated in DB2 9, you need to convert to packages if you did not use packages already. We provide guidance on using a DB2 provided function to convert from DBRM-based plans to packages. We re-examine the application development frameworks for packages: program preparation, package setup, and execution. For distributed applications, we include a discussion of a utility to identify and remove deprecated private protocol and converting to DRDA® as well as an introduction to the new pureQuery function of Data Studio. We also discuss common problems and their resolutions. We then explore administration and operational activities dealing with packages, including security, access path management (where we discuss the newly introduced package stability feature to allow for a seamless fallback), and management and performance aspects. The appendixes include useful queries and mention tools for managing packages effectively.

DB2 9 for z/OS is an exciting new version, with many improvements in performance and little regression. DB2 V9 improves availability and security, as well as adds greatly to SQL and XML functions. Optimization improvements include more SQL functions to optimize, improved statistics for the optimizer, better optimization techniques, and a new approach to providing information for tuning. V8 SQL procedures were not eligible to run on the IBM System z9 Integrated Information Processor (zIIP), but changing to use the native SQL procedures on DB2 V9 makes the work eligible for zIIP processing. The performance of varying length data can improve substantially if there are large numbers of varying length columns. Several improvements in disk access can reduce the time for sequential disk access and improve data rates. The key DB2 9 for z/OS performance improvements include reduced CPU time in many utilities, deep synergy with IBM System z hardware and z/OS software, improved performance and scalability for inserts and LOBs, improved SQL optimization, zIIP processing for remote native SQL procedures, index compression, reduced CPU time for data with varying lengths, and better sequential access. Virtual storage use below the 2 GB bar is also improved. This IBM Redbooks publication provides an overview of the performance impact of DB2 9 for z/OS, especially performance scalability for transactions, CPU, and elapsed time for queries and utilities. We discuss the overall performance and possible impacts when moving from version to version. We include performance measurements that were made in the laboratory and provide some estimates. Keep in mind that your results are likely to vary, as the conditions and work will differ. In this book, we assume that you are familiar with DB2 V9. See DB2 9 for z/OS Technical Overview, SG24-7330, for an introduction to the new functions.

IBM® DB2® Version 10.1 for z/OS® (DB2 10 for z/OS or just DB2 10 throughout this book) is the fourteenth release of DB2 for MVSTM. It brings improved performance and synergy with the System z® hardware and more opportunities to drive business value in the following areas: Cost savings and compliance through optimized innovations DB2 10 delivers value in this area by achieving up to 10% CPU savings for traditional workloads and up to 20% CPU savings for nontraditional workloads, depending on the environments. Synergy with other IBM System z platform components reduces CPU use by taking advantage of the latest processor improvements and z/OS enhancements. Streamline security and regulatory compliance through the separation of roles between security and data administrators, column level security access, and added auditing capabilities. Business insight innovations Productivity improvements are provided by new functions available for pureXML®, data warehousing, and traditional online TP applications Enhanced support for key business partners that allow you to get more from your data in critical business disciplines like ERP Bitemporal support for applications that need to correlate the validity of data with time. Business resiliency innovations Database on demand capabilities to ensure that information design can be changed dynamically, often without database outages DB2 operations and utility improvements enhancing performance, usability, and availability by exploiting disk storage technology. The DB2 10 environment is available either for brand new installations of DB2, or for migrations from DB2 9 for z/OS or from DB2 UDB for z/OS Version 8 subsystems. This IBM Redbooks® publication introduces the enhancements made available with DB2 10 for z/OS. The contents help you understand the new functions and performance enhancements, start planning for exploiting the key new capabilities, and justify the investment in installing or migrating or skip migrating to DB2 10.

This IBM® Redbooks® publication is intended to make System Programmers, Operators, and Availability Managers aware of the enhancements to recent releases of IBM z/OS® and its major subsystems in the area of planned outage avoidance. It is a follow-on to, rather than a replacement for, z/OS Planned Outage Avoidance Checklist, SG24-7328. Its primary objective is to bring together in one place information that is already available, but widely dispersed. It also presents a different perspective on planned outage avoidance. Most businesses care about application availability rather than the availability of a specific system. Also, a planned outage is not necessarily a bad thing, if it does not affect application availability. In fact, running for too long without an IPL or subsystem restart might have a negative impact on application availability because it impacts your ability to apply preventive service. Therefore, this book places more focus on decoupling the ability to make changes and updates to your system from IPLing or restarting your systems.

This IBM® Redbooks® publication discusses in detail the facilities of DB2® for z/OS®, which allow complete monitoring of a DB2 environment. It focuses on the use of the DB2 instrumentation facility component (IFC) to provide monitoring of DB2 data and events and includes suggestions for related tuning. We discuss the collection of statistics for the verification of performance of the various components of the DB2 system and accounting for tracking the behavior of the applications. We have intentionally omitted considerations for query optimization; they are worth a separate document. Use this book to activate the right traces to help you monitor the performance of your DB2 system and to tune the various aspects of subsystem and application performance.

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

IBM® continues to enhance the functionality, performance, availability, and ease of use of IBM DB2® utilities. This IBM Redbooks® publication is the result of a project dedicated to the current DB2 Version 9 Utilities Suite product. It provides information about introducing the functions that help set up and invoke the utilities in operational scenarios, shows how to optimize concurrent execution of utilities and collect information for triggering utilities execution, and provides considerations about partitioning. It also describes the new functions provided by several utilities for SHARE LEVEL CHANGE execution, which maximize availability and the exploitation of DFSMS constructs by the BACKUP and RESTORE SYSTEM utilities. This book concentrates on the enhancements provided by DB2 UDB for z/OS Version 8 and DB2 for z/OS Version 9. It implicitly assumes a basic level of familiarity with the utilities provided by DB2 for z/OS and OS/390® Version 7.

DB2® 10 for z/OS can reduce the total DB2 CPU demand from 5-20%, compared to DB2 9, when you take advantage of all the enhancements. Many CPU reductions are built in directly to DB2, requiring no application changes. Some enhancements are implemented through normal DB2 activities through rebinding, restructuring database definitions, improving applications, and utility processing. The CPU demand reduction features have the potential to provide significant total cost of ownership savings based on the application mix and transaction types. Improvements in optimization reduce costs by processing SQL automatically with more efficient data access paths. Improvements through a range-list index scan access method, list prefetch for IN-list, more parallelism for select and index insert processing, better work file usage, better record identifier (RID) pool overflow management, improved sequential detection, faster log I/O, access path certainty evaluation for static SQL, and improved distributed data facility (DDF) transaction flow all provide more efficiency without changes to applications. These enhancements can reduce total CPU enterprise costs because of improved efficiency in the DB2 10 for z/OS. DB2 10 includes numerous performance enhancements for Large Objects (LOBs) that save disk space for small LOBs and that provide dramatically better performance for LOB retrieval, inserts, load, and import/export using DB2 utilities. DB210 can also more effectively REORG partitions that contain LOBs. This IBM Redbooks® publication® provides an overview of the performance impact of DB2 10 for z/OS discussing the overall performance and possible impacts when moving from version to version. We include performance measurements that were made in the laboratory and provide some estimates. Keep in mind that your results are likely to vary, as the conditions and work will differ. In this book, we assume that you are somewhat familiar with DB2 10 for z/OS. See DB2 10 for z/OS Technical Overview, SG24-7892-00, for an introduction to the new functions.

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®.

This IBM Redbooks publication presents many of the new and improved features and functions of DB2 V9.1 for z/OS and DB2 Connect V9.1. It explains how they complement and benefit your SAP NetWeaver environment. This book also shares some of our experiences in migrating our DB2 V8 SAP data sharing environment to DB2 9 for z/OS with a minimal amount of outage. This book is written for SAP and DB2 administrators. Knowledge of these products and of the z/OS environment is assumed.