Z DevOps – Flexible and

Open with IBM

Sanjay Chandru
Director – Z DevOps
1
Clients increasing momentum with IBM Z

Continuous Reinvention of Enduring

Platforms for Business
PER SECOND
4.3 Million 68,542 google
IMS & CICS vs searches
transactions

DAILY
30 billion 400 million 1 million
transactions retail hotel nights
transactions

ANNUALLY
29 billion 87% of all credit 90% of all
Workload as measured by installed Million Instructions Per Second (MIPS)
ATM transactions card transactions airline
reservations
Z is core to the 5 key principles that define IBM’s approach to
Hybrid Cloud

1 2 3 4 5
Hybrid Multicloud Open Secure Management
Enable Manage other Build capabilities Provide reliability Consistent service
enterprises vendors’ clouds, that are open by and continuous level, support,
across public, acknowledging the design, enabling security for the logging,
private, and reality that client client flexibility, client’s management, and
traditional environments are and reducing environment delivery across
environments heterogeneous vendor “lock in” complete cloud
environment

3
IBM Z Digital Transformation Journey
Hybrid Cloud Applications Hybrid Cloud Data
TRANSFORM WITH AGILITY
Transforming Apps for Hybrid Cloud Transforming Data for Hybrid Cloud

EVOLVE WITH CERTAINTY

MANAGE end-to-end across INFUSE – Operationalize AI with

IaaS on & off premise DELIVER WITH CONFIDENCE trust and transparency

ANALYZE – Scale insights with ML

everywhere
BUILD open and
hybrid applications ORGANIZE – Create
a trusted analytics
foundation

INTEGRATE with
multi-clouds COLLECT – Make data
simple and accessible

Core Infrastructure
for Hybrid Cloud Apps and Data
DevOps is no longer a buzz word

5
Open Source

92% of developers agree that open

source tools are critical to software
innovation*

84% of developers prefer to use open

source over closed or proprietary tools*

*Source: Gitlab Developer Survey. https://about.gitlab.com/developer-survey/2018/

6
Z DevOps  The Technical Value Proposition is Strong
ENTERPRISE WIDE
STANDARDIZATION
Platform neutral, continuous
integration and deployment pipeline
across the enterprise. Uniform
enterprise wide agile delivery
processes and standards facilitates
transferable skills
MODERN DEVELOPMENT
PRACTICES
Advanced Application Intelligence,
Modern development IDEs to
empower the next generation of
developers.
20-50% productivity benefits for
typical development tasks1
Strong Integration with Open Source  84% of developers prefer to use open source over closed or proprietary tools4
AUTOMATION
Powerful and automated unit
testing as part of a continuous
delivery pipeline
50-90% time savings on test
cycles2
DevOps
Tools
SKILLS AVAILABILITY
#2 on Glassdoor’s 50 best
Jobs in America Rankings
Successful DevOps transformation and one of the Top 5
Technical Skills Growth
results in 7x lower software delivery areas
change failure rate3
OPEN TOOL CHAIN
Analysis and Discovery
Modernize Applications with
Minimal Time, Risk & Cost
ADDI
• Automate discovery with mainframe connectors
and SCM integration
• Visualize application dependencies
• Accelerate Digital Transformation by finding API
candidates and discovering business rules
• New and innovative use cases including
provisioning intelligence and application insight to
drive DevOps optimization
General Discovery and
Analysis Products
• Lots of small customized niche products that address
specific areas (narrow not broad)
• No automated way to keep metadata in sync with
application changes
• Not broad enough to cover the variety of use cases that
enterprises would expect
Reliance On SMEs/Manual
Analysis
• Rely on subject matter experts to understand
application dependencies - but many are retiring
• Manually analyze impacts of potential application
changes – time consuming process limits capacity for
transformation projects
8
 IBM Z Open Development (ZOD) / IDz EE

Modern Development • Completely open source, multi vendor, robust

ecosystem
• Enterprise wide standardization, savings, and efficiency
• Ready skills availability
A toolset that provides core capabilities
needed to link z/OS development
IDE
DBB
seamlessly with an established, open
DevOps toolchain

IDz EE Git front end and open source integrations to

legacy SCMs

• Few more bells and whistles but continued isolation –

Enterprise standard across

back to square 1 for the customer in a few years
• Pre-defined streams to mimic parallel development,

mainframe and distributed

and therefore limiting
• Vendor lock-in since any new integrations are
dependent on the vendor support, eventual
(same processes, obsolescence

interchangeable skills,
unlimited talent pool)
Legacy SCMs

• Library managers in disguise that keep z/OS

development isolated
• Inflexible and limiting in the era of agile and DevOps

9
Git & DBB vs. Traditional SCMs

• True parallel development

• Branches on demand
• Freedom from pre-defined streams

• Continuous Improvement to build processes

• Use generic artifact repositories
• Easy integration with CI/CD Pipelines

BOTTOMLINE: If clients really want to adopt DevOps and Agile AND standardize processes across the enterprise
GIT/DBB is the ONLY Option for Z outside of RTC
10
 IBM’s Automated Unit Testing
Automated Unit Testing capability

• Developers can automatically generate unit tests for batch

and CICS programs as part of their daily work
IBM delivers automated unit testing • Easy to install and use
• Integral part of the CI/CD process
tooling for batch and CICS programs. • Mix and match with existing tools and solutions

Eliminates testing bottlenecks and makes

modern development processes a reality
for mainframe development.
Delivered in:
IBM
Developer for z Systems
Assisted testing
• Limited automation with tooling that’s reliant on the
debugger
• Focuses on tester, not the modern developer
• Doesn’t fully support Agile processes
• Heavy weight, installation takes weeks to sometimes
months

OR
Manual Testing

+
• Resource hungry and difficult to integrate into modern
processes

11
12
Why is Unit Testing hard for
Z Development?

Common inhibitors

• Programs are too large and complex.

• Procedural languages make unit testing more difficult

• Application architecture is not modular

• Lack of tooling

• Developer knowledge/skills/
awareness

• Provisioning additional test environments

13
IBM Z
• Key Features

Open Unit Test

• Automated unit testing for batch
and CICS COBOL programs Unit tests are executed
during Build phase -
(ZUnit) • Stubbing capabilities for CICS
meaning you don’t have
to deploy.
programs, meaning developers
don’t need to deploy to CICS during
unit testing (environment
independence)

• Automated data capture and

recording for batch and CICS
programs

• Test scenarios written in COBOL or

PL/I (batch)

• Integration into any CI/CD process

• Complements IBM Z Open

Development to create a powerful
development and testing
environment for any modern SCM.
A cross-platform,
Enterprise tool stack
Mainframe Distributed
Pipeline Coordination Jenkins

Leverage existing cross- Requirements/Tasks Issues or Jira

platform tools
Analysis ADDI

Source Control Git

Build on your current pipeline
Development ZOD, Eclipse (including IDz) , Visual Studio, …

Cross-train developers on Testing Multiple, JUnit, ZUnit

familiar tooling
Quality Control SonarQube

Build Maven, Gradle, Make, DBB

Artifact Repo Artifactory or Nexus

Deployment Mgmt Jenkins or UCD or Ansible

Release Mgmt UCR

15
• End to End
DevOps
The IBM
Way –
Open and
Flexible

IBM Z DevOps / © 2019 IBM Corporation 16

Everyone Plays a part

1.DevOps is about transforming application development and delivery in

order to accelerate digital innovation.
So DevOps is a topic for both business and IT roles in the organization.

2.You don’t buy DevOps, you do DevOps. DevOps is an approach, a

mindset – a combination of culture, process and technology (including
infrastructure, tools and services).

3.DevOps is not only about the hand-off between Development and

Operations. DevOps is about applying lean and agile principles across the
application delivery lifecycle (biz-dev-sec-ops) to achieve continuous delivery
of digital innovation. Key concepts: automation, feedback loops.
 Resources
Continuing your ‘Understanding DevOps’ journey

• DevOps from APIs to z Systems for

Dummies
• https://ibm.biz/apis2zdevops
• Other Resources
• Phoenix Project Book
• DevOps Handbook
• https://puppet.com/resources/whitepaper/state
-of-devops-report
• https://itrevolution.com/book/mythbusting-
devops-enterprise/
• https://itrevolution.com/book/tactics-leading-
change/
18
• http://dearauditor.org
BACKUP

19