®
IBM Software Group
Rational Developer for System z
Rollout Best Practices
Jon Sayles, IBM/Rational
July, 2016
© 2016 IBM Corporation
IBM Trademarks and Copyrights

© Copyright IBM Corporation 2013, 2014, 2015, 2016. 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.
@ Copyright 2016 - IBM
2
Course Contributing Authors

Thanks to the following individuals, for assisting with this course:
 David M Bean/IBM Rational
 David Lawrence
 Brad Adams/IBM Rational
@ Copyright 2016 - IBM
3
Agenda
 Executive Summary
 The Rollout Project (detailed):
 Stages
 Detailed 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
@ Copyright 2016 - IBM
4
UNIT
RDz Rollout Best Practices
Topics:
 Executive Summary
 The Rollout Project (Details)
 Back-up slides
@ Copyright 2016 - IBM
5
Where is the “Bar” Set? (What level of ROI do you want?)
ROI Reached (Product/Development techniques mastered.
Measured improvement of Business Value)
Product Adopted - majority of developers use
RDz for the majority of their day
Users formally trained
RDz deployed to users workstations
RDz installed and working - client and server
@ Copyright 2016 - IBM
6
The Problem
 You want this 
 Magnitude of order
productivity boost using
RDz (7.6 no less) as
opposed to ISPF 6.0
However:
The above results are statistically significant for these seven Use Cases
 But your developers do a lot more every day than what’s been measured
 Because:
Your mainframe system is:
 Complex and unique
– A “closed system” supported by a blend of green-screen tools and dev-processes
These development processes and tools are:
 Unique to your shop
 And built up from decades of expensive lessons-learned
Your developers are (after all) Mainframe developers
 So - in order to realize a high R.O.I. you'll need to plan and execute a
professional rollout that takes four areas into consideration…
@ Copyright 2016 - IBM
7
Adoption Keys to Success
All four areas must be
addressed, in order to roll
RDz out successfully
Executive Mandate and
Project management
Buy-in
Strong Technical
RDz Project Lead
Highest
Adoption
%
Removal of
Technical
Barriers
Before the
User Rollout
High-Quality
Knowledge Transfer
Training + Mentoring
@ Copyright 2016 - IBM
8
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
@ Copyright 2016 - IBM
9
Breaking out the Technical and Human Factors Requirements
Developer transition experience
RDz Server - installation/configuration
Access
Develop
Test
Developer Workflow
Functionality Coverage
RDz Client - installation/configuration
@ Copyright 2016 - IBM
10
Rollout Project – Time and Resource Allocation
This chart represents the
general importance – in
terms of time and resource
commitment to the various
phases of a 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.
35%
Post-training
mentoring
assistance and
self-service
technical help
systems
 For example, even though
Product Education
represents only 30% in
terms of how much time to
allocate to it – without
quality RDz training your
rollout can fail.
@ Copyright 2016 - IBM
30%
Product
Education
(Training)
11
35%
Planning,
Installation,
Configuration,
Optimization,
Integration
with your z/OS
processes
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
@ Copyright 2016 - IBM
12
UNIT
RDz Rollout Best Practices
Topics:
 Executive Summary
 The Rollout Project (Details)
 Back-up slides
@ Copyright 2016 - IBM
13
First Question on RDz Usage
 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
@ Copyright 2016 - IBM
14
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 2nd group:

"New == Unproven" demographic is (most likely) the silent majority of
your mainframe developers
 We address their concerns through best-practices and empiricallyproven methods (see slide notes)
@ Copyright 2016 - IBM
15
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
@ Copyright 2016 - IBM
16
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
@ Copyright 2016 - IBM
17
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
@ Copyright 2016 - IBM
18
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)
@ Copyright 2016 - IBM
19
See slide notes and also
the next slide, for sample
Use Case research,
analysis questions and
JAD Session topics
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?
@ Copyright 2016 - IBM
20
Usage Analysis Modeling – Where you plug-in the results of the Survey
Task
Comments
Tool
z/OS Search – for code and data patterns
Within/Across libraries, throughout and across LPARs
RDz Remote Search
Trivial Source Code Change
~Under 5 minutes effort
HCE + ISPF editing
Minor Source Code Maintenance
5 to 60 minutes effort
RDz – RSE or SCM integration. Use Retrieve Datasets/Find member
Significant Source Code Maintenance
Over 60 minutes
RDz – RSE, SCM. Use MVS Subprojects/Filters for repeated tasks
Multiple tasks in same program source
Re-occurring tasks over multiple days
RDz – Add program source to MVS Subproject
New program development
Create new business logic
RDz – Create new from template
Program Analysis Tasks
Field 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 design
Business computation or algorithm
Rational Software Architect
Scan code for coding standards/best
practices
Performance and maintainability standards
RDz – Software Analyzer (code review) – or HCE/ISPF/REXX
Syntax Check
Syntax errors only (no binary create)
RDz – Real Time Validation, Local then Remote Syntax Check
Program Build
Process to create binaries for testing
RDz – (if outside of SCM) Generate JCL, else use SCM from RDz or HCE/ISPF panels)
SCM – integrated with RDz
Promote to Integration Test Environment
Understand DB2 Data Model
Learn table meta-data, indexes, relationships
RDz – Overview Diagram
Code and test SQL and Stored Procedures
Coding and function test for SQL and Embedded SQL
RDz Data Tools
Optimize SQL code
Analyze DB2 path-length to the data
Visual Explain/OPTIM
DB2 BIND
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 3rd Party file editing tools
Complex VSAM/QSAM File Editing
Edit through copybooks. Copy records/rows/segments
to create test data subsets, etc
File Manager or HCE/ISPF
Reoccurring Data File Editing Tasks
Reoccurring Data File Editing Tasks
Add files to RDz MVS SubProject
Unit and Integration testing
Debugging business functionality during Test phase
RDz with Debug Tool, or Xpeditor/CA-Intertest
Solve ABEND in during Testing phase
Debug ABEND in Test
RDz with Fault Analyzer– combined with RDz source analysis tools
Production ABEND resolution
Analyze production ABEND
Fault Analyzer or ABEND-AID – combined with RDz source analysis tools
Emergency/hot fix for Production ABEND
Required to restart/run production jobs/transactions
HCE and ISPF
Code/maintain JCL, PROCs + control cards
Work with batch job artifacts and Parmlib data
RDz and integrated with JCL Checking products/clists from Menu Manager
Job Submission
Job Submission
RDz – RSE and the JES job list
Create and run one-off utilities through JCL
SORT, table UNLOAD, etc.
RDz – Menu Manager to file-tailor utilities and make them available from RSE/JES
Managing team's batch jobs
Batch Job result analysis, re-submit failed jobs, etc.
RDz or SDSF accessed from HCE
BMS
/ MFS Editing
@ Copyright
2016 - IBM
Create/Maintain 3270 Green Screens
RDz BMS/MFS Editor – or SDF II accessed via HCE
21
Top Down Rollout Pattern
“You were using ISPF weren’t you!?"
"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
@ Copyright 2016 - IBM
22
Bottom-up Rollout Pattern
“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
@ Copyright 2016 - IBM
23
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
@ Copyright 2016 - IBM
24
Sample Rollout Project Timeline – 8 Week Scope – High-Level
Project Planning, Project Management, Project Monitoring, Rollout Evaluation Criteria
Usage Model Surveys
RDz Server Install/Configure/Tune
RDz/SCM Integration
RDz Client Installation
ISPF/z/OS CLIST/REXX Integration
Custom Workspace
Customized Education
Center of Excellence
Prototype
Training
Review Revise
Refine
Plan Mentoring
support
Rollout
Begins
All times hypothetical
@ Copyright 2016 - IBM
25
Continuous
Monitoring
Refinement
Maintenance
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-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-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 – see Slide Notes for details on what to include.
 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
@ Copyright 2016 - IBM
26
3. SCM Integration
Access
Develop
 The 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:
Test
 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?
@ Copyright 2016 - IBM
27
CA-Endevor Integration
Access
 Several approaches:
Develop
Test
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
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
Menu Manager
 Requires:
– Menu Manager coding – see document: xxx
– REXX or CLIST coding – see IBM manuals: xxx
@ Copyright 2016 - IBM
28
Serena Changeman Integration
Access
Changeman/RDz integration options:
1.
Develop
Test
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 RD
- But with limited functionality and requires significant 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/
+ Turnkey solution
- Purchased product
@ Copyright 2016 - IBM
See Slide Notes 29
on
Dynamic vs. Custom RAM
RTC Integration – 1 of 2
Access
 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
@ Copyright 2016 - IBM
30
Develop
Test
RTC Integration – 2 of 2
Access
 Management of build, promote, deploy
Develop
Test
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 (just change
perspectives between Work Items and z/OS Projects)
The actual work is in populating your RDz workspace from the RTC stream
@ Copyright 2016 - IBM
31
RDz & SCLM Developer Toolkit integration
 Eclipse-based view of SCLM
repository including:
Develop
Test
 SCLM-specific environment
 SCLM views providing a treebased 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
@ Copyright 2016 - IBM
Access
32
RDz/SCLM DT Install/Configuration and Documentation
Access
Develop
Test
 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
@ Copyright 2016 - IBM
33
Panvalet/Librarian Integration
Access
 Can integrate through simple process that can be
called from RDz using Menu Manager, CARMA
framework, or Q-Group (proprietary) framework
Develop
Test
 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
@ Copyright 2016 - IBM
34
4. Customizing RDz with external tools and products
Custom CLISTs
and REXX Execs
Any/All native ISPF
functionality
necessary
@ Copyright 2016 - IBM
 Eclipse IDE customization
 MS-Windows integration
35
3rd Party Products
SCM Tooling
ISPF Dialog
Manager Apps
4a. Additional z/OS Green-Screen Tools Integration

Access
Considerations:
Develop
Test
 All shops implement a (usually) large # of CLISTS, REXX Execs,
custom ISPF Dialog Manager, and 3rd party tools to implement lifecycle
coverage for things like JCL scanning, adherence to standards, etc.

There are four ways to provide integration with these mainframe
apps:
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
3rd 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
@ Copyright 2016 - IBM
36
4b. Green Screen Integration – Deeper Dive on Menu Manager and HATS

Access
Solution Design for "conversational CLIST/REXX execs"
and ISPF-based tools
Develop
Test
 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 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 (Menu Manager solutions do not require a client/plugin installation)

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 3rd 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
@ Copyright 2016 - IBM
37
5. Client Software Rollout – Installation and Configuration
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
IBM Data Studio (strongly recommended)
Rational Business Developer (EGL)
IMS or MQ Explorers
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
@ Copyright 2016 - IBM
38
6. Workspace Customization and Management - 1 of 2
 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
@ Copyright 2016 - IBM
39
See Slide Notes
6. Workspace Customization and Management - 2 of 2
When you have finished building out your custom workspace
with your DPO contact you will finish the process off by following these steps:
 Configure the Remote Systems Explorer (RSE) and DB2 Connections
 For your new RSE connection:
Add between 2 and 4 MVS File Filters to common libraries
And add one example of a Saved Search Query
Add your specific z/OS File System Map requirements
Configure Property Groups (see slide notes for details)
 For your DB2 connection
Setup Filters for the common Schemas your groups use
 Save your work - and copy to a LAN
 Write up a process for copying and launching RDz with the default
workspace
 Save someone else test the Workspace copy/RDz launch process from your
document
Note: If you are using additional plug-ins (Serena & Compuware, etc.) when they are
available you'll have to revisit the above in light of any new requirements they impose
@ Copyright 2016 - IBM
40
See Slide Notes for full
details of the above
RDz Knowledge Assimilation … one approach
The outcome of building an on-demand
automated, technical assistance portal
is cost-effective long-term support
On-demand, Self-Help
Technical Assistance Portal
The outcome of effective
mentoring is product
mastery with your own
company’s software
artifacts
The outcome of
effective product
education is
workshop
success using
the educational
software
artifacts
@ Copyright 2016 - IBM
1X1 User Mentoring
High-Quality Product
Technical Education
41
7. Knowledge Transfer – Training Part 1
 First impressions are critically important in the
adoption of any transformative technology - like RDz
 Key aspects of training include:
Building motivation - to master the new development tools and
processes
Educational effectiveness - of the entire training program
(slides/workshops), but especially of the instructor(s)
 Motivation:
 Change > Adoption happen when software professionals are
convinced that new development tools make their work easier
 The job of convincing is a person-to-person concern
 Quality RDz training
Introduces change - convincingly
Builds the on-ramp for the transition from green-screen to RDz tooling technically
@ Copyright 2016 - IBM
42
7. Knowledge Transfer – Training Part 2
 Lessons Learned:
 Video-based training has a poor track record for successful RDz
adoption – when used as initial product education:
– Video-training artifacts are excellent review material
 Internal (in-house) training can work:
– But only when delivered by a professional technical instructor
– Domain Knowledge is only one aspect of effective software education
– Utilize RDz administrators for course design and customization
– Employ qualified technical instructors for this critical Rollout phase
 Quality RDz instructors:
–
–
–
–
Are z/OS developers
Who have mastered RDz - literally every aspect
And are expert communicators
Competent in adult learning theory
Do not confuse learning with teaching. By the time you've finished high school you
probably understand your learning patterns.
But that does not mean you know how to teach others – who go through life with very
different learning patterns.
This is especially true in the case of classroom or group instruction, a deeply specialized
@
Copyright 2016 - IBM
43
discipline.
8. Knowledge Transfer – Mentoring/Post-Training Follow-up - 1 of 2
 After successful RDz training developers should be able to
use RDz effectively
With the training artifacts from class
 JCL, COBOL/Assembler/PL1, Copybooks, Etc.
Using the step-for-step instructions in the Workshop guides
 But, you don’t:
Do “real work” with training artifacts
Have a step-for-step instruction guide for using RDz with every one of your
shop’s software components
 Therefore it’s crucial to provide new RDz developers with:
1X1 mentoring - where the user is “driving RDz” and doing work with your
shop’s production software
 F2F is ideal
 But remote works … as long as the user is “driving”
 Also, an "on-ramp period" for new RDz users to assimilate the tools, processes
and techniques is necessary:
 Project managers must:
 Allow for some minimum amount of time to assimilate the new tooling
 Encourage developers to make the investment in RDz
@ Copyright 2016 - IBM
44
8. Knowledge Transfer – Mentoring/Post-Training Follow-up - 2 of 2
 The “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 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
@ Copyright 2016 - IBM
45
9. Knowledge Transfer – Part 3: Building a Center of Excellence
There will be a need for 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:
1. Federated group of RDz technical champions and coaches
2. Search-able learning portal – library of learning tools integrated into a custom
RDz workspace, that aggregates:
Internal standards:
 Naming conventions
 Product (usage) Best Practices
 Workspace: Backup, management and administration
FAQs + how-to help
 Search facility / Static textual help
 Hyper-links to: Internal documents, Classroom content, Web-based learning
3. Google Searches
@ Copyright 2016 - IBM
46
Federated Group of RDz Technical Champions and Coaches
In the same way that a few Systems Administrators, Systems Programmers,
DBAs and I/T technical teams assist with your existing infrastructure, you will
benefit from “economy of scale” if you federate out your RDz person-toperson help.
This is standard for short term - initial (i.e. once Mentoring has concluded) Rollout
projects.
Over time - as the RDz users become experts, you will be able to minimize the
number of individuals dedicated to this.
Division-level
Level 3
SMEs
Federated
(Project-Level)
SMEs
Federated
(Project-Level)
SMEs
User
@ Copyright 2016 - IBM
User
User
User
47
User
User
Google Search (Don’t laugh)
Google has indexed; The RDz InfoCenter, Slideware from various sources,
Published blogs, articles and white papers, IBM Tech/Support Notes,
Listserv sites and help forums, YouTube videos … probably more.
Sometimes I wonder - if I can’t find something on Google … does it exist?
@ Copyright 2016 - IBM
48
RDz Local Workstation Project – Searchable Learning 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
@ Copyright 2016 - IBM
49
The Importance of Expert Services
RDz product training and mentoring falls into the category of
that-which-is-done-cost-effectively-by-experts:
Singular (one time) activity
Requiring deep-dive specialized expertise - acquired after
years of technology use by talented professionals
 As one Rollout administer put it:
With so much at risk, we couldn’t cost-justify the spend on RDz
product + implementation staffing costs for the Rollout, and fail to
budget a few thousand bucks for expert services to achieve our goals.
 There are a number of qualified RDz technical consulting
companies in each geography
 Your IBM account team can discuss options for obtaining
qualified assistance
@ Copyright 2016 - IBM
50
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
generate interest, 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)
@ Copyright 2016 - IBM
51
10. Momentum Building – Some of the IBM no-charge events
 RDz User Group meetings:
 The North American and European Annual User Group meeting sponsored by development
 Advanced RDz Education:
 Scheduled sessions where developers could ask questions throughout - or surface problems they're
having.
 Advanced training topics, delivered to organizations in the past:
 RDz Editing – advanced productivity tips & techniques
 zUnit testing
 Continuous Integration
 State Analysis/Code Review – interactive, batch, and writing custom rules
 Code Coverage
 Setting up the pre-processor – for work with 4GLs and custom macros
 Search deep dive – Remote, z/OS File, and programmatic searches
 RDz Configuration deep dive – Compile/Link, Property Groups, Preferences and Mapping Datasets/PDS members
 Advanced Source code analysis features and techniques
 Code reusability options (Statement and program templates and Snippets)
 Advanced Debugging techniques (with Debug Tool or the RDz Integrated Debugger)
 Advanced DB2 and SQL development
 The Java/Eclipse editors – PL/I, COBOL, JCL
 Working with 3rd Party languages – Easytrieve, SAS, etc.
 Working with Assembler code
 Using Menu Manager to implement TSO/ISPF functionality
@ Copyright 2016 - IBM
52
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.
@ Copyright 2016 - IBM
53
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
Usage Metrics
@ Copyright 2016 - IBM
54
RDz_Metrics.xml
… \workspace\.metadata
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
@ Copyright 2016 - IBM
55
Rollout Planning – Steps
 Assuming that the RDz client and server are:
 Installed/Configured/Optimized/Tested (functional and stress tested)
 Client deployment scripts written and tested
 Custom Workspace delivery and refinement process defined and tested
 Create/Refine formal Rollout project plan – Rollout v1.0
 Select team: Rollout and Admin
 Define milestones and deliverables
 Formally define RDz business goals
 Create usage model: Based on business goals … 80/20 rule with all business units
 Perform gap-analysis
 Solution options: Menu Manager/HATS or Training
 Obtain product usage mandate:
 Executive sponsor
 Project manager communications
 Define training and mentoring:
 Requirements/Topics (based on Usage Model)
 Consider 3rd Party product tooling and SCM integration
 Mode of delivery … Scheduling options … Evaluative criteria
 Select a training/mentoring vendor
 Establish an RDz internal User Group
 Monitor and synchronize Rollout with IBM team and DPO
 Prepare for v2.0 Updates
 Push to client … incorporate user feedback … new tools/plugins
@ Copyright 2016 - IBM
56
®
IBM Software Group
Back up slides
- RDz Training – Detailed Considerations
- Additional Best Practices (lists)
© 2016 IBM Corporation
Summary – RDz Rollout “Common Failure Points”
 Ineffective executive mandate
 Widespread and successful RDz adoption requires decisive management directive
 Inadequate on-ramp time
 Adequate product assimilation-time must be provided for new users of transformative technologies
 Solution: Project managers must allow for (in fact… encourage) skills on-ramp
 Failure to tune the RDz Server
 Modern z/OS is stable and lightning-fast. The RDz Server must be stable and fast enough
 Solution: Schedule the DPO Server Health Check. Tune and monitor the RDz listener like any other
MVS technology
 Legitimate technical barriers to product use
 These typically take the form of access to needed green-screen processes and applications
 Solution: Provide integration through HATS/RCP and Menu Manager – or Java/Eclipse plug-ins
 Deployment of the default (out-of-the-box) RDz Workspace
 Spending time configuring Workspaces is not what COBOL/PL1 programmers signed up for with RDz
 Solution: Customize Workspace assets to the requirements of individual project environments
 In-house training delivered by RDz Administrator(s) or technical staff
 RDz knowledge transfer will not succeed unless delivered by a qualified/professional technical trainer
(Domain Knowledge is – and has always been just one aspect of effective technical education)
 Solution: Utilize qualified professional software educators to deliver an RDz training course designed
by your RDz administrator(s). Or implement an accredited RDz Train-the-Trainer program for your staff.
 Inadequate Mentoring / Help System
 Product usage challenges begin when developers use RDz to develop production program code.
 Solution: Provide F2F mentoring for a short period of time post-class, and build out a quality internal
self-service help system for longer-term guidance
@ Copyright 2016 - IBM
58
Why all the emphasis on training and mentoring?
 There are two types of approaches to advancing the state of your software
development:
Examples for
3270
Development
Solution type
Characteristics
Requirements
for Adoption
Benefits
Add tool or
function to existing
platform
Similar to
existing tools
and techniques
Documentation
Incremental gain.
At best addresses
partial aspect of
problem
New edit macro
New REXX exec
New ISPF tool
Transformational
Solution
Paradigm Shift
from existing
development
approach
Training,
Mentoring and
On-demand
technical
Support
Magnitudes of
Order
Improves all
aspects of
development
RDz
 Customers and research prove that RDz (on average) raises productivity
between 20% and 30%
 RDz does this by shifting the development paradigm from a manual/typing approach with
tools that are 40 years old, to a hyper-linked graphical-tooling approach with functionality
that is advanced/state-of-the-art
 But paradigm shift technologies bring with them knowledge transfer requirements to
succeed - particularly with developers that have a long-standing attachment to the
technology being replaced
@ Copyright 2016 - IBM
59
Education Effectiveness – Teaching RDz
z/OS
RDz
Subject Matter Expert
Technical Expert
Presentation
Skills
Adult Learning
Expert
@ Copyright 2016 - IBM
60
Who you're
looking for
in an RDz
trainer
7. Training Considerations – Details
 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
@ Copyright 2016 - IBM
61
7. Training – Considerations for traditional product training

Besides standard RDz curriculum (next slide) consider:
1.
2.
3.
4.

SCM integration/development workflow
Subjects – based on your business reason for purchasing RDz
Custom workspace, workbench products and client plug-ins and configuration
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
@ Copyright 2016 - IBM
62
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 of your RDz education:
?
 (by comparison) secondary school 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 the above
There’s also the cost of building up and maintaining a quality RDz curriculum:
 Slideware, workshops, additional collateral such as: samples, workspaces, etc.
 There are “Train the Trainer” programs offered by RDz consulting
companies
Details on the next slide
@ Copyright 2016 - IBM
63
7. Training – Considerations for Train-the-Trainer Programs

Analyze your RDz Rollout:
 Requirements, constraints, limitations, challenges and expectations
… Start 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“ – as described in this document


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 should 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

Certain vendors offer a cloud-based learning environment
@ Copyright 2016 - IBM
64
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
@ Copyright 2016 - IBM
65
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
 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
@ Copyright 2016 - IBM
66
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.
@ Copyright 2016 - IBM
67
Advanced RDz Training Topics

§
§
§
§
§
§
§
§
§
§
§
§
§
§
§
§
§
§
§
§
§
§
Advanced Editing - Productivity tips & techniques
Managing and Organizing Your Source Files
Advanced Search Patterns
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 or the RDz Integrated Debugger)
Advanced SQL development
RDz Application code quality
The COBOL and PL/I Editors
Working with Assembler code
Introduction to z/OS Java for RDz Mainframe Developers
Leveraging Local Workstation Projects
zUnit Part I
CICS Administration Tools
Tricking Out Your RDz Workbench - Custom Colors, Perspectives
andSearch"
Hotkeys
"Leveraging RDz
File Manager
Nine types of RDz Search Options - and usage Best Practices for program and application analysis
Fault Analyzer
.Remote Search
.Remote Indexed Search
Regex
.Occurrences in Compilation Unit
Advanced DB2 Table Work - with Data Studio
.Ctrl+F Search
BMS and MFS Map Editors
.ISPF Search and options (NX, X, etc.)
Using Menu Manager to implement ISPF "COPY" and other commands
.COBOL Editor Search
.Remote File Search (v9.1)
.ISRSUPC/Menu Manager Search
.Searching JES Jobs
Search Results options
Searching across LPARs
Saving Search predicates for reuse
Saving Search Results
Searching RDz Containers/Dataset options:
.MVS File Filters
.MVS Subprojects
.Single and discontiguous Datasets
.Single and discontiguous PDS Members and GDG Datasets
.Retrieved Datasets
.Entering Search without prior selection
.Mixed Search
.Local Workstation Projects
Searching for HEX/Binary values
Compound Search
Find/Replace - with Search - for Global changes
@ Copyright 2016 - IBM
68