May 20, 2008 • 01:30 p.m. – 02:30 p.m.Platform: DB2 for z/OS

Marc CostaFedEx Freight System

Session: B07Urban Legend: Upgrade from DB2 for z/OS V7 to DB2 for z/OS V8 (NFM) In Less Than 90 days

2

Urban Legend

• Is it possible to upgrade to NFM in less than 90 days?

• Timelines and upgrade paths

• Upgrades to other components (not just DB2)

• To rebind or not to rebind?

• Fun days (and nights) after getting to NFM

3

DB2 Timeline (GA and EOS)• DB2 for OS/390 and z/OS Version 7

• GA – March 30, 2001 EOS June 30, 2008

• DB2 for z/OS Version 8• GA – March 26, 2004 EOS Not established

• DB2 for z/OS Version 9• GA – March 16, 2007 EOS Not established

• All versions prior to V7 are out of support• Do you like running on unsupported code?• What about your business partners?

• http://www-306.ibm.com/software/data/support/lifecycle/

4

Training Timeline• September 20 – 24 2004 – IBM DB2 Technical

Conference Las Vegas, NV

• May 22 – 26 2005 – IDUG Denver, CO

• June 15th 2005 – CDUG V8 upgrade workshop training

• September 12 – 16 2005 – IBM DB2 Technical Conference Orlando, FL

5

Upgrade Timeline• August 12th 2005 – Ordered V8

• August 29th 2005 – SMP/E work completed

• September 2005 – Additional RSU’s applied

• October 5th 2005 – Sandbox DB2 upgraded to Compatibility Mode (CM)

• November 24th 2005 – Production to CM

• December 17th 2005 – Production to New Function Mode (NFM)

Total Time from Order to NFM – 127 DaysTotal Time from first member CM to last member NFM – 72 days

6

Horizontal Upgrade

• IBM recommended upgrade path

Test QA Prod

ProdQATest

CM

NFM

• How long do you spend in each mode in each environment?

• Benefits/Drawbacks

7

• Maybe for those that think they are smarter than IBM

Test QA Prod

ProdQATest

CM

NFM

• Complete (through NFM) one environment before moving to next

• Benefits/Drawbacks

Vertical Upgrade

8

CCSID Conversion• How do you know one is needed?

• Get the 27 step conversion plan

• Build into project plan the time to do conversion• All environments

• Why do we need to do a conversion?

• CCSID and Codepage – Do your homework

9

CCSID cont’d• 7 characters between 37 and 500 don’t match

• CCSID 37 CCSID 500• x’BA’ = [ x’5B’ = ¬• x’BB’ = ] x’BB’ = |• x’B0’ = ^ x’B0’ = ¢• x’4A’ = ¢ x’4A’ = [• x’4F’ = | x’4F’ = !• x’5A’ = ! x’5A’ = ]• x’5F’ = ¬ x’5F’ = ^

10

Short Overview of Upgrade Steps• If CCSID conversion needed, complete before CM

• CM – Compatibility Mode• Can your shop run V8 Code?• Fallback to V7 if needed

• ENFM (Enable New Function Mode)• Catalog and Directory Reorg and conversion to

Unicode

• NFM (New Function Mode)• Flip the switch (no easy way back to CM or V7)• Compiler option after last system upgraded?

11

Reorg of Catalog and Directory• Before starting the upgrade• Going to happen in ENFM• When was the last time it was done?• Are you rebinding all plans/packages?

• Help in rebind time

• After upgrade, continue doing?• Regular basis• Need based on rate of change

12

Getting to CM• DSN7100I %DBS1 DSN7GCMD • *** BEGIN DISPLAY OF GROUP(DSNSDBG0) GROUP LEVEL(810) MODE(C) • PROTOCOL LEVEL(1) GROUP ATTACH NAME(DSNS) • -------------------------------------------------------------------- • DB2 DB2 SYSTEM IRLM • MEMBER ID SUBSYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC • -------- --- ---- -------- -------- --- -------- ---- -------- • DBS1 1 DBS1 %DBS1 ACTIVE 810 AFW4 DIS1 DBS1IRLM • DBS2 2 DBS2 %DBS2 QUIESCED 710 AFW4 DIS2 DBS2IRLM • -------------------------------------------------------------------- • DB2 PARALLEL PARALLEL • MEMBER COORDINATOR ASSISTANT • -------- ----------- --------- • DBS1 YES YES • DBS2 **** **** • -------------------------------------------------------------------- • SCA STRUCTURE SIZE: 16640 KB, STATUS= AC, SCA IN USE: < 1 % • LOCK1 STRUCTURE SIZE: 8192 KB • NUMBER LOCK ENTRIES: 2097152 • NUMBER LIST ENTRIES: 16717, LIST ENTRIES IN USE: 0 • *** END DISPLAY OF GROUP(DSNSDBG0) • DSN9022I %DBS1 DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION • ***

13

ENFM – Convert to Unicode• DSN7100I %DBS1 DSN7GCMD • *** BEGIN DISPLAY OF GROUP(DSNSDBG0) GROUP LEVEL(810) MODE(E) • PROTOCOL LEVEL(1) GROUP ATTACH NAME(DSNS) • -------------------------------------------------------------------- • DB2 DB2 SYSTEM IRLM • MEMBER ID SUBSYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC • -------- --- ---- -------- -------- --- -------- ---- -------- • DBS1 1 DBS1 %DBS1 ACTIVE 810 AFW3 DIS1 DBS1IRLM • DBS2 2 DBS2 %DBS2 ACTIVE 810 AFW3 DIS2 DBS2IRLM • -------------------------------------------------------------------- • DB2 PARALLEL PARALLEL • MEMBER COORDINATOR ASSISTANT • -------- ----------- --------- • DBS1 YES YES • DBS2 NO YES • --------------------------------------------------------------------• TABLE ENABLED • SPACE NEW FUNCTION • -------- ------------ • SYSVIEWS YES • SYSDBASE YES • SYSDBAUT YES • SYSDDF YES • SYSGPAUT YES • SYSGROUP YES • SYSGRTNS YES • SYSHIST YES • SYSJAVA NO• ---------

14

NFM – Flip the switch• DSN7100I %DBS1 DSN7GCMD • *** BEGIN DISPLAY OF GROUP(DSNSDBG0) GROUP LEVEL(810) MODE(N) • PROTOCOL LEVEL(2) GROUP ATTACH NAME(DSNS) • -------------------------------------------------------------------- • DB2 DB2 SYSTEM IRLM • MEMBER ID SUBSYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC • -------- --- ---- -------- -------- --- -------- ---- -------- • DBS1 1 DBS1 %DBS1 ACTIVE 810 AFW3 DIS1 DBS1IRLM • DBS2 2 DBS2 %DBS2 ACTIVE 810 AFW3 DIS2 DBS2IRLM • -------------------------------------------------------------------- • SCA STRUCTURE SIZE: 16384 KB, STATUS= AC, SCA IN USE: 1 % • LOCK1 STRUCTURE SIZE: 8192 KB • NUMBER LOCK ENTRIES: 2097152 • NUMBER LIST ENTRIES: 14938, LIST ENTRIES IN USE: 3426 • *** END DISPLAY OF GROUP(DSNSDBG0)

15

Project Plan• Project template available from IBM• Use as a starting point, but need to customize

• Factor in burn time for each mode by environment

• Build “fluff” time to resolve issues that might arise• Catch in test/QA and not production

• Open ETR’s with IBM in advance (recommended)• CCSID• General Upgrade• Site specific “issues”

16

Other things to upgrade• Hardware• z9 Architecture

• Software• z/OS – minimum of 1.4• QMF

• Also have CM and NFM phases

• ISV’s• Probably not as much of an issue now, but

toleration/exploitation of new features

• DB2 Connect or equivalent• Visual Explain (plan/DSN tables) Alias support

17

To rebind or not to rebind?• That isn’t even an option• Real question is what % to rebind

• In CM – top 10% to 20% - maybe all• ~95% of optimizer changes in CM

• In NFM – all or what was not done in CM• Tuning after rebind

• Tuning options• Stats Advisor in Visual Explain • Reorg• Alter clustering index/add columns to index (On-Line

Schema Evolution - OLSE)

• Use opthints only when all other tuning options exhausted – then open ETR

Colgroup Stats in V8

18

Fun times in V8 NFM• No more reading Database Request Modules

(DBRM’s)• Getting off of Opthints• Online Schema Evolution• Main driver to go to V8• Define process, including Data Capture

Changes• Rebind• Ideally do in “quieter” time or down window

• DISTSERV and 2 gig limit• Commit is not over-rated

19

DBRM (V7 and before)

• “Readable”

20

DBRM V8 NFM

• Not so readable

21

Death of Opthints• Prior to V8, many access paths using opthint

• In V8, wanted to use optimizer/utility enhancements • Data type mismatch• DSTATS in V7 and before now built in

• Rebound plans and packages with OPTHINT(‘ ‘)

• One program started giving incorrect output• Tied to backwards index scan and opthint

• Get over fear of rebind

22

OLSE at the wrong time • Request to do OLSE during the week• Down time for object was determined• Process executed• Rebinds for OLSE object collided with Bind tied

to a scheduled move• Rebind job tied to OLSE was cancelled (hard)• Entire system “slowly” started to lock up• Sev 1 ETR opened with IBM• Cancelled IRLM (per IBM recommendation)

• Restart “longer” than normal

23

DISTSERV and 2 gig limit• Distributed application

• Bulk harvesting of data

• Upwards of 200 connections managed by application

• 0 commits

• DIST address space memory increased to 1.6 gig

• DIST address space crashed taking DB2 with it

• Commits added (even read only need commit)

• No issues

24

Should I upgrade in less than 90 days?

Do you have a significant other?

Go For It!

Does your significat other know a good divorce lawyer?

Do you have family/friends that you want to see for the

next 3 months?

Does your significant other know someone that knows a

good divorce lawyer?

Rethink your timeline

NO

NO

NO

YES

YES

YES YES

NO

25

Marc CostaFedEx Freight System

marc.costa@fedex.com

Session B07

Session Title - Urban Legend: Upgrade from DB2 for z/OS V7 to DB2 for z/OS V8 (NFM) In Less Than 90 days