Midwest Database User Group – September 2017

MWDUG – Midwest Database User Group – September 2017

14. September 2017

SEGUS & SOFTWARE ENGINEERING sponsern diese Veranstaltung  & präsentieren

pdf Präsentation 1 Db2 12 Continuous Delivery – New challenges for deployment.

pdf Präsentation 2 – Db2 z/OS Lies, Damn Lies, and Statistics


1- Db2 12 Continuous Delivery – New challenges for deployment.

Fundamental changes in the Db2 z world often lead to concerns. Let’s face it – some changes force us to change! While a Db2 version migration usually took months, or even years, there will be no new Db2 version after 12, but continuous code drops.

This will have a tremendous impact on migration strategies, because we have to find a reliable way to test these code deliveries in a fraction of time. If we make it, Business Divisions will become enthused at how quickly new technology becomes available for new applications. This presentation will describe the difference between Code, Catalog, Function and Application Levels, how you can control them and how you can fallback in case of anomalies. It also illustrates how we still can be pro-active in testing without burning weeks and months.

Learn how to choose from four different levels of testing and a new way of automation. CD-Screening allows you to pick and choose from KPI based test automation. The levels include simple anomaly alerting, access path verification, clone Pre-apply and even workload capture/replay to easily discover different behaviour resulting from a new code Level.


Mehr über Db2 Continuous Delivery – CD

Presentation Outline

Joining this presentation, you’ll learn how to align Continuous Delivery to your Continuous Availability.


1 – Agile, Continuous Delivery, DevOps – just buzz words, or new methodologies?


2 – Db2 Code, Catalog, Function and Application Levels – differences and dependencies.


3 – Activation/Deactivation of new code and how to fallback and when you can’t.


4 – Different flavors of (pro-active) CD-Screening and how it can be automated:

* Anomaly alerting based on Incompatibility Change Indicators (ICIs)
* Dyn./Stat.Access Path Change Detection e.g.via Plan Management
* Clone based code change pre-apply exploiting Backup System
* Workload-KPI verification using SQL replay and KPI comparison


Audience Experience:    Intermediate Advanced
Platform:                          Db2 z/OS
Presentation Length:     60 minutes
Presentation Category:  Database Administration Performance Management Db2 Migration

Speaker Biography

Ulf Heinrich is the Director of Solutions Delivery at SOFTWARE ENGINEERING GmbH. He specializes in Db2 recovery issues and database maintenance, focusing on the growing requirement for cost reduction and 24×7 operations. As a consultant at large customer sites, he has implemented database maintenance procedures and recovery strategies, and also experienced the pitfalls of recovery scenarios under real‐world recovery pressure. His activities cover EMEA, as well as North America through SE’ U.S. subsidiary, SEGUS Inc. He’s involved in the development of SE’ maintenance and recovery Solutions.

 


2- Db2 z/OS Lies, Damn Lies, and Statistics

..Lies, damn lies, and statistics… – Benjamin Disraeli, Prime Minister of England (1868, 1874-1880)

The above line may, or may not, have been spoken well over 100 years ago, but the need for statistics and, above all else, accurate statistics is more important than ever in the Db2 world of today.

Presentation Outline

  • Db2 RUNSTATS basics & catalog tables and Columns used for access path
  • IBM recommendations through the ages : from Db2 V3 to Db2 12
  • Db2 RUNSTATS advanced
  • SYSCOLDIST explained
  • RUNSTATS real world Q&A :
    use of SAMPLE, COLGROUP, PROFILE, REOPT (ONCE), TABLESAMPLE SYSTEM, HISTOGRAM, …
  • RUNSTATS reversal

Speaker Biography

Roy Boxwell has more than 31 years of experience in MVS, OS/390, and z/OS environments – 29 of those in Db2. He specializes in installation, migration, and performance monitoring and tuning. Roy leads the SEG development team responsible for the real time database maintenance solutions. He is also an active participant, speaker and contributor on the IDUG Db2 Listserv and sends out a monthly Db2 z/OS Newsletter.

Wisconsin Db2 Users Group – September 2017

WDUG – Wisconsin Db2 Users Group – September 2017

13. September 2017

SEGUS & SOFTWARE ENGINEERING präsentieren

pdf Präsentation 1 – Db2 12 Continuous Delivery – New challenges for deployment.

pdf Präsentation 2 – Db2 z/OS Lies, Damn Lies, and Statistics

1- Db2 12 Continuous Delivery – New challenges for deployment.

Fundamental changes in the Db2 z world often lead to concerns. Let’s face it – some changes force us to change! While a Db2 version migration usually took months, or even years, there will be no new Db2 version after 12, but continuous code drops.

This will have a tremendous impact on migration strategies, because we have to find a reliable way to test these code deliveries in a fraction of time. If we make it, Business Divisions will become enthused at how quickly new technology becomes available for new applications. This presentation will describe the difference between Code, Catalog, Function and Application Levels, how you can control them and how you can fallback in case of anomalies. It also illustrates how we still can be pro-active in testing without burning weeks and months.

Learn how to choose from four different levels of testing and a new way of automation. CD-Screening allows you to pick and choose from KPI based test automation. The levels include simple anomaly alerting, access path verification, clone Pre-apply and even workload capture/replay to easily discover different behaviour resulting from a new code Level.


Mehr über Db2 Continuous Delivery – CD

Presentation Outline

Joining this presentation, you’ll learn how to align Continuous Delivery to your Continuous Availability.


1 – Agile, Continuous Delivery, DevOps – just buzz words, or new methodologies?


2 – Db2 Code, Catalog, Function and Application Levels – differences and dependencies.


3 – Activation/Deactivation of new code and how to fallback and when you can’t.


4 – Different flavors of (pro-active) CD-Screening and how it can be automated:

* Anomaly alerting based on Incompatibility Change Indicators (ICIs)
* Dyn./Stat.Access Path Change Detection e.g.via Plan Management
* Clone based code change pre-apply exploiting Backup System
* Workload-KPI verification using SQL replay and KPI comparison


Audience Experience:    Intermediate Advanced
Platform:                          Db2 z/OS
Presentation Length:     60 minutes
Presentation Category:  Database Administration Performance Management Db2 Migration

 


2- Db2 z/OS Lies, Damn Lies, and Statistics

..Lies, damn lies, and statistics… – Benjamin Disraeli, Prime Minister of England (1868, 1874-1880)

The above line may, or may not, have been spoken well over 100 years ago, but the need for statistics and, above all else, accurate statistics is more important than ever in the Db2 world of today.

Presentation Outline

  • Db2 RUNSTATS basics & catalog tables and Columns used for access path
  • IBM recommendations through the ages : from Db2 V3 to Db2 12
  • Db2 RUNSTATS advanced
  • SYSCOLDIST explained
  • RUNSTATS real world Q&A :
    use of SAMPLE, COLGROUP, PROFILE, REOPT (ONCE), TABLESAMPLE SYSTEM, HISTOGRAM, …
  • RUNSTATS reversal

Speaker Biography

Roy Boxwell has more than 31 years of experience in MVS, OS/390, and z/OS environments – 29 of those in Db2. He specializes in installation, migration, and performance monitoring and tuning. Roy leads the SEG development team responsible for the real time database maintenance solutions. He is also an active participant, speaker and contributor on the IDUG Db2 Listserv and sends out a monthly Db2 z/OS Newsletter.

 

Saint Louis Db2 Users Group – September 2017

STLDUG – Saint Louis Db2 Users Group – September 2017

12. September 2017

SEGUS & SOFTWARE ENGINEERING präsentieren

Db2 12 Continuous Delivery – New challenges for deployment.

Pdf Präsentation

Fundamental changes in the Db2 z world often lead to concerns. Let’s face it – some changes force us to change! While a Db2 version migration usually took months, or even years, there will be no new Db2 version after 12, but continuous code drops.

This will have a tremendous impact on migration strategies, because we have to find a reliable way to test these code deliveries in a fraction of time. If we make it, Business Divisions will become enthused at how quickly new technology becomes available for new applications. This presentation will describe the difference between Code, Catalog, Function and Application Levels, how you can control them and how you can fallback in case of anomalies. It also illustrates how we still can be pro-active in testing without burning weeks and months.

Learn how to choose from four different levels of testing and a new way of automation. CD-Screening allows you to pick and choose from KPI based test automation. The levels include simple anomaly alerting, access path verification, clone Pre-apply and even workload capture/replay to easily discover different behaviour resulting from a new code Level.


Mehr über Db2 Continuous Delivery – CD

Presentation Outline

Joining this presentation, you’ll learn how to align Continuous Delivery to your Continuous Availability.


1 – Agile, Continuous Delivery, DevOps – just buzz words, or new methodologies?


2 – Db2 Code, Catalog, Function and Application Levels – differences and dependencies.


3 – Activation/Deactivation of new code and how to fallback and when you can’t.


4 – Different flavors of (pro-active) CD-Screening and how it can be automated:

* Anomaly alerting based on Incompatibility Change Indicators (ICIs)
* Dyn./Stat.Access Path Change Detection e.g.via Plan Management
* Clone based code change pre-apply exploiting Backup System
* Workload-KPI verification using SQL replay and KPI comparison


Audience Experience:    Intermediate Advanced
Platform:                          Db2 z/OS
Presentation Length:     60 minutes
Presentation Category:  Database Administration Performance Management Db2 Migration

Speaker Biography

Ulf Heinrich is the Director of Solutions Delivery at SOFTWARE ENGINEERING GmbH. He specializes in Db2 recovery issues and database maintenance, focusing on the growing requirement for cost reduction and 24×7 operations. As a consultant at large customer sites, he has implemented database maintenance procedures and recovery strategies, and also experienced the pitfalls of recovery scenarios under real‐world recovery pressure. His activities cover EMEA, as well as North America through SE’ U.S. subsidiary, SEGUS Inc. He’s involved in the development of SE’ maintenance and recovery Solutions.

Heart of America Db2 Users Group – September 2017

HOADUG – Heart of America Db2 Users Group – September 2017

SEGUS & SOFTWARE ENGINEERING sponsern diese Veranstaltung & präsentieren

11. September 2017

Db2 12 Continuous Delivery – New challenges for deployment.

Pdf Präsentation

Fundamental changes in the Db2 z world often lead to concerns. Let’s face it – some changes force us to change! While a Db2 version migration usually took months, or even years, there will be no new Db2 version after 12, but continuous code drops.

This will have a tremendous impact on migration strategies, because we have to find a reliable way to test these code deliveries in a fraction of time. If we make it, Business Divisions will become enthused at how quickly new technology becomes available for new applications. This presentation will describe the difference between Code, Catalog, Function and Application Levels, how you can control them and how you can fallback in case of anomalies. It also illustrates how we still can be pro-active in testing without burning weeks and months.

Learn how to choose from four different levels of testing and a new way of automation. CD-Screening allows you to pick and choose from KPI based test automation. The levels include simple anomaly alerting, access path verification, clone Pre-apply and even workload capture/replay to easily discover different behaviour resulting from a new code Level.


Mehr über Db2 Continuous Delivery – CD

Presentation Outline

Joining this presentation, you’ll learn how to align Continuous Delivery to your Continuous Availability.


1 – Agile, Continuous Delivery, DevOps – just buzz words, or new methodologies?


2 – Db2 Code, Catalog, Function and Application Levels – differences and dependencies.


3 – Activation/Deactivation of new code and how to fallback and when you can’t.


4 – Different flavors of (pro-active) CD-Screening and how it can be automated:

* Anomaly alerting based on Incompatibility Change Indicators (ICIs)
* Dyn./Stat.Access Path Change Detection e.g.via Plan Management
* Clone based code change pre-apply exploiting Backup System
* Workload-KPI verification using SQL replay and KPI comparison


Audience Experience:    Intermediate Advanced
Platform:                          Db2 z/OS
Presentation Length:     60 minutes
Presentation Category:  Database Administration Performance Management Db2 Migration

Speaker Biography

Ulf Heinrich is the Director of Solutions Delivery at SOFTWARE ENGINEERING GmbH. He specializes in Db2 recovery issues and database maintenance, focusing on the growing requirement for cost reduction and 24×7 operations. As a consultant at large customer sites, he has implemented database maintenance procedures and recovery strategies, and also experienced the pitfalls of recovery scenarios under real‐world recovery pressure. His activities cover EMEA, as well as North America through SE’ U.S. subsidiary, SEGUS Inc. He’s involved in the development of SE’ maintenance and recovery Solutions.

DesignCouncil CDDC for Db2 z/OS Continuous Delivery

Conference language is German

Anmeldung in zwei Schritten : 1 Kontaktformular ausfüllen  &   2  Hotelzimmer buchen (Vorteilpreis darunter)

1 – Anmeldung für die Tagung bei SOFTWARE ENGINEERING

Bitte füllen Sie zuerst das Formular darunter aus, um sich anzumelden:

Beim Klicken auf „Registrieren“ erhalten Sie die Anmeldebestätigung per Email versandt.

    Vorname (Pflichtfeld)

    Nachname Pflichtfeld)

    Firma (Pflichtfeld)

    E-Mail-Adresse (Pflichtfeld)

    captcha

    Sicherheitscode: (Pflichtfeld)

    Beim Klicken auf „Registrieren“ erhalten Sie die Anmeldebestätigung per Email versandt.

    2 – Anmeldung für ein Hotelzimmer im Courtyard Marriot:

    Marriott – Courtyard Hotel  (Hotel Überblick) 
    Speditionstraße 11, 40221 Düsseldorf, Medienhafen

    Gruppentarif für CDDC (buchen) : 

    Unter dem folgenden Link können Sie die reservierten Zimmer bis zum 7.08.2017 abrufen:

    http://www.marriott.de/meeting-event-hotels/group-corporate-travel/groupCorp.mi?resLinkData=CDDC%5Edushf%60sevseva%60130%60EUR%60false%602%609/4/17%609/5/17%6008/07/17&app=resvlink&stop_mobi=yes

    Zimmerkontingente zum Preis von 130,00 € (ohne Frühstück) sind abrufbar bis zum 4. August unter dem Stichwort CDDC.
    Die Übernachtungskosten trägt die teilnehmende Firma selbst.

    SOFTWARE ENGINEERING sponsert diese Veranstaltung & präsentiert


    IBMs Continuous Delivery for Db2 z/OS   +   Continuous Delivery Deployment Check

    Vorabinformation: Recorded Webinar in 4 Teilen   und    Produktflyer zum geplanten Produkt: CCDC for Db2 z/OS


    Agenda                     Detaillierte Agenda >

    1. Tag – Montag, den 4. September von 12:00 bis 17:00 mit Mittagsbuffet

    Abendveranstaltung (SOFTWARE ENGINEERING trägt die gesamten Kosten der Abendveranstaltung)

    2. Tag – Dienstag, den 5. September von 8:00 bis 14:30 mit Mittagsbuffet.
    Maximale Teilnehmeranzahl 30.


     

    Anreise

    Darunter finden Sie die Informationen für Ihre Anreise zum Tagungsort.

    2017-06 APPLCOMPAT in Db2 12: a little bit more agile?

    How to set Collection Ids for a reopt 2, 3 or 4 (Runtime optimization) and avoid the default collection NULLID ?

    Following on from my last newsletter, I have had to do some research about Collection Ids and how to set them.


    Last newsletter:
    2017-05 Db2 version 12: A little bit too agile?
    How to handle APPLCOMPAT when it comes to Dynamic SQL. A support to manage Db2 12 „agile“ release.

    Driven to distraction?

    The first thing you learn, is that the cli.ini file is now gone…all of the data is now found in the db2dsdriver.cfg file. OK, how does this all hang together?

    First Contact

    The very first thing that happens, is it looks up the name and the address of the desired Db2 on z/OS. This is just the TCP/IP data to initiate “first contact”. Once the first contact is done, the User Id and Password are required to validate the connection. All well and good.

    If your CurrentPackageSet and your reopt are *not* set, you then get the default collection NULLID under which all of your dynamic SQL executes

    Reoptimize this!

    Then it gets ugly… If your CurrentPackageSet and your reopt are *not* set, you then get the default collection NULLID under which all of your dynamic SQL executes (Now please re-read my last newsletter to see why that is of major interest!).

    But, what happens if you want to use reopt 2, 3 or 4 ?


    Quick aside:

    The reopt level determines what style of run time optimization to enable on the host. You can set:

    • Reopt 2 – No optimization (and this is the default),
    • Reopt 3 – To get REOPT(ONCE) behavior – so the first time that SQL comes in to execute, it gets optimized with the literal values in it, and then not again, or
    • Reopt 4 – To get REOPT(ALWAYS) behavior, so it drives a re-optimization every time that SQL comes in.

    I have NULL idea what you are talking about…

    So back to my question…

    What happens if you wish to use reopt 2, 3 or 4? Well, you have a problem, as these must use the reserved collection ids NULLID, NULLIDR1 and NULLIDRA respectively, which (remember my last newsletter), all die horribly with APPLCOMPAT getting involved…

    It gets worse

    Naturally, there is a dark lining to this cloud! The use of reopt actually disallows the use of CurrentPackageSet, which was the only way of managing APPLCOMPAT. What on Earth can you do…I have no idea…

    Help is on the way…

    We are conducting a Design Council in Germany  (September 4-5th, 2017) about IBMs Continuous Delivery for Db2 in September, where we will discuss all of this with customers and DB2 users, but I would love to get some feedback from you all too!

     

    As usual, if you have any comments or queries please feel free to drop me a line!

    TTFN

     

    Roy Boxwell

    2017-05 Db2 version 12: A little bit too agile?

     

    How to handle APPLCOMPAT when it comes to Dynamic SQL?

    I have been involved in testing in Db2 version 12 for a while now, and I think we need a discussion about a few features that come in with this “agile” release.

    APPLCOMPAT to the rescue?

    First up, is the use of APPLCOMPAT – This is now available throughout the SQL, but comes with a few problems. If you have static SQL then all is fine and dandy, as the APPLCOMPAT used is stored in the Db2 Catalog. You can easily refer to it and check which package is using what APPLCOMPAT. The real trouble starts with Dynamic SQL.

    Dynamic SQL intro

    A quick discourse about Dynamic SQL is now required…

    All Dynamic SQL that runs, must run “under the control” of a Package.

    This means that we all have loads of empty packages that are just used to run Dynamic SQL. You all have the SYSLHxxx, SYSLNxxx style Packages and probably loads more. These Packages are used for authentication, tracing, and validation of requests from remote users.

    Package is the Boss

    This is all good, apart from when a new Db2 12 Function Level (from now on FL) is activated. Why? Because the “package is boss” – If the package was bound at FL500 and you activate FL501, then any SQL that executes in that package that attempts to use an FL501 statement fails. If the SQL attempts to SET CURRENT APPLCOMPAT = ‘V12R1M501’ it will, of course, also fail.

    REBIND the world?

    To “fix” this, you simply have to REBIND the package to the new FL level.

    Sounds simple, huh?

    Well, what that means is that *all* SQL that uses that package will get the ability to go to FL501 straightaway, unless they are coded with SET CURRENT APPLCOMPAT = ‘V12R1M500’ or which level you would prefer…

    We all have that coded in our JAVA programs don’t we?

    Dynamic Packages always allocated

    So the problem now is – You have hundreds of Packages that you must rebind, but you dare not rebind them! Even worse, is that you probably *cannot* rebind them anyway, as they are permanently allocated and in use!

    . Imagine how many Dynamic SQLs are running in your shop?
    . Can you flush the DSC and rebind all of your “empty” Packages?
    . When can you plan such an outage?

    COLLECTIONs can help

    One work-around is to have a new COLLECTION, which the empty packages are bound to again. This works great, apart from one tiny little problem… The COLLID must then be set/changed in all of the CLI.INI or API places where it is currently set, or just defaulted to, today! At one of my customer sites that would be over 8,000 files to update!

    So now my questions to the readers out there


    How do you plan to manage this?

    How do you plan to roll-out FL levels?

    If using a new collection, how many CLI.INIs etc. must be changed?


     

    As usual, if you have any comments or queries please feel free to drop me a line!

    TTFN

    Roy Boxwell

    Central Canada DB2 Users Group 2017

    Central Canada DB2 Users Group 2017, Toronto, ON, Canada

    CCDB2UG –  5.-6. Juni 2017

     

    SEGUS & SOFTWARE ENGINEERING present

    Pdf – DB2 12 Continuous Delivery – New challenges for deployment.

    Fundamental changes in the DB2 z world often lead to concerns. Let’s face it – some changes force us to change! While a DB2 version migration usually took months, or even years, there will be no new DB2 version after 12, but continuous code drops.

    This will have a tremendous impact on migration strategies, because we have to find a reliable way to test these code deliveries in a fraction of time. If we make it, Business Divisions will become enthused at how quickly new technology becomes available for new applications. This presentation will describe the difference between Code, Catalog, Function and Application Levels, how you can control them and how you can fallback in case of anomalies. It also illustrates how we still can be pro-active in testing without burning weeks and months.

    Learn how to choose from four different levels of testing and a new way of automation. CD-Screening allows you to pick and choose from KPI based test automation. The levels include simple anomaly alerting, access path verification, clone Pre-apply and even workload capture/replay to easily discover different behaviour resulting from a new code Level.


    Mehr über DB2 Continuous Delivery – CD

    Presentation Outline

    Joining this presentation, you’ll learn how to align Continuous Delivery to your Continuous Availability.


    1 – Agile, Continuous Delivery, DevOps – just buzz words, or new methodologies?


    2 – DB2 Code, Catalog, Function and Application Levels – differences and dependencies.


    3 – Activation/Deactivation of new code and how to fallback and when you can’t.


    4 – Different flavors of (pro-active) CD-Screening and how it can be automated:

    * Anomaly alerting based on Incompatibility Change Indicators (ICIs)
    * Dyn./Stat.Access Path Change Detection e.g.via Plan Management
    * Clone based code change pre-apply exploiting Backup System
    * Workload-KPI verification using SQL replay and KPI comparison


    Audience Experience:    Intermediate Advanced
    Platform:                          DB2 z/OS
    Presentation Length:     60 minutes
    Presentation Category:  Database Administration Performance Management DB2 Migration

    Speaker Biography

    Ulf Heinrich is the Director of Solutions Delivery at SOFTWARE ENGINEERING GmbH. He specializes in DB2 recovery issues and database maintenance, focusing on the growing requirement for cost reduction and 24×7 operations. As a consultant at large customer sites, he has implemented database maintenance procedures and recovery strategies, and also experienced the pitfalls of recovery scenarios under real‐world recovery pressure. His activities cover EMEA, as well as North America through SE’ U.S. subsidiary, SEGUS Inc. He’s involved in the development of SE’ maintenance and recovery Solutions.

    IDUG 2017 DB2 North America Tech Conference

    IDUG 2017 North America Tech Conference, Anaheim, Kalifornien, USA

    SEGUS & SOFTWARE ENGINEERING präsentieren:

    Pdf Präsentation db2 12 Continuous Delivery – New challenges for deployment.

    Fundamental changes in the db2 z world often lead to concerns. Let’s face it – some changes force us to change! While a db2 version migration usually took months, or even years, there will be no new db2 version after 12, but continuous code drops.

    This will have a tremendous impact on migration strategies, because we have to find a reliable way to test these code deliveries in a fraction of time. If we make it, Business Divisions will become enthused at how quickly new technology becomes available for new applications. This presentation will describe the difference between Code, Catalog, Function and Application Levels, how you can control them and how you can fallback in case of anomalies. It also illustrates how we still can be pro-active in testing without burning weeks and months.

    Learn how to choose from four different levels of testing and a new way of automation. CD-Screening allows you to pick and choose from KPI based test automation. The levels include simple anomaly alerting, access path verification, clone Pre-apply and even workload capture/replay to easily discover different behaviour resulting from a new code Level.

    Presentation Outline

    Joining this presentation, you’ll learn how to align Continuous Delivery to your Continuous Availability.

    1. Agile, Continuous Delivery, DevOps – just buzz words, or new methodologies?
    2. db2 Code, Catalog, Function and Application Levels – differences and dependencies.
    3. Activation/Deactivation of new code and how to fallback and when you can’t.
    4. Different flavors of (pro-active) CD-Screening and how it can be automated.
      * Anomaly alerting based on Incompatibility Change Indicators (ICIs)
      * Dyn./Stat.Access Path Change Detection e.g.via Plan Management
      * Clone based code change pre-apply exploiting Backup System
      * Workload-KPI verification using SQL replay and KPI comparison

    Audience Experience:    Intermediate Advanced
    Platform:                          db2 z/OS
    Presentation Length:     60 minutes
    Presentation Category:  Database Administration Performance Management db2 Migration

    Speaker Biography

    Roy Boxwell has more than 30 years of experience in MVS, OS/390, and z/OS environments – 27 of those in db2. He specializes in installation, migration, and performance monitoring and tuning. Roy leads the SEG development team responsible for the real time database maintenance solutions. He is also an active participant, speaker and contributor on the IDUG db2 Listserv and sends out a monthly db2 z/OS Newsletter.

     

    New England DB2 Users Group März 2017

    New England DB2 Users Group März 2017, Old Sturbridge Village, MA, USA. NEDB2UG

    SEGUS & SOFTWARE ENGINEERING sponsern diese Veranstaltung und präsentieren:

    DB2 12 Continuous Delivery – New challenges for deployment Pdf

    am 30. März 2017

    Fundamental changes in the DB2 z world often lead to concerns. Let’s face it – some changes force us to change! While a DB2 version migration usually took months, or even years, there will be no new DB2 version after 12, but continuous code drops.

    This will have a tremendous impact on migration strategies, because we have to find a reliable way to test these code deliveries in a fraction of time. If we make it, Business Divisions will become enthused at how quickly new technology becomes available for new applications. This presentation will describe the difference between Code, Catalog, Function and Application Levels, how you can control them and how you can fallback in case of anomalies. It also illustrates how we still can be pro-active in testing without burning weeks and months.

    Learn how to choose from four different levels of testing and a new way of automation. CD-Screening allows you to pick and choose from KPI based test automation. The levels include simple anomaly alerting, access path verification, clone pre-apply and even workload capture/replay to easily discover different behaviour resulting from a new code Level.

    Presentation Outline

    Joining this presentation, you’ll learn how to align Continuous Delivery to your Continuous Availability.

    1. Agile, Continuous Delivery, DevOps – just buzz words, or new methodologies?
    2. DB2 Code, Catalog, Function and Application Levels – differences and dependencies.
    3. Activation/Deactivation of new code and how to fallback and when you can’t.
    4. Different flavors of (pro-active) CD-Screening and how it can be automated.
      * Anomaly alerting based on Incompatibility Change Indicators (ICIs)
      * Dyn./Stat.Access Path Change Detection e.g.via Plan Management
      * Clone based code change pre-apply exploiting Backup System
      * Workload-KPI verification using SQL replay and KPI comparison

    Audience Experience:    Intermediate Advanced
    Platform:                          DB2 z/OS
    Presentation Length:     60 minutes
    Presentation Category:  Database Administration Performance Management DB2 Migration

    Speaker Biography

    Ulf Heinrich is the Director of Solutions Delivery at SOFTWARE ENGINEERING GmbH. He specializes in DB2 recovery issues and database maintenance, focusing on the growing requirement for cost reduction and 24×7 operations. As a consultant at large customer sites, he has implemented database maintenance procedures and recovery strategies, and also experienced the pitfalls of recovery scenarios under real‐world recovery pressure. His activities cover EMEA, as well as North America through SE’ U.S. subsidiary, SEGUS Inc. He’ involved in the development of SE’ maintenance and recovery Solutions.