migrating to db2

| September 2004 © 2004 IBM Corporation

Migrating to DB2® UDB for z/OS Version 8

Charles LewisDB2 for z/OS Technical [email protected]

© 2004 IBM CorporationBaltimore Washington DB2 User Group | September 2004

11

Information contained in this material has not been submitted to any formal IBM review and is distributed on "as is" basis without any warranty either expressed or implied. Measurements data have been obtained in laboratory environment. Information in this presentation about IBM's future plans reflect current thinking and is subject to change at IBM's business discretion. You should not rely on such information to make business plans. The use of this information is a customer responsibility.IBM MAY HAVE PATENTS OR PENDING PATENT APPLICATIONS COVERING SUBJECT MATTER IN THIS DOCUMENT. THE FURNISHING OF THIS DOCUMENT DOES NOT IMPLY GIVING LICENSE TO THESE PATENTS.TRADEMARKS: THE FOLLOWING TERMS ARE TRADEMARKS OR ® REGISTERED TRADEMARKS OF THE IBM CORPORATION IN THE UNITED STATES AND/OR OTHER COUNTRIES: AIX, AS/400, DATABASE 2, DB2, e-business logo, Enterprise Storage Server, ESCON, FICON, OS/390, OS/400, ES/9000, MVS/ESA, Netfinity, RISC, RISC SYSTEM/6000, iSeries, pSeries, xSeries, SYSTEM/390, IBM, Lotus, NOTES, WebSphere, z/Architecture, z/OS, zSeries,The FOLLOWING TERMS ARE TRADEMARKS OR REGISTERED TRADEMARKS OF THE MICROSOFT CORPORATION IN THE UNITED STATES AND/OR OTHER COUNTRIES: MICROSOFT, WINDOWS, WINDOWS NT, ODBC, WINDOWS 95

For additional information see ibm.com/legal/copytrade.phtml

Disclaimer and Trademarks

1-2 Balt-Wash DB2 User Group - Sept 2004.PRZ 09/08/04


DB2 Version 8 highlightsMigration ConsiderationsSummary and sources for additional

information

Agenda


DB2 Version 8:Highlights



DB2 UDB for z/OS Version 8 is

Reengineered for e-businessReengineered for e-business

SQL OLTP Leadership: Multi-row Fetch & Insert, Select within Insert, Dynamic Scrollable Cursors, ...

Breaking through limitations: storage, name lengths, SQL statements, partitions, logging

Performance Enhancements: MQTs, index use

Database changes without an outage: add partition, rotate partitions, alter cluster

Integration: applications, middleware, platform

...


Breaking through limitationsVirtual Storage 2 GB 231 to 264

Table name sizes 18 to 128VIEW & ALIAS names 18 to 128Column name sizes 18 to 30Partitions 254 to 4096SQL statement length 32K to 2 MBIndex key size 255 to 2000Character Literals 255 to 32704Hex literal digits 255 to 32704Predicates 255 to 32704Image of Earth from Moon,

Source: NASA (Public Domain)

Limits: DB2 for z/OS



Breaking through limitations ...Tables in a join 15 to 225Active logs 31 to 93Archive logs 1000 to 10,000Maximum table size 16 TB to 128 TB (partitioned, 32K page)Current optimization 8 to 128CURRENT PACKAGESET 18 to 128CURRENT PATH 254 to 2048SCHEMA 8 to 128

Image of Earth from Moon, Source: NASA (Public Domain)

Limits: DB2 for z/OS


Multi-row INSERT, FETCH & UPDATEGET DIAGNOSTICSINSERT within SELECTIDENTITY Column enhancementsSEQUENCESCURRENT PACKAGE PATH

Dynamic Scrollable CursorsCommon Table ExpressionsScalar FullselectMaterialized Query TablesUNICODE SQL, Multiple CCSIDsXML Publishing...

SQL and DB2 Family



Ability to use indexes more oftenMore matching in predicatesIndex backward scanIndex varying lengthDistribution statistics on non-index columns

Materialized Query TablesMulti-row fetch & insertData Sharing improvements

Performance Enhancements


Schema Evolution: database changes ALTER instead of DROP / CREATEData Partitioned Secondary Indexes (DPSI)System-Level Point in Time RecoveryImproved LPL RecoveryAdditional online zparms

Continuous Availability



System Level Point In Time RecoveryEasier, more flexible, less disruptive, faster recoveryHandle large numbers of table spaces & indexesTwo new utilities are introduced

BACKUP SYSTEM: Fast volume-level backups

DB2 databases and logsData sharing group scopez/OS V1R5 required

RESTORE SYSTEMTo an arbitrary point-in-timeHandles creates, drops, LOG NO events


Multilevel Security by Row



Multilevel Security by Row ...


DB2 Version 8:Getting Ready

Part 1



Hardware prerequisitesCoupling facility prerequisites for data sharing

CFLEVEL=7 with service level 1.06CFLEVEL=8 with service level 1.03Higher CFLEVELs do not currently have additional

service requirementsSoftware prerequisites

z/OS 1.3 or above (in 64-bit mode)z/OS Unicode Conversion ServicesMigration is from DB2 for OS/390 and z/OS V7 only

ISV tools and applications

Prerequisites


Migrate to DB2 for z/OS V7Migrate to z/OS V1R3 or later

Requires WLM goal modeSome functions need z/OS V1R4, V1R5

zSeries, z/Architecture 64 bit modeMigrate to IBM COBOL V2 or V3

No OS/VS COBOL or VS COBOL IIRun Old COBOL modules under LE

IMS V7, CICS TS V1.3, V2.2

Getting ready for V8

V8



Version 7 Performance Topics, Chapter 10

DB2 Version 8 requires:zSeries, z/OS V1R3, 64 bit architecture

DB2 Version 8 also has new uses

z/OS V1R4 & CFLEVEL 12 Parallel Sysplex, z/OS V1R5 DFSMS, multilevel security,

WLM, Cryptography, Unicode, ...DB2 also delivers synergy with instruction set, Compression, FICON, Disk storage, ...

Synergy: zSeries, z/OS & ESS


Process built up over years of DB2 migration experience

Test installation of new subsystem and/or migration of test system

Rollout across strategic development environments

Finally migrate production to the new release

Use no new function during migration timeframe

Verify compatibility of old function on new release

When satisfied with new release, begin to use new function

Typical migration process - V7 and earlier releases



Four step process for Migration to V8

Test with New Install & Migrate Apply the Fallback SPE to all members

Start all members at SPE levelMigrate to new release without new function (COMPAT Mode)Enable New Function Mode

Then in New Function Mode


More robust migration processFewer migration & fallback errorsAll customers apply the Fallback SPE

Customer control for migration process & timing for using new functionReduced risk of problems in Fallback SPE

Reduced number of modules, fewer changesImproved ability to deliver new function,

while still having fallback & coexistence

Tighter Migration Customer Value



Test Install, Migration, Fallback on Test SystemInstall Fallback SPE on all members (required)

UQ81009Migrate to V8 - Compatibility Mode

Normal CATMAINT - no long namesNo new external functions available (almost)

When satisfied with V8 supporting production,Run job to Enable New Function

Fallback and Coexistence with V7 no longer possibleA series of ALTERs and Online Reorgs (RO) of Catalog and Directory table spaces

New Function ModeAll new functions available

Formalize Customary Procedure


Compatibility Mode (CM)Can last as long as necessaryNo new function availableRun tests to ensure that no

regression is taking placeV7 and V8 Data Sharing

coexistence supportedFallback to V7 is allowed

Enable New Function Mode (ENFM)

New Function Mode (NFM)

Administrator runs a job that triggers the ability to use new features of V8No Fallback allowed to V7No Returning to CMDSNTIJEN to return to ENFM

No change to the catalog data or structure

Migration Modes

Convert DB2 so that it is ready to support new functions

Series of ALTERS and ONLINE REORGS of the Catalog and DirectoryProcess can be halted and restartedThis is a group wide event - no V7 allowed even if ENFM not runningHowever, no fallback to DB2 V7 is allowed once this job is started



V7

data sharing coexistence

V8 Compatibility

Mode

V8 Enabling New

Function Mode

V8 New Function

Mode

DSNTIJTC:CATMAINT DSNTIJNF:

set NFM

DB2 V8 libraries

DB2 V7 libraries

DB2 V7 catalog

DB2 V8 catalog

DSNTIJNE:CATENFM

V7with fallback SPE

Overview of migration


Only option!!

V7

data sharing coexistence

V8 Compatibility

Mode

V8 Enabling New

Function Mode

V8 New Function

Mode

DSNTIJTC:CATMAINT DSNTIJNF:

set NFM

DB2 V8 libraries

DB2 V7 libraries

DB2 V7 catalog

DB2 V8 catalog

DSNTIJNE:CATENFM

V7with fallback SPE

Restore

Backup here for full DB2 system restore (BSDS, logs, catalog, application data -- everything!!)

Overview of migration



DB2 Version 8:Getting Ready

Part 2


z/OS Application Connectivty (T4)

DB2 UDB for z/OS

Base Engine No-Charge Features

QMF

Enterprise

QMF TSO/CICS

DB2 Management Clients Package Includes:

DB2 Connect PE 8.1Control CenterDevelopment CenterReplication CenterCommand Center

z/OS Enablement for Control CenterDB2 Administration Server for z/OS (DAS)DB2 Visual Explain (CD/Rom)

Base Includes: Base (msys, Rexx) IRLM 2.2 ODBC/JDBC/SQLJ

JDBC (legacy) JDBC (T2)

DB2 ExtendersText Extender (stabilized)Audio, Video, Image Extender (stabilized)XML Extender

QMF Classic

DB2 Management

Clients Package

Net.Data V7

(stabilized)

QMF Distributed

Net SearchExtender V7(stabilized)

-QMF for WebSphere-For workstation: - QMF for WebSphere - QMF for Windows - QMF VIsionary Studio

-QMF TSO/CICS- QMF for WebSphere- QMF High Performance Option (HPO)-For workstation: - QMF for WebSphere - QMF for Windows - QMF VIsionary Studio

DB2 for z/OS V8 Packaging



Fall Back SPE on DB2 V7 - SPE PQ48486Installed and started on all DB2 V7 members

CCSIDs and UnicodeSpecify a valid CCSID

Identify code character set supported by your I/O deviceCCSIDs for EBCIDIC, ASCII and Unicode (even if application

data is not stored in one of these encoding schemes)Define and customize Unicode Conversion Services

z/OS V1R3.0 Support for Unicode Using Conversion ServicesDefine User DSNHDECP Module

DB2 no longer creates a defaultRun DSNTIJUZ to define it

Ensure BP8K0, BP16K0, and BP32K Buffer Pools are DefinedIf missed, DB2 will create with defaults during ENFM processing

Before Migrating Checklist


Before Migrating Checklist (continued)

Install IRLM 2.2Delivered with DB2 as FMID HIR220Both 31-bit and 64-bit versions - size of libraries doubleIMS V8 still uses the 31-bit version

Use CI size > 4KBSpecifies whether you want DB2 managed data sets to have variable VSAM CI size

Possibly better availability and performanceOnly available after migration

New Utility for Converting BSDSsSupport 93 active logs (372GB) and 10,000 archive logs (40TB)Run when in ENFM or NFM



Increase External Sort SizeNew Default in CM for SORTDATA and SORTKEYS for LOAD and REORGIncreases ParallelismMore concurrent active tasks and more sort work definitions

SYSSTATS Table SpaceSYSCOLDISTSTATS and SYSCOLDIST contain more data in V8

Increase Size of Catalog Table and Index SpacesLong Names, UnicodeWhen is the last time you REORG'd your catalog?

Increase / Decrease EDM Pool Size?More partitions = larger database descriptorsDBDs and Dynamic Statement Cache moved to their own area above the bar

Other Sizes to Consider


Changes to Subsystem Defaults



Language Considerations

LANGUAGE COMPJAVA Not Supported for Stored ProceduresType 2 JDBC/SQLJ Driver will not be enhanced

Use Java Common Client (aka DB2 Application Connectivity for z/OS)

No New DB2SPAS Stored ProceduresExisting will continue to run, but should migrate them

COBOL: Migrate to IBM COBOL V2 or V3No OS/VS COBOL or VS COBOL IICan run old COBOL load modules under LE

64-bit compilers are not currently supported by DB2 for z/OS V8


Shipped as V7 APAR PQ84421Checks for:

Type 1 IndexesCatalog tables with DATACAPTUREPartitioned TS with selective partition locking and/or truncated limit keyStored Procedures with COMPJAVA and/or use DB2SPASUse of DSNWZPR by DSNWZPExistence of V7 Sample DatabaseEvidence of Multiple CCSIDs

Beware of 500

Run DSNTIJPM(8)



Release IncompatibilitiesTrace applications that use statement length fields

May need to change to use 4 byte statement length fieldsBuilt in functions

There are several new built in functions. Make sure existing built in functions are called fully qualified to avoid inadvertent calling of new functionsCould also move SYSIBM to later in the SQL path

Utilities default behavior is changedSORTKEYS is default for REORG, LOAD, and REBUILDSORTDATA is default for REORG

DISPLAY LOCATION commandRequires a parameter in V8. Error will be DSN9010I

The TRANSLATE function operates differentlyMay need to change the translate table for characters that are now double-byte in Unicode

DISPLAY GROUPBUFFERPOOL commandDisplays both operational coupling facility level as well as the actual level


BLOB, CLOB, and DBCLOB function lower limitLower limit is now 1 (not 0) for consistency with VARCHAR & VARGRAPHIC functionsDefaults to 1 with empty input stringWith input string, an error is returned if not specified

Input for GRAPHIC, VARGRAPHIC, and DBCLOBCannot be BIT data. EBCDIC BIT data will return an error

CHAR functionStrings > 255 bytes are truncated and return a warning (for non-blank truncation)V7 issued an error

SQLDA may contain truncated dataSQLDA is not changed for long names to be compatible with prior releases

LOCKPART is deprecatedStill supported in V8 for compatibilityDefault is changed to lock individual parts when accessed

Release Incompatibilites (continued)



Release Incompatibilites (continued)Subsystem parameter UTLRSTRT is no longer supported

DB2 V8 attempts restart of online-restartable utilities regardless of RESTART keyword

Subsystem parameter PKGLDTOL is no longer supportedDB2 V8 requires that a plan/package be bound at an application requesterThis parm was provided as a temporary fix for V7

DB2 Private ProtocolThis is still support in V8, but SQL is limited to pre-V8

SQL Reserved WordsSee the DB2 SQL Reference Guide for new reserved words

Return Code change for DSNU185 (VSAM DATASET DOES NOT EXIST FOR…)

Was RC=8, and is now RC=0Parameter markers of prepared statements are always nullable

Prior to V8 this could be set in the SQLDA


Release Incompatibilites (continued)Savepoint names cannot begin with 'SYS'

This will issue an errorALTER TABLESPACE..ALTER PARTITION must specify the partitionALTER INDEX..ALTER PARTITION

Now issues a warning if no options specifiedInvalidation of Plan / Packages

Plans / Packages that have SQL referencing the catalog may be invalidatedUse DSNTESQ to check for this in advance

SYSIBM.SYSDUMMY1 is recreated during migrationDSNTIJNE drops and recreates this table - invalidating plans / packagesThese will Auto-rebind

Some system catalog table columns cannot be updatedSELECT…FOR UPDATE OF statements may fail.



Release Incompatibilites (continued)

SELECT…FOR UPDATE OF statement cannot have:Nested table expressions, norTable UDFs

Improved validation of host variables may require application changes

Like, a host variable that is smaller than the actual dataCREATE PROCEDURE…PARAMETER STYLE keyword now

requiredThis optional V7 keywords now return an error


DB2 V7 had Unicode. CCSIDs must now be defined. See PQ56697 (March, 2003)Check existing CCSIDs in V7 by running queries in job

DSNTIJP8, supplied in PQ84421If not already done, consider running V7 Unicode IVPs

to test z/OS Unicode Conversion Services setupDB2 V8 requires z/OS Unicode Conversion Services

in all modes. Defaults: OA04069Check CCSIDs for terminal emulators and

workstationsCheck for affect of Unicode on your applications which

Access the DB2 catalogAccess DB2 trace records

Planning for Unicode



UNICODE Catalog

In Compatibility Mode, all table spaces are EBCDICIn Enabling New Function Mode,

some are EBCDIC, some are Unicode-DISPLAY GROUP DETAILSYSTABLES - ENCODING_SCHEMESYSTABLESPACE - ENCODING_SCHEME

In New Function Mode20 are Unicode2 are EBCDIC (SYSCOPY & SYSEBCDC)


Important - You cannot run the Version 8 IVP jobs until DB2 is running in Version 8 new-function modeRun the Version 7 IVP jobs to verify a successful migration to

Version 8 compatibility modeIf migrating, the recommendation is to run portions of the

sample applications from Version 7 Verifies the migrationEnsures that the old jobs work with Version 8 in new-function mode

The Version 8 IVP jobs are created by the installation CLIST as part of Version 8 enabling-new-function mode

Installation Verification Procedure (IVP)



Get education!Read!

DB2 V8 What’s NewPresentations from the webDB2 V8 Installation GuideProgram DirectoriesPreventive Service Planning bucket. . .

Plan!

Strategy for migration


DB2 for z/OS ibm.com/software/db2zoshttp://www.ibm.com/software/data/db2/os390/presentations.html

Online Supportibm.com/software/db2zos/support.htmlibm.com/software/db2zos/osupport.html

IBM iSource ibm.com/isourceEducation ibm.com/services/learningRedbooks ibm.com/redbooksDB2 Magazine www.db2mag.comDB2 Users Groups

www.idug.orgwww.share.org

DeveloperWorks ibm.com/developerwww7b.software.ibm.com/dmdd/

zSeries, z/OS ibm.com/servers/eserver/zseriesibm.com/servers/eserver/zseries/zosibm.com/servers/eserver/zseries/library

DB2 web pointers



DB2 UDB for z/OS V8 Everything you ever wanted to know, …and more, SG24-6079 (May 2004)DB2 UDB for z/OS Version 8 Technical Preview, SG24-6871DB2 UDB for z/OS V8: Through the Looking Glass & What SAP Found There,

SG24-7088DB2 for z/OS and OS/390: Ready for Java, SG24-6435Distributed Functions of DB2 for z/OS and OS/390, SG24-6952Moving Data Across the DB2 Family, SG24-6905Implementing PeopleSoft 8.4 on zSeries, SG24-6549Siebel 7 with DB2 for z/OS: Database Implementation & Administration,

SG24-6868SAP on DB2 for z/OS: Multiple Components in One Database, SG24-6914SAP on DB2 for z/OS: High Availability Using System Automation, SG24-6836Squeezing the Most Out of Dynamic SQL, SG24-6418Large Objects with DB2 for z/OS and OS/390, SG24-6571

Latest DB2 Redbooks


DB2 for z/OS V7 Selected Performance Topics, SG24-6894DB2 for z/OS Application Programming Topics, SG24-6300DB2 for z/OS and OS/390 Version 7 Using the Utilities Suite, SG24-6289DB2 for z/OS and OS/390 V7 Performance Topics, SG24-6129DB2 UDB for z/OS and OS/390 Version 7 Presentation Guide, SG24-6121Cross-Platform DB2 Stored Procedures: Build & Debug, SG24-5485-01A Practical Guide to DB2 UDB Data Replication V8, SG24-6828New Tools for DB2 for OS/390 and z/OS Presentation Guide, SG24-6139SAP R/3 on DB2 for OS/390: Database Availability, SG24-5690DB2 for z/OS and OS/390 e-business Solutions, SG24-6257SAP R/3 on DB2 for OS/390: DB2 Features for SAP (redpaper)e-Business Intelligence Front-End Tool OS/390 Data Warehouse, SG24-5688

Next Latest DB2 Redbooks



Migrating to the IBM Replication Solution, SG24-6140DB2 for OS/390 V6 Technical Update, SG24-6108DB2 for OS/390 V6 Management Tools Package, SG24-5759DB2 Version 6 Performance Topics, SG24-5351Storage Management with DB2 for OS/390, SG24-5462Getting Started with DB2 OLAP Server OS/390, SG24-5665DB2 Enterprise Query – QMF for Windows, SG24-5746Converting from Oracle AIX to DB2 for OS/390, SG24-5478DB2 for OS/390 Continuous Availability SG24-5486DB2 Java Stored Procedures, Learning by Example, SG24-5945SAP on OS/390: Information Warehouse, SG24-5681

Next Next Latest DB2 Redbooks


Status of IBM DB2 Tools can be found at:http://www-1.ibm.com/support/docview.wss?rs=434&context=SSZJXP&uid=swg21162152&loc=en_US&cs=utf-8&lang=en+en

Contact other vendors to determine proper maintenance levels

Are Your DB2 Tools Ready?



DB2Tools

Tools today...DB2 Administration Tool DB2 Object Comparison ToolData Encryption for DB2 and IMSDB2 Batch Thread Cancel

Tools today...DB2 Utilities Suite DB2 Automation ToolDB2 HP UnloadDB2 Utilities Migration Toolkit

Tools today...DB2 Bind Manager DB2 II ClassicFederation for z/OSDB2 Test Database GeneratorDB2 Data Archive ExpertDB2 Path Checker DB2 Table Editor DB2 Web Query Tool

Tools today...DB2 Performance Expert DB2 Performance MonitorDB2 Buffer Pool AnalyzerDB2 Query Monitor DB2 SQL Performance Analyzer

Tools today...Application Recovery Tool for IMS and DB2 DatabasesDB2 Archive Log AcceleratorDB2 Change Accumulation ToolDB2 Log Analysis Tool DB2 Object Restore ToolDB2 Recovery Expert

Tools today...DB2 DataPropagatorReplidata

Utilities Management

Recovery

Replication

Database Administration

Application Management

Performance Management

Available on zSeriesAvailable on zSeries and multiplatforms

Currently only available on multiplatformsPRPQ

DB2 Tools Product Portfolio


Contact your IBM Team. Your DB2 for OS/390 & z/OS Specialist can provide:

DB2 for z/OS V8 Migration Project Planning AssistanceDB2 UDB for z/OS V8 Readiness AssessmentDB2 Solutions Assurance Review

IBM Services (billable)DB2 V7 Health CheckMigration / Implementation Services

V8 Migration Assistance is Available



The End


migrating to db2

Documents