April 18, 2000
IBM DB2 UDB Server for OS/390, Version 7 Delivers the Power for Your e-business and Data Warehouse Applications
At a Glance
With Version 7, DB2 UDB Server for OS/390:
For ordering, contact:
The DB2 Universal Database® Server for OS/390®, Version 7 program delivers improved performance, availability, and scalability for your e-business and data warehouse applications. A new feature, DB2® Warehouse Manager, brings together the tools to build, manage, govern, and access data warehouses based in DB2 for OS/390.
With DB2 UDB for OS/390, Version 7, your e-business and business intelligence applications can be synergized with the powerful, highly available environment provided by S/390 and OS/390. You can leverage your existing applications while developing and expanding your electronic commerce for the future.
In DB2 UDB for OS/390, Version 7, the DB2 Family is expanding the capability of the DB2 server by integrating warehouse management. The new DB2 Warehouse Manager feature gives a full set of tools for building and using a data warehouse based on DB2 for OS/390. This feature includes:
Several DB2 UDB for OS/390, Version 7 enhancements to DB2 can help improve your existing applications. Take advantage of:
Extend the power and flexibility of your applications with DB2 UDB for OS/390, Version 7 enhancements. You can utilize the following:
With Version 7, DB2 UDB Server for OS/390 delivers even more tools. Use the Try and Buy opportunity to discover the benefits of the following, which are added to the existing tools available with DB2 UDB for OS/390, Version 6:
Planned Availability Date
Information on the Version 7 availability date will be provided in an availability announcement.
The DATABASE 2 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, e-business, business intelligence, high-performance, and continuous availability.
DB2 Warehouse Manager, new to DB2 UDB Server for OS/390 in Version 7, delivers a complete warehouse solution along with your DB2 for OS/390. This new offering brings together the tools to build, manage, govern, and access DB2 data warehouses. It is based on proven technologies, which are enhanced to provide additional function and to provide tighter integration among the components. Provided in the optional DB2 Warehouse Manager Feature are:
Improved Performance, Availability, and Scalability
Version 7 includes significant new function to DB2 for OS/390. Whether your requirements are to do any of the following, DB2 UDB for OS/390, Version 7 has the power and function you are seeking to:
With each release, DB2 for OS/390 delivers improvements for performance, availability, and scalability. In DB2 UDB for OS/390, Version 7 you can take advantage of a new utility: UNLOAD, which provides faster data unloading than was available with the DSNTIAUL program. In addition to the unload functions of REORG UNLOAD EXTERNAL, you can also unload data from an image copy, invoke row sampling, specify field selection, and ordering, as well as using parallelism when unloading multiple partitions.
Online REORG is enhanced for data availability. Now, the time required to invoke a dataset rename has been eliminated. Instead you can specify a new keyword FASTSWITCH, which will leave the data set name unchanged, but update the catalog to reference the newly reorganized dataset. When hundreds of table spaces and index objects are involved, the time savings can become quite significant. Also, parallelism is added to the BUILD2 phase. This makes it possible to process logical partitions simultaneously and thereby shorten the elapsed time required for this phase of the Online REORG.
One of the causes of a planned outage for DB2 arises when there is the need to alter one or more of the system parameters (known as ZPARMS). Now, Version 7 introduces the opportunity to change the value of many of these system parameters without stopping DB2.
Data sharing customers can benefit from a new restart option. Restart Light will allow you to restart DB2 with a smaller storage footprint in order to quickly recover retained locks, following an abnormal termination. The reduced storage requirement can make a restart for recovery possible on a system that might not have enough resources to start and stop DB2 in normal mode.
Version 7 continues to enhance the flexibility of DB2 to support your enterprise applications and to ease the integration to the calling application.
DB2 Universal Database introduced support for the new object data types. Along with these objects, DB2 Extenders® provided appropriate functions for defining, accessing, storing, and searching data stored as a specific type. New in Version 7 is DB2 XML Extender with support for data using the XML data type. This extender allows you to store an XML object either:
Scrollable cursors give your application logic ease of movement through the result table using simple SQL and program logic. This frees your application from the need to cache the resultant data or to re-invoke the query in order to reposition within the resultant data.
In the increasingly global world of business and e-commerce, there is a growing need for data arising from geographically disparate users to be stored in a central server. Previous releases of DB2 have offered support for numerous code sets of data in either ASCII or EBCDIC format. However, there was a limitation of only one codeset per system. New in Version 7 is support for UNICODE encoded data. This new code set is an encoding scheme that is able to represent the characters (code points) of many different geographies and languages.
Stored procedures introduced in Version 5 have increased program flexibility and portability among relational databases. Now, with Version 7, DB2 for OS/390 will accept COMMIT and ROLLBACK statements issued from within a stored procedure. This enhancement will prove especially useful for applications in which the stored procedure has been invoked from a remote client.
Now, you can take advantage of Precompiler Services to perform the tasks currently executed by the DB2 precompiler. This API can be called by the COBOL compiler. By using this option, you can eliminate the DB2 precompile step in program preparation. You can take advantage of language capabilities that had been restricted by the precompiler, such as nested COBOL programs. Use of the host language compiler enhances DB2 Family compatibility, making it easier to import applications from other database management systems and from other operating environments.
Greater flexibility and family compatibility comes from several SQL enhancements. Now, you can use a subselect to determine the values used in the SET clause of an UPDATE statement. Also, you can have a self-referencing subselect. The search condition in the WHERE clause can include a subquery in which the object for the subquery and the UPDATE or DELETE is the same. Support is now extended so you can define a view with the operators UNION or UNION ALL. You can also use a row expression to compare with a subselect expression.
Expanding the server, several new tools offer you more assistance to manage and tune your DB2 for OS/390 environment. These new tools:
A basic set of core utilities are included as part of DB2 since Version 1 was first delivered. These utilities initially provided a basic level of services to allow customers to manage data. Some customers have preferred to obtain such functions, however, from independent software vendors that have developed utility and tools offerings that offered additional performance, function, and features beyond that contained in the DB2 core utilities. With recent releases of DB2 for OS/390, in response to clear customer demand, IBM has invested in the improvement of the performance and functional characteristics of these core utilities.
With Version 7, many of these enhanced utility functions have been separated from the base product and are now offered as optional features of DB2 UDB for OS/390.
Included in the DB2 Trial Tools Package are two new utility features:
The DB2 Trial Tools Package Feature will be shipped with all new orders of DB2 UDB for OS/390, Version 7. Install them and give them a test run during the trial period. Discover the benefit they bring to your data administration tasks. A permanent use license is available for each tool by ordering the specific tool feature.
All of the features of DB2 UDB Server for OS/390 were developed to work with Version 7 and have been tested to help assure they install and execute in an integrated environment. This can save you valuable install test time. For detailed descriptions of the optional features, refer to the Features of DB2 UDB Server for OS/390 section.
This product is Year 2000 ready. When used in accordance with its associated documentation, it is capable of correctly processing, providing, and receiving date data within and between the twentieth and twenty-first centuries, provided all products (for example, hardware, software, and firmware) used with the product properly exchange accurate date data with it.
DB2 UDB for OS/390, Version 7 provides the relational database function described in the IBM Open Blueprint. It provides the:
DB2 UDB for OS/390, Version 7 is developed at a lab where the quality management system is certified under ISO 9001.
DB2 UDB for OS/390, Version 7 conforms with the following national and international SQL standards:
DB2 UDB for OS/390, Version 7 is registered by IBM as Advanced ClusterProven. The IBM ClusterProven program introduces new high-availability requirements that may be applied to any combination of operating system, middleware, or end-user application. DB2 for OS/390 is a solution that satisfies the S/390® platform's technical criteria and has been registered to receive ClusterProven status. Specifically, DB2 has obtained the status of Advanced ClusterProven by providing significant benefits above those inherent at the ClusterProven level. More information on ClusterProven is available on the Web at:
DB2 UDB for OS/390 is the super-server of choice for the twenty-first century providing enterprise-wide data management for e-business, business intelligence, CRM, and ERP applications such as Siebel, Vantive, Baan, 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 Web servers, CICS®, IMS 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 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® 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.
Features of DB2® UDB Server for OS/390®
DB2 UDB Server for OS/390 extends DB2 for OS/390, by offering features that combine with DB2 to enhance data warehousing, query access, system management, and replication of your data. The optional features of DB2 Universal Database® Server for OS/390, Version 7 include:
Several optional features are available at no additional charge, including:
DB2 Warehouse Manager Feature
Use DB2 Warehouse Manager to simplify and speed your warehouse prototyping, development, and deployment to production. Benefits include better control of query resources, through query governance, and cost management and usage tracking. Integration with the Information Catalog enables you to satisfy user requirements for finding, understanding, and accessing the right data. QMF gives you the ability to satisfy common reporting requirements, whatever the size of your enterprise.
DB2 Universal Database Version 7.1 Enterprise Edition: The data warehouse management infrastructure and OLAP Starter Kit are delivered as elements of DB2 UDB Version 7.1 Enterprise Edition. This copy of DB2 is included, with a restricted-use license, to permit delivery and utilization of the Windows-based components of the DB2 Warehouse Manager for OS/390.
Data Warehouse Center: The Data Warehouse Center gives you a graphical control facility, fully integrated with DB2 Control Center. Now you can more easily accomplish the diverse tasks of warehouse creation and management:
OS/390 Agents and Transformers: The warehouse agent for OS/390 executes OS/390-based processes on behalf of the Data Warehouse Center. It permits data to be processed in your OS/390 environment without the need to export it to an intermediate platform environment, allowing you to take full advantage of the power, security, reliability, and availability of DB2 and OS/390.
Warehouse transformers are stored procedures or user-defined functions that provide commonly used transformations for building data warehouses. These transformers provide complex transformations commonly used in warehouse development including:
These transformers augment the rich transformations available with SQL built-in functions including:
DB2 OLAP Starter Kit: The DB2 OLAP Starter Kit is a limited user license of DB2 OLAP Server® and the OLAP Integration Server. Use them to quickly build and deploy OLAP applications in a Windows-based environment. The DB2 OLAP server for OS/390 is available separately. You can order and use it for OLAP applications to be run natively on OS/390.
DB2 Query Management Facility (QMF) Family: QMF, the tightly integrated, powerful, reliable, query, and reporting toolset for the DB2 relational database management system family. It 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 7 enables you to work with data all over the enterprise: from DB2 for OS/390, DB2 for VSE and VM, and DB2 for AS/400® to workstation servers running OS/2®, Windows NT, AIX®, and other UNIX® operating systems to massively parallel processors. QMF coupled with the DB2 DataJoiner® product allows access to non-relational and other vendor data sources as well.
The DB2 Warehouse Manager Feature delivers the following QMF Family of integrated tools:
They offer a comprehensive data access and governing solution including:
They also provide for report publishing to the Web for viewing with your favorite Web browser.
The QMF HPO Version 7 includes QMF HPO/Manager and QMF HPO/Compiler.
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 valuable resources. Among the many conditions available for governing are:
For customers with DB2 databases of many sizes, QMF for Windows provides a Windows-based, point-and-click query tool that gives you many benefits, including an intuitive GUI "quick start" user interface and a Java-based query capability. Using QMF for Windows, you can automate tasks and develop powerful native Windows applications. The tool includes a powerful Windows-based API to automate database querying, updating, and report distribution tasks, so you can centralize control over resource consumption. QMF for Windows also gives you 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 can connect to the DB2 family of products including:
QMF for Windows connectivity options include SNA, TCP/IP, and CLI.
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 Administration Tool Feature
Use DB2 Admin to:
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. Its comprehensive set of database management functions helps DB2 systems personnel efficiently and effectively manage your DB2 environment by:
DB2 Admin supports the functionality of DB2 Version 7 by providing panels and options allowing you to quickly view 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:
DB2 Admin offers a powerful 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 the DB2 Admin 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:
DB2 Administration Tool Version 7 provides two new functions called Alter and Migrate.
The Alter function permits users to change the name and attributes of a table column, insert new columns and drop existing columns. After the desired changes have been specified by the user, the jobs required to implement the changes are generated by the DB2 Administration Tool. These jobs unload the data, recreate the table, and reload the data.
The Migrate function supports copying all the objects and data in one or more databases or table spaces to another DB2 subsystem. DB2 Administration Tool creates the jobs needed to copy definitions and data to the target DB2 subsystem.
The DB2 Admin power-packed functionality still includes:
DB2 Bind Manager Feature
After a program with imbedded SQL has been successfully processed by the DB2 Precompiler and the appropriate host language compiler, it must then undergo a DB2 bind before it can be executed. Binding establishes a fixed relationship between a program and the database it will access. The bind process is complex and involves selecting access paths to the data, performing further SQL verification, and various other checks and validations. Unnecessary binds should be avoided, since they can be quite expensive.
Bind Manager can analyze each precompile to determine whether the SQL structure has changed. If the structure has not changed, then a bind is not needed, and this product ensures that one is not executed. When an installation installs DB2 Bind Manager, unnecessary binds become a thing of the past.
Use of Bind Manager can pay major dividends in change management, since it will detect automatically production application changes requiring a bind. This frees DBAs from analyzing bind impacts and allows them to concentrate only on the changes that affect the SQL structure.
Consistency checking may be done between an existing DBRMLIB and a DB2 subsystem using the optional feature DBRM Checker feature of Bind Manager. DBRM Checker will identify DBRMs by plan that have consistency tokens inconsistent with those in the DB2 catalog tables. You can determine which of the DBRMs you need to BIND. An application may have 100s of packages (that is, DBRMs) making up one plan. If you only changed one then you only need to BIND that one package.
DB2 Bind Manager requires:
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:
The DB2 Buffer Pool Tool provides the following advantages:
DB2 Buffer Pool Tool gives you expert tuning knowledge and reduces the time and effort necessary to effectively tune your environment. Make informed decisions with confidence regarding performance improvements.
DB2 DataPropagator Feature
Data Replication is the key technology for controlling the power and potential of distributed database environments. DB2 DataPropagator, part of the comprehensive Data Replication and Warehousing Solutions, provides a highly efficient way to maintain consistent copies of relational data in the DB2 family of databases. It captures automatically the data changes against a source database and propagates those changes to any specified target database, keeping the two consistent. This is all done automatically without requiring any batch processing windows and explicit knowledge of, or changes to, business applications.
DB2 DataPropagator established the base architecture for IBM's data replication solution. The IBM replication architecture is based on individual components that interoperate, allowing for customization of the data replication environment. Capture components capture changes as they occur in the source and store them in the staging area. Apply components read the staging area and apply those changes to targets or copy data directly from the source in full refresh mode. Administration components provide the GUI for defining replication requests. The replication components can be located anywhere in your environment in order to maximize the efficiency of your replication environment.
The DB2 DataPropagator Feature consists of the following components:
The Administration component for the DB2 DataPropagator Version 7 is called the Control Center. The Control Center is the integrated administration tool for DB2 Universal Database 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:
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 causing any changes and running asynchronously to business applications. The captured changes are placed in staging tables. The Capture component of DB2 DataPropagator for OS/390, Version 7 supports DB2 for MVS, Version 4.1, or later.
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:
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:
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 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. You 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 NonRelational (IMS), DataRefresher, DataJoiner, and Lotus NotesPump products to deliver powerful, versatile replication among:
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 powerful conflict detection and compensation, along with on-demand replication for occasionally connected and mobile systems. DB2 Catalog replication is supported for speeding up of ODBC-based queries.
Beginning in Version 6, DB2 DataPropagator has the ability to replicate large objects (BLOB, CLOB, and DBCLOB), and replication for ROWID, a new data type introduced in DB2 UDB for OS/390, Version 7. 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 are 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 Forms Feature
DB2 Forms, IBM's drag-and-drop solution for quickly building user-friendly, powerful e-business front ends to any DB2 database, has added three new features to further enhance its support for rapid development of Java-based applications for Web sites and intranets. DB2 Forms continues to provide a single development environment that enables users to simultaneously build Java-based and 32-bit Windows-based applications (some application features may only be available in 32-bit, Windows-based applications and not in Java-based applications).
DB2 Forms Developer: A rapid development environment for creating custom forms end users can access from virtually any environment or location. In a drag-and-drop interface, developers quickly add command buttons, labels, text boxes, and controls for containing data and "drop down" lists. Behaviors, data sources, and data validation rules are assigned to controls from easy-to-use dialogs that require no programming. Applications can be made available only to their creators, to all users, made fully visible within a Web page, or made available as a link in a Web page. The developer can specify whether a unique DB2 logon is required to access the application.
Each application presents specific data associated with it at development time, and enforces data browsing, data entry, and data update rules embedded within it. Typical applications include:
Whether rolled out for access from within Web pages, as stand-alone Java applications, or as Windows-based applications, no compiling or porting is needed for any DB2 Forms application.
DB2 Forms Console: Sets up DB2 servers to centrally store Java and Windows-based DB2 Forms applications for access by end users. The Console defines servers, installs DB2 Forms packages at the servers, creates the DB2 Forms catalog objects at the servers, and sets various user group permissions. DB2 Forms Console supports and relies upon your existing DB2 security.
DB2 Forms User: The Windows client run-time that provides users with access to Windows-based DB2 Forms applications, which are stored centrally at the database server. Installation of the DB2 Forms User Module is not required when using Java-based DB2 Forms applications. End users select and launch any number of applications from the catalog (stored at the DB2 server) without having to install any additional code on their workstations. Access can be made available to local or remote workstations, including those connecting from any location via the Internet to TCP/IP supported DB2 databases.
DB2 Forms Java Player: Installed by the administrator to your HTTP server for serving your Java-based DB2 Forms applications to Web browsers. It can also be installed on Java-enabled workstations for running Java-based DB2 Forms applications stand-alone without a browser.
Applications can contain a variety of controls for performing commonly required tasks, such as:
Java and XML Standards Compliance: DB2 Forms Version 3 generates online applications that can be run as Java applets embedded in Web pages for access through a browser, or as stand-alone Java applications without a browser.
DB2 Forms also generates the specifications for a Java application in XML vocabulary, laying the groundwork for future integration in Web-based data interchange and leveraging of the DB2 XML Extender.
Java and XML standards compliance adds universal portability to DB2 Forms applications.
At the same time DB2 Forms Version 3 generates your Java-based applications, it can also generate Windows-based applications, which may be distributed freely on demand over networks and are architecturally coupled to DB2 via the open standards of DRDA.
DRDA compliance allows you to easily transcend network, hardware, and operating system differences when connecting Windows-based DB2 Forms client applications to DB2 database servers on multiple platforms. The result is the elimination of database gateways, middleware, and ODBC drivers, while gaining more rapid setup, easier administration, and support for advanced features of DB2.
DRDA compliance also allows inclusion of multivendor databases (including IMS, VSAM, Oracle, and Microsoft SQL Server) via the multidatabase gateway DB2 DataJoiner.
Enhancements to DB2 Forms Version 3: Three new features are provided with DB2 Forms for OS/390 Version 3 to provide additional support to users in development of Java-based applications for Web sites and intranets. They are:
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 7 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:
Enhancements to DB2 PM Feature for Version 7 include:
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 SQL Performance Analyzer Feature
Developing applications under DB2 today requires the cooperative skills of the system architect, the database administrator, the programming staff, and members of the systems support team. In the daily quest to produce applications on time and within budget, too often corners are cut such that performance is not adequately considered. Once put into production, these applications fail to perform adequately, particularly at high transaction volumes. In addition, even applications that originally performed well may deteriorate over time due to changes in data distribution, data volume, system changes, and even changes to the DB2 product itself. Therefore, installations spend a great deal of their budget managing the performance of their applications.
All DB2 problem queries have one thing in common. They run too long. These queries cause the batch production window to shrink. Too often the online queries take what seems like forever to execute, causing customers and users to become frustrated. The most cost effective solution to the problem is prevention. IBM is introducing DB2 SQL Performance Analyzer to aid in preventing queries from running too long. With this tool you can find out how long queries will take:
Query cost can be determined regardless of which DB2 attach is used and regardless of whether static or dynamic SQL is used. Estimates are given in familiar units like CPU time, I/O count, and elapsed time and in even simpler terms, such as a single number representing overall cost. In addition, a monetary cost for each query is computed and delivered with the above.
This product can be used daily in many ways. Some examples are:
DB2 Recovery Manager Feature
In the online transaction environment, it is not uncommon to encounter applications that access and update DB2 and IMS/DB data. When the application commits, IMS and DB2 coordinate the data changes such that all changes occur or none occur. However, if at some later time the user needs to recover IMS and DB2 to the same point, then the user must deal with different logs, different utilities, and different processes to do the recovery. This leads to complex recovery scenarios that are time consuming and error prone as each product has to have its data recovered separately. Recovery Manager is a new product that simplifies this process.
Recovery Manager works with IMS, DB2, or both. It uses image copies for either or both products, processes the individual logs and can work with incremental image copies for DB2 and the change accum process for IMS. Recovery Manager establishes sync points to which recovery may be done. Recovery Manager calls such a sync point a Virtual Image Copy (VIC). In the situation as described, after the application finishes, Recovery Manager is invoked to establish a VIC. No image copies are required. Recovery Manager establishes a quiesce point and notes where it is on the respective logs. During recovery, the user specifies the need to recover to this VIC and Recovery Manager applies the appropriate image copies and causes the log to be applied up to this point.
If you prefer, rather than using VIC for recovery, you can use Recovery Manager to automate the recovery of resources. Recovery Manager will generate the JCL, locate the proper image copies, and control the execution of the job. The product will do this for either DB2 or IMS.
DB2 Management Tools Package
The DB2 Management Tools Package is a no-charge feature of DB2 for OS/390, Version 7. The Management Tools Package is a collection of workstation-based tools you can use to work with and manage your DB2 for OS/390 environment. The elements of the DB2 Management Tools Package Feature are:
DB2 Control Center: Users of DB2 for OS/390 can now manage data in a new way. The Control Center capability of DB2 Universal Database Version 6 for Windows, UNIX, and OS/2 now extends support to DB2 for OS/390, Version 6. As a Java-based tool, the Control Center can run on many types of workstations and on many different operating systems. Users can now use the same tool, with its easy-to-use GUI, to manage DB2 databases on OS/390, and on workstation servers. The GUI supports DB2 for OS/390 SQL statements (such as CREATE and ALTER), DB2 commands (such as DISPLAY, START, and STOP), and utilities (such as REORG and LOAD).
With the Control Center, users can manage the family of DB2 databases on many different operating systems. DB2 for OS/390 objects are displayed on the Control Center main window along with objects of other members of the DB2 UDB family. To initiate an action or utility to manage these objects, users select the object. For example, a user can list the table spaces of a particular database and perform the following actions, and others, on one of the selected table spaces:
The Control Center can run either as a Java application or as an application on your Web server that your Web browser can access. DB2 Control Center is part of the DB2 Application Development Client on Windows, delivered with all editions of DB2 Universal Database and DB2 Connect products on Linux, OS/2, UNIX, and Windows. Because the Control Center requires DB2 Connect, the DB2 Management Tools Package provides a restricted-use copy of DB2 Connect Version 7 to satisfy this functional dependency.
The Control Center approach to managing DB2 is now extended to the System/390® platform. Sites that have multiple DB2 subsystems, on the same or different operating systems, can use the Control Center as a central point of administration. Users who are more experienced in the workstation environment can manage DB2 for OS/390 more easily as a result of the GUI.
DB2 Stored Procedure Builder: The DB2 Stored Procedure Builder (SPB), an element of the DB2 Management Tools Package, provides an easy-to-use development environment for creating, installing, and testing stored procedures. With the DB2 Stored Procedure Builder, you can focus on creating your stored procedure logic rather than on the details of registering, building, and installing stored procedures on a DB2 server. The Stored Procedure Builder provides a single development environment that supports the entire DB2 family ranging from the workstation to System/390. With DB2 Stored Procedure Builder, you can develop stored procedures on one operating system and deploy them on other server operating systems.
The DB2 Stored Procedure Builder has a GUI that guides you through the tasks with the help of basic design patterns, SQL assistants, and costing information. Use the Stored Procedure Builder to perform a variety of tasks associated with stored procedures, such as:
DB2 Stored Procedure Builder support for DB2 for OS/390 is currently available in beta test mode. It can be obtained from the Web at:
DB2 Stored Procedure Builder is part of the DB2 Application Development Client on Windows, delivered with all editions of DB2 Universal Database and DB2 Connect products on Linux, OS/2, UNIX, and Windows. Because the Stored Procedure Builder requires DB2 Connect, the DB2 Management Tools Package provides a restricted-use copy of DB2 Connect Version 7 to satisfy this functional dependency.
DB2 Installer: DB2 Installer is a workstation client delivered as an element of the DB2 Management Tools Package. DB2 Installer enhances your productivity whether you are installing DB2 for OS/390 for the first time or you are an experienced installer. From your workstation, you can:
Enhancements in Version 7 include:
Visual Explain: DB2 Visual Explain, a workstation client that is an element of the DB2 Management Tools Package, is an easy-to-use workstation tool that presents the output from DB2 EXPLAIN and dynamic EXPLAIN in a graphical format. Relationships between database objects, such as tables and indexes, are instantly clear as are various operations, such as table space scans and sorts. DB2 Visual Explain also includes a browser for viewing DB2 subsystem parameters. Enhancements to Visual Explain Version 7 include:
If you are using Control Center, you can launch Visual Explain directly from the Control Center. Because DB2 Visual Explain requires DB2 Connect, the DB2 Management Tools Package provides a restricted-use copy of DB2 Connect Version 7 to satisfy this functional dependency.
DB2 Estimator: DB2 Estimator is an easy-to-use, stand-alone tool for estimating the performance of applications for DB2 for OS/390. DB2 Estimator is one of the elements of the DB2 Management Tools Package. Run it on your desktop personal computer, or take it with you on your portable notebook computer.
With DB2 Estimator, you can model a partial DB2 application or a complete real or planned DB2 application without requiring an actual DB2 system. From simple table sizings to a detailed performance analysis of an entire DB2 application, DB2 Estimator saves time, lowers costs, and reduces risk. You can use DB2 Estimator to investigate the impact to your production system of new or modified applications before you implement them. You can do what-if analysis to assess the impact of changes you're considering. You can also answer many questions, such as:
Use DB2 Estimator during all life-cycle phases of a DB2 application. During the initial design phase, you can easily:
When creating database objects, use the models you specified in DB2 Estimator as a guide for naming columns and for specifying attribute values. You can model your system using actual DB2 information by importing information from the DB2 catalog and, if available, from EXPLAIN or DB2 Performance Monitor, thereby eliminating problems early in the design phase.
When your application is in production, use DB2 Estimator with tools such as DB2 PM to solve application performance problems. You can evaluate alternative SQL designs, without any risk to your production environment, before changing any production database objects. DB2 Estimator also helps you determine the impact of hardware or workload changes.
You can use DB2 Estimator for Versions 5, 6, and 7 of DB2 for OS/390. It runs in any environment that supports Windows (Windows 95, Windows 98, Windows 2000, and Windows NT). Use DB2 Estimator on any data imported from DB2 for OS/390, or you can model an application for which none of the tables, SQL, transactions, or configuration exist.
In Version 7, DB2 Estimator expands support for utilities and SQL statements to help you approximate your working environment more closely. Enhancements in Version 7 include:
The Net.Data Version 7 feature provides high-performance access to DB2 data from the World Wide Web. Net.Data for OS/390, Version 7 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:
Net.Data provides native access to the data you need in your business environment:
In addition, Net.Data can call DB2 stored procedures for additional performance from static SQL.
Net.Data has extensive application development functionality, including:
Net.Data for OS/390, Version 7 adds enhancements for performance, scalability, usability, and serviceability. With Net.Data for OS/390, Version 7, your high-performance, business-critical Web applications can more efficiently utilize the data in your enterprise.
Refer to the Net.Data Web pages for documentation, sample programs, and customer applications. You can find the Net.Data home page at:
REXX Language Support Feature
REXX Language Support lets your REXX programs access DB2 data. You can use this facility to enable your REXX execs or REXX stored procedures to issue calls directly to DB2 for OS/390.
Specified Operating Environment
Processors: DB2 for OS/390 operates on any processor supported by OS/390 Version 2 Release 7 and supports the architectural level set. In this version, DB2 for OS/390 intends to use ESA/390 architectural enhancements, that were implemented on selected S/390® servers.
DB2 UDB for OS/390, Version 7 can run only on servers that implement the architectural enhancements, and cannot run on any servers that have not implemented them. The following IBM servers implement the architectural enhancements:
DB2 UDB for OS/390, Version 7 cannot run on the following IBM servers, because they do not implement the architectural enhancements:
Architectural enhancements provide a variety of performance and reliability improvements. For more information about the specific enhancements in ESA/390, refer to Software Announcement 299-234 , dated August 24, 1999, or the product manuals for ESA/390.
The processor must have enough real storage to satisfy the combined requirements of:
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 OS/390 for the DB2 data sets. The following DB2 data sets are supported by the following device types:
If these data sets are on a disk shared with other OS/390 systems, you should use global resource serialization to prevent concurrent access by more than one OS/390 system.
The minimum DASD space requirement, based on installing DB2 using the Installation Panels default values, is approximately 600 MB. You will need additional DASD space for your data.
If you use dual logging and tape for the log archiving device, you need at least two tape drives.
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.
Optional Programs: You can use the following optional licensed programs with DB2 UDB for OS/390, Version 7. Unless otherwise specified, the release shown for a product and any subsequent release is acceptable. In some cases, earlier versions or releases of IBM licensed programs may also work with DB2 for OS/390, but IBM may not have tested with them at the time of this announcement. If you have questions, check with your IBM representative.
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 Open Class(TM) Library Component, which is licensed with the OS/390 base operating system 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) Java Java for OS/390 (5655-A46) PL/I VisualAge for PL/I for OS/390, Version 2 Release 2 (5655-B22), or IBM PL/I for MVS and VM, Version 1 Release 1 (5688-235); OS PL/I Compiler, Library, and Interactive Test Facility Version 2 Release 3 (5668-909) PROLOG SAA AD/Cycle PROLOG/MVS Version 1 (5696-309) REXX TSO Extensions for MVS REXX, part of OS/390 Smalltalk VisualAge Smalltalk Version 4 Release 5 (5655-B14 or 5802-AAR)
Virtual Storage Requirements: The amount of space needed for the common service area (CSA) below the 16 MB line is less than 40 KB for each DB2 subsystem and 24 KB for each IRLM when APAR PQ12390 and prior service is applied. High concurrent activity, parallelism, or high contention can require more CSA.
Most of the DB2 common data resides in the extended common service area (ECSA). Most modules, control blocks, and buffers reside in the extended private area. A DB2 subsystem with 200 concurrent users and 2,000 open data sets should need less than 2 MB of virtual storage below the 16 MB line.
Prerequisites of Features of DB2 UDB Server for OS/390: DB2 for OS/390, Version 7 includes many features, some of which have requirements of their own, above and beyond what DB2 for OS/390, Version 7 requires. This section identifies the requirements for using these features with DB2 for OS/390, Version 7, but it does not repeat those DB2 for OS/390 requirements that apply to the features. Also, some of these features can be used with prior releases of DB2; these requirements are not included in this section, but rather in the detailed installation information for the specific feature.
You can use subsequent versions or releases of the products mentioned in this section, unless otherwise noted.
Both environments require TCP/IP in any of the following circumstances:
If you do not have TCP/IP, you may still use DB2 Installer to customize your installation jobs on your workstation. However, you will need to use a method outside of DB2 Installer to move jobs from the workstation to OS/390 for execution.
In addition, DB2 Visual Explain requires one of the following communication protocols:
Visual Explain includes a browser that lets users view current values of subsystem parameters. To use this browser, your DB2 subsystem must have:
DB2 Estimator has no hardware requirements.
Net.Data Requirements: Net.Data for OS/390, Version 7 requires an HTTP Web server installed on the same server as Net.Data and DB2 for OS/390. The Web server can be another HTTP-compliant Web server or one of the following servers: This version of Net.Data requires Server for OS/390, OS/390 Version 2 Release 7 and IBM HTTP Server Version 5 Release 1, the version of the HTTP Web server included in OS/390 Version 2 Release 7. Net.Data for OS/390 has no hardware requirements.
Data Warehouse Center can support target data warehouses built on any of the following DB2 for OS/390 versions:
The DB2 PM Workstation-Based Online Monitor has the following dependencies:
Software Requirements: For the host-based Online Monitor and host-based graphics facility, DB2 Performance Monitor has no functional dependencies if you are monitoring DB2 for OS/390, Version 7. The DB2 Performance Monitor feature supports an environment of multiple DB2 releases, namely instrumentation, catalog, and PLAN_TABLE data from:
The DB2 PM Workstation-Based Online Monitor API is supported on the following platforms:
DB2: DB2 UDB for OS/390, Version 7 is upwardly compatible with prior releases of DB2 for OS/390 and DB2 for MVS/ESA. Migration with full fallback protection is available for customers running on either DB2 for OS/390, Version 5 or DB2 UDB for OS/390, Version 6. Thus, existing customers should ensure they are successfully running on DB2 for OS/390, Version 5, or later, before migrating to DB2 UDB for OS/390, Version 7.
User Group Requirements: This announcement satisfies or partially satisfies 63 requirements from one or more of the worldwide user group communities. Groups 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:
REQ00033987 DB2 Unload Utility REQ00048887 Unload Utility REQ00073656 DB2 Utility REORG Unload External Inconvenient to use REQ00075995 REORG Unload Enhancements REQ00039320 COPY with filtering of Table Space Names REQ00039857 Image Copy by Database REQ00039323 Thread Termination without Rollback REQ00041522 Terminate Thread without Backout REQ00072841 Command to Cancel Backout and Recover Objects REQ00075829 CANCEL Thread no Rollback REQ00069335 Online REORG Switch Phase Takes Too Long to Complete REQ00039675 Cursor that can be read backwards REQ00039774 Support scrollable cursor REQ00023873 Fetch previous row REQ00039675 Cursor that can be read backwards REQ00039114 DB2 Unpredictable Results when using Index instead of Temporary REQ00039450 Ensure Predictable results when fetching a row from a cursor REQ00025551 Provide an option to make a CURSOR insensitive to updates REQ00039634 Select max on the first column in a unique index in DB2 REQ00039540 Enhance DB2 to walk backwards through an INDEX REQ00026448 DB2-Precompiler support for SQL statements in nested program REQ00028200 Embedded SQL within VS COBOL II Nested Programs REQ00039163 Extra DB2 precompiler option to suppress generated code REQ00039758 Support Subscripted Host-Variable REQ00039798 Reduce Initialization overhead for SQL in programs containing SQL REQ00029770 Dynamic Alteration of DB2 System Parameters REQ00037642 DB2 -- Provide dynamic ZPARM update capability REQ00039026 DB2 system parameters: dynamic reconfiguration REQ00039704 DSNZPARM REQ00039772 Capability of Dynamically changing to DSNZPARM parameters REQ00062092 Dynamic Assignment of DSNZPARM REQ00062114 Dynamic Updating of DSNZPARM REQ00068708 DB2 DSNZPARM, ZPARM, changing while DB2 is running REQ00068708_1 DB2 DSNZPARM, ZPARM, changing while DB2 is running REQ00072132 ZPARM Alteration Function While Running DB2 System REQ00072836 Dynamic change for DSNZPARM parameters REQ00072848 Dynamic Modification of Unit type for Archive Logs REQ00074416 Improvement of DB2 subquery performance REQ00029459 Allow DB2 Delete From Table with Subselect From Same Table REQ0007521 Reduce recovery time in data sharing environments REQ00065739 Online Utilities REQ00073348 LOAD RESUME with OLTP concurrency/ generic insert bmp capability REQ00039004 COMMENT ON for all DB2 objects REQ00039628 Only a few tables have remark columns All of the tables ought REQ00039640 Get DSNTINST values from running DSNZPARM REQ00075134 DB2 Optimizer REQ00075699 Catalog column for immedwrite bind parameter REQ00039011 Prize-list REQ00039296 Adding new statement SELECT FIRST (n) REQ00040253 Allow a limit to be placed on the number of rows retrieved REQ00074553 Limit the number of rows returned on a select statement REQ00068551_1 Increase of acceptable values for QUERYNO in Plan_table REQ00068551 Increase of acceptable values for QUERYNO in Plan_table REQ00069866 Top Secret DB2 Interface REQ00070041 Authorization exit needs to pass DATABASE name for ALTER and DROP REQ00034332 Allow DBADM to create view with different qualifier REQ00039156 DB2 -- Enhance DBADM authority REQ00041745 DBADM authority to create views REQ00045374 Specify a owner in CREATE VIEW REQ00058505 DBADM-Authority for CREATE VIEW REQ00065735 DBADM-Authority for CREATE VIEW REQ00074704 Full RACF DB2 Security Management REQ00072517 Accounting traces running a full day
DB2 UDB for OS/390, Version 7 has support for migration from Version 5 or 6. Customers not yet on Version 5, should plan to migrate to DB2 for OS/390, Version 5, or later, as preparation for a migration to Version 7.
Migration Considerations: IBM added many universal database capabilities in DB2 UDB for OS/390, Version 6 and removed support for some functions. As you prepare to migrate your subsystems, you should be aware of the following changes:
Also included will be a Program Directory, and under separate cover, one copy of the entitled publications.
The workstation client functions of DB2 Management Tools Package, DB2 Extenders, and Buffer Pool Tool will be shipped on CD-ROM.
The QMF for Windows product CD-ROM also contains all supported national languages and all U.S. English and translated publications in softcopy format. Two publications are shipped:
Security, Auditability, and Control
DB2 UDB for OS/390, Version 7 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:
The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.
Terms and Conditions
Single Version Charging Replaced Program Replacement Program Applies DB2 Version 1 DB2 UDB Version 7 Yes 5740-XYR 5675-DB2 DB2 Version 2 DB2 UDB Version 7 Yes 5665-DB2 5675-DB2 DB2 Version 3 DB2 UDB Version 7 Yes 5685-DB2 5675-DB2 DB2 Version 4 DB2 UDB Version 7 Yes 5695-DB2 5675-DB2 DB2 Version 5 DB2 UDB Version 7 Yes 5655-DB2 5675-DB2 DB2 Version 6 DB2 UDB Version 7 Yes 5645-DB2 5675-DB2 DB2 Version 7 To a follow-on program, N/A 5675-DB2 if any. Single Version Charging Replaced Program Replacement Program Applies DB2 Performance Monitor (PM) Feature DB2 PM Version 1 DB2 UDB Version 7 Yes(2) 5665-354 5675-DB2 DB2 PM Version 2 DB2 UDB Version 7 Yes(2) 5685-140 5675-DB2 DB2 PM Version 3 DB2 UDB Version 7 Yes(2) 5655-047 5675-DB2 DB2 PM Version 4 DB2 UDB Version 7 Yes(2) 5655-102 5675-DB2 QMF Feature QMF Version 1 DB2 UDB Version 7 Yes(2) 5668-972 5675-DB2 QMF Version 2 DB2 UDB Version 7 Yes(2) 5668-721 5675-DB2 QMF Version 3 DB2 UDB Version 7 Yes(2) 5706-254 5675-DB2 QMF for Windows Feature QMF for Windows, DB2 UDB Version 7 Yes(2) Version 3.3 5675-DB2 5697-D27 DB2 DataPropagator Feature DataPropagator DB2 UDB Version 7 Yes(2) Relational Apply 5675-DB2 for MVS, Version 1.2.1 5622-267 DataPropagator DB2 UDB Version 7 Yes(2) Relational Capture 5675-DB2 for MVS, Version 1.2.1 5655-076 DataPropagator DB2 UDB Version 7 Yes(2) Relational Apply 5675-DB2 for MVS, Version 5.1 5655-A22 DataPropagator DB2 UDB Version 7 Yes(2) Relational Capture 5675-DB2 for MVS, Version 5.1 5655-A23 DB2 Admin Tool Feature DB2 Administration DB2 UDB Version 7 Yes(2) Tool Version 1 5675-DB2 5688-515 DB2 Buffer Pool Tool Feature DB2 Buffer Pool DB2 UDB Version 7 Yes(2) Tool Version 1 5675-DB2 5697-D16
Try and Buy Program: Several of the optional priced features of DB2 Universal Database Server for OS/390, Version 7 are combined into the DB2 Trial Tools Package feature, which is shipped with each new order of DB2 UDB Server for OS/390. These tools are available for customer evaluation under a limited term trial license. The following priced features are included in the Try and Buy program:
These features may be installed and used on a trial basis for 90 days from the date of installation of the feature, except for the DB2 Buffer Pool Tool and DB2 Forms Features, 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.
Authorization to use this copy of DB2 Connect is to enable access to DB2 for OS/390 data by the following workstation tools only:
For all other remote connections to DB2 for OS/390 that are provided through DB2 Connect, or for any use of DB2 Connect not specifically described above, you must obtain a separate license for DB2 Connect
Authorization to use this copy of DB2 UDB Enterprise Edition is to enable database management of DB2 for OS/390 data warehouse control databases by the following workstation tools only:
For use of DB2 UDB Enterprise Edition other than the uses specifically described above, you must obtain a separate license for DB2 UDB Enterprise Edition from IBM.
Use Priority/Reference Code: LE001 Phone: 800-IBM-CALL Fax: 800-2IBM-FAX Internet: firstname.lastname@example.org Mail: IBM Atlanta Sales Center Dept. LE001 P.O. Box 2690 Atlanta, GA 30301-2690
You can also contact your local IBM Business Partner or IBM representative. To identify them, call 800-IBM-4YOU.
Note: Shipments will begin after the planned availability date.