Slides from the webinar titled "Drinking our own champagne z Systems Development and Test Environment V10" posted here watch the replay on http://ibm.biz/zDevandTest

1. Drinking our own champagne
z Systems Development and Test Environment V10
Christopher Cook,
zPDT development manager
Alisa Morse
z Systems Development and Test offering manager

2. • zD&T- why and what
• What’s new
• Internal use cases
– General
– Integral to zNext delivery
2
Agenda

3. 3
@IBMzSystems
#EZSource and #IBMz
Companies need to transform to become a digital enterprise
What was Is now
Crossing industries and transforming
customer experience
Finance
App
Auto
App
Home
Buyer
App
Finance
App
Auto
App

4. Product Owner
Senior Executives
Developer Domain ExpertsAuditors
QA Support Staff
External Vendor
Operations Staff
Enterprise
Architect
PMO Lead
ApproverProject Manager
Line-of-business Customer
IT
Agility - Velocity – Innovation – Cost - Quality
App Development, Orchestration, Integration, Security, Management, Governance
What does the Line of Business want from IT?

5. Typical z Systems Testing Architecture
Organized by project team, vertically scaled, sharing resources, limited automation
z/OS
Dev/Test LPARProject
Team
[April Maintain]
Project
Team
[May prototype]
Project
Team
[June New Func]
Project
Team
[Dec Upgrade]
Data
App
App
App
1.Shared resources combined with
overlapping schedules can elicit
conflicts, impede innovation and
slow code delivery
2.Coordination of environmental
changes and releases cause
bottlenecks, delays and additional
overhead
3.Shared test data is difficult to
manage and can lead to over
testing or incorrect test results

6. Interactive Poll # 1
6
Which of the following challenges do you have? (Can choose multiples)
• Insufficient mainframe Dev & Test LPAR availability leads to
defects and missed schedules
• Tightly controlled mainframe environment prevents agile
experimentation and prototyping
• High cost of mainframe development and test hardware and
software
• Skill gaps due to off shoring, outsourcing or the majority of skills
being near retirement
• Slow response time for off shore teams needing development
access

7. Add mainframe dev & test capacity
without increasing your MIPS
Affordable off host development
and test environment
IMS DB2
CICS
WAS MQ
z/OS
COBOL, PL/I, C++, Java,
EGL, Batch, Assembler,
X86 PC or HX5 Blade
running Linux
IBM SoftLayer Infrastructure
zD&T
RTC RIT
Rational
Development and
Test Environment
for z Systems
(zD&T)
• Develop and test z/OS applications anywhere,
anytime
• Free up mainframe development MIPS
for production workload
• Eliminate costly delays by reducing burden on
existing IT operations staff
• Reduce time to value and minimize ongoing
administration and capital expense with zD&T Cloud
Managed DevOps
• Exploit the z13 hardware capability, including z13
Crypto Express 5S
• Comprehensive z/OS 2.2 software distribution:
• z/OS plus major subsystems
• Underpinned by the z/OS components of DevOps for
the Enterprise development, test, and deployment
tooling
Note: This Program is licensed only for development and test of applications that run on IBM z/OS. The Program may not be used to run production workloads of any kind, nor more robust development workloads including without
limitation production module builds, pre-production testing, stress testing, or performance testing.
“RD&T improved our development and testing timeline and
provided stability and quality” Developer, Large Enterprise
Computer Services Company
https://www.techvalidate.com/tvid/C99-3E2-1ED
UCD
IDz
DT

8. • Drive new software to production faster
– Prototyping
– z/OS software betas or upgrades
– Development
• Employee Education in an indestructible, easy-to-use environment
• Distributing development and test activities to improve availability, quality, productivity.
Improved mainframe environment availability
Elimination of shared data issues
Enable self-service for simple z/OS administration changes
• Enabling Continuous Integration and Agile Development methodologies for z/OS
• Providing easy environment access for geographically dispersed and outsourced teams
• Application demonstration
Typical zD&T use cases

9. z Systems Development and Test Environment V10
Announce 10/11/16, eGA 11/17/16
More flexible licensing with an updated z/OS software distribution:
• Cloud friendly software-based licensing for enterprise customers, with up to 8 CPs per instance
• Hardware-based licensing for personal and portable use cases, 3 CPs per instance
• Adopt newer levels of z/OS software- with z/OS 2.2, z/OS Connect, CICS 5.3, IMS 14.1, RDz 9.5.1, z/OS Explorer 3,
RTC 6.0.1, and UCD 6.2

10. 10
zD&T requirements
• Same as product license server
• Cannot run on same Linux system with
a zD&T instance
• Hardware requirements
• 2 GB RAM
• 12 GB Disk space
• Software requirements
• RHEL 6.0 and above
• Virtualization platforms
• VMWare ESXi 5.0
• zBX model 3
• KVM
• XEN
• 32 bit runtime libraries
• 32 bit Linux glibc libraries
• Same as previous releases
• Hardware requirements
• 2-4 GB RAM per CP
• 1 GB per core for Linux
• USB for Personal Edition
• 150 GB disk space z/OS ADCD
• Software requirements
• RHEL 6.0 and above
• Virtualization platforms
• VMWare ESXi 5.0
• zBX model 3
• KVM
• XEN
• 32 bit runtime libraries
• 32 bit Linux glibc libraries if using
software-based licensing
License ManagerzD&T Instance

11. Product Structure Changes
RD&T PID
5725-G39
Rational Development
and Test Environment
• AUSI
• RVU
• Token
Rational Development
and Test Environment
with Parallel Sysplex*
• RVU
• Token
zD&T PID
5725-G39
z Systems Development
and Test Environment
Personal Edition
• AUSI
z Systems Development
and Test Environment
• RVU
• Token
z Systems Development
and Test Environment
with Parallel Sysplex*
• RVU
• Token
• The zD&T 10 RVU metric has
new license and S&S part
numbers
• Old part numbers have been
automatically migrated to new
part numbers 1:1
• Withdrawal announcement was
11/17/16. Effective dates are
2/13/17 for license parts and
11/15/17 for S&S parts
• Link: https://www-
01.ibm.com/common/ssi/cgi-
bin/ssialias?infotype=AN&subtyp
e=CA&htmlfid=899/ENUSLP16-
0635

12. z/OS 2.2 Distribution
• z/OS V2.2, including sub-features
• Encryption Facility
• z/OS Security Level 3 Feature and z/OS
Communications Server Security Level 3
Feature
• IBM HTTP Server
• DITTO/ESA
• IBM z/OS Management Facility
• IBM PD Tools
• Tools Base for z/OS
• IBM Debug Tool 13.1
• IBM File Manager 13.1- evaluation
• IBM Fault Analyzer 13.1- evaluation
• CICS Transaction Server
• CICS 5.1, 5.2, 5.3
• CICS/VSAM Recovery 5.1, 5.2
• CICS Transaction Gateway 9.0
• CICS Tools
• CICS Deployment Assistant 5.3
• Tivoli
• Tivoli System Automation for z/OS 3.5
• Tivoli NetView 6.2.1
• Tivoli Workload Scheduler for z/OS
• Compilers
• IBM Compiler for REXX 1.4
• IBM Enterprise PL/I 4.5
• IBM COBOL 5.2
• IBM Rational COBOL Runtime 6.0.1 (EGL)
• XL C++ 2.1
• IBM Java SDK for z/OS 7.1, 8.0
• WebSphere Application Server for z/OS 8.0, 8.5,
Liberty Profile
• DB2 for z/OS
• DB2 for z/OS 10, 11
• DB2 Utility Suite for z/OS
• DB2 Administration Tool for z/OS
• DB2 Object Comparison Tool for z/OS
• DB2 for z/OS QMF
• IMS
• IMS 13, 14.1
• WebSphere MQ for z/OS 8
• Rational Developer for System z 9.5.1 z/OS
components
• Rational Team Concert 6.0.1 z/OS components
• UrbanCode Deploy 6.2 z/OS Agent
• IBM Sterling Connect Direct for z/OS 5.2
• IBM Explorer for z/OS Aqua V3.0
• IBM z/OS Connect Enterprise Edition V2.0
Green indicates New

13. 13
IBM Developer for z Systems + z Systems Development and Test Environment
Develop and test off host, increase speed and quality
Better quality by shifting left with zD&T
-- Better development (including
debug) and unit test coverage early in
the cycle
-- Reduce errors caused by
contention. Enable easier problem
determination with isolated
environments
-- Lower defect rates by automating
zUnit (Unit Test) without consuming
mainframe resources
-- Defects eliminated at code phase
cost 12x less than those found in QA
Free up development and test MIPS for higher value
workloads
-- Implement DevOps practices
(eg TDD, CI, CD) to improve
quality and delivery time
without additional
development and test MIPS
consumption
-- Reduce development and
test costs, including
development and test capacity
chargebacks
Boost development productivity
-- Enable more parallel work and
provide more control to teams.
-- Liberate developers to rapidly
prototype new applications
-- Improve the value of your
application portfolio through
electronic/automated code review
-- Develop and test System z
applications anywhere, anytime

14. 14
Rational Team Concert + z Systems Development and Test Environment:
Modern processes and the environment to support them

15. z Systems Development and Test Environment + UrbanCode Deploy
Efficiently manage configurations across environments and provide self-service capabilities
Introduce DevOps practices and improve software delivery
-- Implement DevOps practices (eg
TDD, CI, CD) to improve quality and
delivery time
-- Provide a unified solution for
continuous delivery of heterogeneous
enterprise applications
-- Ensure that throughput of each
process (Develop, Build, Deploy) is
equal
Reduce costs
-- Accelerate delivery and reduce
deployment time by over 95% to
develop/test multi-tier applications
across heterogeneous environments
and platforms
-- Reduce amount of manual labor,
resource wait-time, and rework by
eliminating errors & providing self-
service environments
Remove bottlenecks
-- Accelerate deployment by enabling
development teams to self deploy with
automation
-- Automate managing configuration and
version deployment reducing deployment
outages
-- Greater visibility of “what is where” with
the ability rollback to any prior version at
ease

16. RD&T via Cloud Managed DevOps Services provides the core RD&T offering on
a virtual private cloud, without the setup and maintenance IT costs
• Provides the
RD&T offering, customized
and configured for each client
• On a scalable, single-tenant,
IBM SoftLayer Infrastructure
• Provides 99.9% availability
(SLO)
• Managed by
IBM Services
IBM Customer
Success Services
IBM SoftLayer Infrastructure

17. 17
Keep up with the latest deliveries at Mainframe DEV:
https://developer.ibm.com/mainframe/

18. 18
zPDT Universe
Commercial customers
o Offering = zD&T
o z/OS
o Physical or virtual
o Cloud or On Prem
ISVs
o Offering = zPDT
o z/OS, z/VM, z/VSE, Linux
on z
o Physical
o On Prem
IBM Internal
o z/OS, z/VM, z/VSE, Linux
on z
o Physical
o Cloud or On Prem

19. 19
IBM internal usage

20. • Deploying and Testing a build takes a long time
• Installing the SMP/E build takes hours
• Testing takes another couple hours
• There’s also a zip build which doubles the install effort
• SVT has to test in multiple z/OS environments
20
Challenges for the UrbanCode team

21. Auto build, deploy and test in 5 minutes
The solution to these challenges
Auto Deploy &
TestIBM UrbanCode
Deploy
Rational Team Concert
Selective Deploy
Build
Push
builds
Kick-off deploy
z/OS 2.2DEV
z/OS 2.1Primary Test
z/OS 2.2
zD&T
Extended
Test
z/OS 2.2
Performance
Test
z/OS 1.13
zD&T
Extended
Test

22. • Deploy time greatly reduced.
– Build + deploy takes 5 minutes
• Compared with several hours before
• No manual deploy effort at all
– Increased velocity
• Allowed us to do 7 deployments a day last release,
• Verification test effort greatly reduced
– Automated build verification, failure notification by email
• Shift left testing, fewer/no conflicts in integration
– Before this, we merged multiple changes into one deploy, leading to conflicts and complexity in problem
diagnosis
– Now individual changes are tested independently
• The real benefit: Developers now focus on developing new features and fixing bugs. They are much more productive
and are focused on the tasks that they enjoy. 22
The benefits of the solution

23. – Support early version of zNext architecture in zPDT
– Long before production GA level release of zPDT and availability of real hardware machine with
these capabilities.
– Currently only CPU architecture/facilities.
– Available only to IBM internals for confidentiality and security under DOU control.
– zPDT Team sets up Central Servers for group access, or can have single user lap-top version
23
𝑧𝑃𝐷𝑇 − 𝛼 (Alpha Driver)

24. • zPDT engineers work closely with the developers of the SAK (System Architecture
Kernel) program
• SAK is the key test vehicle used in zNext Bring Up
• SAK & zPDT collaborate on initial Architecture implementations
• Once we are both satisfied that emulation of a feature/instruction is working correctly, we
make it available in the next zPDT Alpha code drop
• Most IBM internal groups make use of Central Servers that the zPDT team sets up.
These are very large configuration x86 servers with access to IBM File Sharing systems
which users can load their code to (e.g. zOS images, new Compilers)
• The Central Server concept allows us to control access and to more easily roll out new
versions of the code. This is new in the current cycle and has made the zPDT Alpha code
much more accessible to internal users.
• zPDT team works closely with users and plans to conduct survey to review what we can
do to improve.
24
Process to maximize use of alpha code (Shift Left Testing)

25. • zOS Development – able to test new architectural implementations several months
ahead of HW access. Found and fixed several issues.
• Linux on z – tested a number of new features
• KVM for z – tested additional virtualization capabilities
• Compiler team – able to build executables containing new instructions and test prior to
HW being available
• Research – several research users have experimented with enhanced security and
vector capabilities
25
Groups Using zPDT − α

26. – Architecture flux/evolution sensitive
• Potential for recode, rework, and/or discard of development/test depending on stability of architecture
• User version management
– Shift-left of development/test of software for new architecture support
26
Challenges

27. • Finding problems earlier!!!
• zNext on a laptop or Central Server for personal/group development
– Reduces need for hardware machines, scheduling development/debug time, etc.
– zNext HW access is at a premium so being able to test SW via Emulation prior to HW availability
really helps
• Enables earlier software exploitation of new hardware features. Decreases time of software GA from
new hardware GA.
• Enables earlier development/test of various z ecosystem components
– OS, service, performance, library routines, testcase generators, etc. prior to hardware availability
on a high performance platform.
• Validates architecture usage by OSes, services, testcase generators, etc.
– Found various architecture areas needing resolution and updated architecture.
• Differing interpretations
• Deficiencies in scenario handling
• Mutual benefit of early pre-validating/verifying zPDT for zD&T and ISV customers 27
Benefits

28. Interactive Poll # 2
28
Which of these use cases would be most valuable for your organization?
• Prototyping
• z/OS software betas or upgrades
• Employee Education / Skill Building
• Distribution and isolation of development and test activities
• Enabling Agile Development methodologies for z/OS
• Providing mainframe access for geographically dispersed teams
• Application demonstration

29. 29
zD&T Benefits
• Insufficient mainframe Dev & Test LPAR availability leads to defects and missed schedules
• Tightly controlled mainframe environment prevents agile experimentation and prototyping
• High cost of mainframe development and test hardware and software
• Skill gaps due to off shoring, outsourcing and the majority of skills being near retirement
Business Challenges
Business Benefits
Cost Savings
Lower cost dev/test LPARS:
Additional capacity necessary for
adopting DevOps practices
available on Intel compatible
hardware
MIPS reallocation : Initial Dev &
Test activities performed on zD&T
enables reallocation of MIPS to
higher value production workload
Economical training platform:
Portable, indestructible
environment for skill building
Quality
Shift Left testing : Better test
coverage earlier in the cycle on
high fidelity z/OS Dev & Test
environment leads to quality
and quicker delivery
Work in parallel vs serially:
Distributed environments
reduce errors caused by
contention and enable easier
problem determination on easily
provisioned systems
Agility
Adapt to changing
business requirements :
z/OS on x86 hardware that
can be
virtualized and reset offers a
developer sandbox for
prototyping and V2V
migration
Portability: Teams can Dev
& Test z/OS applications
anytime, anywhere.
Outsourced teams can work
without mainframe access.

30. Resources
• zD&T Product Page
• Short zD&T video
• zD&T on Mainframe Dev
• Beta community
• DevOps for the Enterprise tech talks: http://bit.ly/1b4wl18
• IBM Cloud Managed DevOps Services
• Automated z Systems Application Testing on the Cloud
• zD&T Tech Validate facts
• zD&T Product Documentation, including zPDT Redbooks
• zD&T Hub
• Request your test drive today:
http://www.ibm.com/developerworks/downloads/rdtsandbox_systemz/index.html

31. Thank You