Webinar presented by SEGUS & SOFTWARE ENGINEERING
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 webinar 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.
How to align Continuous Delivery to your Continuous Availability?
Recording from March 16th, 2018
The Db2Night Show z/OS Edition #Z85
How does Db2 12 Continuous Delivery affect
Db2 12 migration/maintenance strategies?
Code, Catalog, Function & Application Levels
Martin Hubel, IBM Gold Consultant & IBM Champion for IM
Roy Boxwell, Senior Software Architect
Recording from April 25th, 2017
Webinar video in 4 parts
Webinar presentation from April 25, 2017
- 1 – Video replay – 10 min.
Agile, Continuous Delivery, DevOps – just buzz words, or new methodologies?
- 2 – Video replay – 10 min.
Db2 Code, Catalog, Function and Application Levels – differences and dependencies
- 3 – Video replay – 5 min.
Activation/Deactivation of new code and how to fallback and when you can’t
- 4 – Video replay – 30 min.
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
. Q&A: Questions & answers : SQL Replay, BIFCID power
Cloning tool, masking, Code level check/Db2 code check.
1 – Agile, Continuous Delivery, DevOps
2 – Db2 Levels: Code, Catalog, Function, Application Levels
3 – Activation/Deactivation of Db2 levels (new code)
4 – Automating CD-Screening
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.