Slide 1

ISPW Natural Demo Mar 2011 Created by the kindness of CN Rail using the their Test ISPW system Through the efforts of Paul Vaenas CN - IT - Release Management

Slide 2

Introduction The following 5 minute video shows typical processes including: Adding an ISPW task to complete a change to an existing Natural program from Check out, thru Edit, Compile, Bind, Promote to Prod level and deploy to production runtime systems in less than 3 minutes. Fall back, returns to the prior version of the application, takes about 38 seconds Regress, puts the module back into a checkout library for correction, is a user option after a fall back This has been excerpted from a longer video (available on request) that shows many different processes and verification steps against real Natural Libraries, invoking standard Natural tools, necessary to convince even the most sceptical.

Slide 3

CN is one of the largest railroads in North America Employs 22,696 people in Canada / USA Approximately 20,421 miles of track (Canada, US) Earned CDN $7.9 billion in revenue in 2007 Trades on New York and Toronto exchanges Among lowest Class 1 rail road operating ratios Operate the largest rail network in Canada Only transcontinental network in North America Introduction to CN Rail

Slide 4

Computing Environment 2 physical mainframe computers 81 UNIX Servers (inc 6 power servers) 500 Windows Servers 12,000 desk tops in Canada and USA 28,387 Natural Modules 200 programmers About the Speaker (Paul Vaenas) I started working at CN in 2001 I was involved with the transition from manual processing to ISPW I have seen first hand the positive impact of ISPW on development processes

Slide 5

Natural Demo Video shows actual ISPW / Natural development steps Add ISPW work list task Checkout existing program Make program changes Compile program Generate JCL & run jobs Execute DB2 Bind Promote thru change cycle Deploy to runtime systems Takes under 3 minutes 3270 Interface shown, Eclipse GUI also available!

Slide 6

Natural Demo Video shows Fall Back to prior version Execute FB command Verify prior release active In 38 seconds could include mainframe & distributed components

Slide 7

Natural Demo Video shows regressing source Select option X to put failed program / application back in development level Instantaneous

Slide 8

The Customers Words CN has been operating with ISPW as its primary mainframe Deployment, Promotion and Source Control tool since 2001 ISPW continues to provide CN with Genuine IT support keeping customer interests at heart Prior to ISPW CNs Release Management team handled each change from Dev -> Test -> QA -> Staging -> Production manually In a nutshell: Workload was overwhelming Standards were more difficult to maintain Programmers and QA teams sat idle while waiting for promotions to be processed More effort was required on a day to day basis managing source code ISPW has given control and speed of delivery back to the developers, all the while respecting IT processes