DB2 10 for z/OS Migration Facts&News from the Region

Saso PrekIBM SWG

Agenda:

●DB2 10 for z/OS migration hints

●Justifying DB2 10 for z/OS

●Existing limits: CPU, virtual storage, latching, DB2catalog and directory, utilities, …

●Process of getting ready, migrating

●Prerequisites and deprecated functions

●What to expect from migrating to DB2 10 for z/OS

●Real Customer Examples

V8 – V9 – V10 split (Q12011)

V8 xx%V9 xx%V10 xx%

●DB2 10 has had the fastest uptake that we have seen in many many releases - about 3x what we saw at the same time in V9.

●It's still early in terms of having a lot of customers in production yet, but it's off to a strong start.

Compared to V8 – V9 ?•Lower overall PMR volume•Less Severity 1 APARs•Lower PE rate•Lower HIPER rate

DB2 V8 DB2 9 DB2 10

Key Questions are WHEN? and HOW?

Feedback: Top Items Driving DB2 10 Migration Decisi ons

CPU / Performance improvements

Virtual storage enhancements•Reduce number of members, save money

Security enhancements•Built-in security, trace & audit features,

new roles, end-to-end auditing•Better audit/compliance

Temporal tables

Skip-level migration DB2 V8 -> DB2 10

Vast majority of beta customers plan migration in 2 011

Sample Improvements

Run time CPU reductions 5% - 10%1 MB page size 0% - 5% z10, z196Page fix buffers 0% - 8% V8 & high IO, in use?Release deallocate 0% - 15% short trans, batchVirtual storage constraints 0% - 5% memory, latches

Improved dynamic SQL cache 0% - 20% literalsInsert 0% - 40% high volume insertPredicate evaluation 0% - 60% complex predicatesAccess: hash, index include 0% - 5% access improvedIncreased use of zIIP 0% - 3% IO, RUNSTATS, parallelUtilities (from V8) 3% - 20% about same for 9 -* 10Productivity: memory, temporal, security, admin, ... priceless

Migration path options:

DB2 10

DB2 9

V8

V7

DB2 9 -> DB2 10

DB2 8 -> DB2 9 -> DB2 10

DB2 8 -> DB2 10

Are you ready for DB2 10?

●Check prerequisites●Migration planning workshop●Plan gains, testing, memory, and performance●Build detailed migration plan●Contact vendors●Get all the parts out of the box●Check information APAR●Apply required service●Run premigration checks DSNTIJPA (or M) early and often●Resolve incompatible changes●Get rid of private protocol●Convert to packages from DBRMs in plans●Upgrade plan table formats to Unicode V8 or DB2 9 level●Get ready for SMS●Save performance and access path information – how?

Free Migration Planning Workshops DB2 10, 9, 8

The primary components:- DB2 10 for z/OS Overview- DB2 10 Migration - general- DB2 10 Migration – step by step- Checklists- DB2 10 Project Plan

Free Migration Planning Workshops DB2 10, 9, 8

Understand breadth of features in DB2 for z/OS

Bring together a toolbox of resources for your migr ationplanning

Explain the current migration processBring a project focus to migration

Remain relevant through GA life of the product• Updated with field experiences

Free Migration Planning Workshops DB2 10, 9, 8

Convert plans with DBRMs to packages

•Convert from DBRMs in PLAN to packages•Specify the collection id for the packages•REBIND plan option: COLLID•Default collection id

DSN_DEFAULT_COLLID_planname•Able to specify plan name, list of plans, *•DB2 9 APARs PK62876, PK85833, PM01821•V8 APARs PK79925, PM01821•See Packages Revisited book

SG24-7688 chapter 4

Convert private protocol to DRDA•Trace to find use of private protocol•JCL DSNTIJPT •Private protocol trace analysis program DSN1PPTP•Use DRDA protocol REXX tool DSNTP2DP•Private protocol statement checker DSNTPPCK•Set PRIVATE_PROTOCOL parameter to NO•Changes provided in base, PK92339, PK64045•See Distributed bookSG24-6952-01 chapter 5.2

SMS now a prerequisite for DB2 catalog & directoryImportant – All new catalog indexes and new table

spaces WILL be SMS controlled.“SMS now a prerequisite of DB2 10”. So be prepared!

All new indexes & new table spaces in the catalog and directorycreated SMS-controlled with extended addressability (EA & EF)

DSNTIJSS provides SMS classes for customers without SMS in useEnvironment ONLY for DB2 Catalog & Directory data sets Other DB2 data sets such as logs and BSDS not covered

.Useful SMS reference material includes:

z/OS DFSMS Introduction.z/OS DFSMS Implementing System Managed Storage.z/OS DFSMS Storage Administration Reference.

IBM Redbooks publication: Maintaining your SMS environment

Package or Access Path Stability

PLANMGMT default changed to EXTENDED•Retains 3 versions: Current, Previous, Original•Ability to SWITCH to another version or fallback•Catalog information provided, new structures•BIND costs in CPU, disk space, and memory•If cost is too high, change default, use selectively

Performance enhancements requiring few changes (CM)

SQL runtime improved efficiencyAddress space, memory changes to 64 bit, some REBINDsFaster single row retrievals via open / fetch / close chainingDistributed thread reuse High Performance DBATsDB2 9 utility enhancements in CM8Parallel index update at insertWorkfile in-memory enhancementsIndex list prefetchSolid State Disk use

Buffer pool enhancements•Utilize 1 MB page size on z1 0

Performance enhancements requiring REBIND (CM)

Most access path enhancementsFurther SQL runtime improvementsUse of RELEASE(DEALLOCATE)SQL paging performance enhancements

•Single index access for complex OR predicates:IN list performance

•Optimized Stage1 processing (single or multiple IN lists)•Matching index scan on multiple IN listsSafe query optimizationQuery parallelism improvementsMore stage 2 predicates can be pushed down to stage 1More aggressive merge of views and table expressions

•Avoid materialization of viewsIf migrating from V8, get new RUNSTATS before mass rebind

Performance enhancements requiring NFM

DB2 catalog concurrency and productivityCompress on insert

Most utility enhancements

LOB streaming between DDF and rest of DB2Faster fetch and insert, lower virtual storage consumption

SQL Procedure Language performance improvements

Workfile spanned records, partition by growthAccess to currently committed data

Insert improvement for universal table spaces

Locking improvement for multirow insertEfficient caching of dynamic SQL statements with literals

1

Performance enhancements which need NFM + DBA work

Hash access path Create + Reorg + rebind to activate

Index include columns Alter + Rebuild + rebind to activate

Inline LOBs Alter (need universal table spaceand reordered row format)

DEFINE NO for LOB and XML columns

MEMBER CLUSTER for universal table space Alter + Reorg

Online reorg for all catalog and directory table spaces

Update installation CLIST input (DSNTIDxx) to reflectcurrent subsystem parameters & bufferpool settings

DSNTXAZP(job DSNTIJXZ)

E x i s t i n g S S I D DSNTIDxx

DSNTZAZP

UpdatedDSNTIDxx

Stored procedure information improvements

© 2009 IBM Corporation

Stored procedure information

easier to find

•Implementing stored procedures

•DB2 reference information added

Added more information:

Setting up WLM

Granting privileges

Moving stored procedures from

test to production.

Clearer information

Important features of information centerFind helpful usage instructions in the “Information center home” section.

Easily send feedback by clicking the Feedback link at the bottom of any topic.Conveniently download the PDF version of the information from the link at thebottom of any topic. (Look for the PDF icon!)Efficiently search for the information you need by using the search features.

Why Migrate to DB2 10 for z/OS?Business needs to save money•Reduce CPU time & disk space•Improve business agility•Service Oriented ArchitectureApplication developers need•PureXML for a powerful SQL

and XML interface to XML data•Powerful new SQL

enhancements•Portability with SQL and data

definition compatibility

Database Administrators need•Improve availability and

performance•More flexible security and

easier regulatory compliance•Better web application &

data warehouse function andperformance

•LOB function, performance,usability

Best Practices/RecommendationsStart with latest RSU + Identified HipersLeverage CST/RSU process: DB2 9 & 10

•Apply 2 to 3 preventative service drops annually•Exploit Enhanced HOLD DATA to be vigilant on HIPERs and PEs

Use the DB2 9 'Package Stability' function for stat ic SQL•Offers access path preserving option. Recovers to prior access path

if regression is encountered•PK52523 - DB2 Access Path Stability

Minimize potential query performance issues•Use Optimization Service Center to capture SQL statements•Run Stats Advisor to generate the recommendation for stats

collection•Run RUNSTATS to ensure critical stats are collected as

recommended by the advisorEnsure a PMR is opened prior to migration start

So where do I go from here?

No need to fear DB2 migration; but be cautious & th oughtful•Ensure good planning, staying reasonably current on

preventative service and application regression testing•Follow best practices/recommendations

•PMR opened•Trends are improving!Procedural upgrade easier

Every customer experience is different

Compared to V8 – V9 ?•Lower overall PMR volume•Less Severity 1 APARs•Lower PE rate•Lower HIPER rate

Old COBOL? Old programs? DSNHPC7

"Understand the options DB2 CICS V3●Compiler and Run-Time Migration Guide●No compiles OS/VS COBOL or VS COBOL II CICS V3 also●Run Old COBOL modules

"Set strategy & plan for Enterprise COBOL V4.2●Use old precompiler?●NEWFUN(V9 or V8)?

"Plan staging and Migrate

Old PL/I? Old programs? DSNHPC7

Understand the options●Compiler and Run-Time Migration Guide●Run Old PL/I modules

Set strategy & plan for Enterprise PL/I V3.9●Support requires at least V3.7 now

●Use V8 precompiler?, NEWFUN(NO)?Plan staging and Migrate

DB2 9 and 10 require DB2 client & Connect 9 FP1Recommend latest level9.7 fixpack 3a needed for DB2 10 new functions:

●Dynamic statement cache enhancements.●Timestamp with timezone.●Greater timestamp precision.●Client/Server Binary XML Format●Extended indicator variables●Explain mode special register●Unicode collection and package names

http://www.ibm.com/support/docview.wss?uid=swg24028306

DB2 Connect V8 out of

service April 30, 2009

Temporary Space DB2 9 Picture

Createdglobal

temporarytables

Work files

WORKFILE

Declaredglobal

temporarytables

Installation and migration support (REXX program called by DSNTIJTM)

CREATE DATABASE xxx as WORKFILE;

DSNTWFG DB41 DB2ADM xxx +

SSC

BP32K SYSDEFLT16201temporarytables for

BP0 SYSDEFLT +16103Declared

Declared Global Temporary Tables and Static Scrollable Cursors nowuse the WORKFILE database instead of the TEMP databaseUse DB2-managed (instead of user-managed) storage inSYSDEFLT storage groupSegmented table space organisation (user-defined SEGSIZE or defaultof 16)4KB and 32KB page sizes only – no 8KB or 16KB, Much more 32KBChanges in PK70060, more in PM02528, install PM17336

Service Best PracticeDB2 9 or 10

Use Consolidated Service Test

Recommended ServiceCross product tested levels Best

practice for service:two or three per year ?

http://www.ibm.com/servers/eserver/zseries/zos/servicetst/mission.html

II14401 & II14464 install service II14474 or II14477 for 10

Premigration Activity ... Manage Performance

Prepare to manage performance

•Save accounting reports•Save critical access paths•Be sure you have PLAN_TABLE access paths &

DSN_STATEMNT_TABLE &DSN_FUNCTION_TABLE for criticalapplications (or Visual Explain reports or OQT).

•Run EXPLAIN on queries before migrating.•Add new columns to PLAN_TABLE•Differentiate by plans & packages

To REBIND or not to REBINDWHEN? is the question•When to take the chance of access path regression ?•For the potential benefits of improved perfrmance & memory

When migrating? Test Before•Parallel individual binds•More disruptive, longer

Incrementally or later•More potential for problem calls•Resolution could be more difficult

Package or Access Path Stability PK52523At REBIND, save old copies ofpackages

•Catalog tables•Directory (SPT01 table

space)Two flavors

•BASIC and EXTENDED•REBIND options•Default new DSNZPARMREBIND PACKAGE ...

•PLANMGMT (BASIC) 2copies: Current & Previous

•PLAN MGMT (EXTENDED)3: Current, Previous, & Original

Most bind options can be changedat REBIND.

REBIND PACKAGE ...•SWITCH(PREVIOUS)

Switch between current & previous•SWITCH(ORIGINAL)

Switch between current & originalFREE PACKAGE ...•SCOPE(ALL) – Free package

completely•SCOPE(INACTIVE) – Free old

copiesEach copy invalidated separatelyCost of stability•2-3 X size in SPT01 - PK80375

compression•30% CPU overhead for REBIND•No impact on statement runtime

processing, fast switch

Best practices for DB2 upgrade1) Get the right service level2) Be ready for performance & access path

management3) Set up the work space carefully, more 32K, limit4) Use new dynamic data format – only for T45) Watch for recent and upcoming changes6) Check the web for the latest books, advice,

service, and best practices informationwww.ibm.com/developerworks/data/bestpractices/db2zos/

Next phase: Use the new function, get the valueReduce CPU timeSave disk space

Productivity for applications &administrators

•PureXML & Data Studio•SQL & LOBs•Portability via SQL & data

definition compatibility

Improve availabilityMore flexible securityEasier regulatorycompliance

Web applicationsData warehouse functionand performance

Customer Experiences

Customer experiences say pay attention to:Read the web, books, Info APARs, PSP

Have a plan that includes performance

Run premigration job DSNTIJPM– Use DSNTIJP9 or DSNTIJPA job

On every subsystem

Current maintenance for DB2, z/OS & CF

Get the latest books: library, IBM Redbookspublications, Information Center

Get updated bookshttp://publib.boulder.ibm.com/infocenter/imzic/"'Administration Guide"'Data Sharing: Planning and Administration"'Performance Guide"'Utility Guide and Reference

"'Application Programming Guide & Reference

"'Application Programming Guide & Reference for JAVATM"'ODBC, Spatial, ..."'Red books"'Installation Guide

"'RACF Access Control Module Guide"'Messages"'Codes

More information and resources

DB2 for z/OS Lifecyclehttp://www.ibm.com/software/data/db2/support/db2zos/

© 2009 IBM Corporation9

ClickPlanning,then the“ProductSupportLifecycle”

link

DB2 9 Technical Resources pageibm.com/support/docview.wss?rs=64&uid=swg27011656

•Download 30PDF books

•Access htmlbooks

•DB2 newDecember2010

•ProgramDirectories

•InformationCenter

www.ibm.com/developerworks/data/bestpractices/db2zos/

Watch recorded presentations. Read papers from your favorite DB2 experts.Get practical recommendations for areas such as:

•Virtual storage tuning•Security•Software maintenance strategies•Migration•Setting up application servers to

access DB2 for z/OS•Partitioning table spaces•Debugging stored procedures

And more!

Send feedback and topic suggestions to db2zinfo@us.ibm.com

© 2009 IBM Corporation

Planning Your Migration to DB2 10 for z/OS

Questions?

113

43 © 2011 IBM Corporation

Real situation: Customer #1Reason to migrate

- Existing Z10 - CPU improvements expected - New authorization improvements – granular security - row permission - Native SQL SP enhancements ( ‘extreme’ WLM problems in production)

o Casting from numeric to character - SELECT '1' + 1 from SYSIBM.SYSDUMMY1 o SQL scalar functions by allowing the use of SQL Procedural Language (SQL PL) in

the function body Decision process

- based on strict customer philosophy (be up-to-date with SW Rel for all platforms) GTS support or not - Partially in process of PTF handling (++HOLD,....) Project stages - Standard – as recommended by MPW Additional tools used for migration

- OMEGAMON XE for DB2 PE – saved KPI - DB2 Administration Tool - GEN command, EXPLAIN, - DB2 SQL Performance Analyzer reports

Issues during migration - DB2 UDB on LUW – old versions - PMR - abend in job DSNTIJEN – problem solved – waiting for PTF Benefits after migration from customer point of view

- few instances already in production - NFM - CPU improvements according to expectations - SQL SP and Functions used efficiently - Starting with new features – Temporal tables

43 © 2011 IBM Corporation

Real situation: Customer #2Reason to migrate

- V2V skipped release (V8 > V10) – requirement from SAP - OM PE V5 installation - EI support (z/OS 1.10 is prereq)

Decision process - defined within existing project for SW upgrade (i.e. DGPS, Sysplex, etc.) GTS support or not - Partially in process of PTF handling (++HOLD,....) Project stages

- standard – as recommended by MPW

Additional tools used for migration - OMEGAMON XE for DB2 PE - DB2 Administration Tool - GEN, EXPLAIN ... - DB2 Query Monitor – track SQL performance before and after

Issues before migration - installation of >1300 PTFs (++HOLD ) Benefits after migration from customer point of view

- Currently in CM - CPU improvements – additional to z196

43 © 2011 IBM Corporation

Real situation: Customer #3Reason to migrate

- BI OLAP functions – aggregate functions (moving SUM & moving AVG) - Temporal tables - XML advanced functionality

Decision process GTS support or not - only in phase of PTF handling (++HOLD,....) Project stages

- standard – as recommended by MPW

Additional tools used for migration - OMEGAMON XE for DB2 PE - DB2 Administration Tool - GEN, ...

Issues during migration

- DB2 UDB on LUW - V8 - OA33920 PTF on USS kernel - UK63819 PTF for trigger handling

Benefits after migration from customer point of view

- Currently in CM - CPU improvements already - additional to z196