Application Modernization – DB2 for i Style

IBM Power Systems

1

Application Modernization – Db2 for i Style

Kent Milligan & Mike Cain

IBM STG Lab Services – Db2 Center of Excellence

ISV Enablement – IBM i & Db2 for i

IBM Power Systems

2

Agenda



Why?



Approaches & Options



Modernizing Database Definitions



Modernizing Data Access

 Next Steps

IBM Power Systems

3

Why SQL?



Strategic database interface for industry



Portability of code & skills



Strategic interface for IBM i



Faster delivery on IT requirements



Performance & Scalability



Increased Data Integrity

 Image

Want More Details…

NEW White Paper on Benefits of Modernizing with SQL

Click Here

IBM Power Systems

4

Enhancements to non-SQL interfaces SQL enhancements

Unicode support - UTF-16 and UTF-8

Binary character data type

CRTLF PAGESIZE parameter

CREATE INDEX PAGESIZE keyword

Larger decimal support

SSD enablement for physical & logical files

SSD enablement for tables and Indexes

XML, National Character, and ROWID data types

Identity column attribute

Hidden and Automatic Timestamp column attributes

Field Procedure column attribute

Sequence object

Column-level and Instead-Of triggers

Merge statement

OLAP and Super Group expressions

Create Table from Select and Insert from Select

SQL functional indexes

XML Publishing and Decomposition functions

IBM OmniFind Text Search Server

SQL Query Engine (SQE)

SQE Result Set Caching

SQE Autonomic Indexes

SQE Self-Learning Query Optimization & Adaptive Query Processing

SQE Encoded Vector Index fast path for aggregate processing

SQE In-memory Database Enablement

IBM i Navigator Plan Cache Tool

IBM Power Systems

5

Traditional Record-Level Access

ORDERS SUPPLIERS

PARTS CUSTOMERS

HLL PGM

Db2

Results

IBM Power Systems

6

SQL Data-Centric Programming

CUSTOMERSPARTS

SUPPLIERS

ORDERS

HLL PGM or Interface

Db2

Results

IBM Power Systems

7

Approaches & Options

ODBC / JDBC / ADO / DRDA / XDA

Host Server

Static Dynamic Extended

Dynamic

Compiled

embedded

statements

Prepare

every time

Prepare

once and

then

reference

Optimizer

Native

(Record

I/O)

SQL

Network

Db2

(Data Storage & Management)

CLI / JDBC

IBM Power Systems

8

Approaches & Options

*Restrictions:

EVIs, LOB

columns,

XML, UDTs, etc.

DDS-created

objects

SQL-created

objects

Native*

Programs

SQL

Programs

Considerations:

Multi-member &

multi-format files

IBM Power Systems

9

Modernizing Definitions & Objects



Modeling



Terminology



Moving from DDS to SQL DDL



SQL object management



Embedding business logic into database definitions

IBM Power Systems

10

Modernizing Definitions & Objects

Data modeling



Database normalization

–Define a separate table for each related set of values

–Define the primary key (surrogate or natural)

–Eliminate redundant data

–Design for Fifth normal form (5NF), performance & storage may drop back to 3NF

–Establish RI constraints



Consider Master Data Management

–Services created to retrieve data – what if multiple copies exist?

Normalization

IBM Power Systems

11

Modernizing Definitions & Objects

Data Modeling - IBM InfoSphere Data Architect



Enterprise data modeling and management

– Compare & synchronize

– Forward & reverse engineering

– Logical file support – Fixpack 003

– Model analyzer for enterprise standard conformance



Database development – SQL Stored Procedures and Function



Trial Download: http://ibm.com/software/data/optim/data-architect/

IBM Power Systems

12

Modernizing Database Objects

IBM i

SQL

Terminology

schema/collection

table

view

index

row

column

log

library

physical file

logical file

keyed logical file

record

field

journal

IBM Power Systems

13

Modernizing Objects: CREATE TABLE vs CRTPF

CREATE TABLE EMP_MAST (

EMP_MAST_PK BIGINT

GENERATED BY DEFAULT AS IDENTITY

IMPLICITLY HIDDEN

PRIMARY KEY,

EMPNO CHAR(6) UNIQUE,

FIRSTNME VARCHAR(12),

MIDINIT CHAR(1),

LASTNAME VARCHAR(15),

EMP_PICTURE BLOB(102400) ,

EM_ROW_CHANGE_TS TIMESTAMP NOT NULL

FOR EACH ROW ON UPDATE

AS ROW CHANGE TIMESTAMP

IMPLICITLY HIDDEN)

CRTPF FILE(EMPLOYEE) SRCFILE(QDDSSRC)

SRCMBR(EMPLOYEE)

--Source Data

A UNIQUE

A R EMPLOYEE

A EMPNO 6

A

FIRSTNME 12 VARLEN

A

MIDINIT 1

A

LASTNAME 15 VARLEN

A K EMPNO

ADDPFCST FILE(EMPLOYEE) TYPE(*PRIKEY) KEY(EMPNO)

Limited set of data types & attributes

Format sharing & field attributes

(CHECK, RANGE, DATFMT)

Keyed support, but only 1 key per

definition.

Constraints must be defined separately

Wider selection of data types & column

attributes

Longer, more descriptive identifiers

Data modeling tool support

Self-contained source statement, can

include constraint definitions

IBM Power Systems

14

Modernizing Objects: CREATE INDEX vs CRTLF (Keyed)

CREATE INDEX EMP_LASTNAME_DEPT

ON EMP_MAST(WORKDEPT, LASTNAME)

RCDFMT EMPLOYEER1

ADD COLUMNS

EMPNO, FIRSTNME, MIDINIT

CREATE ENCODED VECTOR INDEX RegionIX

ON SALES(REGION)

CRTLF FILE(EMPLOYEEL1) SRCFILE(QDDSSRC)

SRCMBR(EMPLOYEEL1)

--Source Data

A R EMPLOYEER1 PFILE(EMPLOYEE)

A WORKDEPT

A LASTNAME

A EMPNO

A FIRSTNME

A MIDINIT

A K WORKDEPT

A K LASTNAME

Encoded Vector Index (EVI) structure

Expressions can be used in the

definition of the key columns

Sparse Indexes with WHERE clause

(ie, Select/Omit)

EVI “Instant” Aggregate support

Larger default logical page size

Only Binary Radix Tree structure support

– no EVIs

Limited support for key derivations and

expressions

Key attributes –FCFO, FIFO, LIFO,

Smaller default logical page size

IBM Power Systems

15

Modernizing Objects: CREATE VIEW vs CRTLF (non-keyed)

CREATE VIEW

EMPLOYEE_BONUSES_BY_DEPARTMENT

_WITHIN_STATE

AS

SELECT EA.STATE, DM.DEPTNAME,

SUM(EM.BONUS)

FROM EMAST EM

JOIN EADDR EA USING (EM_PK)

JOIN DMAST DM ON WRKDPT = DPTNO

GROUP BY EA.STATE, DM.DEPTNAME

CRTLF FILE(EMPLOYEEJ1) SRCFILE(QDDSSRC)

SRCMBR(EMPLOYEEJ1)

--Source Data

A R EMPLOYEEJA JFILE(EMAST EADDR +

A DMAST)

A J JOIN(1 2)

A JFLD(EM_PK EM_PK)

A J JOIN(1 3)

A JFLD(WRKDPT DPTNO)

A STATE

A DEPTNAME

A BONUS

Full access to advanced query

capabilities of SQL

Can be used as logical files to

enhance native functionality

No support for keying/ordering

Limited Join support

No support for Grouping, Case,

Subqueries, User-Defined

functions, …

Multiple members & formats

IBM Power Systems

16

Modernizing Database Definitions & Objects

DDS to SQL Conversion Tool



System i Navigator Generate SQL Task (QSQGNDDL API)

– Useful in converting object definitions from DDS to SQL

– Supports physical & logical files

•Not all DDS features can be converted, tool will

convert as much as possible and generate warnings for

unconvertible options (e.g., EDTCDE)

•Logical files converted to SQL Views

•SQL Field Reference File support not used

– Can convert a single object or

a group of objects

– Output can be edited &

saved directly into source

file members

IBM Power Systems

17

Modernizing Database Definitions - Transparently



Converting DDS PF to SQL DDL Table

results in format identifiers being changed

– HLL programs accessing the SQL

Table will receive a “level check”

exception message.

– Only solutions prior to V5R4

•recompile the program or

•ignore the exception

•(not recommended)



A surrogate file preserves the original DDS

PF format

– Allows new columns to be added to

SQL DDL Table

– FORMAT keyword used to share

surrogate format

•Prevents level check IDs for

programs accessing original PF or

LFs sharing format



“Best” method for avoiding format id

changes!

PGM1

ORDHST

ORDHSTR

FMT123

ORDHST

ORDHSTR

FMT123

ORD_HST

FMT321

Reverse

Engineer

DDS to

DDL

I

O

Level

Check

Error

PF

ORD_HST

FMT321

Table

ORDHST

ORDHSTR

FMT123

PGM1

ORDHST

ORDHSTR

FMT123

ORDHST

ORDHSTR

FORMAT

(ORDHSTR)

Surrogate LF

IO

Actual IO

IBM Power Systems

18

Modernizing Database Definitions – Transparently



Logical files also need to re-engineered to reference the SQL table

– For each logical file which shared the physical file format (FMT123):

•PFILE modified to point at SQL table (FMT321)

•FORMAT keyword specifies surrogate LF (FMT123)

– Some LFs don’t require re-engineering

•DDS LF with unique format name

•DDS Join Logical Files have unique format IDs

ORDHST

ORDHSTR

FORMAT

(ORDHSTR)

ORD_HST

FMT321

Table

PGM2

ORDHLF1

ORDHSTR

FMT123

ORDHLF1

ORDHSTR

FORMAT

(ORDHSTR)

Surrogate LF

IO

Actual IO

Existing LF

IBM Power Systems

19

Modernizing Database Definitions - Transparently

1. Convert PF to SQL Table (with new name)

2. Create SQL indexes to replace any implicitly created keyed access paths

that exist for DDS files (use “Show Indexes”)

3. Create “Surrogate” LF with same name as original PF name

4. Modify existing LFs to reference SQL table

IBM Power Systems

20

Transparent SQL Migration - Example



Existing PF – INVENTORY

A R INVFMTR

A ITEM 15A

A ORDER 10A

A SUPPLY 15A

A QTY 5P

A QTYDUE 5P



Existing LF - INVLF

A R INVFMTR PFILE(INVENTORY)

A K ITEM

A K ORDER



Surrogate LF – INVENTORY

A R INVFMTR PFILE(SQL_INVENT)

A ITEM 15A

A ORDER 10A

A SUPPLY 15A

A QTY 5P

A QTYDUE 5P



Existing LF - INVLF

A R INVFMTR PFILE(SQL_INVENT)

FORMAT(INVENTORY)

A K ITEM

A K ORDER



Converted SQL Table:

CREATE TABLE sql_invent(

item CHAR(15),

order CHAR(10),

supply CHAR(15),

qty DECIMAL(5,0),

qtydue DECIMAL(5,0))

IBM Power Systems

21

Transparent SQL Migration - Tooling



XCase for i tooling that automates and manages this migration process

(www.xcaseforsystemi.com

)

– Free Diagnostic Modernization download

– Data modeling tool also available

IBM Power Systems

22

Modernizing Database Definitions & Objects

SQL Object management



SQL Source Management best practices:

– Just like DDS SQL sour

ce can be stored in source physical file members

just and

referenced with the RUNSQLSTM CL command instead of CRTPF/CRTLF

• If change management tools are not IBM i specific, s

tore SQL scripts in IFS or

PC

•

If SQL s

ource misplaced, Generate SQL can be used to re

trieve the SQL source

from System Catalogs (SYSIBM & QSYS2)

• Navigator

Run SQL Scripts in 6.1 can store and retrieve SQL from source members

– SQL Table definitions can use Field Reference File

CREATE TABLE customer AS

(SELECT id

cust_id, lname cust_lastname, fname cust_firstname,

city cust_city FROM RefFile)

WITH NO DATA

 May need to adjust process for moving from development to production

– Best practice is to re-execute SQL creation script

–

Save/Restore process for SQL databases documented at:

ibm.com/developerworks/Db2/library/

techarticle/0305milligan/0305milligan.html

IBM Power Systems

23

SQL Object Management



SQL Column & Object names have maximum lengths of 128, but many IBM i utilities,

commands and interfaces only support a 10-character length. Ho

w does that work?!?!

– System automatically generates a shor

t 10 character name

• First 5 chars with unique 5 digit number

CUSTOMER_MASTER >>

CUSTO00001

 Might be different each time a specific table is created, depending on creation or

der and

what other

objects share the same 5 character prefix



Use IBM i SQL syntax to specify your own short name

– RENAME TABL

E (tables & view

s) & RENAME INDEX

–

FOR COLUMN clause for columns

– SPECIFIC clause for

procedures, functions

Modernizing Database Definitions & Objects

IBM Power Systems

24

SQL Object Management



Short & Long Name Co-existence Example

– Specify the short name at creation:

CREATE TABLE dbtest/cusmst

(customer_name FOR COLUMN cusnam CHAR(20),

customer_city FOR COLUMN cuscty CHAR(40))

– Specify a long name for existing short-name:

RENAME TABLE dbtest/cusmst TO customer_master

FOR SYSTEM NAME cusmst



If long name specified on SQL Table definition, can also add/control the short name after table

created:

RENAME TABLE dbtest/customer_master TO SYSTEM NAME cusmst

Modernizing Database Definitions & Objects

IBM Power Systems

25

SQL Object Management



RPG requires system name and record format name to be different

– SQL defaults record format name to the system name

– RCDFMT keyword can be used to override default behavior



CREATE TABLE dbtest/customer_master



(customer_name FOR COLUMN cusnam CHAR(20),



customer_city FOR COLUMN cuscty CHAR(40))



RCDFMT cmfmt

Modernizing Database Definitions & Objects

IBM Power Systems

26

SQL & Non-relational data

 User-Defined Table Functions

– Allows non-relational & legacy data to be virtualized as an SQL table

SEL

ECT * FROM TABLE(myudtf('Part XYZ'))

 LOBs

– Both SQL & External Table Functions supported

• External UDTFs can be easily written to access multi-format files, S/36 files, and

stream files

• Table functions need to be invoked from SQL-based interfaces or SQL view

• External UDTF Examples: http://ibm.com/systems/i/Db2/db2code.html

– Allows you to keep non-relational data along with all the other business data

Modernizing Definitions & Objects

IBM Power Systems

27



Identity Column Attribute

– Attribute that can be added to any “whole”

n

umeric columns

–

Not guaranteed to be unique -

primary key or unique index must be defined

– Only available for SQL tables, BUT identity column value generated for non-SQL interfaces (eg, R

PG)

–

CREATE TABLE emp( empno

INTEGER GENERATED ALWAYS AS IDENTITY

(START WITH 10 , INCREMENT BY 10),

name CHAR(30), dept# CHAR(4))

INSERT INTO employee(name,dept) VALUES('MIKE','503A') or…

– INSERT INTO employ

ee VALUES(DEFAULT,'MIKE', '503A')



Sequence Object

–

Separate object that can be shared across multiple tables

– Generated value to be part of non-numeric keys

CREATE SEQUENCE order_

seq START WITH 10 IN

CREMENT BY 10

INSERT INTO orders(ordnum,custnum)

– VALUES( NEXT VALUE FOR order_seq, 123 )

Modernizing Definitions & Objects

Moving Business Logic into Db2 - Automatic Key Generation

IBM Power Systems

28

CREATE TRIGGER audit_salary

AFTER UPDATE ON employee(salary)

REFERENCING NEW AS n

REFERENCING OLD AS o

FOR EACH ROW

WHEN (n.salary - o.salary >= 5000)

INSERT INTO audit

VALUES(n.empno, n.deptno, n.salary,current timestamp)

 Triggers allow you initiate business policies & processes whenever new data comes in or

existing data is changed

–

Db2responsible for always invoking the trigger program

– Execution is independent of the user interface

– Can be used to transform data before it gets into Db2

 Db2 for i Trigger Support

– Before & After: Insert, Update, & Delete events (up to 300 triggers)

–

SQL & External(ADDPFTRG) Triggers

• Column-level, Statement-level, and Instead Of triggers only available with SQL Triggers

Modernizing Definitions & Objects

Moving Business Logic into Db2 - Triggers

IBM Power Systems

29

Modernizing Data Access



Programming Interfaces



Native I/O to SQL Comparison

IBM Power Systems

30

**Db2 SQL Development Kit only required if embedded SQL (& STRSQL)

is going to be used

Static SQL Extended Dynamic SQL

Embedded Static

QSQP

RCED

SQL Procedures,

Functions, Triggers

Toolbox JDBC driver

IBM i Access ODBC & OLE DB

Dynamic SQL

Embedded Dynamic

SQL Procedures, Functions,

Triggers

JDBC, SQLJ

ADO.NET, OLE DB

CLI, ODBC

PHP ibm_Db2

RUNSQLSTM

Modernizing Data Access – Programming Interfaces

IBM Power Systems

31

Modernizing Data Access

C SearchKey KList

C Kfld SearchYear

C Kfld SearchMonth

...

C Times Occur Result_Set

C SearchKey Setll TIME_DIML1

C If %FOUND

C DOU RowsReq = Rows Rd

C READ TIME_DIML1

C If %EOF

C Leave

C Endif

C DATEKEY Setll ITEMFACTL1

C If %FOUND

C DOU RowsReq = RowsRd

C DATEKEY READE ITEMFACTL1

C If %EOF

C Leave

C Endif

C PARTKEY CHAIN PART_DIML1

C If Not %FOUND

C Iter

C Endif

C CUSTKEY CHAIN CUST_DIML1

C If Not %FOUND

C Iter

C Endif

C SUPPKEY CHAIN SUPP_DIML1

C If Not %FOUND

C Iter

C Endif ...

...

C/EXEC SQL

C+ DECLAREsql_jn CURSOR FOR SELECT

C+ t.year,t.month,i.orderdt,c.country,c.cust

C+ p.part,s.supplier,i.quantity,i.revenue

C+ FROM item_fact i

C+ INNER JOIN part_dim p ON (i.partid =p.partid)

C+ INNER JOIN time_dim t ON (i.orderdt=t.datekey)

C+ INNER JOIN cust_dim c ON (i.custid=c.custid)

C+ INNER JOIN supp_dim s ON (i.suppid=s.suppid)

C+ WHERE year=2008 AND month=6

C/END-EXEC

C/EXEC SQL

C+ OPEN sql_jn

C/END-EXEC

C/EXEC SQL

C+ FETCH NEXT FROM sql_jn FOR :RowsReq ROWS

C+ INTO :result_set

C/END-EXEC

C If SQLCOD = 0 and

C SQLER5 = 100 and

C SQLER3 > 0

C Eval RowsRd = SQLER3

...

Native I/O to SQL Example

IBM Power Systems

32

Modernizing Data Access

...

C/EXEC SQL

C+ DECLARE sql_jn CURSOR FOR

C+ SELECT * FROM JoinView

C+ WHERE year=2008 AND month=6

C/END-EXEC

C/EXEC SQL

C+ OPEN sql_jn

C/END-EXEC

C/EXEC SQL

C+ FETCH NEXT FROM sql_jn FOR

C+ :RowsReq ROWS INTO :result_set

C/END-EXEC

C If SQLCOD = 0 and

C SQLER5 = 100 and

C SQLER3 > 0

C Eval RowsRd = SQLER3

..

C SearchKey KList

C Kfld SearchYear

C Kfld SearchMonth

...

C SearchKey SETLL NTVJOIN002

C If %FOUND

C DO RowsReq Times

C Times Occur Result_Set

C READ NTVJOIN002

C If %EOF

C Leave

C Endif

C Eval RowsRd = RowsRd + 1

C ENDDO

C Endif

Native I/O to SQL Example - Joined LFs & Views

IBM Power Systems

33

Native I/O to SQL Example - Performance Comparison

Modernizing Data Access

Note: Tests run on Model 720 w/1600 CPW & 2 GB Memory - your performance results may vary

Number of Rows

0

5

10

15

20

25

Time (sec)

Native File Join

Native JoinLF

w

SQL - No IOA

SQL IOA

SQL SQE IOA

1

100 100

0

1000

0

0.00251

2

0.26024

8

2.21950

4

23.22817

6

0.00230

4

0.36212

8

2.54460

8

21.36648

0

0.00240

0

2.14428

8

2.12503

2

19.31146

4

0.14516

0

0.48913

6

3.16670

4

20.45298

4

0.25116

8

0.26720

8

0.41780

0

1.89880

0

0.01353

6

0.01932

0

0.25016

0

1.57653

6

IBM Power Systems

34

Modernizing Data Access



The issue is throughput not response time

– As growth occurs, programs with Record Level Access (RLA) have a harder time scaling on IBM POWER

Systems

– Throwing hardware at the problem no longer an option

– Application changes will be inevitable

Traditional IO does not

scale as volumes

increase

SQL set based

access remains flat

as growth occurs

SQL and Scalability

IBM Power Systems

35

Native to SQL Considerations

Modernizing Data Access

 ORDER BY clause is the only way to guarantee the sequencing of results when using SQL - no clause,

means ordering by chance

 SQL Precompilers do not always support all the latest features in the high-level language, still missing from

RPG SQL Precompiler:

–

Support for qualified names with more than one level of qualification

 Consider impact of SQL isolation level & journaling on native applications

 Critical Performance Success Factors

– Sound Indexing & Statistics Strategy

ibm.com/partnerworld/wps/servlet/ContentHandler/servers/enable/site/bi/strategy/index.html

– Maximize Open Data Path (ODP) Reuse

• Prepare Once, Execute Many

• Connection Pooling

• Keep Connections & Jobs active as long as possible

• Reference:

ibm.com/partnerworld/wps/servlet/ContentHandler/servers/enable/site/education/ibp/4fa6/

– Use Blocked Fetches & Inserts

– Attend SQL Performance Workshop – ibm.com/systems/i/Db2/db2performance.html

IBM Power Systems

36

Next Steps

1) Identify First Project

– Write a new function/program component using SQL

– Rewrite an existing component using SQL (eg, reporting)

• OPNQRYF to SQL

• Query/400 to Db2 Web Query

– Port SQL-based program to DB2 for i

• Porting guides & conversion tools at:

• http://ibm.com/partnerworld/i/db2porting

IBM Power Systems

37

Next Steps

2) Get Education

– IBM i Database Modernization Workshop

• http://ibm.com/systems/i/support/itc/educ/lsdb2mod.html

– Modernizing iSeries Application Data Access Redbooks document

www.redbooks.ibm.com/abstracts/sg246393.html?Open

– Case Study: Modernizing a DB2 for iSeries Application white paper

ibm.com/partnerworld/wps/servlet/ContentHandler/servers/enable/site/education/wp/9e5a/index.html

– DB2 for i SQL Performance Workshop

• ibm.com/systems/i/db2/db2performance.html

• ibm.com/partnerworld/wps/training/i5os/courses

– Indexing & Stats Strategy White Paper

ibm.com/partnerworld/wps/servlet/ContentHandler/servers/enable/site/bi/strategy/index.html

– Database modernization roadmaps

• Modernizing DB2 definitions and usage

https://www.ibm.com/partnerworld/wps/servlet/ContentHandler/SOX_TwGV47Qq9ppycFAT

• Modernizing data access with SQL

https://www.ibm.com/partnerworld/wps/servlet/ContentHandler/SOX_JUGV47Q9cz7ycFAT

• Optimizing SQL performance

https://www.ibm.com/partnerworld/wps/servlet/ContentHandler/SOX_G7FV47QlUAiycFAT

IBM Power Systems

38

Conclusion



DDS and Native Record-Level Access are



not sustainable



Must migrate both Native to SQL, and your Mind to SQL



There is no reason

not to keep your business data in DB2 for i

IBM Power Systems

39

Additional Information



DB2 for i Websites

– Homepage: ibm.com/systems/i/db2

– developerWorks Zone: ibm.com/developerworks/db2/products/db2i5OS



Newsgroups

– DeveloperWorks: https://www.ibm.com/developerworks/forums/forum.jspa?forumID=292

– System i Network DB2 Forum - http://forums.systeminetwork.com/isnetforums/



Education Resources - Classroom & Online

– http://ibm.com/systems/i/db2/db2educ_m.html

– http://ibm.com/partnerworld/wps/training/i5os/courses



DB2 for i Publications

– Online Manuals: http://ibm.com/systems/i/db2/books.html

– White Papers: ibm.com/partnerworld/wps/whitepaper/i5os

– Porting Help: http://ibm.com/partnerworld/i/db2porting

– DB2 for i5/OS Redbooks (http://ibm.com/systemi/db2/relredbooks.html)

• Stored Procedures, Triggers, & User-Defined Functions on DB2 for iSeries (SG24-6503)

• DB2 for AS/400 Object Relational Support (SG24-5409)

• Advanced Functions & Administration on DB2 for iSeries (SG24-4249)

• Getting Started with DB2 Web Query for System i (SG24-7214)

– SQL for DB2 by Conte & Cooper

• http://www.amazon.com/SQL-James-Cooper-Paul-Conte/dp/1583041230/

IBM Power Systems

40

IBM DB2 for i Consulting and Services



Database modernization



DB2 Web Query



Database design, features and functions



DB2 SQL performance analysis and tuning



Data warehousing and Business Intelligence



DB2 for i education and training

Contact: Mike Cain [email protected]

IBM Systems and Technology Group

Rochester, MN USA

S

L

O

W

Need help?

DB2 Modernization Assistance

DB2 for i Modernization Workshop

http://ibm.com/systems/i/support/itc/educ/lsdb2mod.html