DB2 Universal Database Server for OS/390 Version 6 -- Power to Develop Tomorrow's Applications and Meet Today's Business Needs

Software Announcement
May 12, 1998
Announcement Letter Number: 298-159


Table of Contents:



At a Glance

With Version 6, DB2 UDB Server for OS/390 provides databases that are:

  • Universally extensible
    • Very large objects
    • User-defined functions
    • User-defined distinct data types
    • Triggers for active data
  • Universally accessible through network computing
    • SQLJ (Java embedded SQL)
    • DDF connection pooling
    • DRDA (R) three-part names
    • Stored procedure enhancements
    • Net.Data Version 2 with enhanced performance
    • QMF, QMF HPO, and QMF for Windows
    • DB2 DataPropagator
  • Universally scalable and reliable
    • Support for 16 TB tables
    • Faster, more usable, more parallel utilities
    • Data sharing enhancements
    • Easier to alter partitions
    • Virtual storage constraint relief
    • Faster restart and recovery
    • Query enhancements, prediction/governing
    • 8 and 16 KB page sizes
  • Universally manageable
    • Workstation tools for Windows NT (R) and OS/2 (R):
        DB2 Installer Visual Explain Tuning and Analysis DB2 Estimator
    • DB2 PM
    • DB2 Administration Tool
    • DB2 Buffer Pool Tool

The DB2 Universal Database (R) Server for OS/390 (TM) Version 6 extends the DB2 Universal Database to the System/390 (R) platform. Now IBM combines the power of PC and UNIX (R) application development and query tools with the industrial-strength, reliability, and performance of DB2 (R) Universal Database Server for OS/390 (DB2 UDB Server for OS/390). This new class of databases, universal databases, lets you store and query not only alphanumeric data, but also text documents, images, audio, video, and other complex objects.

With Version 6, it is now possible to have an enterprise-wide DB2 strategy that can take full advantage of these UDB object-relational capabilities across major IBM and non-IBM operating systems. With it, you can develop tomorrow's applications while continuing to meet today's business needs.

DB2 UDB for OS/390 Version 6 delivers enhancements and improvements that can be utilized by existing applications. You can take advantage of performance improvements for utilities, faster restart and recovery, better query performance, greater data capacity, and more built-in functions. Version 6 also delivers more power for network computing with Java (TM) support for static SQL, further improvements to stored procedures, and connection pooling that permits Distributed Data Facility (DDF) to better support large client networks. Version 6 now has the capability to:

  • Enhance your data sharing availability with duplexing support for group buffer pools

  • Manage system utilization with predictive governing and statement cost estimation

  • Improve data I/O with the new buffer pool sizes of 8 and 16 KB

  • Use data spaces to cache your buffer pools and free up virtual memory in your DB2 address space
With Version 6, DB2 for OS/390, a leader for OLTP business solutions, works with S/390 (R) to provide the power, capacity, and reliability needed for today's demanding business intelligence (BI) and enterprise resource planning (ERP) solutions. DB2 UDB for OS/390 can hold the largest data warehouses, manage effective throughput for mixed workloads of decision support and operational transactions, and provide mission-critical data services for ERP solutions from suppliers such as SAP and PeopleSoft.

DB2 UDB Server for OS/390 is expanded to offer even more of the features you need to manage, access, and tune your DB2 environment. Version 5 offered DB2 Performance Monitor and Net.Data (TM). Now Version 6 also provides QMF (TM) and QMF for Windows (TM), DB2 DataPropagator (TM), DB2 Administration Tool, and DB2 Buffer Pool Tool as features of the server. Take advantage of these optional features and discover how they can help you to obtain even more from your DB2.

Shipment of the product to customers in the Quality Partnership Program will begin on September 25, 1998.

------------------------------

This announcement is provided for your information only. For additional information, contact your IBM representative, call 800-IBM-4YOU, or visit the IBM home page at: http://www.ibm.com



DESCRIPTION

DATABASE 2 (TM) Universal Database Server for OS/390 is IBM's super-server of choice for enterprise-wide data management in the twenty-first century. It is the premier relational database server solution for OS/390. The database server builds upon the momentum of previous releases furthering the themes of user productivity, network computing, high-performance, and continuous availability.



Universal Database

In response to customer and marketplace demands, Version 6 of DB2 UDB for OS/390 delivers universal database capabilities for:

  • Universally extensible data through object-relational extensions and triggers

  • Universal access through network computing improvements

  • Universal reliability and scalability through performance and availability enhancements

  • Universal applicability with improved support for OLTP, business intelligence, data warehousing, decision support, and enterprise resource planning applications

  • Universal manageability through the addition of data management, query, and tuning functions to the DB2 UDB Server for OS/390
Relational databases are extensively used for mission-critical applications. Building on the strength of the relational technology, this release delivers, through object-relational extensions, support for non-traditional object-oriented applications like multimedia. Very Large Objects (LOBs), User-Defined Functions, and User-Defined Distinct Data Types together support the handling of new, large, and complex data types needed in object-oriented applications like image, voice or multimedia. With the object-relational support delivered in Version 6, DB2 UDB for OS/390 becomes a database of choice for object-oriented application programming. In addition, this release of DB2 delivers triggers making it possible to convert the database from a passive to an active database.



DB2 Extenders (R)

DB2 UDB for OS/390 has the capacity required to handle and store these new complex data types. A LOB column can be up to 2 GB in length and a collection of all LOB values can be up to 4,000 TB. The DB2 Extenders build on the object-relational infrastructure of DB2. Each extender is a package of predefined UDTs, UDFs, triggers, constraints, and stored procedures that satisfies a specific application domain. With the extenders, you can store text documents, images, videos, and audio clips in DB2 tables by adding columns of the new data types provided by the extenders. The actual data can be stored inside the table or outside in external files. These new data types also have attributes that describe aspects of their internal structures, such as "language" and "format" for text data. Each extender provides the appropriate functions for creating, updating, deleting, and searching through data stored in its data types. You can now include these new data types and functions in SQL statements for integrated content searching across all types of data. Four DB2 Extenders are provided as part of the DB2 UDB Server for OS/390.

The DB2 Text Extender adds the power of full-text retrieval to SQL queries by making use of features available in DB2 that let you store unstructured text documents of up to 2 GB in databases. Text Extender offers DB2 users and application programmers a fast, versatile, and intelligent method of searching through such text documents. Text Extender's strength lies in its ability to search through many thousands of large text documents at high speed, helping you to find not only what you directly ask for, but also word variations and synonyms. You are not restricted to searching only in text documents stored in DB2 databases, you can also search in text documents stored in files.

The DB2 Image Extender defines a new data type and functions for images using DB2 UDB's built-in support for user-defined types and user-defined functions. It also exploits DB2 UDB's support for large objects of up to 2 GB and uses DB2 UDB triggers to automatically store and maintain attribute information for images. The DB2 Image Extender supports a wide variety of image formats, such as GIF (including animated GIFs), JPEG, BMP, and TIFF.

The DB2 Audio Extender defines a new data type and functions for audio using DB2 UDB's built-in support for user-defined types and user-defined functions. It also exploits DB2 UDB's support for large objects of up to 2 GB and uses DB2 UDB triggers to automatically store and maintain attribute information for audio objects. The DB2 Audio Extender supports a variety of audio file formats, such as WAVE, MIDI, MPEG1, and AU, and it can work with different file-based audio servers.

The DB2 Video Extender defines a new data type and functions for video using DB2 UDB's built-in support for user-defined types and user-defined functions. It also exploits DB2 UDB's support for large objects of up to 2 GB and uses DB2 UDB triggers to automatically store and maintain attribute information for video objects. The DB2 Video Extender supports a variety of video file formats, such as MPEG1, MPEG2, AVI, and QuickTime, and can it work with different file-based video servers.

Traditional business applications can also profit from the new UDTs and UDFs provided in DB2 UDB for OS/390 Version 6. Distinct types allow your business model to expand beyond DB2's built-in data types. For instance, a numeric field for currency value could be defined as a distinct type of currency, such as the euro or U.S. dollars. Now, your application logic can be guarded against erroneously summing euro currency with U.S. dollars. User-defined functions allow you to write your own extensions to the capability provided by SQL. UDFs are similar to stored procedures, written in high-level languages like COBOL, Java, C, and C++. They run in the stored procedures address space managed by the MVS (TM) Workload manager.

Triggers help you to bring application logic into the database. A trigger defines a set of actions to be executed when a specific SQL data change operation occurs. Uses for triggers include enforcing business rules, such as restricting the range of change for a data value, updating summary data when changes occur in another table, initiation of "alerts" outside the database, such as e-mail notification or job scheduling, or generating automatic values for newly inserted rows.



Universal Access

Version 6 delivers universal access for Web applications and other distributed network computing applications. In Version 5, DB2 added support for Java access via JDBC connectivity. Now combine the portability of Java application development with the performance advantage of using static Structured Query Language (SQL). SQLJ is SQL embedded in the Java programming language. SQLJ gives you more control over authorization checking, because now table privileges can be granted to the package owner. With dynamic SQL that JDBC uses, table privileges must be granted to each end user.

Distributed Relational Database Architecture (TM) (DRDA) includes support for three-part names. Applications using the private protocol to access distributed DB2 data on other MVS systems can now enjoy all the benefits of DRDA without having to make any program revisions.

Stored procedures are also enhanced for DB2 UDB for OS/390 Version 6. Easier management is afforded now, through the use of CREATE, ALTER GRANT, and REVOKE to manage your stored procedures. Additionally, a new register, CURRENT PATH, and the PATH bind option allow implicitly qualified stored procedure names in CALL statements. Stored procedures now permit nested calls by stored procedures and user-defined functions, and you can also use stored procedures for DB2 utility invocation. The Call Level Interface (CLI) introduced in Version 5 is enhanced to support the new object-relational functions:

  • Large objects
  • User-defined functions
  • User-defined data types
  • Newly built-in functions
CLI calls can now be issued from within a stored procedure. This can enhance portability of existing ODBC applications to the OS/390 platform.

DDF Connection Pooling can support thousands of TCP/IP or SNA connections to a small number of database access threads with much less storage than was required in previous releases.

The power of the SQL language is enhanced by the increase in SQL functions provided in Version 6. Now, about 100 new built-in functions are available to permit you to obtain results such as absolute value, modulus, square root, standard deviation, or calendar conversions as part of your SQL operation. This extended list of functions contributes to increased compatibility among the DB2 UDB family.



Universal Scalability, Reliability, Availability

In every release, DB2 provides more function to help you deliver mission-critical applications. With DB2 UDB for OS/390 Version 6, you can rebalance partitions more easily, run more queries and utilities in parallel, take advantage of more flexible page sizes, and use the Workload Manager to balance priorities of stored procedures and user-defined functions. Unbalanced table spaces can be adjusted by altering the partitioning key for affected partitions, the rest of the table space can remain available to your application while the altered partitions are reorganized. Utility improvements include parallelism for COPY and RECOVER utilities so that a list of image copies can be processed in parallel and thus reduce the elapsed time of these jobs. REBUILD INDEX is the new name for RECOVER INDEX. Now the RECOVER utility can rebuild indexes and table spaces from one utility statement. For table spaces with more than one index, DB2 can sort, build, and rebuild indexes in parallel, thus saving elapsed time for LOAD, REORG, and REBUILD INDEX. Further elapsed time savings can occur by including RUNSTATS within the execution of LOAD REPLACE, REORG TABLESPACE, REORG INDEX, and REBUILD INDEX. The in-line statistics eliminates the need for a separate RUNSTATS pass over the same data. A new option of REORG permits the discarding of data. The discarded data can be optionally saved to a file. You can avoid unnecessary execution of REORG by specifying threshold limits for relevant statistics from the DB2 catalog, which determine when the REORG will execute.

Restart and Recovery is improved by permitting some of the backout work to be postponed until after system restart. When many backouts are required at restart, this will contribute to a significantly faster restart than was available with prior releases. Also, a faster log apply process can improve restart and recovery times with fewer I/O operations and with reduced CPU time.

Your largest applications and data warehouse projects can benefit from the expansion in table size. Now individual tables can be defined to be up to 16 TB in size, adding an order of magnitude to your database capacity.

Query parallelism has been extended to include more types of queries. Now with Version 6, outer joins, queries on non-partitioned tables, and queries using IN list index access are eligible for parallel processing. Sysplex Query Parallelism has been enhanced to better balance workloads for Sysplexes comprised of unlike processor models. Also, re-evaluation at run-time can redistribute work when the number of members has changed or there are shortages of buffer pool resource.

Several query improvements will be especially valuable for data warehouse and business intelligence applications. Join processing for columns of different length but same data types has been improved. This will be especially important for joins of tables with a million or more rows. Both outer-join and star-join processing are improved and enhanced.

DB2 UDB for OS/390 Version 6 gives you more choices for sizing your data pages. In addition to the previously supported 4 and 32 KB page sizes, you can now choose from 8 and 16 KB page sizes. You can store your data more efficiently and balance the I/O costs for random access processing.

New with DB2 UDB for OS/390 Version 6 is support for buffer pools in data spaces. Now, you can move buffer pools out of the DB2 address space into data spaces. This provides relief for applications facing virtual storage constraints. DB2 is positioned to take advantage of any future changes that would permit S/390 processors to expand beyond 2 GB of real memory.



Server Features

Expanding upon the server features delivered in Version 5, QMF, QMF HPO, QMF for Windows, DB2 DataPropagator, DB2 Administration Tool, and DB2 Buffer Pool Tool are now features of DB2 UDB Server for OS/390. These optional, priced features add query, administration, and data management services that extend the power and utility of DB2. All of the optional, priced features are shipped as a time-limited "Try and Buy" with DB2 UDB for OS/390. Install and try these features and discover the value they bring to your DB2. A full-use license may be obtained by ordering the "Buy" feature that delivers the key that removes the time restriction. The features of DB2 UDB Server for OS/390 were developed to work with Version 6 and are tested to help assure they install and execute in an integrated environment. This can save you valuable install test time. For detailed descriptions of these optional features, refer to Optional Features of DB2 UDB Server for OS/390 section.



Year 2000

This product is Year 2000 ready. When used in accordance with its associated documentation, it is capable of correctly processing, providing, and/or receiving date data within and between the twentieth and twenty-first centuries, provided all other products (for example, software, hardware, and firmware) used with the product properly exchange accurate date data with it.



Open Blueprint (R)

DB2 UDB for OS/390 Version 6 provides the relational database function described in IBM's Open Blueprint. It provides the:

  • SQL industry-standard interface from the International Organization for Standardization (ISO)

  • SQL SQL CLI industry-standard from the ISO

  • Open Database Connectivity (ODBC) for Windows client systems interface from Microsoft (TM) Corp.
It supports the DRDA protocol from IBM to facilitate open, distributed, multivendor interoperability.



Open Enterprise

DB2 UDB for OS/390 Version 6 is developed at a lab where the quality management system is certified under ISO 9001.

DB2 UDB for OS/390 Version 6 conforms with the following national and international SQL standards:

  • Federal Information Processing Standards (FIPS) publication 127-2, Database Language SQL. FIPS publication 127-2 announces ANSI (American National Standards Institute) X3.135-1992 as the standard for SQL, so conformance with FIPS publication 127-2 also means conformance with:
    • ANSI X3.135-1992, Database Language SQL
    • ISO 9075-1992, Database Language SQL
    The above are referenced collectively as the SQL92 standard. DB2 UDB for OS/390 conforms to SQL92 Entry Level.
Additionally, the ODBC function included in DB2 UDB for OS/390 Version 6 is validated per the extensive ODBC Verification System (OVS) developed by INTERSOLV Inc., a recognized leader in ODBC technology. This test suite consists of approximately 4,000 test cases written to the Microsoft ODBC Version 2.5 specifications and represents broad usage of ODBC typical of many client server applications.



PRODUCT POSITIONING

DB2 UDB for OS/390 is the super-server of choice for the twenty-first century providing enterprise-wide data management for business intelligence, enterprise resource planning applications such as PeopleSoft and SAP R/3, and operational transaction processing. It offers large data capacity, high transaction performance, and extensive connectivity. It works with the DB2 UDB family to bring a full relational solution to the market place. DB2 supports transactions arising from CICS (R), IMS (TM) transaction management, MVS batch jobs, and via distributed connections from remote clients on numerous platforms.

DB2 UDB Server for OS/390 is the relational database server solution for OS/390. It combines the power and reliability of DB2 with additional features such as DB2 Performance Monitor, QMF, QMF for Windows, Net.Data, DataPropagator, DB2 Estimator for Windows, DB2 Administration Tool, and DB2 Buffer Pool Tool.

DB2 UDB for OS/390 extends the object-relational functions of DB2 UDB to the S/390 environment. Now the full power and capacity of OS/390 and Parallel Sysplex (R) are available to store object data, which can be delivered to applications originating on the S/390 or connected via DRDA from a remote requestor or from Internet and intranet applications.



STATEMENT OF GENERAL DIRECTION

DB2 table spaces larger than 1 terabyte will require the use of VSAM Extended Addressability for Linear Data Sets in DFSMS/MVS (R). This particular function is not currently available in DFSMS/MVS. IBM intends to develop and provide this function in a future release of DFSMS/MVS.

Trademarks

      OS/390, Net.Data, DataPropagator, QMF, DATABASE 2, MVS,
      Distributed Relational Database Architecture, and IMS are
      trademarks of International Business Machines Corporation in
      the United States or other countries or both.
      DB2 Universal Database, System/390, DB2, S/390, DRDA, OS/2, DB2
      Extenders, Open Blueprint, CICS, Parallel Sysplex, and
      DFSMS/MVS are registered trademarks of International Business
      Machines Corporation in the United States or other countries or
      both.
      Windows and Microsoft are trademarks of Microsoft Corporation.
      Windows NT is a registered trademark of Microsoft Corporation.
      Java is a trademark of Sun Microsystems, Inc.
      UNIX is a registered trademark in the United States and other
      countries exclusively through X/Open Company Limited.
      Other company, product, and service names may be trademarks or
      service marks of others.



SUPPLEMENTAL INFORMATION



OPTIONAL FEATURES OF DB2 (R) UDB SERVER FOR OS/390 (TM)

DB2 UDB Server for OS/390 expands the offering of features that combine with DB2 to enhance query access, management, and replication of your data. Features new in Version 6 include:

  • QMF (TM), QMF/HPO, and QMF for Windows (TM)
  • DB2 DataPropagator (TM) for OS/390
  • DB2 Administration Tool
  • DB2 Buffer Pool Tool
These features are in addition to the features added in Version 5:
  • DB2 Performance Monitor
  • Net.Data (TM)
  • DB2 Estimator
Following is a detailed description of each of these features.



DB2 QMF Feature

IBM Query Management Facility (QMF), the tightly integrated, powerful, reliable query and reporting tool for the IBM DB2 relational database Management System Family, provides new capabilities for the workstation environment and enhancements for the mainframe that help you access and present mission-critical data better than ever before. QMF Version 6 enables you to work with data all over the enterprise -- from DB2 for OS/390 to DB2 for VSE and VM to workstation servers running OS/2 (R), Windows NT (R), AIX (R), and other UNIX (R) operating systems to massively parallel processors. QMF coupled with the DB2 DataJoiner (R) product allows access to non-relational and other vendor data sources as well.

The QMF Family consists of the following integrated tools:

  • QMF for OS/390
  • QMF High Performance Option (HPO) Feature
  • QMF for Windows Feature
They offer a total solution that includes accessing large amounts of data, sharing central repositories of queries and enterprise reports, and/or implementing tightly controlled distributed or client/server solutions. They also provide for report publishing to the Web for viewing with your favorite Web browser.

The components in QMF HPO Version 6 (QMF HPO/Manager and QMF HPO/Compiler) were available as separately orderable QMF features in QMF Version 3.3. They are no longer available as separately orderable features in Version 6. QMF HPO/Complete is now simply called QMF HPO and includes the QMF HPO/Manager, QMF HPO/Compiler, and QMF for Windows as one comprehensive feature.

The QMF HPO/Compiler lets you convert automatically queries and reports into efficient programs in OS/VS COBOL or COBOL II. This reduces CPU consumption, DB2 catalog contention, DB2 Optimizer overhead, and security concerns as converted programs use static Structured Query Language (SQL) in place of dynamic SQL.

The QMF HPO/Manager consists of a group of functions that improves governing and object management capabilities, including a preemptive governor to analyze QMF queries. The governing capabilities allow you to establish controls that protect production applications, while delivering "on demand" information. Many governing parameters are included, such as time of day, day of week, maximum number of rows to fetch, allow/disallow SQL verbs and QMF commands, and controlling resource consumption based on the use of QMF commands and SQL statements.

For customers with DB2 databases of many sizes, QMF for Windows provides a Windows-based, point-and-click query tool that provides many benefits, including an intuitive GUI "quick start" user interface. Using QMF for Windows, you can automate tasks and develop powerful native Windows applications. The tool includes a robust, Windows-based API to automate database querying, updating, and report distribution tasks so you can centralize control over resource consumption. QMF for windows also provides support for TCP/IP, static SQL, create and edit QMF forms and procedures, and a full-screen table editor for updating enterprise data.

QMF for Windows is available in three distinct ordering configurations:

  1. Included with the QMF HPO feature at no additional charge

  2. As a companion feature to provide workstation Client Access (TM) to the QMF feature

  3. As a direct feature of DB2 for customers who do not require QMF for OS/390
QMF Version 6 includes enhancements and support for:
  • DB2 Universal Database (R), including TCP/IP for DB2 for OS/390 Version 5 and DB2 UDB for OS/390 Version 6

  • DB2 Version 6 Predictive Governor with a warning prompt to QMF users, or an error message, indicating the query could not be run as it exceeded the resource limit

  • Additional DB2 Special Registers that allow QMF to maintain the same set of special registers values during a QMF-DB2 server connection for all updatable special registers on each DB2 product supported

  • ISPF LIBDEF service that can now be used to allocate QMF program libraries

  • New edit code (zero-suppression) to replace zeros with blanks in a QMF report

  • LE/370 for QMF user-written edit codes

  • User control of the QMF scroll amount default

  • An enhanced SAVE command that enables QMF to default to the current object type (query, form, procedure)

  • Column default for CHANGE mode in the QMF Table Editor

  • The ability to erase an alias name

  • Sample applications and examples in the QMF publications, updated and improved

  • Euro currency symbol when formatting numbers

  • The ability to use two different currency symbols in the same report
QMF For Windows Version 6 enhancements include support for:
  • DB2 stored procedures

  • DB2 for OS/390 server load balancing

  • DB2 Version 6 predictive governor so you can set QMF for Windows to block queries that exceed the thresholds set by the DB2 administrator

  • Creating and running QMF linear procedures (QMF host and Windows)

  • Command line parameters, which allow you to more easily automate start-up procedures and integration with other applications, such as Visual Warehouse (TM)

  • Enhanced object tracking, which allows you to view a detailed run history for all QMF objects to locate unused objects, determine frequently accessed data sources (tables/columns), and spot potential problem areas

  • Web publishing, which allows you to convert a standard QMF form to an HTML format

  • Specialized form variables for HTML publishing, which lets you build advanced Web features into your QMF report, such as hyperlink, e-mail link, and embedding images in reports: includes report preview feature

  • Global Variables for use in QMF for Windows procedures, forms, queries, and session variables

  • QMF Form calculations (requires 32-bit QMF for Windows and IBM Object REXX)

  • The most commonly used attributes of form components, now grouped together on a new form dialog for ease of use

  • Custom edit codes that can be added to QMF (a sample user edit code routine that formats a social security number supplied)

  • Euro currency symbol

  • Control of formatting of data and time values in your QMF reports

  • Multiple formatted reports displayed on your desktop at the same time, while performing other application functions

  • Control over what tables and QMF objects are displayed when users view lists

  • Import/Export data using the PC IXF format, allows you to use your QMF query results to create new (or append to existing) DB2 tables

  • Users to change their passwords from within QMF for Windows

  • Users to locate, run, create, and save reports from within Windows Explorer (32-bit only)
QMF for Windows Version 6 is now only available on CD-ROMs.

For more information on the QMF Family of integrated tools, including a QMF Family demo and a QMF for Windows Try and Buy download, access the QMF Web site at:



DB2 DataPropagator Feature

DB2 DataPropagator, Version 6 provides read-only, update-anywhere, and on-demand replication between relational sources and targets and defines the architecture for the comprehensive IBM Data Replication solution.

The DB2 DataPropagator consists of the following autonomous components/programs:

  • Administration (Control Center)
  • Capture
  • Apply
The ADMINISTRATION component for the DB2 DataPropagator, Version 6 is called the Control Center. The Control Center is the integrated administration tool for DB2 Universal Database, Version 5 and includes replication administration. The Control Center runs on OS/2, Windows NT, and Windows 95 platforms and does not require a local DB2 database. The Control Center is used to:
  • Define tables as sources, called replication sources

  • Define views and joins views as replication sources

  • Define target table definitions, called replication subscriptions

  • Clone replication subscriptions to other servers

  • Remove replication sources or subscriptions no longer needed
Whenever you submit a replication request from the Control Center, such as defining a replication source, the processing information is generated as SQL statements. You can choose to run the statements immediately, or you can save the SQL statements to a plain ASCII file, which you can edit and run at a later time from a replication folder object in the Control Center.

Deferred SQL files allow you to customize the replication tasks for your shop or application and give you the flexibility as to when and how you run the SQL files.

The CAPTURE component captures changes made to data in tables defined as replication sources by reading the database log or journal -- without any changes and asynchronously to business applications. The captured changes are placed in staging tables. DB2 DataPropagator Capture for OS/390, Version 6 supports DB2 for MVS (TM), Version 3.1, or later. However, the following functions are available with DB2 for MVS, Version 4.1, or later:

  • Reading data from archived logs in addition to active logs
  • Compressed DB2 data tables as sources
  • DB2 data sharing in a Sysplex environment
The APPLY component reads the changed data, previously captured and stored in a staging table, and applies it to the target tables. Apply components can also read data directly from source tables, for example, for a full refresh. Supporting update and refresh copying provides greater flexibility and automation in a replication environment. The Apply component also enhances the data to your specifications as it copies data to the targets. You can exploit the full power of SQL to:
  • Create new columns
  • Summarize data
  • Translate data
  • Join data
You can define run-time processing statements using SQL statements and stored procedures before and after the Apply program processes the replication subscription. The run-time processing statements can be run at the source server before the answer set is fetched, and at the target server before and after the answer set is applied. The stored procedures use the SQL CALL statement, newly supported by IBM Replication, without parameters. The run-time procedures are executed together in a single unit-of-work. Acceptable SQLSTATEs can be defined for each processing statement as well.

The Apply component allows you to create:

  • Read-only copies
    • User copy tables, which represent source data at a particular point in time

    • Point-in-time tables, which represent source data at a particular point in time plus some overhead columns

    • History tables

    • Staging tables, which can be used as a source for further copies, without recapturing changes, supporting a consistent data environment and providing flexibility in data distribution across the network
  • Updatable copies
    • Replica tables -- updates to a Replica table are applied automatically to the original source table of the Replica, provided no conflicts are detected.

      The Apply component, running at the replica site, detects update conflicts after they occur during the subscription cycle. When transactions are rejected, the Apply compensates the transactions at the replica site. During this process, the Apply inserts rejection codes for every rejected transaction in the control table. Conflict detection is provided at three levels: no detection, standard detection, and enhanced detection, specified while defining the replication source. When a conflict is detected and compensated, the replication subscription is considered failed. All related transactions are checked for conflicts and are also rejected.

      After the Apply completes the subscription cycle, the ASNDONE exit notifies you the cycle is complete and whether there were conflicts. ASNDONE user exits can be used to manage recovery from conflicts.

You can subset data for distribution through column and row specifications, replicating only the data you need. Unique to DB2 DataPropagator is the ability to subselect for joins and unions, allowing you to subset according to a value not in the table being replicated. This can be a key requirement when replicating to mobile laptops from normalized databases where most values are not redundantly stored.

Finally, an Apply instance can process many subscriptions at a single site. Multiple Apply instances can run concurrently at different sites/platforms, each processing different numbers and types of subscriptions from the same source. Each subscription can have different definitions, refresh criteria, and timing.

The On-Demand replication capability offers a solution to the challenge of infrequent and unpredictable connections present in the mobile computing community. Data transfers are initiated from the mobile unit where control should be based. This implementation allows downloading from a central server (pulling), or uploading for consolidated processing (pushing).

DB2 DataPropagator Version 6 offers a highly efficient architecture for automatic capture and asynchronous propagation of data changes to the DB2 family of databases. It contains a high-performance log-based change-capture component that captures all DB2 updates without response-time impact or requiring any user application changes. The user can make powerful data enhancements using standard SQL including multitable joins and the use of stored procedures. There is support for full refresh and update change replication, including update of denormalized copies. DataPropagator supports seamless interoperation with DataPropagator Non-Relational (IMS (TM)), DataRefresher (TM), DataJoiner, and Lotus NotesPump (TM) products to deliver robust, versatile replication among IMS, DB2, Oracle, Sybase, Informix, Microsoft (TM) SQL Server, and Lotus Notes (R). There is easier, intuitive administration from the DB2 Universal Database Control Center running on OS/2, Windows NT, and Windows 95 platforms. Support exists for subscription sets allowing for transaction consistency. DB2 view-based replication, including join views, is supported as well as event-driven and continuous replication. Also supported is update-anywhere replication with robust conflict detection and compensation, along with on-demand replication for occasionally connected and mobile systems. DB2 Catalog replication is now supported for speeding up of ODBC-based queries.

New with Version 6 for DB2 DataPropagator is the ability to replicate large objects (BLOB, CLOB and DBCLOB) as well as replication for ROWID, a new data type introduced in DB2 UDB for OS/390. Installation of DataPropagator is easier and integrated using the DB2 installer. Support for a mixed data sharing environment consisting of different versions of DB2 is now included as well as better resource utilization for continuous replication scenarios. Additional capturing choices have been added allowing you to capture changes when any column changes or only when one of the registered columns changes. There is improved scalability, performance, and concurrency along with support for many popular versions of DB2 including DB2 UDB for OS/390 Version 6, DB2 for OS/390 Version 5.1, and DB2 for MVS/ESA (TM) Version 4.1.



DB2 Administration Tool (DB2 Admin) Feature

Use DB2 Admin to:

  • Display and interpret objects in the DB2 catalog
  • Execute dynamic SQL statements
  • Generate JCL and run DB2 utilities
  • Issue DB2 commands against databases and table spaces
  • Manage SQLIDs
  • Perform complex performance and space utilization queries
  • Simplify system administration functions
As the number and complexity of DB2 applications and systems increase, having the right DB2 tools has never been more important.

DB2 Admin is the right tool to help you get the most from your DB2 system. It's comprehensive set of database management functions helps DB2 systems personnel efficiently and effectively manage your DB2 environment by:

  • Saving time in DB2 administration
  • Simplifying routine day-to-day DB2 tasks
  • Increasing knowledge and understanding of your DB2 system
DB2 Admin supports the functionality of DB2 Version 6 by providing panels and options allowing you to quickly see new pertinent catalog information. DB2 Admin works on a data sharing group member level.

DB2 Admin provides usability enhancements, lower overhead costs, better error recovery, and more extensive online help. Highlights include:

  • Calculation and display of the hit ratios of the buffer pools
  • Display of all indexes and index columns for a table
  • Improved DB2 Admin print capabilities
  • EXPLAIN of long SQL statements
  • Reuse of DB2 commands
  • User initiated stopping of SQL processing
DB2 Admin offers a robust set of database management functions for DB2 MVS systems personnel. As your enterprise expands its DB2 usage and systems environment, you may need to manage multiple complex DB2 systems, perhaps in several locations. DB2 Admin simplifies database administration and allows you to manage these systems more efficiently and effectively.

DB2 Admin is an easy-to-use ISPF panel driven tool, which overviews DB2 system tables and provides relevant DB2 catalog information in a logical format. Designed to be an interactive and intuitive tool to learn and use, DB2 Admin integrates with DB2 utilities and simplifies creation of DB2 utility jobs. Among DB2 Admin's strengths is the extensive support to simplify understanding and analysis of the DB2 catalog and allow you to intelligently act on the information presented. The abundant DB2 catalog query capabilities in DB2 Admin include:

  • Predefined select criteria (predicates) for most commonly used SELECTs on the catalog

  • DB2 objects authorization and relationships can be shown

  • GRANT and REVOKE on the objects

  • BIND, REBIND, and FREE for selected plans and packages

  • Display of the static SQL for selected Database Request Modules (DBRMs) and packages
DB2 Admin offers new panels and options for DB2 Version 6 including:
  • Partition independence
  • Type 2 indexes
  • Row locking
  • Maximum number of user locks
  • Read through locks
  • Parallel query processing
  • DFSMS (TM) Concurrent Copy
  • Stored procedures
  • Outer Join
  • Table check constraints
  • User defined default values
  • Cancel thread
  • Dynamic rules BIND option
  • Restrict on DROP
  • New REFERENCES privilege
DB2 Admin's power-packed functionality still includes:
  • Display of the DDL for existing views

  • Generation of DB2 utility jobs for selected objects (COPY, REORG, RUNSTATS for selected TABLESPACEs)

  • Support of DB2 Distributed Database Facilities (DDF) including remote DB2 catalog support, ALIAS support, and Communications Data Base (CDB)

  • Catalog functions optionally running on tables containing a copy of the system catalog

  • Functions for administration of the Resource Limit tables (RLIMIT)

  • Dynamic SQL statement execution without knowing the exact SQL syntax

  • COMMIT/ROLLBACK issued before each display

  • Ability to be extended to display/update any DB2 table (sample function provided with the product)

  • Ability to issue any DB2 command (commands passed to IFI and the result shown in ISPF browse)

  • A quick EXPLAIN function that can show the inserted rows in the PLAN_TABLE

  • Ability to save results of a SQL SELECT as ISPF tables

  • Ability to (re)display the saved tables

  • Ability to print selected columns from the ISPF tables
With the power-packed capabilities of DB2 Admin, there's never been a better time than now to consider ordering DB2 Admin.



DB2 Buffer Pool Tool Feature

While DB2 online performance monitors can tell you when something is wrong, it may be a difficult and time-consuming effort to determine what is the right corrective action to take. Take the guesswork out of tuning and avoid making costly mistakes with DB2 Buffer Pool Tool.

DB2 Buffer Pool Tool helps performance analysts evaluate tuning alternatives and achieve optimal performance with minimal effort. Accurate tuning of buffer pools is one of the single, most-critical factors to improving DB2 performance and getting the most out of your system resources. By now, we all know the best I/O is no I/O; however, eliminating I/O can be a challenging task.

DB2 Buffer Pool Tool gives you comprehensive statistical data and easy-to-read reports and graphs for all pools and objects. The type of information provided by DB2 Buffer Pool Tool is not available from any other monitor or tool in the industry.

DB2 Buffer Pool Tool provides the ability to simulate the effects of changing pool sizes and thresholds. It can also help you predict the effects of moving DB2 objects into different pools or into new pools that do not currently exist. This "what if" analysis allows you to make expert decisions on maximizing resource utilization and reducing elapsed time of your DB2 transactions through effective buffer pool usage. DB2 Buffer Pool Tool is the ultimate tuning aid. If you need a better way of realizing performance improvements, then consider the advantages DB2 Buffer Pool Tool can provide. DB2 Buffer Pool Tool makes it easier to maximize system resources and optimize DB2 performance. Eliminate I/O and realize better utilization of your existing, expanded, and real storage with DB2 Buffer Pool Tool. DB2 Buffer Pool Tool allows you to reduce CPU cycles, improve DB2 transaction and batch job elapsed times, and save money.

The DB2 Buffer Pool Tool provides the following advantages:

  • Low Overhead

    The last thing you want to have is a performance tool that causes a performance problem because it uses too much overhead in collecting statistical information. The advantage of DB2 Buffer Pool Tool is it uses the IFI interface and its own data collection facility to avoid the costly overhead associated with other tools. Further, DB2 Buffer Pool Tool easily processes a statistically meaningful data collection interval (more than 30 minutes) other trace facilities cannot handle efficiently.

  • Unique Information

    No other DB2 tool provides the level and type of statistical analysis available in DB2 Buffer Pool Tool. DB2 Buffer Pool Tool shows you exactly how the pool and objects are used. The extensive statistics include:

    • System and Application Hit Ratios
    • Getpage Activity and I/O Rates
    • Random Access Activity
    • Prefetch (including Dynamic and List) Access Activity
    • Read and Write I/O Activity
    • Average and Maximum I/O Elapsed Times
    • Random Page HiperPool Retrieval
    • Average Page Residency Times
    • Average Pages/Write
    In addition, the statistical analysis is ranked for each object within each pool. Statistical object usage analysis is provided by Plan and AUTHID.

  • Expert Knowledge

    Although this tool provides the most comprehensive set of data related to DB2 activity available today, DB2 Buffer Pool Tool synthesizes, summarizes, and analyzes this information so you won't suffer from "information overload" or have "analysis paralysis," which is common with other types of tuning aids. In addition, you can optionally adjust threshold to bypass reporting for objects having very low usage rates.

    DB2 Buffer Pool Tool makes it easy to clearly see which objects are the poorest and best performing and the impact each is having on its current pool. Look no further than DB2 Buffer Pool Tool output to determine which objects will obtain the greatest benefit from changes.

    Not only does DB2 Buffer Pool Tool provide easy to read reports and graphs, it even offers general tuning advice based on information gathered from your environment. For example, these recommendations can range from separating indexes from table spaces to moving Sort Work objects into their own pool or to lowering virtual write threshold.

    Additionally, as you move to a data sharing environment, DB2 Buffer Pool Tool can be invaluable in providing initial sizing specifications for the Coupling Facility structures.

  • Simulation Analysis

    DB2 Buffer Pool Tool gives you powerful simulation capabilities to determine how to best optimize memory usage, eliminate I/O, and improve response times. DB2 Buffer Pool Tool turns tuning into a scientific process by allowing you to perform many "what if" analyses to evaluate various scenarios.

    DB2 Buffer Pool Tool is a superior solution since it can:

    • Predict system performance levels at varying pool sizes

    • Predict improved object performance within each pool

    • Model VPSEQT or HPSEQT threshold adjustments
    Further, DB2 Buffer Pool Tool is more effective and accurate than pool isolation tuning techniques because it shows the interaction between multiple objects within a pool.

    DB2 Buffer Pool Tool gives you the advantage to completely model the effects that proposed changes may have without impacting the operating DB2 system. Up to eight simulation sizes for a pool can be done with one pass of the data.

DB2 Buffer Pool Tool gives you the expert knowledge and reduces the time and effort necessary to effectively tune your environment. Make informed decisions with confidence regarding performance improvements.



DB2 Performance Monitor (DB2 PM) Feature

The DB2 PM Feature enables you to monitor, analyze, and optimize the performance of DB2 UDB for OS/390 Version 6 and its subsystems. It includes an online monitor to provide an immediate "snap-shot" view of DB2 for OS/390 activities and to allow for exception processing while the system is operational. In addition, it offers a history facility to view events that happened recently and in a more distant past, a wide variety of customizable reports for an in-depth performance analysis, and an EXPLAIN function to analyze and optimize SQL statements.

Enhancements to DB2 PM Feature for Version 6 include:

  • Comprehensive support of all DB2 Version 6 changes

    The DB2 PM Feature supports all instrumentation, catalog, and PLAN_TABLE changes, introduced in DB2 Version 6. With DB2 PM, you can rely on a timely and comprehensive support of performance evaluation and analysis.

The DB2 PM Feature is the right solution for you, even if you have an environment of multiple DB2 releases. Ensuring protection of your investment, DB2 PM fully supports instrumentation, catalog, and PLAN_TABLE data from:
  • DB2 UDB for OS/390 Version 6 (5645-DB2)
  • DB2 for OS/390 Version 5 (5655-DB2)
  • DB2 for MVS/ESA Version 4 (5695-DB2)



Net.Data Feature

The new Net.Data Version 2 feature provides high performance access to DB2 data from the World Wide Web. Net.Data for OS/390 Version 2 exploits the S/390's capabilities as a premier platform for electronic commerce and Internet technology.

Businesses are finding many reasons to provide Internet and intranet connectivity from the World Wide Web to their business information. Businesses want to build business-critical Web applications to reach the global marketplace. With Net.Data, your business can have interactive Web sites with dynamic data from the sources you have in your business today: relational data on OS/390 and a variety of other platforms. Whether you are building interactive catalogs of products, allowing customers to track orders, or conducting electronic commerce, your Net.Data-driven application gets your data to (and from) a worldwide audience.

Net.Data delivers a powerful framework for Web applications. In addition to connecting to diverse data sources, Net.Data provides for high performance, robust application development function, and exploitation of existing business logic.

Net.Data provides native access to the data you need in your business environment: DB2 on all platforms, other heterogeneous data sources through DB2 DataJoiner, and HFS flat file data. In addition, Net.Data can call DB2 stored procedures for additional performance from static SQL.

Net.Data has extensive application development functionality, including a rich macro language, conditional logic, HTML and VRML support, and HTML variable substitution. Net.Data for OS/390 Version 2 has enhancements for performance, scalability, and application development.

Refer to the Net.Data Web pages for documentation, sample programs, and customer applications. You can find the Net.Data home page at:



DB2 Estimator Feature

The DB2 Estimator Feature delivers application performance evaluation. DB2 Estimator provides an easy-to-use capacity planning tool helping database administrators, capacity planners, and application programmers test the feasibility of system and design changes before investing more time and money. By providing performance estimates for DB2 UDB for OS/390 Version 6 SQL and utilities, the user can perform "what if" scenarios for feasibility studies and determine if utility processing will fit the available batch window.

In support of DB2 UDB for OS/390 Version 6, DB2 Estimator improvements include support for the new object-relational functions:

  • Triggers
  • Large objects
  • User defined functions and types
  • New utilities and utility keywords
  • New built-in functions
The usability of DB2 Estimator is extended to include:
  • Support for DB2 Versions 5 and 6 performance estimates

  • SQL Advanced Override window enhancements

  • Table Expression support

  • Multitable utilities, which permit you to operate Estimator utility definitions on multiple tables in a single pass

  • Bulk SQL item parsing, which allows you to process all of the SQL items in a sub-project in a single pass
Refer to the DB2 Estimator Web page at: Customers can contact IBM regarding Estimator at this e-mail address:
    estimate@vnet.ibm.com



TECHNICAL INFORMATION



Specified Operating Environment

This product uses only existing attachment interfaces.

Hardware Requirements: DB2 UDB for OS/390 Version 6 operates on any processor supported by OS/390 Version 1 Release 3, or later. The processor must have enough real storage to satisfy the combined requirements of DB2, of OS/390, of the appropriate Data Facility Product, appropriate access methods, telecommunications, batch requirements, and other customer required applications.

OS/390 will run on the following hardware:

  • All models of the S/390 Parallel Enterprise Servers or S/390 (R) Parallel Transaction Servers (IBM 9672)

  • All models of the ES/9000 (R) Processor Unit 9021, the 9121, or the 9221

  • PC Server System/390 (R) or RS/6000 (TM) with S/390 Server-on-Board

  • S/390 Multiprise (TM) 2000
The configuration must include sufficient I/O devices to support the requirements for system output, system residence, and system data sets. Sufficient direct access storage (DASD) must be available to satisfy the user's information storage requirements and can consist of any direct access facility supported by the system configuration and the programming system.

Auxiliary Storage: DB2 is independent of DASD and tape device type. The customer can use any magnetic or tape device supported by the data facilities component of DFSMS/MVS (R) for the DB2 data sets. The following DB2 data sets are supported by the following device types:

  • Active recovery log data sets: DASD
  • Archive recovery log data sets: DASD, tape
  • Image copy data sets: DASD, tape
  • Bootstrap data sets: DASD
  • User data sets: DASD
  • DB2 catalog data sets: DASD
  • Work data sets (for utilities): DASD, tape
If these data sets are on DASD shared with other MVS systems, the customer should use global resource serialization in order to prevent concurrent access by more than one MVS system.

The minimum DASD space requirements (based on installing DB2 using the panel default values) is approximately 400 MB. Users need additional DASD space for their data.

If dual logging is used and tape is being used for the log archiving device, at least two tape drives are needed.

Data Communications Devices: DB2 operations can be controlled from:

  • The system console
  • Authorized IMS/ESA (R) Transaction Manager terminals
  • Authorized CICS (R) terminals
  • TSO terminals (by authorized users)
For the data communication devices supported by IMS/ESA Transaction Manager, CICS, and TSO, refer to the manuals for these products.

Function Dependent Hardware Requirements

  • Copy Index/Recover Objects

    To use the COPY utility to take DFSMS concurrent copies of indexes, the 3390 Model 3 or 3990 Model 6 controller at the extended platform attached to the DASD is required.

  • Group Buffer Pool Duplexing

    CFLEVEL=5 coupling facility architecture support.

  • DB2 Installer requires:
    • 20 MB disk memory on the target drive, and 1 MB of disk space for each subsystem defined
    • Monitor capable of displaying 1024 by 768 resolution
  • Visual Explain for DB2 for OS/390 Version 6 requires:
    • High-resolution monitor
    • Workstation with OS/2 or Windows NT 4.0
    • Approximately 8.5 MB of hard disk space
  • Workstation-Based Analysis and Tuning requires:
    • High resolution monitor
    • Workstation with OS/2 Warp 3 or Windows NT 4.0
    • Approximately 20 MB of hard disk space
  • DB2 Performance Monitor Feature requires:
    • For the host-based Online Monitor, a display station supported by Interactive System Productivity (ISPF)

    • For the host-based graphics facility, an IBM color graphics display station, or equivalent, supported by Graphical Data Display Manager (GDDM (R))

    • For the workstation-based Online Monitor:
      • High-resolution monitor
      • Workstation that supports OS/2 Warp 3 or Windows NT 4.0
      • Approximately 20 MB of hard disk space
  • QMF for DB2 for OS/390 requires:
    • DASD or Tape

      QMF can access all storage devices supported by the operating system and the supported databases.

      QMF uses disk devices for the following objects in the OS/390 environment:

      • Spill file data set, which holds the data for the report a user views (but only when the data does not fit in virtual storage)

      • Database objects managed by DB2

      • Import data sets that hold data, queries, forms, or procedures

      • Export data sets that hold data, queries, forms, procedures, reports, or charts

      • Temporary files created for editing a SQL query or procedure

      • Print and debug (trace) data sets

        Optionally, QMF can use tape devices for the print and debug (trace) data sets.

    • Data Communication Devices

      QMF can display on all terminals supported by GDDM.

    • Virtual Storage Considerations

      The storage requirements in this section are based upon development laboratory measurements using the following releases of support products (storage requirements may vary when using versions or releases other than those shown below):

      For TSO:

      • ISPF Version 4
      • GDDM Version 3
      • DB2 UDB for OS/390 Version 6
      For CICS:
      • CICS Version 3
      • GDDM Version 3
      • DB2 UDB for OS/390 Version 6
      In the OS/390 environment, minimum storage for users to execute QMF queries and hold QMF report data is between 0.5 MB and 1.0 MB. As an example, if you run in a standard TSO environment with ISPF and GDDM, you need about 6.0 MB of storage. The generation of complex reports, or the use of TSO CLIST commands to run other functions within a QMF session, might require additional storage. The use of graphics (for example, CHART) requires additional storage.

      The MVS/ESA 31-bit virtual storage addressing capability allows most QMF modules to reside in the EPLPA or PLPA.

      If QMF modules are placed in the OS/390 EPLPA/PLPA, up to 2.8 MB can be located in the EPLPA, and 52 KB can be located in the PLPA, decreasing the demand for space in the user's region. The size of the region may be further reduced by placing ISPF and GDDM into the PLPA, which increases the common area accordingly.

      CICS Environment

      QMF runs as a conversational transaction in CICS and there are multiple users of QMF in the same CICS address space. Each user that runs a QMF transaction requires at least 1.0 MB of storage from the CICS region. All but 24 KB can be allocated to storage above 16.0 MB. A single copy of the QMF module, up to 2.7 MB, can be placed in the EPLPA or within the CICS region above 16.0 MB, and 52 KB can be located in PLPA or within the CICS region below 16.0 MB.

    • QMF for Windows

      Host hardware requirements are those required to run the supported DB2 platforms.

      Workstation hardware requirements are those needed to run the Windows software, as described in the Software Requirements section.

      QMF for Windows requires approximately 10 MB of free disk space on each Windows workstation, and about the same memory as needed by a typical Windows suite application.

Software Requirements

Operating System and Support Programs: For an OS/390 environment, DB2 requires the function provided by the following licensed programs or their equivalents; later versions or releases of any product are acceptable.

  • OS/390 Version 1 Release 3 Base Services (5645-001)

  • OS/390 Version 1 Release 3 Application Enablement optional feature for DFSORT (TM)
Optional Programs: Following are the optional program products for use with DB2 UDB for OS/390 Version 6. Unless otherwise specified, the release shown for a product and any follow-on release, currently available, is acceptable.
  • Connectivity

    In addition to any DRDA (R) compliant database management systems, DB2 for OS/390 Version 6 supports the following IBM relational database products:

    • DB2 Universal Database Version 5 with DB2 Connect (R)

    • DB2 DataJoiner Version 2 Release 1

    • Operating System/400 (R) (OS/400 (R)) Version 4 Release 1 with DB2/400 (5769-SS1)

    • DB2 Server for VM and VSE Version 5 (5648-158)

    • Net.Data for OS/390 Version 2, a feature of DB2 UDB for OS/390 Version 6 for connectivity to DB2 from the web
  • Capacity Planning

    The following capacity planning tool works with DB2 data to estimate application feasibility, to model application cost and performance, and to estimate required CPU and I/O capacity:

    • DB2 Estimator for Windows, a feature of DB2 for OS/390 Version 6
  • Transaction Management

    The following transaction management products work with DB2:

    • Information Management System (IMS)
      • IMS/ESA Version 6 (5655-158)
      • IMS/ESA Version 5 (5695-176)
    • Customer Information Control System (CICS)
      • CICS Transaction server for OS/390 Release 1 (5655-147)
      • CICS/ESA (R) Version 4 (5655-018)
  • Query Support
    • Query Management Facility (QMF), a feature of DB2 UDB for OS/390 Version 6
    • DB2 Extenders (R), a feature of DB2 UDB for OS/390 Version 6
  • Application Development
    • VisualAge (R) PL/I Version 2 (Refer to Software Announcement 297-372 dated September 23, 1997)

    • VisualAge COBOL Version 2 (Refer to Software Announcement 297-371 dated September 23, 1997)

    • VisualAge Generator Version 3 (Refer to Software Announcement 297-395 dated September 30, 1997)

    • Application System (AS) Version 3 (5648-018)
  • Operational Support
    • DATABASE 2 (TM) Performance Monitor (DB2 PM), a feature of DB2 UDB for OS/390 Version 6

    • OS/390 Version 1 Release 3 System Services, an optional feature for DFSMS features

    • OS/390 Version 1 Release 3 Security Server, an optional feature for RACF (R)

    • NetView (R) Version 2 Release 4 (5685-111) or NetView Version 3 for MVS/ESA (5655-007)

    • Performance Reporter for MVS Version 1 Release 2 (5695-101)

    • Library Readers included on the CD-ROMs for BookManager (R) books
  • Replication Support
    • DataPropagator Relational Apply for MVS Version 5 Release 1 (5655-A22) or DB2 DataPropagator Apply for OS/390, an optional feature of DB2 for OS/390 Version 6

    • DataPropagator Relational Capture for MVS Version 5 Release 1 (5655-A23) or DB2 DataPropagator Capture for OS/390, an optional feature of DB2 for OS/390 Version 6

    • DataPropagator Non-Relational MVS/ESA Version 2 (5696-705)

    • DataRefresher Version 1 (5696-703)
  • Database Administration and Systems Management Support
    • DB2 Automated Utility Generator (DB2AUG) Version 1 Release 2 (5695-077)

    • DB2 Administration Tool for OS/390 Version 6, a feature of DB2 UDB for OS/390 Version 6

    • DB2 Buffer Pool Tool for OS/390 Version 6, a feature of DB2 UDB for OS/390 Version 6
  • Programming Languages

    The following IBM Programming Languages in addition to Assembler have an interface to DB2:

       ADA   ADA/370 Version 1 Release 3 (5706-292) and IBM ADA Runtime
             Library 370 Version 1 Release 3 (5706-295) with SQL MP
             feature for DB2.
       APL2 (R) APL2 Version 2 Release 2 (5688-228); APL2 Application
             Environment Version 2 Release 2 (5688-229)
       BASIC BASIC/MVS Version 1 Release 2 (5665-948)
       C     AD/Cycle (R) C/370 (TM) Compiler Version 1 Release 2
             (5688-216); IBM C/370 Library Version 2 Release 2 (5688-188)
       C++   OS/390 Version 1 Release 3 Application Enablement, optional
             feature
             for C/C++
       COBOL COBOL for MVS and VM Version 1 Release 2 (5688-197) or COBOL
             for OS/390 and VM Version 2 Release 1 (5648-A25) or VS COBOL
             II Compiler and Library Version 1 Release 4 (5668-958)
       FORTRAN VS FORTRAN Compiler, Library, and Interactive Debugger
             Version 2 Release 6 (5668-806).
       PL/I  PL/I for MVS and VM Version 1 Release 1.1 (5688-235); OS
             PL/I Compiler, Library, and Interactive Test Facility
             Version 2 Release 3 (5668-909)
       PROLOG SAA (R) AD/Cycle PROLOG/MVS Version 1 (5696-309)
    

Function Dependent Program Requirements: DB2 has the following function specific dependencies:
  • User Defined Functions

    You must include Language Environment mapping macros and macros that generate a Language Environment conforming prolog and epilog. Language Environment is part of the OS/390 Version 1 Release 3 Application Enablement base feature.

    Refer to the Language Environment for MVS & VM Programming Guide for details. Refer to the Programming Languages section above for specific levels of COBOL, C, C++, PL/I, and Assembler.

  • Java (TM) Database Connectivity

    Java for OS/390 (5655-A46)

  • Predictive Governor

    For DB2 UDB clients using deferred prepare, use DB2 Connect Version 5, a feature of DB2 UDB for OS/390 Version 6

  • Group Bufferpool Duplexing

    CFLEVEL=5 CFCC and APAR OW28460 (for OS/390 releases before OS/390 Version 2 Release 6) required

  • Language Environment Built-In functions

    OS/390 Version 2 Release 6

  • 16 Terabyte Table Support

    DB2 table spaces larger than 1 terabyte will require the use of VSAM Extended Addressability for Linear Data Sets in DFSMS/MVS. Refer to the Statement of General Direction section.

  • CLI
      Execution of CLI component in the application address space
        - OS/390 Version 1 Release 3 Application Enablement, optional feature for C/C++
      Customer applications are supported in the following compiler language levels, or later:
        - C/C++ for MVS/ESA Version 3 Release 2 (6566-121)

        - SAA AD/Cycle C/370 Version 1 Release 2 (5688-194)

    Note: For specific software requirements for the above products, refer to the respective product announcements.
Optional Features of DB2 UDB Server for OS/390 Program Requirements: In addition to the requirements previously described for DB2 UDB for OS/390 Version 6, the following features have additional requirements:
  • DB2 Installer

    Note: TCP/IP is required if you want to run jobs or use the "copy jobs to host" function from the workstation. TCP/IP is required if you want to use all the functions in DB2 Installer. You can use DB2 Installer to customize your installation jobs if you do not have TCP/IP, but you will need to use a method outside of DB2 Installer to move jobs from the workstation to MVS for execution.

    • Windows NT Requirements
      • Microsoft Windows NT, Version 4.0
    • OS/2 Warp Requirements
      • OS/2 Version 3.0 (Warp)
      • TCP/IP on OS/2, Version 3.0
  • DB2 Visual Explain

    DB2 Visual Explain requires a DB2 for OS/2 Version 2 client workstation and the following software installed:

    • OS/2 Warp Version 3
    • DB2 Connect Version 5
    • DB2 for OS/2 Client Application Enabler (CAE)
    • Communications Manager 1.11
    • Personal Communications AS/400 (R) and 3270 Version 4.1 (5622-972)
    DB2 Visual Explain for NT requires Windows NT Version 4.0 and one of the following:
    • DB2 Connect Version 5 and one of the following communications software: Communications Server 5.0 or SNA Version 3.0 or the integrated SNA support in DB2 Universal Database

    • Distributed Database Connection Services (DDCS) Version 2 Release 4 and DB2 CAE
    DB2 Visual Explain includes a browser to view current values of subsystem parameters. To use the browser, your subsystem must also meet these requirements:
    • Stored procedures capability on the DB2 subsystem
    • DSNWZP stored procedure enabled
  • Net.Data for OS/390 Version 2
    • HTTP Web Server

      You must have an HTTP Web server installed on the server with Net.Data. It must be an HTTP-compliant Web server, such as one of the following:

      • IBM Internet Connection Secure Server for OS/390 Version 2 Release 2 (5697-B14)

      • Domino (TM) Go Webserver 4.6.1 for OS/390 (5697-C58)
    • Language Environment

      Language Environment 370 Version 1.5 (5688-198), or later. You must apply LE 1.5 Service: UN88194, UN88461, UN87133, and UN88416.

    Refer to these products for their list of prerequisites.

    Optional Software for Net.Data for OS/390 Version 2

    • For access to heterogeneous data sources through DB2 DataJoiner, you need DB2 DataJoiner Version 2.1.

    • For REXX applications, GDDM REXX Version 3 Release 2 is available as an optional feature of OS/390 Release 3.

    • For Perl applications, you need a Perl interpreter for OS/390.

    • For C and C++ applications, the C/C++ runtime library is available as an optional feature of OS/390 Release 3.

    • To use Java applets, you must have an applet enabled Web browser.

    • To use JavaScript, you must have a JavaScript enabled Web browser.
  • DB2 Extenders

    DB2 Extenders require:

    • OS/390 Version 2 Release 4 (5647-A01)

    • UNIX Services need to be configured and operational
  • Workstation-Based Tuning and Analysis

    Workstation-Based Tuning and Analysis requires one of the following:

    • OS/2 Warp Version 3 and Personal Communications AS/400 and 3270 Version 4.1 (5622-972)

    • Windows NT Version 4.0
  • DB2 Estimator

    DB2 Estimator can be used with any of the following:

    • OS/2 with WIN-OS2
    • Microsoft Windows 3.1 and subsequent releases
    • Microsoft Windows 95
    • Microsoft Windows NT
  • DB2 Performance Monitor

    For workstation-based monitoring, the DB2 Performance Monitor Feature requires one of the following:

    • OS/2 Warp Version 3 and Personal Communications AS/400 and 3270 Version 4.1 (5622-972)

    • Windows NT Version 4.0
    The use of MVS Host IRF Graphics Operation requires the following:
    • OS/390 Version 1 Release 3 Application Enablement Optional Feature for GDDM-PGF Version 2 Release 1.3
  • QMF for OS/390
    • For the CICS environment:
      • CICS/ESA Version 3 Release 3 (5683-083)
      • CICS/MVS (R) Version 2 Release 1.1 (5665-403)
      • CICS/ESA Version 4 Release 1.1 (5655-018)
    • For the QMF Document Interface:
      • Requires Personal Services/TSO (PS/TSO) Release 1 (5665-346) Editor
    • For the Callable Interface:

      The OS/390 Online Library has the following supported products that can be used with the QMF Callable Interface:

      • C/C++ for MVS/ESA, Version 3 Release 2.0 (5655-121)

      • COBOL for MVS and VM, Version 1 Release 2 (5688-197)

      • COBOL for OS/390 and VM, Version 2.1 (5648-A25)

      • VS COBOL II, Version 1 Release 4 (5668-958) or (5688-023) or (5688-022)

      • VS FORTRAN, Version 2 Release 6 (5668-806) or (5688-087) or (5668-805)

      • OS PL/I, Version 2 Release 3 (5668-909) or (5668-910) or (5668-911)

      • PL/I for MVS and VM, Version 1 Release 1.1 (5688-235)
    • For the User Edit Exit:

      QMF User Edit routines can be written in:

      • COBOL for MVS and VM, Version 1 Release 2 (5688-197)

      • COBOL for OS/390 and VM, Version 2.1 (5648-A25)

      • VS COBOL II, Version 1 Release 4 (5668-958) or (5688-023) or (5688-022)

      • OS PL/I, Version 2 Release 3 (5668-909) or (5668-910) or (5668-911)

      • PL/I for MVS and VM, Version 1 Release 1.1 (5688-235)
    • Connection to DB2 Workstation Databases:

      At the remote database configured for APPC communications:

      • DB2 Universal Database Version 5

      • DB2 Parallel Edition for AIX, Version 1 Release 2 (5765-328)

      • DataJoiner for AIX, Version 1 Release 2 (84H1212)

      • DB2 for Windows NT, Version 2 Release 1 (53H7474)

      • DB2 for OS/2, Version 2 Release 1 (41H2114)

      • DB2 for AIX, Version 2 Release 1 (41H2128)

      • DB2 for HP-UX, Version 2 Release 1 (10H2366)

      • DB2 for Solaris, Version 2 Release 1 (10H2421)

      • DB2 for SCO OpenServer, Version 2 Release 1 (79H5359)

      • DB2 for SINIX, Version 2 Release 1 (79H4133)
  • QMF HPO Feature

    The QMF HPO/Compiler generates programs in OS/VS COBOL and VS COBOL II. Since VS COBOL II is source compatible with AD/Cycle COBOL/370 (TM) and COBOL for MVS, those products are supported also.

    The QMF HPO/Compiler for OS/390 runs only under:

    • ISPF for MVS Version 2 Release 3 (5665-319) or
    • ISPF for MVS Version 3 (for execution) (5685-054)
    It generates programs that run under TSO/ISPF, batch, or CICS.

    The QMF HPO/Manager runs only under TSO/ISPF (with the exception of the enhanced HPO governor module supplied with the feature, which runs under TSO/ISPF, batch, or CICS).

    QMF for Windows runs under:

    • Windows 3.1, and later
    • Windows 95
    • Windows NT
    • OS/2 (R)
    It accesses:
    • DB2 for OS/390
    • MVS DB2 for VM
    • DB2 for VSE
    • DB2 for AIX
    • DB2 Parallel Edition
    • DB2 for OS/2
    • DB2 for Windows NT
    • DataJoiner on AIX
    Separate network connectivity requirements must be satisfied.

  • QMF Product Limitations in the CICS Environment

    Some functions provided by QMF are dependent on underlying system services and other program products available in VM/CMS and MVS/TSO, but not in CICS (including CICS/MVS and CICS/VSE (R)). The following commands require ISPF and are not available in CICS:

    • ISPF command synonym
    • DPRE command synonym
    • BATCH command synonym
    • LAYOUT command synonym
    • EXTRACT command
    • QMF command interface
    Existing applications and procedures containing commands requiring ISPF will run only if QMF Version 3.3 is started as an ISPF dialog.

    Existing QMF Version 3.1.0 programs must be re-linked. Refer to the Developing QMF Applications section for more information.

    These functions depend on REXX and are not supported by QMF in CICS:

    • Report calculations
    • Conditional formatting
    • Column definition
    • Procedures with logic
    Other functions not available in CICS:
    • Document Interface
    The EDIT PROC and EDIT QUERY commands are not available in CICS. However, it is possible to edit procedures and queries using the DISPLAY command with QMF.

  • QMF for Windows:

    Host software requirements are those required to run DB2 UDB for OS/390.

  • QMF for Windows runs on:
    • Microsoft Windows 3.1
    • Microsoft Windows for Workgroups 3.1 or 3.11
    • Microsoft Windows 95
    • Microsoft Windows NT
QMF for Windows for a DBCS language can only be run on Windows 95 and Windows NT (32-bit).

QMF for Windows can connect to DB2 for OS/390 Version 5 and DB2 UDB for OS/390 Version 6 via native TCP/IP, or to the SNA environments of that or other DB2 versions.

For TCP/IP connectivity, QMF for Windows must be able to establish a TCP connection from the Windows workstation to the remote host and remote port (the port on which DB2 is listening). This can be established with many 16- and 32-bit WinSock products, including those provided with Windows 95 and Windows NT.

For SNA connectivity, QMF for Windows requires an SNA/CPI-C product on each Windows workstation. These products are the interface between QMF for Windows and the APPC verb set used by the SNA environment to manage server/requester relationships.

The following table indicates the configurations that QMF for Windows has been tested with and supports. The columns under WIN 3.x, WIN 95, and WIN NT indicate whether or not the 16-bit or the 32-bit version of QMF for Windows works with the listed SNA product on that platform.

.----------------------------+-------+------+------+---------.
|SNA Product                 |WIN 3.X|WIN 95|WIN NT|WIN-OS/2 |
|----------------------------+-------+------+------+---------|
|                            |       |      |      |         |
|Attachmate EXTRA! APPC      |16-bit |      |      |         |
|  Client 3.11               |       |      |      |         |
|----------------------------+-------+------+------+---------|
|IBM APPC Networking Services|16-bit |      |      |         |
|  for Windows Version 1.0   |       |      |      |         |
|----------------------------+-------+------+------+---------|
|IBM Communications Server   |       |      |      | 16-bit  |
|  for OS/2 Version 4.1      |       |      |      |         |
|----------------------------+-------+------+------+---------|
|IBM Personal Communications |       |32-bit|      |         |
|  AS/400 and 3270           |       |      |      |         |
|  Version 4.1 for Windows 95|       |      |      |         |
|----------------------------+-------+------+------+---------|
|IBM Personal Communications |       |      |32-bit|         |
|  AS/400 and 3270           |       |      |      |         |
|  Version 4.1 for Windows NT|       |      |      |         |
|----------------------------+-------+------+------+---------|
|IBM eNetwork (TM) Personal  |       |32-bit|32-bit|         |
|  Communications            |       |      |      |         |
|  Version 4.21 for          |       |      |      |         |
|  Windows 95 and Windows NT |       |      |      |         |
|----------------------------+-------+------+------+---------|
|IBM Personal Communications |       |      |      | 16-bit  |
|  AS/400 and 3270           |       |      |      |         |
|  Version 4.1 for OS/2      |       |      |      |         |
|----------------------------+-------+------+------+---------|
|IBM eNetwork Personal       |       |      |      | 16-bit  |
|  Communications            |       |      |      |         |
|  4.21 for OS/2 Warp        |       |      |      |         |
|----------------------------+-------+------+------+---------|
|Microsoft SNA Server 2.11   |16-bit |16-bit|16-bit|         |
|  or 3.0 Windows 3.X Client |       |      |      |         |
|----------------------------+-------+------+------+---------|
|Microsoft SNA Server 2.11   |       |32-bit|      |         |
|  or 3.0 Windows 95 Client  |       |      |      |         |
|----------------------------+-------+------+------+---------|
|Microsoft SNA Server 2.11   |       |      |32-bit|         |
|  or 3.0 Windows NT Client  |       |      |      |         |
|----------------------------+-------+------+------+---------|
|NetSoft DynaComm/Elite      |16-bit |      |      |         |
|  3.51 APPC                 |       |      |      |         |
|----------------------------+-------+------+------+---------|
|Novell NetWare for SAA 2.2  |       |32-bit|32-bit|         |
|----------------------------+-------+------+------+---------|
|Wall Data Rumba 95/NT 5.0   |       |32-bit|32-bit|         |
'----------------------------+-------+------+------+---------'

Customers should ensure they have the latest corrective service or maintenance for their SNA product. Contact your SNA software vendor's technical support services personnel for this information.

QMF for Windows requires a WinSock 1.1 interface to the installed TCP protocol stack. The following table indicates the configurations QMF for Windows has been tested with and supports. The columns under WIN 3.x, WIN 95, and WIN NT indicate whether or not the 16-bit or 32-bit version of QMF for Windows works with the listed TCP/IP product on that platform.

.----------------------------+-------+------+------+---------.
|SNA Product                 |WIN 3.X|WIN 95|WIN NT|WIN-OS/2 |
|----------------------------+-------+------+------+---------|
|                            |       |      |      |         |
|Microsoft Windows 95 TCP    |       |16-bit|      |         |
|  Protocol                  |       |32-bit|      |         |
|----------------------------+-------+------+------+---------|
|Microsoft Windows NT TCP    |       |      |16-bit|         |
|  Protocol                  |       |      |32-bit|         |
|----------------------------+-------+------+------+---------|
|Microsoft TCP/IP-32 for     |16-bit |      |      |         |
|  Windows for Workgroups    |       |      |      |         |
|  2.11b                     |       |      |      |         |
'----------------------------+-------+------+------+---------'

Compatibility

DB2: DB2 UDB for OS/390 Version 6 is upwardly compatible with prior releases of DB2 for OS/390 and DB2 for MVS/ESA. Successful migration with full fallback protection requires customers to migrate DB2 releases sequentially. Thus, existing customers should ensure they are successfully running on DB2 for OS/390 Version 5 before migrating to DB2 UDB for OS/390 Version 6.

DB2 Performance Monitor Feature: The DB2 Performance Monitor Feature supports an environment of multiple DB2 releases, namely instrumentation, catalog, and PLAN_TABLE data from:

  • DB2 UDB for OS/390 Version 6 (5645-DB2)
  • DB2 for OS/390 Version 5 (5655-DB2)
  • DB2 for MVS/ESA Version 4 (5695-DB2)
User Group Requirements: This announcement satisfies or partially satisfies 124 requirements from one or more of the worldwide user group communities, which include Australasian SHARE/GUIDE (ASG), COMMON, COMMON Europe, GUIDE International, G.U.I.D.E. Europe, Japan GUIDE/SHARE (JGS), Guide Latin American (LAG), SHARE EUROPE, and SHARE Incorporated. Requirements satisfied include:
  • REQ00068566 ABILITY TO SET CURRENT DEGREE = TO A SPECIFIC NUMBER FOR DB2 P

  • REQ00068565 TELL DB2 HOW MANY CPU ENGINES ARE AVAILABLE FOR PARALLELISM

  • REQ00068130 TYPE2 INDEX GARBAGE COLLECTION

  • REQ00067975 ENABLE MULTIPLE SMALL INDEXES TO SHARE VSAM D'SET

  • REQ00067344 BETTER ESTIMATION OF FILSZ IN DB2 UTILITIES

  • REQ00066941 USE OF REORG UNLOAD ONLY OUTPUT FOR LOAD WITH COLUMN SPECS

  • REQ00066785 DB2 INADEQUATE SECONDARY ALLOCATION CAUSES DASD FRAGMENTATION

  • REQ00066711 LOAD RETURN CODE

  • REQ00066633 TEMP-4K-SPACE ON SCREEN DSNTIPD MAXIMUM TOO SMALL

  • REQ00066571 DB2 WRITE LARGE AMOUNT OF ACCOUNTING TRACE RECORD

  • REQ00066099 ARCHIVE OF DB2 LOG

  • REQ00065744 DB2 RECOVERY WITH ARCHLOG2

  • REQ00065742 BETTER DIAGNOSTIC INFORMATION FOR LOCK ESCALATIONS

  • REQ00065740 ALLOW SYNCHRON AND ASYNCHRON COMMAND PROCESSING VIA PARM

  • REQ00065733 REPORT UTILITY WITH NEW PARM FOR "RECOVERYSITE ARCHLOG"

  • REQ00065726 MORE QUALIFIED OUTPUT FOR THE REPORT UTILITY

  • REQ00065222 LOAD PHASE ELAPSED TIME IS TOO LONG DURING ONLINE REORG

  • REQ00065040 ENHANCED OPTIMIZER SUPPORT FOR OUTER JOIN WITH VIEWS

  • REQ00065023 BAD PERFORMANCE WITH PARALLEL PROCESSING AND SEQUENTIAL PREFET

  • REQ00064338 DELETING & INSERTING ROWS IN SYSTABSTATS

  • REQ00064267 DSNB232I SHOULD SHOW LEVELID = X' ' IF NO HEADER PAGE

  • REQ00064169 ABILITY TO CHOOSE THE INDEX IN AN SQL STATEMENT

  • REQ00063810 ADD BLOB/CLOB SUPPORT IN DB2

  • REQ00063597 AUTOMATE RCT ADMINISTRATION

  • REQ00062869 CONCATINATION WITH INSERT

  • REQ00062488_1 DB2 VERSION-UP METHOD UNDER DATA SHARING ENVIRONMENT

  • REQ00062488 DB2 VERSION-UP METHOD UNDER DATA SHARING ENVIRONMENT

  • REQ00062323_1 DB2 GOES DOWN WITH 04E-00E20029 WHEN THERE'S BAD DATA IN LOAD

  • REQ00062323 DB2 GOES DOWN WITH 04E-00E20029 WHEN THERE'S BAD DATA IN LOAD

  • REQ00062183 ENHANCE DB2 MESSAGE DSNT376I

  • REQ00061670 STREAMLINE DB2 MESSAGES FOR AUTOMATED OPERATION

  • REQ00061585 DSNTEP2 SHOULD DISPLAY -905 MESSAGE AT END OF ANSWER SET

  • REQ00061259 PROVIDE BUFFER POOL INFO ON DATA SET LEVEL IN IFC

  • REQ00061096 MAKE DCLGEN USABLE WITH ANY DRDA AS

  • REQ00061032 "DESCRIBE" PARAMETER IN DB2/MVS TO SUPPORT APAR JR09226 NEEDED

  • REQ00060686 DB2 ALLOW CONCATENATED STRING EXPRESSIONS FOR INSERTS

  • REQ00060541 HOST VARIABLES IN DB2 STORED PROCEDURES

  • REQ00060520 NEED CONCURRENT COPY OF MULTIPLE TABLESPACES TO BE ON 1 DATASE

  • REQ00059531 PREVENT LINK WARNING MESSAGES AT SYSTEM/PTF INSTALLATION

  • REQ00059463 BSDS OPEN INTERVAL FOR DPROPR SHOULD BE CHANGEABLE BY CUSTOMER

  • REQ00059381 DB2 UTILITY DSN1CHKR

  • REQ00058977 SPEED UP OF UNLOAD UTILITY

  • REQ00058513 ENHANCEMENTS TO THE DISPLAY BUFFERPOOL COMMAND

  • REQ00058512 BETTER DIAGNOSTIC INFORMATION FOR LOCK ESCALATIONS

  • REQ00058508 IDENTIFY REMOTE CLIENTS IN DISPLAY THREAD COMMAND

  • REQ00058503 REPORT UTILITY WITH NEW PARM FOR "RECOVERYSITE ARCHLOG"

  • REQ00058496 MORE QUALIFIED OUTPUT FOR THE REPORT UTILITY

  • REQ00058299 DSNTEP2 SHOULD ALLOW A SELECTED NUMBER OF ROWS RETURNED

  • REQ00058268 PROCESS OF OUTER JOIN

  • REQ00058266 PARALLEL FUNCTION FOR OUTER JOIN

  • REQ00058195 SEND SAMPLES OF VTAM (R) APPL STATEMENT AND MODEENT MACRO

  • REQ00057467 TERM UTILITY CAPABILITY FROM ANYONE IN THE DB2 DATA SHARING GR

  • REQ00057206 IMAGE COPY TO VERIFY FOSMLENT IN SPACEMAP PAGE

  • REQ00057147_2 DB2 TIMERONS

  • REQ00057147_1 DB2 TIMERONS

  • REQ00057147 DB2 TIMERONS

  • REQ00056732 CONVERT P/P TO NON GBP-DEP WHEN CACHED STATE BECOMES X

  • REQ00056158 QUIESCE WRITE YES NEEDS TO UPDATE HPGRBRBA FOR SYSTEM TABLESPA

  • REQ00054620 MONITORING FOR LONG TIME I/O PROCESSING

  • REQ00053573 ADD COLUMN "TIMERON" IN PLAN_TABLE

  • REQ00053219 A NEW OPTION OF REBIND TO BYPASS THE CHANGE OF ACCESS PATHS

  • REQ00052469 DSNTIJIN AND SMS MANAGED DATASETS

  • REQ00052319 SECONDARY AUTHID FOR BIND AND FREE COMMAND

  • REQ00051654 DB2 LOAD UTILITY WITH FORMAT UNLOAD CHECKING OF ROW INPUT LENG

  • REQ00051045 DB2 RECOVER FROM FULL WORKFILE WITHOUT MANUAL INTERVENTION

  • REQ00049893 DSNCCOM1 SHOULD NOT DEFAULT TO SHUTTING DOWN CICS ATTACH

  • REQ00048884 ALTERING KEYRANGES FOR PARTITIONED TS AND NO OF PARTITIONS

  • REQ00048193_2 DB2 SUPPORT OF BLOBS

  • REQ00048193_1 DB2 SUPPORT OF BLOBS

  • REQ00048193 DB2 SUPPORT OF BLOBS

  • REQ00047531_2 ALLOW MORE FLEXIBILTY IN ALTER STATEMENT FOR PARTITIONING INDE

  • REQ00046917 DEVELOP A COMMAND THAT WOULD CAUSE THREADS TO BE RE-SIGNED ON

  • REQ00046511 RUNSTAT FUNCTION ASSOCIATED WITH UTILITIES REORG/LOAD

  • REQ00046306_1 DB2PM CANNOT TELL WHAT TRACE CLASSES ARE ACTIVE

  • REQ00045378 TIME SAVING IN UTILITY EXECUTION

  • REQ00045147 NEED ADDITIONAL FILTERS IN DB2 TRACE CONSTRAINT BLOCK

  • REQ00044852_4 EXTERNALIZE ZPARMS PCLOSET PCLOSEN ON DSNTINST PANELS

  • REQ00044852_3 EXTERNALIZE ZPARMS PCLOSET PCLOSEN ON DSNTINST PANELS

  • REQ00044852_1 EXTERNALIZE ZPARMS PCLOSET PCLOSEN ON DSNTINST PANELS

  • REQ00044852 EXTERNALIZE ZPARMS PCLOSET PCLOSEN ON DSNTINST PANELS.

  • REQ00044642_1 DB2 PREDICTIVE GOVERNOR

  • REQ00044642 DB2 PREDICTIVE GOVERNOR

  • REQ00044304 INCLUDING COMMANDS IN THE AUDIT TRACES

  • REQ00043695 THREAD RESCHEDULING FOR SYNCPOINT IN CICS NON-TERMINAL TXNS

  • REQ00039868 LOAD UTILITY STATISTICS

  • REQ00039829 USE REORG UNLOAD ONLY OUTPUT AS INPUT FOR LOAD OF LIKE TABLE

  • REQ00039800 SHOW 'TIMERON' UNITS IN DB2 EXPLAIN TABLE

  • REQ00039743 TRIGGER SUPPORT

  • REQ00039694 SYSOPR TO BE ABLE TO START CATALOG DATABASE

  • REQ00039591 COST ESTIMATE BEFORE EXECUTION

  • REQ00039294 ALTER OF PARTIONED TABLE SPACES

  • REQ00039160 DB2 -- PREDICTING APPLICATION (SQL) PERFORMANCE

  • REQ00039135 PROVIDE ESTIMATED COST (IO AND CPU) FIGURES ON EXPLAIN OUTPU

  • REQ00039121 PROVIDE BETTER SUPPORT FOR DB2 BACKUP/RECOVERY INDX/DS LEV

  • REQ00038626 DYNAMIC PLAN SELECTION FOR NON-TERMINAL ORIENTED XONS

  • REQ00038411 ALLOW INSTALL SYSOPR START OF STOP/DEFER SYSTEM DATABASES

  • REQ00038192 ADD RUNSTATS OPTION TO LOAD, REORG, CREATE INDEX, AND/OR IMAGE

  • REQ00037785 PROVIDE OPTION TO FORWARD RECOVER INDEXES

  • REQ00037776 RESOURCE ESTIMATOR FOR DB2

  • REQ00037775 OPTIMIZER COST ESTIMATES

  • REQ00036914 INCREASE NUMBER OF ENTRIES IN THE PAGE ID MAP

  • REQ00034341 PROVIDE FAST DATA EXTRACT CAPABILITY

  • REQ00033975 FASTER DB2 RESTART FOR INFLIGHT TRANSACTIONS

  • REQ00031814 DB2 RECOVER WITH RUNSTATS

  • REQ00031813 DB2 REORG WITH RUNSTATS

  • REQ00031812 DB2 LOAD WITH RUNSTATS

  • REQ00030842 USER DEFINED FUNCTIONS

  • REQ00030498 DURING CONNECTION FAILURE, MARK AFFECTED PARTITIONS WITH STOPE

  • REQ00029458 ALLOW DB2 INSERT INTO TABLE WITH SUBSELECT FROM SAME TABLE

  • REQ00029443 ACCELERAT THE RECOVER-UTILITY

  • REQ00023669 STORED PROCEDURE AND TRIGGER FUNCTION FOR DB2

  • REQ00022158_4 DB2 AND UPPER/LOWER CASE INSENSITIVE ROW SELECTION

  • REQ00022158_3 DB2 AND UPPER/LOWER CASE INSENSITIVE ROW SELECTION

  • REQ00022158_2 DB2 AND UPPER/LOWER CASE INSENSITIVE ROW SELECTION

  • REQ00020491_1 DB2 PARTITION INDEPENDENCE

  • REQ00020491 DB2 PARTITION INDEPENDENCE

  • REQ00013758 ELIMINATE REPETITIVE MESSAGES REFLECTING SAME ERROR CONDITION

  • REQ00013112 REUSE SEGMENTED TABLESPACE BEFORE ALLOCATING SECONDARY EXTENT

  • REQ00010714 DB2 FORWARD RECOVERY PERFORMANCE

  • REQ00010665_1 NEED DB2 TO SUPPORT THE ABSOLUTE VALUE COLUMN FUNCTION

  • REQ00010665 NEED DB2 TO SUPPORT THE ABSOLUTE VALUE COLUMN FUNCTION

  • REQ00009778 THE DB2 GOVENOR (RLF) SHOULD SUPPORT A WARNING MODE

  • REQ00008588 CUSTOMER REQUIRES A COST ESTIMATE OF DYNAMIC SQL QUERY

  • REQ00006785 CAPTURE RUNSTATS INFORMATION AT TIME OF TABLE LOAD



Planning Information

Customer Responsibilities: Customers should review the sections in this announcement that describe the hardware and software dependencies for DB2 UDB for OS/390 Version 6.

DB2 UDB for OS/390 Version 6 has support for migration from Version 5. Customers not yet on Version 5, should plan to migrate to DB2 for OS/390 Version 5 as preparation for a migration to Version 6.

Migration Considerations: With DB2 UDB for OS/390 Version 6, IBM removes support for some functions. As you prepare to migrate your subsystems, you should be aware of the following changes:

  • Type 1 indexes are no longer supported. All indexes should be converted to type 2 before migrating.

  • Data set password protection is no longer supported. Data sets should be protected by a security subsystem, such as RACF, an element of the OS/390 Security Server, rather than by passwords. Remove all passwords from all indexes and table spaces before migrating.

  • Shared read-only data replaced by more substantial, more usable data sharing. Convert or drop all shared read-only databases before migrating.

  • A preceding colon is now required and no longer optional for a host variable in an SQL statement. Ensure all host variable references include a preceding colon before migrating.
Installability: Customers should refer to the planning sections of the Release Guide (SC26-9013) available from an IBM representative, as well as the Program Directory shipped with the product.

Packaging: The DB2 UDB Server for OS/390, except as noted below, will be shipped on 9-track magnetic tapes (written at 6250 BPI), 3480 cartridges, or 4-mm DAT cartridges.

Also included will be a memo to users, a Program Directory, and under separate cover, one copy of the publications.

The Workstation-based Installer, Visual Explain, Estimator and QMF for Windows functions will be shipped on CD-ROM.

Workstation-Based Analysis and Tuning will be shipped on the same media with the DB2 PM "Try" software.

Note: The components in QMF HPO Version 6 (QMF HPO/Manager and QMF HPO/Compiler) were available as separately orderable QMF features in QMF Version 3.3. They are no longer available as separately orderable features in Version 6. QMF HPO/Complete is now simply called QMF HPO and includes the QMF HPO/Manager, QMF HPO/Compiler, and QMF for Windows as one comprehensive feature.



Security, Auditability, and Control

DB2 UDB for OS/390 Version 6 uses the security and auditability features of the host OS/390 systems. It also provides facilities for the protection and control of its resources. These facilities include controls for:

  • System access
  • Data access and control
  • Concurrent access
  • Data recovery
  • Accounting



TERMS AND CONDITIONS

Licensing: IBM Customer Agreement

Try and Buy Program: The optional priced features of DB2 Universal Database Server for OS/390 Version 6 are shipped with each new order of DB2 UDB Server for OS/390 and are available for customer evaluation under a limited term trial license. The following priced features are included in the Try and Buy program:

  • DB2 Administration Tool Feature
  • DB2 Buffer Pool Tool Features
  • DB2 DataPropagator Apply Feature
  • DB2 DataPropagator Capture Feature
  • QMF Feature
  • QMF for Windows Feature
  • QMF HPO Feature
  • DB2 Performance Monitor Feature
These features may be installed and used on a trial basis for 90 days from the date of installation of the feature, except for QMF for Windows Feature, which may be installed and used on a trial basis for 60 days from the date of installation. A full-use license for each of the above priced features may be obtained by ordering the appropriate billing feature number and media feature number, labeled as "Buy" for the optional priced feature. The trial version of these priced features contain time disabling devices that will prevent their use upon expiration of the trial period.

Variable Charges Apply: Yes

Measured Usage License Charge (MULC): Applies

Parallel Sysplex (R) License Charge (PSLC): Applies

Location License Applies: No

Use Limitation Applies: No

Educational Allowance: Yes, to qualified education customers.

Volume Orders: Not applicable

Version-to-Version Upgrade Credits Apply: Yes

                                                        Single
  Replaced Programs         Replacement Programs       Version
Program       Program       Program       Program      Charging
Number        Name          Number        Name         Applies

5740-XYR DB2 V1 5645-DB2 DB2 UDB V6 Yes 5665-DB2 DB2 V2 5645-DB2 DB2 UDB V6 Yes 5685-DB2 DB2 V3 5645-DB2 DB2 UDB V6 Yes 5695-DB2 DB2 V4 5645-DB2 DB2 UDB V6 Yes 5655-DB2 DB2 V5 5645-DB2 DB2 UDB V6 Yes 5645-DB2 DB2 V6 To a follow-on program, N/A if any.

DB2 Performance Monitor Feature

5665-354 DB2 PM V1 5645-DB2 DB2 UDB V6 Yes* 5685-140 DB2 PM V2 5645-DB2 DB2 UDB V6 Yes* 5655-047 DB2 PM V3 5645-DB2 DB2 UDB V6 Yes* 5655-102 DB2 PM V4 5645-DB2 DB2 UDB V6 Yes*

QMF Feature

5668-972 QMF V1 5645-DB2 DB2 UDB V6 Yes* 5668-721 QMF V2 5645-DB2 DB2 UDB V6 Yes* 5706-254 QMF V3 5645-DB2 DB2 UDB V6 Yes*

DB2 DataPropagator Feature

5622-267 Data- 5645-DB2 DB2 UDB V6 Yes* Propagator Relational Apply for MVS, V1.2.1

5655-076 Data- 5645-DB2 DB2 UDB V6 Yes* Propagator Relational Capture for MVS, V1.2.1

5655-A22 Data- 5645-DB2 DB2 UDB V6 Yes* Propagator Relational Apply for MVS, V5.1

5655-A23 Data- 5645-DB2 DB2 UDB V6 Yes* Propagator Relational Capture for MVS, V5.1

DB2 Admin Tool Feature

5688-515 DB2 5645-DB2 DB2 UDB V6 Yes* Administration Tool V1

DB2 Buffer Pool Tool Feature

5697-D16 DB2 Buffer 5645-DB2 DB2 UDB V6 Yes* Pool Tool V1

*     Note 3 of DAWN-0040 applies

Warranty Applies: Yes

Licensed Program Materials Availability

  • Restricted Materials of IBM: None
  • Non-Restricted Source Materials: None
  • Object Code Only (OCO): All
Testing Period: Two months (basic license only)

Satisfaction Guarantee: Two months for basic licenses, starts:

  • 10 days after IBM ships

    or

  • On the day a non-DSLO additional licence authorized
Program Services
  • Support Center applies: Yes, access is available through the IBM Support Center.

  • Available until discontinued: 12 months written notice

  • APAR Mailing Address:
      IBM Corporation APAR Processing P.O. Box 49023 San Jose, CA 95161-9023
  • APAR Mailing Address (QMF for Windows Feature):
      IBM Corporation APAR Processing One Innovation Drive Natick, MA 01760
  • Services for DSLO Licenses: Provided through basic license location



CHARGES

The charges provided in this announcement are suggested retail prices for the U.S. only and are provided for your information only. Dealer prices may vary, and prices may also vary by country. Prices are subject to change without notice. For additional information and current prices, contact your local IBM representative.

Charges will be communicated before general availability.

Trademarks

      OS/390, QMF, DataPropagator, Net.Data, Client Access, Visual
      Warehouse, MVS, IMS, DataRefresher, MVS/ESA, DFSMS, RS/6000,
      Multiprise, DFSORT, DATABASE 2, C/370, COBOL/370, and eNetwork
      are trademarks of International Business Machines Corporation
      in the United States or other countries or both.
      DB2, AIX, OS/2, DataJoiner, DB2 Universal Database, S/390,
      ES/9000, System/390, DFSMS/MVS, IMS/ESA, CICS, GDDM, DRDA, DB2
      Connect, Operating System/400, OS/400, CICS/ESA, DB2 Extenders,
      VisualAge, RACF, NetView, BookManager, APL2, AD/Cycle, SAA,
      AS/400, CICS/MVS, WIN-OS/2, CICS/VSE, AT, VTAM, and Parallel
      Sysplex are registered trademarks of International Business
      Machines Corporation in the United States or other countries or
      both.
      Windows and Microsoft are trademarks of Microsoft Corporation.
      Windows NT is a registered trademark of Microsoft Corporation.
      Java is a trademark of Sun Microsystems, Inc.
      UNIX is a registered trademark in the United States and other
      countries exclusively through X/Open Company Limited.
      NotesPump and Domino are trademarks of Lotus Development
      Corporation.
      Lotus Notes is a registered trademark of Lotus Development
      Corporation.
      Other company, product, and service names may be trademarks or
      service marks of others.