1. ® IBM Software Group © 2012 IBM Corporation Rational Developer for System z Rollout Best Practices Jon Sayles, IBM/Rational April 20th, 2013

2. 2 @ Copyright 2013 - IBM IBM Trademarks and Copyrights  © Copyright IBM Corporation 2007,2008, 2009, 2010, 2011, 2012. All rights reserved.  The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates.  This information is based on current IBM product plans and strategy, which are subject to change by IBM without notice. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way.  IBM, the IBM logo, the on-demand business logo, Rational, the Rational logo, and other IBM Rational products and services are trademarks or registered trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

3. 3 @ Copyright 2013 - IBM Course Contributing Authors  Thanks to the following individuals, for assisting with this course:  David M Bean/IBM Rational  David Lawrence  Brad Adams/IBM Rational

4. 4 @ Copyright 2013 - IBM Agenda Topics:  Introductory thoughts  The rollout project: –Steps –Milestones  Note that the ideas presented in this slide deck have been collected and organized from a number of sources, over several decades of transformative software implementation – with the assistance and input of many expert consultants in this domain.  The slides present what is essentially a 1,000 foot view of rollout best practices "what is" – not "how to" information

5. 5 @ Copyright 2013 - IBM The Problem  You want this   Magnitude of order productivity boost using RDz (7.6 no less) as opposed to ISPF 6.0 But:  Your mainframe system is:  Complex and unique  Your development processes are:  Unique  Locked-down, based on decades of hard-fought lessons-learned  Your developers are (after all) Mainframe developers  These results are statistically significant for these seven use cases.  Your developers do a lot more of other things  In order to bring RDz's benefits to "a lot more" you'll need to plan and integrate  There is no magic wand or silver bullet  Just old-fashioned software project management and the application of talented individuals' time

6. 6 @ Copyright 2013 - IBM Rollout Planning – Final Thoughts "Any transformative solution rollout is like a software project. But instead of outputting code, you're outputting change." Two focus areas: 1.Technical 2.Human factors Each focus area requires time and resource allocation, as part of an overall project plan

7. 7 @ Copyright 2013 - IBM Breaking out the Technical and Human Factors Requirements Develop Test Access RDz Client - installation/configuration RDz Server - installation/configuration Developer transition experience Developer Workflow Functionality Coverage

8. 8 @ Copyright 2013 - IBM The Gist of the RDz Rollout Challenge Technical requirements are known and are relatively straightforward to solve 1.Tool performance 2.Scalability Human Factors requirements can be more complicated There are two groups of developers in your shop. 1. Those who equate "New == Superior" 2. Those for whom "New = Unproven" This presentation deals with rolling RDz out to the 2 nd group:  "New == Unproven" demographic is (most likely) the silent majority of your mainframe developers  We address their concerns through best-practices and empirically- proven methods (see slide notes)

9. 9 @ Copyright 2013 - IBM Rollout Project – Time and Resource Allocation This chart represents the general importance – in terms of time and resource commitment to the various phases of an Rollout. It should be noted that, while these percentages are useful (in terms of project planning) – the absence of any one of these can potentially cause a rollout to fail.  For example, even though Product Education represents only 25% in terms of how much time to allocate to it – without quality RDz training your rollout will most likely fail. Executive Sponsorship It is also extremely important to understand the role played by " Executive Sponsorship ". However that critical success factor is not a matter of resource allocation – but an overarching requirement. Planning,Installation, Configuration, Optimization, Integration with your z/OS processes ProductEducation(Training) Post-training mentoring assistance and self-service technical help systems 35% 30% 35%

10. 10 @ Copyright 2013 - IBM The Fundamental Question  Will RDz be a point-product (tactical development tool), or do you want RDz to be used strategically - instead of or in addition to ISPF for z/OS maintenance/development/support?  If RDz is to be a "point-product" you need to consider when and how to use RDz's feature/function:  Examples of RDz's use as a point-product: –SOA / Web Service Development/Test –Software analytics/Code review –Unit testing  If you want RDz to be used for traditional z/OS maintenance and development work:  The business benefits can be significant  But there is more integration effort  In either case you will benefit from a systematic approach to Rollout – which begins on the next slide

11. 11 @ Copyright 2013 - IBM The Rollout Project – Steps and Milestones 1. Rollout Project Planning – Develop Use Cases, specific to your business driver(s), software stack (z/OS and distributed), and development culture 2. RDz z/OS Server Installation, Verification, Optimization - plans and execution 3. SCM Integration - custom coding almost always required. Many different approaches 4. Other z/OS (ISPF) Tools Integration (frequently-accessed CLIST, REXX Exec, Dialog Manager, 3rd Party TSO tools). 5. Client Software - Plans for installation/plug-in customization, update 6. Workspace customization - Decision points on customized configuration and preferences, management automation solution (initial rollout and updates) 7. Education Plan and training - With customized training 8. Mentoring and follow-up assistance - Planning and execution. 9. Center of Excellence - Becoming Self-Reliant, by setting up internal user groups, help providers, etc. 10. Momentum Building – Creating and taking advantage of internal product "pull" 11. ROI Measurement - Measuring derived value 12. Lessons Learned – Leveraging the experience of rolling out powerful, innovative technology

12. 12 @ Copyright 2013 - IBM 1. Rollout Project Planning  The initial and most important task:  Checklists/spreadsheets/process models and sample project plans can be provided by IBM  But you must refine, customize and ultimately "own"  Stakeholders in this process include:  From your company:  Executive sponsor  Technical management  Development: –RDz lead technical developers –MVS Systems Programmers/DBA  From IBM:  Sales/Technical account team  Technical support and/or RDz Deployment Project Office (DPO)  The place of a qualified Business Partner:  Provide technology and rollout leadership  Technical implementation, training and mentoring skills  Like all project planning, rollout planning is iterative

13. 13 @ Copyright 2013 - IBM Planning Session (Sample High-level Considerations)  Goals and considerations for planning:  Establish and document your RDz business value proposition (BVP)  Fundamental in developing the criteria and will be the basis for interaction with: –Executives/Management –Technical/Application/Systems  BVP might be formulated during your RDz Proof of Capability  Translate the RDz BVP into high-level functional Use Cases for implementation  Decide on RDz as a point-product vs. as a tool for z/OS development  Determine rollout approach (Top Down vs. Bottom Up)  Create project plan, readiness documents, checklists, milestones, timelines  Site and culture and tools specific  Project checkpoints and milestones  High-level samples documented in this slide deck  Decide on a formal process of communication and collaboration  Document sharing, etc.  Question/concern escalation process: Internally and with IBM  Formulate ROI Metrics for management reporting/assessment  Discuss and document evaluation criteria –Apples-to-Apples "objective" benchmark vs. subjective - –Need for historical data on evaluation criteria –Sample RDz Rollout Evaluation Criteria can be obtained from IBM

14. 14 @ Copyright 2013 - IBM Top Six Business Value Propositions (BVP) for RDz 1. Productivity  Customers state achieved goals of between 5% and 47% increased productivity – with an average increase of 20% 2. Attract/Retain the next generation of z/Developers  Easily attained goal 3. Application/Software Modernization  RDz's mature SOA tools, wizards and generators make this aspect of the product a "no-brainer" 4. Cross-platform development using one tool  RDz can provide developers doing both Java and Distributed application work and z/OS development and maintenance a single integrated workbench 5. Code Quality  With 8.x RDz functionality static application scanners and formatting tools available to improve code performance and maintain-ability 6. Development MIPS Reduction  Heavily dependent on usage and architecture  Big numbers more easily achieved if combined with IBM's RD&T offering

15. 15 @ Copyright 2013 - IBM Stakeholder Input and Building High-Level Use Cases for RDz  Developing the RDz "Use Cases"  Various stakeholders in your development organization must provide input into the planning session, in order to create the high-level use cases:  Stakeholder roles include (but are not necessarily limited to):  Management and possibly senior management  DBA and MVS Systems Programmers  Tools Architects  Technical Project Leaders and their developer community  Stakeholder input can be obtained through surveys, or you can reach consensus and obtain input via "JAD" sessions  The research will create high-level RDz Use Cases, which in turn will be used to drive:  The Rollout planning process details  Installation/configuration  Product and plug-in decisions  Workspace customization  Education and mentoring needs  Priorities and emphasis (time management) See slide notes and also the next slide, for sample Use Case research, analysis questions and JAD Session topics

16. 16 @ Copyright 2013 - IBM Planning Session ("A Day in the Life" – Developer Time/Task Analysis) Sample questionnaire for development community:  (In order to fine-tune RDz functionality with the daily projects/tasks of your programming staff) how do you spend their time?  Developing new z/OS functionality  Maintaining existing z/OS application code  z/OS Production Support tasks  Enterprise Modernization projects  Other projects (please list types): _______________________________________  Over the course of a week, what % of your project/task time is spent doing the following: –Analyzing code/Researching/Learning applications and programs: ____ –Editing/developing functionality : ____ –Modifying and maintaining test data (VSAM, QSAM, DB2) : ____ –Unit testing : ____ –Developing/Testing SQL code : ____ –Other (comments, etc) : ____  List 5 REXX or CLIST applications you access – in the order of importance  (Besides accessing: Your SCM, ISPF =1 (browse), =2 (edit), (=3.x) Dataset Utilities, Job Outlist and SPUFI – Please list 5 ISPF tools and/or panels that you use frequently  List 5 DSNs (library names) that contain source code  List 5 DSNs (QSAM dataset names) that you work with  Do you have your compile/build JCL for the Unit Test environment you work in?  How much time have you spent using either Eclipse or other graphical development software?

17. 17 @ Copyright 2013 - IBM Usage Analysis Modeling – Where you plug-in the results of the Survey TaskCommentsTool z/OS Search – for code and data patternsWithin/Across libraries, throughout and across LPARsRDz Remote Search Trivial Source Code Change~Under 5 minutes effortHCE + ISPF editing Minor Source Code Maintenance5 to 60 minutes effortRDz – RSE or SCM integration. Use Retrieve Datasets/Find member Significant Source Code MaintenanceOver 60 minutesRDz – RSE, SCM. Use MVS Subprojects/Filters for repeated tasks Multiple tasks in same program sourceRe-occurring tasks over multiple daysRDz – Add program source to MVS Subproject New program developmentCreate new business logicRDz – Create new from template Program Analysis TasksField expansion, Impact/Data Flow Analysis, Program Discover RDz – Perform Hierarchy,Multiple window views, Program Filters. Control Flow Diagram, Data Element table, Data Flow Analysis techniques, Advanced Search Solution designBusiness computation or algorithmRational Software Architect Scan code for coding standards/best practices Performance and maintainability standardsRDz – Software Analyzer (code review) – or HCE/ISPF/REXX Syntax CheckSyntax errors only (no binary create)RDz – Real Time Validation, Local then Remote Syntax Check Program BuildProcess to create binaries for testingRDz – (if outside of SCM) Generate JCL, else use SCM from RDz or HCE/ISPF panels Promote to Integration Test EnvironmentSCM – integrated with RDz Understand DB2 Data ModelLearn table meta-data, indexes, relationshipsRDz – Overview Diagram Code and test SQL and Stored ProceduresCoding and function test for SQL and Embedded SQLRDz Data Tools Optimize SQL codeAnalyze DB2 path-length to the dataVisual Explain/OPTIM DB2 BIND Create BIND JCL using Menu Manager Browse/Edit VSAM/QSAM Files and Databases Build test cases. View production data for business analysis. Use File Manager or RDz for QSAM files. Use File Manager or Ditto/ESA for VSAM files or 3 rd Party file editing tools Complex VSAM/QSAM File EditingEdit through copybooks. Copy records/rows/segments to create test data subsets, etc File Manager or HCE/ISPF Reoccurring Data File Editing Tasks Add files to RDz MVS SubProject Unit and Integration testingDebugging business functionality during Test phaseRDz with Debug Tool, or Xpeditor/CA-Intertest Solve ABEND in during Testing phaseDebug ABEND in TestRDz with Fault Analyzer– combined with RDz source analysis tools Production ABEND resolutionAnalyze production ABENDFault Analyzer or ABEND-AID – combined with RDz source analysis tools Emergency/hot fix for Production ABENDRequired to restart/run production jobs/transactionsHCE and ISPF Code/maintain JCL, PROCs + control cardsWork with batch job artifacts and Parmlib dataRDz and integrated with JCL Checking products/clists from Menu Manager Job Submission RDz – RSE and the JES job list Create and run one-off utilities through JCLSORT, table UNLOAD, etc.RDz – Menu Manager to file-tailor utilities and make them available from RSE/JES Managing team's batch jobsBatch Job result analysis, re-submit failed jobs, etc.RDz or SDSF accessed from HCE BMS / MFS EditingCreate/Maintain 3270 Green ScreensRDz BMS/MFS Editor – or SDF II accessed via HCE REXX/CLIST-driven function or processJCLCheck, Scan codeHCE until REXX Application is integrated with RDz ISPF Dialog Application or 3 rd Party productCustom ISPF Dialog SystemHCE until REXX Application is integrated with RDz

18. 18 @ Copyright 2013 - IBM Top Down Rollout Pattern "Don't let me catch you using ISPF" "Imperative" model  Works in hierarchical institutions  More prevalent in certain corporate cultures than others  Requires buy-in at all levels of management throughout the organization  Has allowed a few shops to completely un-plug ISPF  Better potential for maximum adoption  Can engender push-back from developers who are resistant to change

19. 19 @ Copyright 2013 - IBM Bottom-up Rollout Pattern "Dude… when did you start coding Java?"  Viral "street-cred" model - Interest in RDz developed organically, from within the development community  Rollouts occur in phases:  Build initial base of enthusiasts: –"Early Adopters" interested in leading-edge technologies –Millenials (aka "20-somethings")  Technical credibility of RDz as a superior development solution and enthusiasm of users leads to word-of-mouth marketing from within the organization  Interpersonal "buzz" generated, leads to more individuals wanting RDz –Which accelerates rollout and adoption  Requires communication and marketing vehicle to leverage and communicate success  Effective antidote for traditional developer resistance-to-change, but:  Assumes the kind of "cooperative" development environment and company culture that is conducive to this approach

20. 20 @ Copyright 2013 - IBM Bottom-up or Top-down Rollout Pattern (Review)  Depends on (analyze your):  Your adoption rate target/goals  Top-down more likely to hit high usage %  Executive/Management/Developer culture  How effective are "mandates" with new products and technology initiatives at your shop?  Technical project management/and team leads must be "bought-in"  How much effort you want to spend on rolling out transformative technology:  Top-down requires more planning and resource dedication  Bottom-up feeds off of and requires interactive "connected" developer/development teams  Team demographics and usage/task analysis:  How likely is it that a 35 year TSO/ISPF veteran, who does primarily systems analysis and is 6 months away from retirement will want to adopt a GUI IDE? Key Consideration:  Because adopting RDz as a replacement for ISPF is as much (if not more) an emotional issue than a technical challenge, a certain level of executive sponsorship is essential to the Rollout project's success

21. 21 @ Copyright 2013 - IBM Sample Rollout Project Timeline – 8 Week Scope – High-Level Project Planning, Project Management, Project Monitoring, Rollout Evaluation Criteria RDz Server Install/Configure/Tune RDz Client Installation Custom Workspace Rollout Begins Continuous Monitoring Refinement Maintenance RDz/SCM Integration ISPF/z/OS CLIST/REXX Integration Usage Model Surveys All times hypothetical Center of Excellence Review Revise Refine Prototype Training Customized Education

22. 22 @ Copyright 2013 - IBM 2. RDz z/OS Server Installation, Verification, Optimization  Poor RDz z/OS server installation, configuration and tuning can cause response-time issues  This is absolutely avoidable – but requires the involvement of:  IBM technical support + your MVS Systems Programming staff  Be sure to have your Sysprogs research the following documentation:  The RDz install and configuration library: –http://www-01.ibm.com/software/rational/products/developer/systemz/library/index.html#pd-v803http://www-01.ibm.com/software/rational/products/developer/systemz/library/index.html#pd-v803  ISPF Configuration – an ISPF dialog that walks your MVS Systems Programmers through the install/customization steps –http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC14-7282-02http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC14-7282-02  IBM can provide  RDz server tuning assistance and advice  Checklists in the form of spreadsheets – "Server Health Check"  Level 2 Support for mentoring and guidance  Sample server installation/optimization "Best Practices" and considerations  Whether SSL-level encryption is needed  Stress test/Monitor and optimize the server  You may need to: –Bump the priority of RSE job – especially in a CPU-constrained environment –Configure Workload Manager settings for the server  Allocate enough real memory and Java Heap size  Double-check the ISPF Gateway configuration through RDz/RSE usage  RDz makes effective use of zAAP and zIIP technology – which can help lower costs and improve performance

23. 23 @ Copyright 2013 - IBM 3. SCM Integration  T he vast majority of z/OS development shops are heavily dependent on SCM utilization. And programmers access the SCM seemingly on anywhere from an occasional to an hourly basis  SCM software routinely used in:  Source control  Version management  Build process management  Dependency checking and simple forms of code analysis  Integrating with a shop's SCM is a make-or-break aspect of a Rollout  Need (full-function) industrial-strength solution:  Access for developers to complete usage model  Maintenance plans for next-version releases of: RDz, SCM  No additional superfluous tasks/steps should be required to access from RDz  A qualified SCM technical person needs to participate in the SCM Integration phase  Your approach to SCM/RDz integration will take into account:  SCM product-specific  Access (usage model) specific  How heavily do your developers utilize the native SCM tooling during the SDLC? Develop Test Access

24. 24 @ Copyright 2013 - IBM CA-Endevor Integration  Several approaches:  CARMA/RAM – simple/effective approach to Endevor Integration  Documentation at:  http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC23-7660-05 http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC23-7660-05  Requires:  CA-Endevor systems experience: –Knowledge of: –API set –Libraries and datasets – Usage model (what in-the-box and customized use cases are employed) –Skills and authorization  CARMA framework: –Development skills –Experience with the framework  Q-Group solutions for integration:  CSAR – proprietary framework that extends the CARMA framework  http://www.qgrp.com/index.php?show=produkte&id=1&detail=endevor http://www.qgrp.com/index.php?show=produkte&id=1&detail=endevor  Menu Manager  Requires: –Menu Manager coding – see document: xxx –REXX or CLIST coding – see IBM manuals: xxx Develop Test Access

25. 25 @ Copyright 2013 - IBM Serena Changeman Integration Changeman/RDz integration options: 1.Serena plug-ins + Vendor-provided integration - RDz release-dependent - Not free - Managing issues can lead to the infamous "corporate salute" 2.Menu Manager + Quick way to get integrate with RDz - Requires custom REXX/CLIST coding on the host 3.CARMA with Dynamic RAM + Quick way to get Check-in/Check-out, Promote, Build + All efforts are strategic value - May need custom UI enhancements 4.CARMA Custom RAM + All custom, matches what you need - Takes time and investment to develop custom RAM and UI 5.Integration Framework-from IBM or Q-Group: http://qgrp.com/english/products/csar-for-changeman/ http://qgrp.com/english/products/csar-for-changeman/ + Turnkey solution - Purchased product Develop Test Access See Slide Notes - on Dynamic vs. Custom RAM

26. 26 @ Copyright 2013 - IBM RTC Integration – 1 of 2  Use RTC integration to support SDLC best practices:  Workspace management  Asset management and control  Management of build, promote, deploy  Workflow and approvals management  Workspace management and control  RDz workspace is populated from RTC streams  Asset management and control  Deliver updates from RDz workspace to RTC streams  Repository and stream design critical to success – Factors are:  Architecture  Organizational structure  Asset ownership and usage patterns  Interaction (if any) with CARMA repositories, ie CA-Endevor Develop Test Access

27. 27 @ Copyright 2013 - IBM RTC Integration – 2 of 2  Management of build, promote, deploy  Implementing RTC build definitions  Reuse existing scripts?  Coordination with off-host (distributed) components  Workflow and approvals management  Use RTC's process templates to implement workflows and approvals  Define users, roles  Define lifecycle states, transitions, sign-offs  RTC Implementation  Determine location of RTC source code repository  Identify target environments, install RTC build agents as needed  Implement/deploy process template  Populate repository, implement stream structure  No additional work effort to integrate RTC  No additional work effort to integrate RTC (just change perspectives between Work Items and z/OS Projects)  The actual work is in populating your RDz workspace from the RTC stream Develop Test Access

28. 28 @ Copyright 2013 - IBM RDz & SCLM Developer Toolkit integration  Eclipse-based view of SCLM repository including:  SCLM-specific environment  SCLM views providing a tree- based list of:  groups  types  members  audit/version information  Wizards for performing common SCM operations  Store COBOL, PL/I, Java, Web service artifacts, documents, spreadsheets, etc. into SCLM  SCLM accounting information available via properties page and via SCLM Status function  Integration with RDz syntax check, content assist, and error feedback mechanism  SCLM managed build and deployment services Develop Test Access

29. 29 @ Copyright 2013 - IBM RDz/SCLM DT Install/Configuration and Documentation  RDz client install –  Configuration requirements  SCLM Developer Toolkit configuration required on the RDz server side....the steps are documented in the RDz Host Configuration Guide, (Chapter 4, for v8.0.3)...(Optional) SCLM Developer Toolkit.  SCLM Developer Toolkit viewlets  Overview of many SCLM DT features  http://publib.boulder.ibm.com/infocenter/ieduasst/rtnv1r0/topic/com.ibm.iea.rdz /rdz/7.6z/SCLMDT.html?dmuid=20100827150518078212  SCLM DT usability enhancements in RDz V8.0.1  http://publib.boulder.ibm.com/infocenter/ieduasst/rtnv1r0/topic/com.ibm.iea.rdz /rdz/8.0.1z/SCLMDT.html?dmuid=20101118160124549007 Develop Test Access

30. 30 @ Copyright 2013 - IBM Panvalet/Librarian Integration  Can integrate through simple process that can be called from RDz using Menu Manager, CARMA framework, or Q-Group (proprietary) framework  Menu Manager solution requires:  Menu Manager coding skills (easy)  REXX or CLIST coding  Knowledge of the APIs or CLIST/REXX execs used to access Panvalet/Librarian  CARMA Framework:  Can create RAM for Librarian/Panvalet usage  Q-Group solutions for integration:  CSAR – proprietary framework  http://www.qgrp.com/index.php?show=produkte&id=1&detail=endevor http://www.qgrp.com/index.php?show=produkte&id=1&detail=endevor Develop Test Access

31. 31 @ Copyright 2013 - IBM 4a. Additional z/OS Green-Screen Tools Integration  Considerations:  All shops implement a (usually) large # of CLISTS, REXX Execs, custom ISPF Dialog Manager, and 3 rd party tools to implement lifecycle coverage for things like JCL scanning, adherence to standards, etc.  There are four ways to provide integration with these tools: 1.Menu Manager: –For simple CLISTS and REXX execs, you can usually integrate them with RDz easily through Menu Manager 2.HATS/RCP: –For multi-step (conversational) CLISTS and REXX execs – and for ISPF Dialog Manager and 3 rd party applications and tools you can use HATS/RCP – a screen-scraping product from IBM that is free for developing integration points, with RDz. 3.CARMA: –CARMA provides a generic interface to z/OS software which can be used to access REXX and CLIST applications 4.Java eclipse plug-ins: –Java eclipse plug-ins can be used to freely integrate with remote Resource APIs (RSE) to do almost anything Develop Test Access

32. 32 @ Copyright 2013 - IBM 4b. Green Screen Application Integration  Solution Design for "conversational CLIST/REXX execs" and ISPF-based tools  It is important to survey developers to find and prioritize requirements for integration with critical z/OS Green-Screen functionality unique to your company's SDLC and ISPF-based toolset (but not supported in RDz out-of-the-box solutions)  When you have compiled such a list:  Menu Manager  Menu Manager can be effective for providing access to "single round-trip" (request/response) functionality –Easy to build/test through a simple scripting language –Easy to deploy  HATS  HATS is the preferred (most cost-effective) method for supporting: –Conversational (multi-step) CLIST/REXX execs –ISPF-based tooling, such as custom Dialog Manager applications and/or 3 rd Party products  Because HATS generates "rich-client" (RCP) plug-ins and because these must be deployed through an RDz installation process, you are best served to minimize the number and frequency of HATS plug-ins needed: –Create a REXX/Dialog Manager menu on z/OS that consolidates key ISPF-based functionality –Do as much error and exception handling in the REXX/Dialog Manager application to: - Minimize the need for HATS exception handling - Maximize the extensibility of the REXX/Dialog Manager application, to add new functions –Screen-scrape the REXX/Dialog Manager application with HATS and generate an RCP –Create a Menu Manager access to the HATS/RCP application – for consistent RDz U.I. and Context menu functionality Develop Test Access

33. 33 @ Copyright 2013 - IBM 5. Client Software Rollout – Installation Considerations:  Start by creating a "prototype workbench" consisting of standard hardware, your corporate desktop image and including, a custom workspace (next topic), the RDz client software and:  Additional eclipse plug-ins on top of the RDz base:  Custom HATS/RCP plug-ins, RAAi, PD Tools plug-ins: (File Manager, DTCN, APA), Compuware plug-ins, CA-Easytrieve editor, etc.  Custom JDBC drivers:  IMS Universal Driver, CA-IDMS, CA-Datacom, other relational database systems  Additional products:  Rational Team Concert  Rational Software Architect  Rational Functional/Performance Tester  Rational Business Developer (EGL)  TXSeries for Multi-platforms (CICS)  IBM DB2 Workgroup Edition (DB2/UDB) Note TXSeries and UDB are required if developers wish to use: –RDz Local Syntax Check capability of RDz –Local DB2/SQL development (leads to additional MIPS reduction)  Additional considerations include how to automate/manage RDz base install rollout and maintenance:  Packaged Install  Silent install vs. Installation Manager See Slide Notes for Client Tuning Recommendations

34. 34 @ Copyright 2013 - IBM 6. Workspace Customization and Management  Analyze elements of custom workspace:  Configurations/preferences (~60) for:  Connections  Filters  Menu Manager scripts & custom Context Menu options  z/OS File System Mapping and Property Groups  Custom JDBC driver preferences  Preferences –Editor – and many editor preferences, –Language features, preferences and options, –Reusable code options, RSE behavior, DB2/SQL, –Overall workbench options (colors, hot-key and editor mapping), etc  Training artifacts  Post-training support/mentoring/knowledge acquisition  Approach to automating configuration management:  Push to Client – esp. powerful in 8.0.3 and later  Custom workspace See Slide Notes

35. 35 @ Copyright 2013 - IBM 7. Knowledge Transfer – Part 1: Training First impressions are critically important in the adoption of any transformative technology Key aspects include: 1.Motivation 2.Relevance 3.Education effectiveness Motivation:  Change (Adoption) happens when professionals are convinced that new technology will make their jobs easier – see slide notes:  The job of convincing is a uniquely human endeavor  Quality training  Introduces/sells change  Builds the onramp for the transition from green-screen to RDz Lesson Learned: Lesson Learned: Passive (documentation) – or video-based learning has a poor track record when it comes to successful technology adoption

36. 36 @ Copyright 2013 - IBM 7. Training – Overview  Product training scope:  RDz and plug-ins +  SCM Integration +  Other products in the workbench RAA, RTC, RD&T, etc.  Business/Application development constraints:  Time away from task  Classroom / Remote (travel)  Geography and languages (both written and verbal) for education delivery  Training approaches:  Vendor-led:  Traditional classroom instruction and F2F mentoring  Remote training and remote mentoring  Self-service education - product documentation and web-based content  Only effective as review/look-up knowledge transfer  Internally developed/delivered education - for In-house RDz training programs

37. 37 @ Copyright 2013 - IBM 7. Training – In-house Training Considerations  Why in-house training?  Cost savings  Multi-national language requirements and geography proximity  Application/SDLC practices and familiarity  Control over content and delivery  Why not in-house training?  You cannot expect professional software developers to become effective technical trainers without a high-quality Train-the-Trainer program tailored to the requirements RDz education:  Classroom teachers go through 4 years of undergraduate study, including a 6+ month supervised teaching apprenticeship – and then do graduate-level "teacher effectiveness" training.  RDz training layers additional requirements on top of this (next slide)  Then there's the cost of building up and maintaining a quality RDz curriculum:  Slideware, workshops, additional collateral such as: samples, workspaces, etc.  Best Practice Train-the-Trainer programs for In-house RDz education: An effective in-house RDz training program is a complex undertaking… Get a guide  Look for a professional/qualified RDz Train-the-Trainer program in order to maximize your investment in people and in the product. ?

38. 38 @ Copyright 2013 - IBM 7. Training – Considerations for Train-the-Trainer Programs  Program should start by analyzing your RDz Rollout:  Requirements, constraints, limitations, challenges and expectations ……..Starting top down from the business problem you're solving with RDz  Your vendor should provide (as part of a Train-the-Trainer program):  High quality courseware:  Slides, workshops and post-education/review artifacts  Comprehensive instructor guides  Capabilities for cost-effective courseware/content and training customization  Training that is based on "best practices"  Centered on SCM-Workflow integration  Stakeholder variants  Flexibility necessary to help you with any unique requirements:  Coverage of RDz technology features – programming languages – including any plug-in training  Geography-specific interests  Training modes - F2F vs. Remote, self-study, etc.  Additionally Train-the-Trainer programs will offer formal assistance in:  Candidate assessment  Presentation/teaching and mentoring effectiveness training  RDz technical subjects:  Baseline product knowledge transfer  Advanced training  RDz continuous education – how to become an expert  Courseware modification and maintenance  Some vendors can provide a cloud-based learning environment

39. 39 @ Copyright 2013 - IBM 7. Training – Considerations for traditional product training  Besides standard RDz curriculum (next slide) consider: 1.SCM integration/development workflow 2.Subjects – based on your business reason for purchasing RDz 3.Custom workspace, workbench products and client plug-ins and configuration 4.z/OS green-screen tool integration  Considerations for customized education:  How are you going to create content?  And manage the content year-over-year to take advantage of new:  RDz releases  SCM and plug-in releases  CLIST/REXX integration through Menu Manager or HATS  Products added to the workbench  Are you in the RDz technical education business? Key consideration for customized training:  If your SCM/editing workflow is continual – where developers spend multiple hours/per day working within or under the control of your SCM software you will want a fully customized curriculum, with a heavy emphasis on SCM workflow that mirrors current developer habits  If your SCM/editing workflow is sporadic – where developers check source code out of the SCM and work on it within a "Sandbox" PDS environment you have more flexibility with the training approach: SCM-oriented vs. "native RDz" content

40. 40 @ Copyright 2013 - IBM 7. Training – Best Practice Details  Standard curriculum – foundation/essential training topics:  Eclipse  SCM integration  "Native RDz" education to cover the breadth/scope of "a day in the life" for developers:  Analysis tooling - Editing/Syntax Check - Code Quality tooling  z/OS Access tooling – Remote Systems Explorer and MVS Subprojects  Data Tools – for IMS and DB2  Web Services  Additional options: –BMS and MFS map editors –Plug-ins such as: File Manager, Fault Analyzer and any of your custom functionality (JCL checking tools, etc.)  Consider stakeholder needs with focused classes that :  Programmer/Analysts … vs … Application Analysts  Start every class with a short, high-quality product demonstration that provides:  Level-setting/Terms & Concepts  Motivation  Key recommendation:  RDz ships with a quality 3270-emulator, which is used by RDz developers to access ISPF-based functionality not yet integrated with RDz  Consider removing/returning your existing emulator – so that your developers utilize the RDz-packaged functionality

41. 41 @ Copyright 2013 - IBM Education Effectiveness – Teaching RDz z/OS Subject Matter Expert RDz Technical Expert Presentation Skills Adult Learning Expert Who you're looking for in an RDz trainer

42. 42 @ Copyright 2013 - IBM 8. Knowledge Transfer – Part 2: Mentoring/Post-Training Follow-up  After RDz training finishes, it is crucial to provide new RDz developers with "on-ramp period " to assimilate new the new tools, processes and techniques  Project managers must:  Allow for some minimum amount of time to assimilate the new tooling  Encourage developers to make the investment in RDz  Best practice for experienced z/OS personnel is to have provide on-site/in- person mentoring immediately following each training class  Key to success for  F2F is best – but remote works with 2-way screen sharing technology  While a less obvious need than classroom teaching, quality mentors don't just spontaneously combust (you need to cultivate and develop them) Considerations for post-training mentoring/support:  Pro-active:  Scheduled follow-up with new RDz users  Short-term:  Defined period of time post-training for new users – example: Mentoring to be available for 2 weeks  Real-world mentoring:  Expert "over-the-shoulder" help while working on real (company) software tasks and requirements

43. 43 @ Copyright 2013 - IBM 9. Knowledge Transfer – Part 3: Building a Center of Excellence Post mentoring there is a need for long-term on-demand technical assistance that Post mentoring there is a need for long-term on-demand technical assistance that:  Provides experienced RDz developers with technical help for advanced topics and advanced RDz development techniques that are outside the scope of initial training  Lowers the initial on-ramp costs of education and mentoring Recommendations for building a center of excellence:  Create a search-able learning portal – basically a library of learning tools integrated into a custom RDz workspace, that aggregates:  Internal standards and best-practices  FAQs  How-to help  Can include:  Search facility  Static textual help  Hyper-links to:  Internal documents  Classroom content  Web-based learning

44. 44 @ Copyright 2013 - IBM 9. Center of Excellence (Automated Help System)  Here is a sample JavaScript tree control-style help system you could build with EGL, or some other simple web-app technology, that you could install on an internal intranet application – with links to specific documents and other RDz artifacts:   - RDz FAQ at Acme Corp.   - IBM product help  - Links to IBM InfoCenter  - Links to RDz Forum  - Links to RDz Collaboration Community  - IBM Request for Enhancements   - Links to obtain custom workspaces   - Install product and plug-in updates   - Technical Topics  - RDz Search and Analysis topics  - Coding and Build  - Testing with RDz  - DB2 and SQL Development  - Creating and Testing Web Services  - Internal RDz standards and procedures  - Internal Best Practices  - Client Configuration Connection Details  - Request Mentoring Assistance

45. 45 @ Copyright 2013 - IBM RDz Local Workstation Project – Used as Mentoring/Support Portal IBM can provide a comprehensive set of folders that can be imported into a Local Workstation Project – and provide:  RDz technical help  Powerpoints  Topic-based help  Usage Best Practices  Links to web resources  General z/OS technical help and education  Corporate Information Systems resource links

46. 46 @ Copyright 2013 - IBM The Importance of Expert Services As part of this and especially after the rollout it will help to have access to some level of expert RDz technical services:  To assist with many deep/technical project tasks  Create and plug-ins for z/OS custom software  Build Menu Manager scripts for CLIST/REXX execs  Optimize the RDz client or server image  To provide Face-to-Face  Custom training  Mentoring – post training  Helping to setup and hand over a Center of Excellence  There are a number of qualified RDz technical consulting companies in each geography  Your IBM account team can discuss options with you for obtaining skilled consultants

47. 47 @ Copyright 2013 - IBM 10. Momentum Building  RDz adoption will occur organically when developers within your organization start demanding the product based on:  Word-of-mouth testimonials  Watching other developer's success  This is actually the concept behind the "Bottom Up" Rollout pattern  In order to focus attention on your progress/achievement, and build "street cred", many shops have utilized:  Internal User Groups  Lunch & Learns  Newsletters  eMails – that communicate successes, tips & techniques, testimonials, how to obtain RDz, class enrollment schedules, where to go to get help  Announcements of IBM/RDz events (see next slide)

48. 48 @ Copyright 2013 - IBM 10. Momentum Building – You are not alone – the IBM no-charge events  RDz User Group meetings:  Virtual (web-conference-based)  The North American and European Annual User Group meeting sponsored by development  Special programs such as "The RDz Dr. is In"  Scheduled and on-demand briefings from your IBM account team  Advanced RDz Education:  Scheduled sessions where developers could ask questions throughout - or surface problems they're having  Here is an example of advanced training topics, delivered to organizations in the past:  RDz Editing productivity tips & techniques  Advanced Search techniques  RDz Configuration - Property Groups, Preferences and Mapping Datasets and PDS members  Advanced Source code analysis features and techniques  RDz and code reuse options (Statement and program templates and Snippets)  Advanced Debugging techniques (with Debug tool)  Advanced DB2 and SQL development  RDz Application code quality features  The COBOL and PL/I Editors  Working with Assembler code  Using Menu Manager to implement ISPF "COPY" and other commands  RDz Forum – for "one-off" technical questions: http://www.ibm.com/developerworks/forums/forum.jspa?forumID=1131&start=0 http://www.ibm.com/developerworks/forums/forum.jspa?forumID=1131&start=0

49. 49 @ Copyright 2013 - IBM 11. ROI Measurement – 1 of 2  Measurements include:  Productivity:  Code – Function points delivered  Influenced by quality of Rollout – especially training/mentoring/quality of workspace  Quality:  Percentage of defects reduced using RDz  Cost:  Development MIPS offloaded –Highly dependent on product usage model  Three approaches:  Subjective:  Surveys with RDz users on their experiences  Relative ratings of RDz and ISPF functionality (see spreadsheet)  Objective:  Obtaining electronically produced logging information, TSO charges, etc.  Or audit information (Data Center ABENDs etc.)  Benchmarking:  Do "apples-to-apples" research, filtering out human factors such as typing speed, learning curve, experience, etc.

50. 50 @ Copyright 2013 - IBM 11. ROI Measurement – 2 of 2 Considerations:  What are you comparing? Do you have historical data? How accurate (how was it derived)?  "Apples to Apples" comparisons are very difficult to perform  Considerable on-ramp time  Can use IBM's Benchmark scripts and code (but still requires full-time execution)  Relative measures: See PoC Evaluation matrix  Measured Improvement statistics gathering will show different tasks being performed RDz_Metrics.xml … \workspace\.metadata Usage Metrics

51. 51 @ Copyright 2013 - IBM 12. Lessons Learned  If you document the process, your experience successfully rolling out a transformative development platform (RDz) will provide a spring board for future growth and allow you to take advantage of:  Innovate software solutions  Process solutions  No one ever said that being an agent of change is easy  But consider the alternative

52. ® IBM Software Group © 2012 IBM Corporation Back up slides - RDz Training – Detailed Considerations - Additional Best Practices (lists)

53. 53 @ Copyright 2013 - IBM Additional Training Considerations – 1 of n How much training is necessary? Eclipse or developers with distributed background: 16 hours Traditional (veteran) ISPF developers: 24 hours How to deliver: On-site/Classroom training is best Remote/Instructor-led training can work Minimal/recording-based training does not work Recall that, RDz education is primarily the overcoming of resistance and fear (of "new") – RDz is

54. 54 @ Copyright 2013 - IBM Brad's Keys to Success List 1.Define formal success criteria for the implementation. 2.Ensure that each new group of RDz users includes at least one RDz champion. 3.Keep the entire development staff informed early and often. 4.Select a subset of RDz features to implement initially. 5.Include a mainframe systems administrator on the implementation team. 6.Implement the tuning recommendations in the RDz Host Configuration Reference 7.Include a desktop support person on the implementation team. 8.Ensure that all teams are adequately trained. 9.Offer additional training and mentoring to long time “green screen” developers. 10. Prepare for opposition from “green screen” advocates. 11. Select staff that is not on mission-critical projects to be the first adopters. 12. Conduct regular status reviews during the first few weeks of the implementation for the first adopters. 13. Conduct a formal technical review after a short period of usage by the first adopters. 14. Conduct a formal business review after a short period of usage by the second wave of adopters. 15. Form a partnership with IBM for the implementation. 16. Designate someone on the implementation team to be the primary point of contact for the RDz user community.

55. 55 @ Copyright 2013 - IBM Editing  Check Out function provides an SCLM Check-out service for selected member. Workstation tools can then be used on it.  SCLM member contents are copied to workstation and are edited locally. However the member is locked in SCLM to stop other users editing it  Associating the SCLM language type to an appropriate file extension, allows the file to be opened in preferred editors. For example, COBOL files in RDz LPEX, BMS maps in the RDz BMS map editor, spreadsheets and documents in office editors, etc.  Content assist, Open/browse copybook, and ‘Real-time’ syntax check from SCLM edit session  Dependency time-stamp checking  Allow submission of long running tasks to be executed in background for refresh dependencies, remote and local syntax check  Check In copies edited files back to SCLM and release the locks on the members  Update Member information such as Change Code, Language and authcode is also provided. Similar to SPROF in SCLM

56. 56 @ Copyright 2013 - IBM Building and Promoting  Build/Promote services provided in SCLM DT can be invoked either on-line or in batch mode  Both services offer the same functionality as the ISPF SCLM functions  Batch operations enable user to execute long running SCLM processes independent of Eclipse  Monitor jobs using the RSE job monitor.  Operations Log  Logs every operation, providing a useful diagnostic tool  Log data is stored chronologically and may be stored for future examination and cleared manually or automatically.  The SCLM View is updated with each SCLM operation  The SCLM View, following a successful promote, will be updated and the member moved to the next group level  When a member from a higher level group is selected for editing it will be moved down to the user’s development group  Build errors shown in RDz Remote Error List  SCLM language translators can be configured to specify that the SCLM Build return error feedback information, populated in the Remote Error List and double clicking on the error highlights the line in error.

57. 57 @ Copyright 2013 - IBM Usage Analysis Modeling – Time (?) TaskTool Task under 5 minutesEmulator or HCE Tasks 5  20 minutesEmulator/HCE or RDz – if RDz is already launched Tasks  20 minutesRDz Tasks not supported by RDz – at current level of z/OS Integration Emulator or HCE

58. 58 @ Copyright 2013 - IBM Audit, Versioning, Database Utility Report, Search, etc.  Full Audit/Versioning similar to option 3.8 in SCLM  Context-sensitive menus show Audit and Version options  Browse, Delete, Recover versions plus view deleted versions and version history  Compare with latest version in SCLM and compare with another version  SCLM Search support  SCLM Database Utility (DBUTIL function) is also available, SCLM option 3.4  Build Forge and SCLM integration and support

59. 59 @ Copyright 2013 - IBM 59 Common Access Host Repository Manager (CARMA) (used for the framework for other mainframe SCM and Endevor) Distributed Client (Windows) RDz CARMA GUI GUI z/OS CARMAmodelCARMAmodel TransportLayerTransportLayer CARMA-390CARMA-390 PDS SCLM Changeman Host Tooling Host Tooling RSE RAM RAM = Repository Access Manager CARMA provides a generic interface to z/OS software configuration managers (SCMs) Customers can leverage a set of APIs (along with samples) to access their SCM on Rational Developer for System z.

60. 60 @ Copyright 2013 - IBM Dynamic RAM  Access to the Changeman interfaces  JCL procedures  REXX execs and CLISTs  Integrate with RDz  Dynamic-Ram links users actions to appropriate JCL or Rexx  End user experience  CARMA UI exists for:  Check out to RDz  Check in from RDz to Changeman  Trigger a Changeman build  Promote in Changeman  Add something to Changeman

61. 61 @ Copyright 2013 - IBM Serena with RDz

62. 62 @ Copyright 2013 - IBM Training constructs?  Simple answer – better training materials + quality post-class mentoring  Deep and engaging workshops  Customized to your environment – and to your rollout: –Customized configuration –SCM integration –Access to additional z/OS resources (CLISTs, REXX Execs, etc.) –Libraries/Programs/JCL/etc.  Can use: Snippets, Templates, etc. to simplify management ~70% workshop and only 30% lecture/demo  As a "windows/GUI-technology" learning domain, RDz training should be ~70% workshop and only 30% lecture/demo  Having high-quality training workshops will:  Improve the quality of the course and substantially improve the training efficiency – measured by retention and application  Take the pressure off of your instructors – in the classroom  Provide your shop with "How to" guides downstream