Jim DeeDecember, 2019

Continuous Delivery and BMC Db2

BMC Plans

We must support IBM changes in a timely manner

In addition, we plan to deliver enhancements in the maintenance stream

• Increases flexibility to implement new but important requirements

• We can identify impacts (what won’t get done)

We Will Have a Regular Cadence

We plan to deliver in May and November• Was April, July, and November

• Maximize QA time and deliver higher quality

• Balance between delivery frequency and development time

• A Technical Bulletin will document the SPE for each product line

There will be exceptions!• Function we want to deliver out of cycle

We do not plan “function levels”• As in the past, we will provide options if necessary, to avoid changing product

behavior

FIXCAT

We want to exploit FIXCAT HOLDDATA support in SMPE• SMPE converts to SOURCEID during RECEIVE

Can group related fixes by categories• REPORT MISSINGFIX

• We hope to support customer use of RECEIVE ORDER in the future

FIXCAT

BMC categories:• BMC.TargetSystem-RequiredService.DB2.VvvRrMmmm and

BMC.TargetSystem-Exploitation.DB2.VvvRrMmmm (IBM suggested)

• Example is BMC.TargetSystem-Exploitation.DB2.V12R1M502

• BMC.Function.<function> or BMC.DB2.Function.<function>

• Example is BMC.Function.DataSetEncryption

• BMC.DB2.<yyyy><mm> for our periodic deliveries

What Does This Mean To You?

Enhancement delivery will be independent of our RSL’s

• Like IBM

We still recommend applying all maintenance to whatever point in time you’re comfortable with

• Use Internet Service Retrieval (ISR)

Reduces prereq problems

Speaking of Long Prereq Chains…

It can happen that a PTF for an enhancement will be the prereqfor a fix PTF

• This will not change the default behavior of the product!

• The only change is that we now ship more PTF’s because of the enhancements in the maintenance stream

If you are back leveled on maintenance, applying a recent PTF can pull in many prereqs!

Thank You