system z10 enterprise class providing new business ... · – new system z solutions and offerings...

1

Technical Sales Support Americas

© Copyright IBM Corporation, 2008

March 11th Oracle Solutions on DB2 for zOS Conference Call

Agenda

11:00 (EST) - Welcome 11:05 - Introducing the IBM System z10 Enterprise Class11:15 - DB2 Version 9 for zOS12:25 - Questions and Answers12:30 - Closing Comments and Adjourn

© Copyright IBM Corporation, 2008 IBM Systems

Introducing the IBM System z10 Enterprise Class

The cornerstone of the New Enterprise Data Center


September 6th Siebel on IBM System z Conference Call

Agenda

11:30 - Welcome

11:35 – Siebel on System z Update

12:20 - Questions and Answers

12:30 - System z9 Integrated Information Processor1:00 - Questions and Answers

1:15 – Closing Comments and Adjourn


• Dedication to every client’s success

• Innovation that matters – for our company and for the world

IBM introduced our vision for the future Data Center:

The “New Enterprise Data Center”

IBM announced the next generation System z™:

The IBM System z10™

– IBM System z10 Enterprise Class (z10™ EC)

– New System z Solutions and Offerings

– IBM Storage – Information Infrastructure Solutions

(hardware, software, services)

– SWG Enterprise Modernization (Rational®), Security (Tivoli®)

On February 26 IBM announced a new vision of the data center and the next generation mainframe — the IBM System z10 Enterprise Class


1 Planned availability 2Q08

"IBM’s z10 is the computer industry’s pinnacle systems platform. Blow-away performance, increased capacity, and expanded memory makes this system the absolute best scale-up architecture — bar none — in the computing industry“

Joe Clabby, President, Clabby Analytics 2008

IBM System z10 Enterprise Class Continuing the modular design for flexibility

Enterprise Quad Core technology – 4.4 GHz – Decimal Floating Point

Enhanced capacity 64-way model

Up to 1.5 TB Memory, 3x more

Star topology reduces latency

6 GBps InfiniBand® for faster I/O and Coupling Links


Unprecedented performance and capacity Transforms the economics of the data center paving the way for new server consolidation and software hosting opportunities

Lower software license costsLower labor costsLower energy and facilities costs50% average increase in specialty engine performanceUp to 2x performance increase in CPU intensive tasks Up to 10x improvement in decimal floating point instructions 50% more performance

Mor

e En

gine

s

z9 EC

z990

z900

z10 EC

70% more usable capacity

One System z10 core can do work of up to 30 x86 Cores, helping to reduce licensing costs by up to 30 to 1 and lower

TCO by up to 80% *Comparison is versus x86 Blade servers without virtualization, reflecting a current-day consolidation. Reductions will vary by the number and age of the x86 servers being consolidated.


Resource Link™ provides tools to estimate server energy requirements before you purchase a new system or an upgradeOffers a 14% improvement in performance per KWh over the IBM System z9® Enterprise Class (z9™ EC)Has energy efficiency monitoring tool

– Introduced on IBM System z9 platform in April 2007– Power and thermal information displayed via the System Activity Display (SAD)

New IBM Systems Director Active Energy Manager (AEM) for Linux® on System z V3.1– Offers a single view of actual energy usage across multiple heterogeneous IBM platforms within the

infrastructure– AEM V3.1 energy management data can be exploited by Tivoli enterprise solutions such

as IBM Tivoli Monitoring, IBM Tivoli Usage and Accounting Manager, and IBM Tivoli OMEGAMON® XE on z/OS®

– AEM V3.1 is a key component of IBM’s Cool Blue™ portfolio within Project Big Green

The IBM System z10 continues to build on the System z “green” leadership, a focus of many customers


Preplanning capabilities to avoid future planned outages, e.g. dynamic LPAR allocation without a system outage100 available capacity settings – 30% more than z9 ECIntegrated enterprise level resiliency for heterogeneous data center disaster recovery management Policy driven flexibility to add capacity and backup processorsBasic HyperSwap™ improves storage availability *Integrated cryptographic accelerator

– Advanced Encryption Standard (AES) 192 and 256 and Stronger hash algorithm with Secure Hash Algorithm (SHA-512)

Tamper-resistant Crypto Express2 feature – Supports high levels of security for demanding applications– Fully programmable and configurable– High scale performance for SSL transactions

Trusted Key Entry (TKE) 5.2 with optional Smart card readerSystem z – the only platform that is EAL5 certified

* All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represents goals and objectives only.

World-class Business Resiliency solutions can provide new opportunities in security and business continuity engagements


IBM System z10 – For More Information

www.ibm.com/systems/z

Customer Roadshow– 22 Cities in March– www.ibm.com/events/systemzGaylan [email protected]

http://www.ibm.com/events/systemz

1

© 2007 IBM Corporation

IBM Software Group

March 11th 2008 | DB2 for z/OS © 2008 IBM Corporation

DB2 9 for z/OS

March 11th, 2009

Chris Crone

DB2 for z/OS Development

IBM Software Group | Information Management Software

DB2 for z/OS | March 11th 2008 © 2007 IBM Corporation

Agenda

DB2 9 Overview

DB2 9 XML

Migrating to DB2 9

What’s next?

2


IBM Software Group


DB2 9 Overview



• Index compression• Partition By Growth tables• Cloned tables• Volume based backup / recovery

Simplification, Reduced TCO

• Many SQL improvements• Dynamic index ANDing• Histogram statistics• New built-in OLAP expressions• Optimization Service Center

Dynamic Warehousing

• pureXML• Optimistic locking for WebSphere• LOB performance, usability

SOA Enablement

• More online schema changes • Online REBUILD INDEX• Trusted context and ROLEs• Parallel Sysplex clustering improvements

WorkloadConsolidation

DB2 9 for z/OSAddressing Corporate Data Goals

3



DB2 SQLz z/OS V9commonluw Linux, Unix & Windows V9

Multi-row INSERT, FETCH & multi-row cursor UPDATE, Dynamic Scrollable Cursors, GET DIAGNOSTICS, Enhanced UNICODE for SQL, join across encoding schemes, IS NOT DISTINCT FROM, Session variables, TRUNCATE, DECIMAL FLOAT, VARBINARY, optimistic locking, FETCH CONTINUE, ROLE, MERGE, SELECT from MERGE

Inner and Outer Joins, Table Expressions, Subqueries, GROUP BY, Complex Correlation, Global Temporary Tables, CASE, 100+ Built-in Functions including SQL/XML, Limited Fetch, Insensitive Scroll Cursors, UNION Everywhere, MIN/MAX Single Index, Self Referencing Updates with Subqueries, Sort Avoidance for ORDER BY, and Row Expressions, 2M Statement Length, GROUP BY Expression, Sequences, Scalar Fullselect, Materialized Query Tables, Common Table Expressions, Recursive SQL, CURRENT PACKAGE PATH, VOLATILE Tables, Star Join Sparse Index, Qualified Column names, Multiple DISTINCT clauses, ON COMMIT DROP, Transparent ROWID Column, Call from trigger, statement isolation, FOR READ ONLY KEEP UPDATE LOCKS, SET CURRENT SCHEMA, Client special registers, long SQL object names, SELECT from INSERT, UPDATE or DELETE, INSTEAD OF TRIGGER, Native SQL Procedure Language, BIGINT, file reference variables, XML, FETCH FIRST & ORDER BY in subselect and fullselect, caselesscomparisons, INTERSECT, EXCEPT, not logged tables, range partitioning, compression

Updateable UNION in Views, GROUPING SETS, ROLLUP, CUBE, 16 Built-in Functions, SET CURRENT ISOLATION, multi-site join, MERGE, MDC, XQuery

z

luw

common



Text function improvements in DB2 9New built-in character functions: COLLATION_KEY,

ASCII_CHR, ASCII_STR, COLLATION_KEYDIFFERENCE, EBCDIC_CHR, EBCDIC_STRIS_IDENTICAL_TO, LEFT, LOCATE_IN_STRINGLPAD, NORMALIZE_STRING, OVERLAYRIGHT, RPAD, SOUNDEX, UNICODEUNICODE_STR, VARCHAR_FORMATXMLATTRIBUTES, XMLCOMMENT, XMLDOCUMENT, XMLPARSE, XMLPIXMLQUERY, XMLSERIALIZE, XMLTEXT

Index on expression: e.g. UPPER, LOWER

4



DDL Porting ImprovementsAutomatic selection of DATABASE and TABLESPACE when DDL omits these keywords

Automatic CREATE of UNIQUE index for PRIMARY KEY

Deprecated simple table space, default to segmented structure, partition by growth


IBM Software Group


Warehousing and BI

5



Query EnhancementsSQL enhancements: INTERSECT, EXCEPT, cultural sort, caseless comparisons, FETCH FIRST in fullselect, OLAP specifications: RANK, DENSE_RANK, ROW_NUMBER …Index improvements: Index on expression, Index compression, …Improved Optimization statistics: Histogram Optimization techniques– Cross query block optimization and REOPT(AUTO)

– Generalize sparse index & in-memory data cache method

– Dynamic Index ANDing for Star Schema

Analysis: instrumentation & Optimization Service Center



Modified BW WorkloadData– Fact table size: 58.4M rows , 8 indexes– Dimension tables: 8 (2 ~ 99326 rows)– Snowflakes: 6 (added to increase query complexity)

Queries (100)– Developed by DB2 development and performance– Based on V8 BW workload – New queries added to better reflect the customer scenarios learned

from the V8 service stream

Represent customer workloads without adequate (multi-column) index support (this is the norm)

6



Performance Comparison

-1.5 %75147400 Total CPU time (seconds)

6775 (90%)2924 (39.5%)CPU time eligible for zIIP off-load

88%854471660Total Elapse Time (seconds)

ImprovementDB2 9DB2 V8



Optimization Service CenterIdentify Problem QueryTune Problem QueryMonitor & Capture Query WorkloadTune Query Workload

7


IBM Software Group


Cost Savings through optimization and reduced complexity



DB2 Server

CREATE CONTEXT WAS1SYSTEM USERID WASPRODADDRESS MY.WAS.SERVERALLOW USER

JOE WITHOUT AUTHENTICATION,SAM WITHOUT AUTHENTICATION;

Trusted Security ContextIdentifies “trusted” DDF, RRS Attach, or DSN application serversAllows selected DB2 authids on connections without passwords

reduces complexity of password managementreduces need for an all-inclusive “system authid” in app

servers with ability to switch usersmore visibility/auditability of which user is current runningenables mixed security capabilities from a single app server

MY.WAS.SERVERSAM or JOE w/o password

8



Database ROLEsROLE is a “virtual authid”–Assigned via TRUSTED CONTEXT–Provides additional privileges only when in a trusted environment using existing primary AUTHID.–Can optionally be the OWNER of DB2 objects

CREATE ROLE PROD_DBA;GRANT DBADM … TO PROD_DBA;

CREATE TRUSTED CONTEXT DBA1 …DEFAULT ROLE PROD_DBA OWNER(ROLE);



DB2 Server

CREATE CONTEXT APP_1SYSTEM USERID APP_PRODATTRIBUTES( ADDRESS ‘1.2.3.4’)

ooo

DEFAULT ROLE APP_ROLE

Example 1: ROLEs and Trusted Context used to Secure App Servers

• Most existing application servers connect to DB2 using userid/password pairs:

Significant exposure if someone steals the userid/password!!!• Trusted Context and ROLEs can be used to limit exposure:

GRANTs to APP_ROLE can be restricted so that they are only valid when used by a valid app server IP address

• No change required to the code in the application server

App Server

IP Address=1.2.3.4

APP_PRODconnections

9



DB2 Server

CREATE CONTEXT WAS1SYSTEM USERID WASPROD …ALLOW USER

JOE DEFAULT ROLE JDBC_ROLE,SAM DEFAULT ROLE JDBC_ROLE

Example 2: ROLEs and Trusted Context for Dynamic SQL Auditing

• Better auditing controls:• GRANT dynamic SQL privileges to a ROLE• End user identity can be delegated directly to DB2 without

granting dynamic SQL privileges directly to the end user• End user passwords can be optional.• No added complexity for administration of GRANTs, while

retaining the ability to audit the end user’s identity!!!

WebSphereJOE

SAM

WASPRODconnections

SAM



Auditing: DB2 Trace FilteringNew filtering capabilities for –START TRACE that INCLUDE or EXCLUDE based on these keywords:–USERID -- client userid–WRKSTN -- client workstation name–APPNAME -- client application name–PKGLOC -- package LOCATION name–PKGCOL -- package COLLECTION name–PKGPROG -- PACKAGE name–CONNID -- connection ID–CORRID -- correlation ID–ROLE – end user’s database ROLE

10


IBM Software Group


Performance and Scalability



LOB Performance/Scalability

LOB lock avoidance – LRSN and page latching is used instead for consistency checksNew network flows for delivering LOBs–JDBC, SQLJ, and CLI will let server determine whether to flow LOB values or LOCATORs based on size thresholds–Significant reduction in network traffic–Greatly reduces frequency of FREE LOCATOR statements

11



CREATE TABLE … APPEND(YES)

New APPEND option:–Maximizes performance for “INSERT at end”–Avoids overhead of attempting to preserve clustering sequence–CREATE or ALTER table



DDF Improvements64-bit addressing by DDF– Special “shared private” with xxxDBM1 to eliminate many

data moves on SQL operations

Support for IPv6 and SSL

VTAM definition is now optional

Prepare for elimination of PRIVATE protocol requester– Includes tools for identifying which packages need to be

bound at remote servers

12



Index ImprovementsINDEX on expressionPage sizes 8K, 16K, 32K

– Fewer page splits for long keys– More key values per page

Improved page split– INSERT at the end of the key range used to result in 50% free space in each

index page– Enhanced support dynamically adapts page split boundary to minimize wasted

space in index pages

Online REBUILD INDEX REORG without BUILD2 – not just for DPSINot logged index spaceXML indexIndex key randomization



Index CompressionCompression of indexes for BI workloads– Indexes are often larger than tables in BI

Solution provides page-level compression– Data is compressed to 4K pages on disk

– 8K, 16K or 32K pages results in 2x, 4X or 8x disk savings

– No compression dictionaries – compression on the fly

13



Index Compression: Differences between data and index compression

25% - 75% (3)10% - 90%Average Comp Ratio

No (2)YesComp Dictionary

NoYesComp in Log

NoYesComp in Buffer Pool

YesYesComp on disk

Page (1)RowLevel

Index Data



Converged TEMP Space

Single source for all temporary space in DB2, replacing: DSNDB07, temp databases, workfiledatabase

Access is virtualized for small amounts of data, eliminating cost of work file creation (reduced CPU and I/O)

Supports 4K and 32K page sizes, with automatic selection of the appropriate page size

New Zparm for preventing workfile monopolization

14



DB2 9 Vstor Constraint ReliefDDF address space runs in 64-bit addressing mode– Shared 64-bit memory object avoids xmem moves between DBM1 and

DDF and improves performance– Constraint relief

DBM1, the following are moved above the bar in V9– Parse trees– EDM fixed pools- SKPTs / SKCTs (primarily static SQL). Also part of CTs/PTs- Pageset blocks, RTS blocks- Local SQL statement cache- Some thread-related storage

For installations that are constrained on DBM1 vstor:– 200 to 300MB or more of savings expected– Mainly from EDM related storage (static SQL) and dynamic statement

cache (dynamic SQL)



Other cost of ownership improvements

Resource Limit Facility enhanced to allow CPU cost to be controlled based on:

• Client workstation / app name• Client userid, IP address

SMS integration– CREATE & ALTER STOGROUP SMS constructs

Utilities template switching

RENAME SCHEMA, VCAT

Command line processor

Optimization Service Center

15



Utility CPU time reduction up to –* primarily from index processing

10% to 20% in Copy, Recover table space / index*5% to 30% in Load*, Reorg*, Rebuild Index*20% to 60% in Check Index*35% in Load Partition*30% to 40% in Runstats Index*40% to 50% in Reorg Index*70% in Load Replace Partition with dummy input*


IBM Software Group


Continuous Availability

16



Schema Evolution – Database Definition On Demand

Rename column and indexImprove ability to rebuild an index onlineOnline reorganization with no BUILD2 phaseModify early code without requiring an IPLAlter table space and index logging



CLONE TablesAllows fast replacing production data without renames and rebinds – A capability to support online load replace

ALTER TABLE to create a Clone Table– All indexes are also cloned

– Table and Index data are not copied

– Base and Clone tables share the same table space and index names

– Underlying data sets are differentiated by a data set instance number

17



CLONE Tables…

A clone table can only be created – On a single table in a table space (partitioned or non-

partitioned)

– No RI or Trigger on the base table

Use insert or load to populate clone tables

Utilities (except RUNSTATS) can operate on clone tables with a new CLONE keyword



Partition by GrowthNew partitioning scheme:– Single table tablespace, where each partition contains a segmented pageset (allows segmented to increase from 64GB to 16TB or 128 TB with 32K pages)–Eliminates need to define partitioning key and assign key ranges–A new partition is created when a given partition reaches DSSIZE (defaults to 64G)–Retains benefits of Utilities and SQL parallelism optimizations for partitioned tables

18



DB2 9 UtilitiesSupport for new functions (universal table spaces, XML, not logged, etc.)Rebuild Index SHRLEVEL CHANGE

– Great for building new non-unique indexes

Reorg enhancements– Reorg LOB now supports SHRLEVEL REFERENCE – LOB space reclamation– Partition-level capabilities (not available with REBALANCE)

• Partition parallelism (UNLOAD/RELOAD) in a single utility statement• Elimination of the BUILD2 phase outage

Recover to consistent PIT without need for a quiesceAlways perform CHECKPAGE on the COPY utility

– Prior to V9, CHECKPAGE was optional, with about ~5% CPU overhead, and if a broken page was encountered (DSNU441I for space maps or DSNU518I for others, both RC8), then copy-pending was set

– Now, COPY always performs these checks (with reduced overall CPU!) and no longer sets copy-pending, so…. Check those RCs!

– A new SYSCOPY record type is written if a broken page is detected to force a full image next since dirty bits may have already been flipped off in the space map pages



Volume-based COPY/RECOVERFlashCopy technology used to capture entire content of disk volumes

RECOVER modified to enable object-level recovery from volume FlashCopy– Restore assumes that the object has not moved volumes

Eliminates labor associated with setting up COPY jobs for each database / table space

Full integration of tape into BACKUP/RESTORE SYSTEM utilities

19



DB2 9 Data Sharing EnhancementsRestart performance enhancements– Reduced impact of retained locks– Open datasets ahead of log apply– Avoid locks that have potential of ‘hanging’ restart

Auto-recover GRECP/LPL objects on group restart– Useful in Disaster Recovery or GDPS scenarios

Use of DPSI to avoid data sharing overhead– DPSI can be unique within partition

Detect use of unused indexes so they can be dropped– Reduces data sharing overhead



DB2 9 Data Sharing Enhancements…Command to remove GBP-dependency at object level– ACCESS DB MODE(NGBPDEP)– Typical usage would be before batch run– Issue on the member on which you plan to run batch

Command to “prime” open dataset– ACCESS DB MODE(OPEN) [PART]

Log latch contention relief (avoid LRSN “spinning”)Improved performance for GBP writes– Avoid copying pages for batched writes

DB2 overall health taken into account for WLM routingBalance group attach connections across multiple members on same LPAR (V7, V8 usermod)

20


IBM Software Group


DB2 9 XML



DB2 9A New Generation Hybrid Data Server

Business data in XML form managed in relational database

Business data in XML formmanaged with DB2 pureXML

High cost developmentPoor performance

Streamlined developmentHigh performance

Or

21



Contrasting the ModelsXML and Relational

Over $20B Annual Customer Technology Investment in RDB Alone…

Relational– Strength: Static data

• Strict schema ensures data integrity• High performance indexing on fixed data

– Strength: ‘Set-based’ data• Multiple results returned• Retrieving rows

XML– Strength: Semi-structured, frequently changing

data• Self-describing, flexible schema• Easily modified format

– Strength: Retrieving sequences• Documents, subdocuments, related documents XML database investments

growing twice as fast as total database investment…



XML Data Needs Relational MaturityComplementing XML Processing

XML Data Needs Protection– Backup and recovery features to ensure continuity– Data is protected using database security

Simplified XML Data Access– Centrally store and access difficult to retrieve data– SQL or XPath can be used to retrieve data– Join XML data with it’s related relational data

Search Speed– Search documents quickly and efficiently using proven

search optimization engine of mature database

Optimize Existing Investments– Use existing technology infrastructure and skills to store

and manage both relational and XML

22



pureXMLSupport XML data typeStore the XML document nativelyDDL --– CREATE/ALTER Table with XML type column

• Implicitly create XML Auxiliary objects (tablespace/table/index) - one per XML column

– Index support• Created by users• uses XPath to determine which nodes in the XML document to index.

CREATE INDEX dependentName ON deptTable(deptDocs) GENERATE KEY USING XMLPATTERN '/department/empl/dependent/name'

ATOMIC AS SQL VARCHAR(20);

INSERT/UPDATE/DELETE– INSERT with VALUES and SUBSELECT– No Subdocument update



pureXML -- QueryEnhanced V8 XML Constructors (XML Publishing Functions)SQL/XML Functions and Predicates– XMLParse - Convert a XML text to XML value– XMLSerialize - Converts XML to character type– XMLQuery - executes an XPath expression against an XML value.

SELECT XMLQUERY ( '//item[USPrice = $price] ' PASSING PO.POrder,T.price AS “price”) FROM PurchaseOrders PO, T;

– XMLCast - Cast XML to other types or other types to XML– XMLExists - a predicate, which returns TRUE if the XPath expression

evaluates to a non-empty sequence

SELECT PO.pid FROM PurchaseOrders PO, TWHERE XMLEXISTS( '//item[USPrice = $price] '

PASSING PO.POrder, T.price AS “price”)

23



pureXMLXPATH supported features from XPath 2.0:Utility Support– LOAD/UNLOAD, CHECK DATA/INDEX, COPY, REBUILD,

RECOVER, REORG, etc.

XML Schema Support– XSR – XML Schema Repository– Tables to store XML schemas– Stored procedures to register XML schemas

DSN_XMLVALIDATE() SQL/XML function– Test XML values for validity against XML schema– Obtain default values and schema normalized values from XML

schema

XML decomposition using annotated XML schema


IBM Software Group


Migrating to DB2 9

24



V9 Catalog

V8

V9

Data Sharing

Coexistence

V9 Compatibility

Mode (CM)

V9 Enabling

New Function

Mode (ENFM)

V9 New Function Mode

(NFM)

V9 Migration Overview

CATMAINT UPDATE

(DSNTIJTC)

CATENFM COMPLETE (DSNTIJNF)

CATENFM START

(DSNTIJEN)

V8 Catalog

V9 Libraries

V8 Libraries

ONE WAYONE WAY

STOP

1 – 2 months 10 minutes

V8 NFM with SPE

weekend



Migration & Fallback Paths

DB2 9 CM DB2 9 ENFM DB2 9 NFM

DB2 9 CM*

DB2 9 ENFM*

DB2 V8NFM

DB2 9 CM*

25



V9 Modes – An OverviewCM “Compatibility” Mode - This is the DB2 mode DB2 V9 migrated from V8 and is started forthe first time. It will still be in CM when migration job DSNTIJTC has completed. Very little new function can be executed in CM. Data sharing systems can have V8 and V9 members in this mode, called coexistence. Coexistence should be very short, such as a weekend or a week. DB2 can only migrate to CM from V8 NFM. This mode is not so much compatibility, as the ability to fall back. We try to move most (but not all) problems for migration from NFM to CM, so that fallback can be used, if necessary.ENFM Enabling New Function Mode - This mode is entered when CATENFM START is executed (the first step of job DSNTIJEN). DB2 remains in this mode until all the enabling functions are completed. Data sharing systems can only have V9 members in this mode. NFM New Function Mode - This mode is entered when CATENFM COMPLETE is executed (the only step of job DSNTIJNF). This mode indicates that all catalog changes are complete and new function can be used.ENFM* This is the same as ENFM but the * indicates that at one time DB2 was at NFM. Objects that were created when the system was at NFM can still be accessed but no new objects can be created. When the system is in ENFM* it can not fallback to V8 or coexist with a V8 system.CM* This is the same as CM but the * indicates that at one time DB2 was at a higher level. Objects that were created at the higher level can still be accessed. When DB2 is in CM* it can not fallback to V8 or coexist with a V8 system.



V8 best practice performance plan example

-2-101234567

V7 V8 CM V8 NFM V8 use

CPU

Data sharing Better statistics DB design adjustments REBIND Cluster, index PGFIX(YES) application changeszIIP multirow fetch & insertzparms SQL adjustments

Your situation will vary. Less CPU is better.

26



DB2 9 z9 & z990 performance plan example

-6

-5

-4

-3

-2

-1

0

V8 V9 CM V9 NFM V9 Use

CPU

Utilities DB design adjustments Histogram statistics Index improvementsREBIND application changesDSNZPARMS native SQL procedures

SQL adjustmentsYour situation will vary. Less CPU is better.



Migration Strategy: Test and Production

Short time for data sharing coexistenceOne to two months for compatibility modeƒNot able to use most new performance

Short time for enabling new function modeMove to new function modeƒStage in new function

Test to QA to ProductionƒBetter controls for not using new functionƒStill don't want long gap test to productionƒVendor support may affect strategy, e.g. NFM certifiedƒImproved granularity, stage by modes

27



Premigration Activity ...

Find problems with incompatibilitiesƒIt is important to look at these now because many

have actions that you must address before migrating.

ƒGet the complete list from the Installation Guide (Get the latest from the web).

ƒNew V8 job DSNTIJP9 APAR PK31841



Installation Guide for detailsChapter 8. Migrating the DB2 subsystem to compatibility mode

Changes to DB2 that might impact your migration to Version 9.1 compatibility mode

Application and SQL release incompatibilities Utility release incompatibilities Command release incompatibilities Storage release incompatibilities Other release incompatibilities Functions that are no longer supported Functions that are deprecated Data sharing group or distributed environment migration

Chapter 9. Enabling new-function mode Conversion considerations (for NFM changes)

Application Programming and SQL frontApplication and SQL release incompatibilities

Version 9 incompatibilities

28



DB2-managed stored procedures WLM-managed SPsAIV Extender Content ManagementText, Net Search Extenders new text searchNet.Data WebSphere, REXX, CLP, …DB2 Estimator capacity planning productsOld JDBC / SQLJ driver Current driverCreate simple table space segmented partition by growthOnline help Information CenterVery old plans and packages (V3 and before) REBIND

Version 9 removed function



XML Extender new XML typeLoading DSNHDECP directly new interfaceDB2 MQ XML user-defined functions and stored procedures

new XML functionsmsys for Setup DB2 Customization Center install panelsDB2 Management Clients feature, which includes DB2

Administration Server, DB2 Control Center, and DB2 Development Center new administration servicesPrivate protocol DRDA (new help in DSNTP2DP) Simple table spaces segmented or partitioned by growthPlans containing DBRMs, ACQUIRE(USE)

Version 9 deprecated function

29



Best process is rebind all in NFM, top 10% in CMHighly recommended to rebind all V8 and below

PDSE is required for SDSNLOAD. PDSE service needed.Premigration job DSNTIJP9 APAR PK31841SPE PK11129, PK33664, PK39850, Info APARs: Install II12423, Unicode II13048 & II13049,

DFSORT II14047, II14213 & II13495, DDF II14203, zIIP II14219, Performance II13579, Storage II10817, Parallel II12836, LOBs II13767, DSNUTILS sec. id. II13133, Coprocessor II13782, PDSE II14067, …

Version 9 migration process changes, APARs



Changes to defaultsBIND ISOLATION defaults to CS

Not changed for distributed, REBINDBIND CURRENTDATA defaults to NO

Not changed for REBINDDB2-managed data set secondary extent allocation default YES, even for migrationVarying length data changes row formatOnline REORG processes changeConfigure shared virtual storage (128 GB for each DB2)

Version 9 default and process changes

30



V9 Prerequisites: See Program Directories

Processor requirements:– Processor that supports z/Architecture, including IBM System z9,

zSeries z990, z890, z900, z800– DB2 9 will generally require increased real storage for a workload

compared to DB2 V8Base Software Requirements:– z/OS V1.7

• DFSMS Version 1 Release 7• Language Environment Base Services• z/OS Version 1 Release 7 Security Server (RACF)

– IRLM V2.2– z/OS Unicode Services & appropriate conversion definitions– DB2 Utilities Suite or equivalent function



V9 Prerequisites: Current software

– Migrate only from DB2 V8 in NFM– DB2 for Linux, UNIX, Windows V9.1 FP1 or V8.1 FP13 (V8.2 FP6 is

the same as V8.1 FP13)– DB2 Connect V9.1 FP1 or V8.1 FP13– IMS V10, V9, V8– CICS V3.1, V2.3– Enterprise COBOL V3.4– Enterprise PL/I V3.4 Move to V3.6– IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS, V4

or Performance Monitor, PK36297

31



V9 Requirements for Dependent Functions

Volume based utilities require:– z/OS 1.8– DFSMShsm 1.8– DFSMSdss 1.8– FlashCopy Version 2Group Bufferpool Batching:– CF level 15 or 14 recommended when using System Managed

Duplexing for lock or SCA structures • CFLEVEL 15 structure sizes grow

– CF level 13 recommended for castout and lock table cleanup enhancements

– CF level 12 for improved V8 and 9 performance GBP batching

These are highlights only, not

a complete list!

See Program Directories.



DB2 Connect Version 8.1: Fixpak 13 now, minimum 10DB2 9 requires V9 FP1 or V8.1 FP13

Performance & ScalabilityImproved Application AvailabilityInnovative manageabilityProgrammer productivity

Crypto V8.2 FP 10

32



How current should we be?Stay reasonably current with DB2 releases & fixesBalance for severities. Use Consolidated Service Test.ƒPotential PTF in Error or PE: Enhanced HoldDataƒProblems encountered instead of avoidedƒBusiness constraints and work load



Use Consolidated Service Test

Service Update (SUP) June 15, 2007

Recommended Service

Cross product tested levels Best practice for service:

two or three per yearhttp://www.ibm.com/servers/eserver/zseries/zos/servicetst/mission.html

Service Best Practice

33



Plan to REBIND plans and packages

Old plans and packages have more to gain and less to lose, in general

Compat mode – how long?ƒMost optimizations included ƒRebind key packages at least

New function mode – as you adjust database design, applicationsƒClustering, NOT PADDED indexes, DPSIƒIS NOT DISTINCT predicate, MQTƒMultirow fetch & insertƒUnicode DBRMƒRebind all plans and packages (may stage)



USS ODBC Driver Updates

Shipped– PQ86094

• Separate the INI keyword CURRENTAPPENSCH from the wide APIs and the C data type SQL_C_WCHAR.

• Allow ccsid override in retrieving LOB data through the API SQLGetData(). The INI keyword CURRENTAPPENSCH will now accept a CCSID value in addition to the encoding schemes EBCDIC, ASCII and UNICODE.

– PQ92072 – Optimize the array input method for bulk insert

In progress– PQ15288 – Optimize bulk fetch for the ODBC API SQLExtendedFetch()

when retrieving data into arrays

– PK29427 – Support Unicode literals in the input SQL statement texts with the PATCH2 keyword

34


IBM Software Group


What’s Next



DB2 9 additions after GA XML extensions: e.g. XMLTABLE and XMLCAST Text index server

• Text search CHAR, VARCHAR, CLOB & XML columns• Efficient communication interaction with DB2 for z/OS• Text indexes kept in DB2 tables for backup & recovery

Optimization, utilities, spatial, security and ALTER changes

DB2

DB2

DB2DB2

ParallelSysplex

TextServer

TextServer

TCP/IP

35



DeployDeploy

ManageManage

GovernGovern

DevelopDevelop

DesignDesign

Common InterfaceUser

DatabaseArchitect

DatabaseDeveloper

IBM

Other

Design• Logical Modeling• Physical Modeling • Integration Modeling

Develop• Coding• Debugging• Teaming• Testing• Tuning

Govern• Security Access• Security Analysis• Data Auditing• Data Archiving• Data Masking• Data Encryption

Database Administrator

Manage• Database Administration• Data Management • Change Management• Recovery Management• Storage Management• Performance Management

BusinessAnalyst

Application Developer

Security Administrator

A Consistent, Integrated SolutionA Consistent, Integrated Solution

IBM Data StudioIBM Data Studio



Application Development & Administration Client

API support – Java pureQuery (JLinQ)– Open Source (PHP, Python, Ruby, etc.)– .NET, EGL, and other technologies

SOA / Web Services / Web Access– Data Server Web Services

AD tooling F10, F11– .NET, DWB, RAD

Administration tooling– Rational Data Architect (RDA) – IBM Data Servers Administration Console

36



Beyond DB2 9 Improvement Focus AreasPerformance: OLTP, Query, Index & LOBsScalability & 64 Bit MemorySQL & SQL Procedures XMLSOASecurityAvailabilityAutonomics

AdministrationSecurity



Utilities and Tools Futures

Web-based administrative consoleHigh priority requirements– Auto-stats– Auto-storage management– Auto-compression– Recover to a different table space in a different DB2 with

consistency– Reduce RUNSTATS resource consumption– Dataset-level FlashCopy– UTSERIAL elimination– REORG Enhancements (LOBs, etc.)– …

Manual invocation of•RUNSTATS•COPY/BACKUP SYSTEM•QUIESCE•MODIFY RECOVERY•REORG

37



DB2 for z/OSDelivering Customer Value / Future Version Philosophy

V7V8

DB2 92001

2004

2007

20xx

DB2 X

64 bit data definition on demand

pureXMLtm



IBM System z10 Enterprise Class Faster CPUs, more CPUs, more memory– 50% more n-way performance “on average”, 62% more uniprocessor

performance, 70% more server capacity (56->64 CPUs)

– Up to 64 CPUs, z/OS 1.9 needed for 64-way in a single lpar

– Up to 1.5 TB, z/OS 1.8 needed for >256G in a single lpar

Decfloat facility

1MB page size (DB2 vNext)

Infiniband CF links (also z9, will benefit all DB2 releases, z/OS support rolled back to 1.7)

New OSA-Express3, 10 GbE for faster remote apps

New CPU instructions. V10 will exploit

38



z/OS 1.10 (benefits all DB2 releases, unless specifically noted)HiperDispatch (rolled back to z/OS 1.7)EAV up to 223 GB/volume– VSAM data sets only in first release– needs appropriate DS8000 ucode, DB2 apars on V8/9

Additional XML exploitation of zAAP and zIIPXMLSS enhancements (DB2 V9)WLM enhancements for lower priority lock holders to boost priority when higher priority waiters (plan is for V8 and above)TCP/IP performance enhancementsHash DSAB for better Open/Close performanceBasic Hyperswap, rolled back to 1.9 (Remove DASD controller as a SPOF)zIIP assisted Global Mirroring, rolled back to 1.9DS8000 enhancements– Lower cost for long distance Global Mirroring– Incremental Metro/Global Mirroring, up to 95% faster resync times after a

HyperSwap



39


IBM Software Group


References



DB2 9 for z/OS Redbooks

Powering SOA with IBM Data Servers SG24-7259

LOBs with DB2 for z/OS: SG24-7270

Securing DB2 & MLS z/OS SG24-6480-01

DB2 9 Technical Overview SG24-7330

DB2 9 Performance Topics SG24-7473

DB2 9 Optimization Service Center SG24-7421

DB2 Stored Procedures SG24-7083-01 update

40



DB2 9 for z/OS Web Page ibm.com/software/db2zos/db2zosv91.html



zIIP ibm.com/systems/z/ziip/ II14219 II12836 II10817

41



Library page ibm.com/software/db2zos/library.html

•Download 40 PDF books•Access html books

•DB2 updatesMar 2007•QMF•Program Directories•Information Center



DB2 Cross-Platform SQL Referencehttp://www.ibm.com/developerworks/db2/library/techarticle/0206sqlref/0206sqlref.html

42



http://www.ibm.com/support/docview.wss?rs=434&context=SSZJXP&dc=D600&uid=swg21256800