IBM z/OS Continuous Delivery

Have you guys heard  of continuous Delivery in technology?  Here is what Wikipedia says:

Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time.[1]It aims at building, testing, and releasing software faster and more frequently. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery

Well, if you are Mainframe customer, then you might be interested in knowing that IBM z/OS is moving to continuous delivery approach.  Here the redbook they released titled IBM z/OS Continuous Delivery

What was presented in that redbook was, The z/OS continuous delivery might use small programming enhancements (SPEs) to deliver the functionality. The z/OS continuous delivery offers discreet additions of functionality that you can choose to deploy on specific logical partitions (LPARs) or across sysplexes. The z/OS continuous delivery model provides the opportunity to advance the availability of new functionality. When that new function arrives via the service stream or version or release upgrades, this process can provide you with a balanced approach by receiving some functions sooner than others. When new functions are provided via the z/OS service stream, the Recommended Service Units (RSUs) process is in place to provide a quality test in a robust environment for those program temporary fixes (PTFs).

z/OS continuous delivery offers the following opportunities:

  • Select new SPE functionality and turn it on where it is most effective.
  • Gain the advantages of the SPE’s functionality before the next release availability.
  • If available, implement the SPE functionality to lower-level systems.
  • Check higher systems to avoid new functionality regression.
  • Reduce the risk of introducing a large change at release level by implementing SPE functionality earlier.
  • Use z/OSMF workflow if it is available with the SPE.
  • Check notifications to keep up-to-date with opportunities for implementing new functionality.
  • Absorb the SPE process into your normal system software update cycles.

What do you guys think? are you adaptable to this new change? As per vendors that provide system applications software, they are already tuned into this continuous delivery.

All data points to say “continuous delivery is here to stay”!  we need to deal with it!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s