Richard Brunkhorst presented on using Rational Development and Test Environment for z Systems (RD&T) to enable continuous integration and deployment for mainframe applications without requiring a physical mainframe. The demo showed using RD&T, Rational Developer for z Systems (RDz), and Rational Team Concert (RTC) for continuous development, building, and testing. UrbanCode Deploy (UCD) was used for continuous deployment to RD&T. The demo featured modifying a CICS application to use a DB2 database instead of VSAM, with code changes developed and tested on RD&T before deployment.

1. DEZ-3478: Continuous Integration and
Deployment on Rational Development
and Test Environment for z Systems
Richard Brunkhorst
RD&T Development Team Lead

2. Abstract
How do you do DevOps for z without requiring z (hardware) for the initial
phases of development? By coding, testing, and deploying on Rational
Development and Test Environment for System z (RD&T), users are able
to develop using the DevOps lifecycle without impacting their production
mainframe environments.
This session focuses on the use of UrbanCode Deploy (UCD) to deploy
to an RD&T target. It will feature a demo that includes Rational
Developer for z Systems (RDz) and Rational Team Concert (RTC) to
develop, build, and test on RD&T, and uses UCD to deploy to a test area
on Rational Development and Test Environment for z Systems in
preparation for formal QA.

3. Agenda
• Acronyms used in Presentation
• Why does Continuous Integration Matter?
• Traditional mainframe development work flow
• Demo development work flow using DevOps model
• DevOps Model & Demo Focus Points
• Maintenance Scenario used for demo
• Demo Presentation
• Summary
• Q&A

4. Acronyms
• UCD – UrbanCode Deploy:
A tool for automating application deployments through your environments.
• RD&T – Rational Development and Test Environment for System z:
A Linux based platform that emulates z Hardware and allows users to run z
Software stacks (z/OS, z/VM) on an Intel based platform.
• RDz – Rational Developer for z Systems:
A modern IDE for productive development of cross-platform applications written
in COBOL, PL/I, ASM, Java, or C/C++ in System z CICS, IMS, DB2, Batch
applications
• RTC – Rational Team Concert:
A team-aware software development platform that integrates work item
tracking, builds, source control, and agile planning.
• CLM – Collaborative Lifecycle Management:
A solution that delivers requirements management, quality management,
change and configuration management, and project planning and tracking
capabilities on a single platform.
• SCM – Software Configuration Management:

5. Why does Continuous Integration Matter:
Key Trends in Development Today
• ManagingApplications & Infrastructure TOGETHER
• Use of Hybrid Cloud environments
• Adoption of DevOps practices
• Growing use of Services
• Flexibility in Cloud application delivery
–Containers, Virtual Machines, Cloud Foundry
• “Multi-Speed IT”- DevOps includes the Mainframe

6. The need: Integrate systems of engagement with
systems of record
Systems of Engagement (SoE) Apps
Rapid
Releases AppStore
Monitor
and Optimize
Release
and Deploy
Develop
and Test
IntegrationTest
6
Monitor
and Optimize
Develop
and Test
Web Apps
Frequent
Releases
Production
Environment
Databases
Systems ofRecord (SoR) Apps
Fewer
Releases
Databases
By bringing together the culture, processes, and tools across the entire
software delivery lifecycle – spanning mobile to mainframe platforms

7. Change
Request
Opened
Implement
Change
•Developer
Checks
code out
from SCM
•Developer
implements
change
•Developer
checks
code into
SCM
Build
•Developer
Requests a
build
•Build is
queued
•Build is run
during non-
peak hours
Stage for
test
•Load
modules
moved to
test area
Test
•Manual
testing
performed
on
application
•Automated
testing
performed
on
application
•Defects
identified
Approval for
next stage
•Approved
for next
state of
testing or
for
production
Stage for
production
•Load
modules
moved to
production
area
Traditional Mainframe Development Workflow
Mainframe Environment

8. Change
Request
Opened
Implement
Change Build
Stage for
test Test
Approval
for next
stage
Stage for
production
Application
Moved to
RD&T
•UrbanCode
Deploy copies
Application
code from
production
Implement
Change
•Developer
Checks code
out from SCM
•Developer
implements
change
•Developer
checks code
into SCM
Build
•Developer
builds changes
on demand
•Automated
Test Cases
are run
•Defects
Identified
•Package
Created
Deploy
•Package
deployed on
demand for
function testing
•Automated
tests &
analysis are
run on
deployed
modules
•Failed
tests/analysis
flagged on
deployment
Test Cycle
•Manual
Testing of
application
code
•Automated
Testing of
application
code
•Defects
Identified
Stage for
moving to
Mainframe
Demo Development Work Flow
Mainframe Environment
RD&T Environment

9. DevOps Model & Demo Focus Points
99
Continuous
Customer Feedback
& Optimization
Continuous Release
and Deployment
Continuous
Monitoring
Continuous
Business Planning
Continuous
Testing
Operate Develop/
Test
Deploy
Steer
DevOps
Continuous
Feedback
• Continuous Integration
is achieved by using
Collaborative
Development &
Continuous Testing
via:
RD&T, RDz, & RTC
• Continuous Release and Deployment via:
UCD, RTC, & RD&T
Collaborative
Development

10. Development Topology

11. Maintenance Scenario
• There is an existing CICS application used for calculating mortgages
• The CICS application uses a VSAM file for application data
• There is a new requirement to have the CICS application use a DB2
database instead of a VSAM file

12. Video Demo

13. Checkpoint #1 – RD&T Environment is primed for
Development
UrbanCode Deploy - Deployment to RD&T

14. Checkpoint #2 – Developer has implemented
change and is ready for building
RDz + RTC Workbench – Developer has checked in new change set

15. Checkpoint #3 – Developer has built and packaged
a new change set and is ready for deployment
RTC Build Results – Build results with integrated zUnit Results

16. Checkpoint #4 – Package has been deployed and
ready for function test
UCD – Deployment results with zUnit + Code Coverage steps

17. Demo Highlights
• With the use of RD&T, code development, unit test, and function test
can be offloaded from the mainframe to the RD&T platform. RD&T has
the capability of running the same software stack as the mainframe.
• With the use of RDz, developers can perform program analysis, make
source code changes, and debug from a modern development
environment. In addition RDz provides quality analysis tooling that can
integrate into the build and deployment processes.
• RTC provides work item tracking, builds, and source control. It also
has the capabilities for custom post-build processing (automated
running of zUnit and Code Coverage) and reporting features allowing
users to gain insight into the quality of builds being produced.
• UCD provides deployment management, allowing deployable
packages to be moved between environments. It also has the
capabilities for custom deployment process, allowing the use of
analysis tooling integrations (zUnit and Code Coverage), which can
give users insight into the quality of the deployment packages being
produced

18. Q&A

19. Resources
• Rational Development and Test Environment for System z:
http://www-03.ibm.com/software/products/en/ratideveandtestenviforsystz
• Rational Developer for z System:
http://www-03.ibm.com/software/products/en/rational-developer-for-z-
systems
• Collaborative Lifecycle Management:
https://jazz.net/products/clm/
• Rational Team Concert:
https://jazz.net/products/rational-team-concert/
• UrbanCode Deploy:
https://developer.ibm.com/urbancode/products/urbancode-deploy/

20. Notices and Disclaimers
20
Copyright © 2016 by International Business Machines Corporation (IBM). No part of this documentmaybe reproduced or transmitted in any form withoutwritten permission
from IBM.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restrictedby GSA ADP Schedule Contract with IBM.
Information in these presentations (including information relating to products thathave not yet been announced byIBM) has been reviewed for accuracy as of the date of
initial publication and could include unintentional technical or typographical errors.IBM shall have no responsibilityto update this information.THIS DOCUMENT IS
DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE
USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY.
IBM products and services are warranted according to the terms and conditions ofthe agreements under which they are provided.
Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawalwithout notice.
Performance data contained herein was generallyobtained in a controlled,isolated environments. Customer examples are presented as illustrations ofhow those customers
have used IBM products and the results they may have achieved. Actual performance,cost,savings or other results in other operating environments mayvary.
References in this documentto IBM products,programs,or services does notimplythat IBM intends to make such products,programs or services available in all countries in
which IBM operates or does business.
Workshops,sessions and associated materials mayhave been prepared by independentsession speakers,and do not necessarilyreflectthe views of IBM. All materials
and discussions are provided for informational purposes only,and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participantor
their specific situation.
It is the customer’s responsibilityto insure its own compliance with legal requirements and to obtain advice of competentlegal counsel as to the identification and
interpretation of any relevant laws and regulatory requirements thatmayaffect the customer’s business and anyactions the customer mayneed to take to complywith such
laws. IBM does notprovide legal advice or representor warrant that its services or products will ensure thatthe customer is in compliance with anylaw

21. Notices and Disclaimers Con’t.
21
Information concerning non-IBMproducts was obtained from the suppliers ofthose products,their published announcements or other publiclyavailable sources. IBM has not
tested those products in connection with this publication and cannotconfirm the accuracy of performance,compatibilityor any other claims related to non-IBM products.
Questions on the capabilities ofnon-IBM products should be addressed to the suppliers ofthose products.IBM does notwarrantthe quality of any third-party products,or the
ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDINGBUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
The provision of the information contained h erein is notintended to, and does not, grantany right or license under anyIBM patents,copyrights,trademarks or other intellectual
property right.
IBM, the IBM logo,ibm.com,Aspera®,Bluemix,Blueworks Live,CICS, Clearcase,Cognos®,DOORS®,Emptoris®,Enterprise DocumentManagementSystem™,FASP®,
FileNet®,Global Business Services ®,Global Technology Services ®, IBM ExperienceOne™,IBM SmartCloud®,IBM Social Business®,Information on Demand,ILOG,
Maximo®, MQIntegrator®, MQSeries®,Netcool®, OMEGAMON, OpenPower,PureAnalytics™, PureApplication®,pureCluster™,PureCoverage®, PureData®,
PureExperience®,PureFlex®, pureQuery®, pureScale®,PureSystems®,QRadar®,Rational®,Rhapsody®,Smarter Commerce®,SoDA,SPSS, Sterling Commerce®,
StoredIQ, Tealeaf®,Tivoli®, Trusteer®,Unica®,urban{code}®,Watson,WebSphere®,Worklight®,X-Force® and System z® Z/OS, are trademarks ofInternational Business
Machines Corporation,registered in manyjurisdictions worldwide.Other product and service names mightbe trademarks ofIBM or other companies.A current listof IBM
trademarks is available on the Web at "Copyright and trademark information"at: www.ibm.com/legal/copytrade.shtml.

22. Thank You
Your Feedback is Important!
Access the InterConnect 2016 Conference Attendee
Portal to complete your session surveys from your
smartphone,
laptop or conference kiosk.