Phil Grainger

More automated install
Catalog restructure (to UTS)
Deprecation of Plans with DBRMs, old plan_table formats, DB2 Private Protocol, classic partitioned table spaces
 
Performance
Out of the box up to 10% cpu savings
Hash access to data
Include columns in indexes
In-line LOBs
Dynamic statement cache improvements
Dynamis SQL stability and the access path repository
 
Availability
On-line schema evolution and deferred alter
Data "as of" last commit
Reorg Aux table improvements
Recover backout
Security
Row and column level access control
Finer administrator privileges
Administrator privileges without data access
New audit abilities
 
Productivity
Immediate compression
LISTDEF partition range support
REORG SHRLEVEL CHANGE enhancements
Temporal data
SQL PL improvements
Moving sum and average
 
XML
XML schema validation in z/OS
Multi versioning of XML data
XML update, insert and delete
XML schema as column modifier
CHECK DATA for XML
 
And much MUCH more

During the design of a DB2 application, there is now a lot more to consider than just “what should the tables look like”. We need to take into onsideration where we should create indexes, and why. We might think about partitioning for performance or for manageability. What about partitioned and non partitioned indexes – they each have their advantages and disadvantages. More recently, we’ve been given the option to create Materialized Query Tables, but when would these be good to use?

This presentation steps through some of the new (and not so new) elements of DB2 database design and highlights pros and cons of each

Unfortunately, as with a lot of DB2 decisions, there are no absolute correct answers – the right answer in your case will always “depend” on circumstances, but opefully this presentation will give you the information you need to make informed choices

Objectives:
To learn how CA Detector helps you not only find your high cpu consumers but also helps you find those that you will get the most benefit from tuning. We will look at the work flow process used to track down the best tuning candidates.
We will also look at some ways you can use the Detector information to track your tuning successes over time and to help your company get the best use out of your valuable cpu resources.

Outline:
What is CA Detector?
And what it isn’t
Why is proactive better?
Examples of Detector screens – finding those cpu hogs
Advanced categorisation of activity
Externalising the data
Summary

Full Abstract:
One of the best tuning measures is to look at high cpu consumers and tune them so that they consume less. The snag is, how DO you find them? In fact, is it good enough to just find the highest cpu consuming statement or program – surely you also need to consider how often the application or statement is being used. Tuning a statement that is only executed once per hour, might give you a good feeling, but you would have been better looking for highly active things to tune.
This presentation looks at how CA Detector helps you not only find your high cpu consumers but also helps you find those that you will get the most benefit from tuning
 

Objectives:
We will look at CAs Mainframe 2.0 initiative the exciting new drive to resolve many of the issues faced by todays mainframe data centers.
The second part of this presentation covers the mainframe Database Management section of CAs Mainframe Business Unit and the changes in the IMS and DB2 tools.
Finally we will review CAs new Annual Delivery Model, which will provide a new release of ALL mainframe software from CA on an annual basis - allowing customers a better ability to plan for upgrades.

Outline:
What is Mainframe 2.0
What has the Database Management team been doing
The Annual Delivery Mode

Full Abstract:
Join Phil Grainger, Senior Principal Product Manager for the DB2 tools at CA, for this look at the current state of CAs Mainframe Database Management solutions. We will start the session with look at CAs Mainframe 2.0 initiative. This exciting new drive aims to resolve many of the issues faced by todays mainframe datacenters. From a simpler installation mechanism to smarter configuration, Mainframe 2.0 will be 'Valued Today, Essential Tomorrow'.
The second part of this presentation will examine the mainframe Database Management section of CAs Mainframe Business Unit - summarising the changes in the IMS and DB2 tools.
We will also review CAs new Annual Delivery Model, which will provide a new release of ALL mainframe software from CA on an annual basis - allowing customers a better ability to plan for upgrades.

Objectives:
To gain an understanding of how to choose a software tool to assist with your daily jobs. This presentation is not aimed at any particular tool choice, nor at any particular vendor (honest!) but is a summary of my experiences over the years of why people choose some tools over others

Outline:
Who makes the choices anyway?
What makes a good choice?
What is “value for money”?
Why do some vendors “muddy the waters”?
Who has the most negotiating power?

Full Abstract:
You might think that finding the right software tool to help you do your job would be simplicity itself. This presentation looks at some of the ways you may be losing control of your choice without even realising it and how to get that control back. The session will be a completely open and independent consideration of the processes you should be working through as you make your tools choice

Objectives:
Join Phil to hear what has been happening in DB2 tools development at CA and what we have planned for the near future

Outline:

Full Abstract:
Join Phil to hear what has been happening in DB2 tools development at CA and what we have planned for the future. As well as further support for DB2 9 we have also introduced new features and functions through the product maintenance stream.

We all know that Version 8 of DB2 for z/OS introduces a new way to partition your data - we now have Table Based as well as Index Based partitioning. Is it all good news though? This presentation looks at the new capabilities of table based partitioning, considers the advantages (and there are many) before looking at some of the pitfalls awaiting the unwary. As with all new features of DB2, there are some hidden surprises that may cause problems that are not immediately aparrent
 

This presentation takes a high level look at the new features and functions of the latest version of DB2 for the z/OS platform. As well as the much publicised XML support, there are many other new SQL, security and availability items. This session will give you a good overview of DB2 9 for z/OS
 
 

One of the major changes to DB2 for z/OS Version 8 is in the way partitioned tablespaces are created and managed. This presentation will introduce you to table-based partitioning, all of the new features that are available and some pointers on how these enhancements will benefit application design and operation. Unfortunately, there are one or two scares along the way, but these are easily understood and by the end of the session, Version 8 partitioning should hold no fears!

Release 11 of the Unicenter Database Management tools for DB2 for z/OS is the first release of tools from CA (indeed from any major software vendor) that supports DB2 UDB for z/OS Version 8. However, there is much more to r11 than Version 8 support. In this session, Phil will summarise many of the key enhancements to our DB2 tools.

OK, so we can have up to 4,096 partitions in a single partitioned tablespace and we can now add new partitions to existing partitioned tablespaces - this is simple, so what's the big deal with this presentation? Well, just as with on-line schema evolution, there are a number of "gotchas" just waiting for you to trip up. These little features are examined in this presentation whilst we look at the wider implications of a new type of partitioned tablespace management.

At last the next version of DB2 for the mainframe is available (or I hope it will be by the time of this conference!). This presentation takes a brief and high level look at the new features and facilities that are available with Version 8. We also look at the migration path, and consider some differences to a traditional DB2 version migration. Lastly, we look at the pre-requisites for Version 8 and summarise the features of earlier versions that have been removed.