1. RDz Workbench – Cheat Sheets
Jon Sayles, Rational System z Products -

2. IBM Trademarks and Copyrights
© Copyright IBM Corporation 2007,2008, 2009, 2010, 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. Contributing Authors
Thanks to the following individuals, for assisting with this document:
Reginaldo Barosa/IBM
Chris Sellers/TSYS

4. Overview Audience Prerequisites
These Cheat Sheets are designed for application developers who have learned or programmed in COBOL, and who need to do z/OS Traditional Development and Maintenance as well as build leading-edge applications using COBOL and Rational Developer for System z.
Prerequisites
These Cheat Sheets assume that you have learned and have used RDz, and that RDz is setup and working in your company, both:
RDz Client – on your workstation
RDz Server – on your z/OS mainframe
Further, we assume on your part:
A basic understanding and knowledge of software computing technologies, and general data processing terms, concepts and vocabulary, as well as a working knowledge of COBOL and z/OS.
Knowledge of SQL (Structured Query Language) is assumed for database access is assumed as well.
Basic PC and mouse-driven development skills, terms and concepts are also assumed.

5. Table of Contents Basic Development Techniques:
Accessing Source and Data Sets
Program Quick Fix (Trivial Edit)
Program Maintenance (Non-Trivial Edit)
Program Compile (build)
Testing your programs
Editing QSAM and VSAM Data Sets
Working with DB2 and SQL
Access and Manage Batch Jobs
ISPF 3.x Utilities (data set allocation, delete, copy, etc.)
Advanced Development Techniques:
Development techniques
DB2 / SQL Techniques
Debugging Techniques
RDz Client Configuration and Administration
Connecting to your mainframe
Connecting to DB2
Mapping z/OS Files to RDz
Setting up Property Groups
Customizing RDz Client Workspace Defaults
Working with Views and Perspectives
Terms and Vocabulary

6. Basic Development Techniques
UNIT
Basic Development Techniques
Topics:
Accessing source and data sets
Analyzing your programs
Program "quick fix" (Trivial Edit)
Program maintenance (Non-Trivial Edit)
Program compile and link
Testing your programs
Editing QSAM and VSAM data sets
Working with DB2 and SQL
Access and manage batch jobs
ISPF 3.x Utilities (Data Set allocation, delete, copy, etc.)

7. Accessing Source and Data Sets
1. Connect - See RDz Setup and Customization Cheat Sheet, for steps on connecting to your mainframe
2. Access a data set in Remote Systems Explorer (RSE):
Files that belong to you (with your TSO ID as the high-level qualifier) are in "My Datasets"
Scroll through the list of libraries under MVS Files / My Datasets
If you have RDz version or later installed, use the "Locate" option (Ctrl+L) to find a specific member within a library
…or… Expand the PDS and find the source member you wish to edit
Files that don't belong to you are accessed through Filters or Retrieve Data Sets (DSLIST)
To use Retrieve Data Sets – right-click over MVS Files and select Retrieve Data Sets
Enter your Data Set search string - literals and the * wildcard character – like ISPF 3.4
Press Enter
Open an existing Filter in your connection, or to create a new Filter for files that aren't defined to your high-level qualifier:
Right-click over MVS Files and select New > Filter...
Enter the z/OS file-spec with or without wildcards in the Filter string, and click Next
Name the Filter and click OK
Once you define a Filter you can modify the Filter patterns by right-clicking over the filter, and selecting Properties
To add a second (or third) string pattern to an existing Filter – from the Filter's properties select: New filter string
Access files through your Source Control Management System's RDz interface
Search for the data set or library member you need
Select one or more libraries (press the Ctrl key while clicking to select multiple PDSs)
Click Remote Search
Enter the Search criteria (wildcards can be used in the search pattern):
Search for text inside the members and search on member names
Click Search
Double-click entries the Search Results view, to open the file and position the cursor at the found line
FAQ
What if I don't see Remote Systems Explorer? See Cheat Sheet on resetting your perspective
What if I want to edit a data file (VSAM or QSAM file)? See section on editing VSAM/QSAM files
What if the file I need is on some other LPAR? See Cheat Sheet on connecting to your mainframe
How do I transfer a file from my PC to the mainframe? Drag and Drop the file to a PDS, or Copy and Paste
What if the correct editor isn't opened for a file (no colorization, etc) See Cheat Sheet on File System Mapping
How do I know who has a file locked? Right-click over a dataset, select Monitor and scroll right, to see Lock Owner
See: for File Manager product installation and documentation

8. Program Analysis 1. Access your source
2. Understand the code before making source changes. Here are some RDz key features:
Navigate within your source:
ISPF Commands: top, bottom, enter a line # to go immediately to that line. (Easier) use the scroll bars for positioning
PF7/PF8, PgUp/PgDn – Ctrl+PgUp, Ctrl+PgDn, Ctrl+Home, Ctrl+End
Visual analysis – Maximize your program understanding through optimal use of window/screen "real estate"
Split screen – Press Ctrl+2.
Double-click the editor tab to maximize your source view. Double-click the tab a 2nd time to restore the Workbench
Open the program's copybooks alongside the program in a multi-source view
Select the copy statements copybook or include name. Right-click and browse or open the copybook
Drag the editor tab to the right (or to the bottom) to create a multi-source view
Hover (mouse over) a variable or section name – Displays the variable declaration or paragraphs within the section
Filter the source to isolate program content
Right-click in the editor. Select: Filter view > Outline, or Code (filters out comments), or Comments (filters out code)
Control Flow analysis - How is the program structured?
Use the Perform Hierarchy – See Cheat Sheet for details
Dependency analysis - What copybooks and includes does this program use?
From Remote Systems Explorer – Right-click, select Show Dependencies
Data Flow analysis – How does a data value move from field to field within the program?
Ctrl/F search with Regular expressions - See Cheat Sheet for details
Use the Search sub-menu and Pin the results- See Cheat Sheet for details
Version analysis – What are the differences between this program and the last version?
From Remote Systems Explorer - Select both source files. Right-click and select: Compare With
3. Close the File or continue with program source modification
FAQ
What if the Perform Hierarchy is grayed out?
Ensure that there are no validation and syntax errors. Make sure you have selected the Paragraph name
What if I can't browse a copybook?
Ensure that Property Group settings for Copy Libraries are correct - See Cheat Sheet on Property Groups
See: for File Manager product installation and documentation

9. Program "Quick Fix" (short or, trivial edit session)
Access your source – see prior Cheat Sheet "Accessing Source and Data Sets"
Double-click to open the file - Right-click and select Browse to open the file Read-Only
Perform Quick Fix edit:
Find the statement(s):
Scroll through the source, use the Outline view or use ISPF "Find" commands
Change the code, as per your requirements:
Type or use Content Assist (Ctrl+Spacebar) for Intelli-sense editing of new statements
Check for Validation errors
Optionally perform a Remote Syntax Check:
Press Ctrl+Alt+R, or Right-click inside the source and from the Context menu select:
Syntax Check > Remote
Open the Remote Error List view, and check the results.
Double-click on an error to position your cursor on the line in the editor
Save (Ctrl+S) and Close the file
FAQ
What if my source is not colorized? - See z/OS File System Mapping Cheat Sheet
What if I closed a view (like the Outline view)? – See Cheat Sheet on working with views and perspectives
See: for File Manager product installation and documentation

10. Program Maintenance (non-trivial edit session)
1. Access your source
2. Understand the code and your source changes:
3. Modify the code:
Use your ISPF editing skills (Prefix area and Command line commands) – supplemented by RDz editing features:
Ctrl+2 to split screen - Edit in either side of the split screen. Copy/paste from one side to the other
Use the Context Menu (Right-Click) to:
Refactor (rename) a field, paragraph or section – Select the variable. Right-click and select: Refactor > Rename
Hex edit a line
Note that if you need to make a change in Hex - Select the line. Right-click and select Hex edit line, and from the CP037 (bottom) row, Change the EBDCIC Hex value and press <Enter>
Select a variable, paragraph or section name and press PF3 to access its declaration. Even if the field is in a copybook
Click the left (Back) arrow icon on the toolbar (top of the workbench) to return to your previous source position
Comment out (or un-comment) one or more lines
Select the lines
Right-click and select Source > Comment or Uncomment
Select source and
Copy/Paste
Change the selected source lines to upper or lower case
Open copybooks – Select the copybook name. Right-click and select: Open or Browse Copy Member
Remote Syntax Check.
From the Remote Error List – double-click an error line to navigate to the syntax error in the source
As you type, check for Validation (syntax) errors (little yellow triangle icons in the left-hand border of the file)
Use Content Assist (Press Ctrl+Spacebar) - Intelli-sense editing for:
Keywords
Variables and paragraph names
Custom code templates – Press Ctrl+Spacebar to bring up the list of customized code templates
4. Save and Close the File
FAQ
What if Content Assist or Refactor doesn't work?
Ensure that there are no validation and syntax errors – and ensure that your Property Group file is correct
See: for File Manager product installation and documentation

11. Compile Your Program
To compile your program in order to create .OBJ and .EXE (Load Modules) use your Source Control Management System's build function ...or...
Access/Open your JCL Library in RSE
Select the member to compile your program.
Right-click and select: Submit
...or...
Select the source file in the library
Right-click and select Generate JCL – for Compile, or Compile/Link
Submit the generated JCL
From the JES icon, verify your compile results
FAQ
How do I know if my build worked?
Access JES – and open the output spool for the COBOL and/or Link Edit steps
What if there are JCL errors
Check your Properties Group file for correct COBOL PROC entries – see Cheat Sheet on this topic
What is Local Syntax Check?
A function of RDz that allows you to syntax check your program on your workstation (locally) using the Enterprise COBOL version 4 compiler
Does Remote Syntax Check compile a program?
No, it only syntax checks your code on the mainframe. Use one of the above methods to compile/link your code
What is the difference between LOCAL and Remote Syntax checking?
Local Syntax Check uses your workstation and the Enterprise COBOLV4 compiler to find syntax errors
Remote Syntax Check uses
Why could Local Syntax Checking display if the program is correct ?
My property group for LOCAL Workstation project syntax checking is incorrect – see Cheat Sheet on Property Groups
I'm editing an OSVS/COBOL program, that has statements not compatible with Enterprise COBOL V4
I am using special includes or COBOL statements not recognized by Enterprise COBOL V4 (example: TRANSFORM)
My program contains EXEC CICS but have not installed TXSeries - or have not specified CICS in my Local Property group
My program has EXEC SQL but have not specified SQL in my Local Property Group
See: for File Manager product installation and documentation

12. Access and Manage Batch Jobs
Submit a batch job:
From Remote Systems Explorer:
Open your JCL Library
Right-Click over the run-stream JCL file, and select: Submit
From a JCL file open in the editor:
Right-click, and from the context-menu, select: Submit
From the command-line, type:
sub - to submit the job to the LPAR the file resides in
Sub <ConnectionName> - to submit the job to a specific connection (which could be to a different LPAR)
Note that your JCL file can reside in a Local Workstation project, and you can submit to any LPAR you are connected to
Open your Job from the JES queue:
Jobs that you submitted will be found under My Jobs – a Filter for <HLQ>.*
Jobs submitted by others can be accessed through Filters:
Right-click over JES and select: New > JES Job Filter…
Enter the Filter criteria (typically on Job Owner or Job Name Prefix)
Expand the Job spool files and double-click to open:
Output for the entire job
Output for any given job step
To see your jobs in a table (so you can arrange/re-sort them):
Right-click and select Show in Table
To re-run any job:
Right-click over the job and select: Show JCL(SJ)
To cancel a running job:
Right-click over the job and select cancel
To Purge a job:
Right click over the job, select Purge
FAQ
What if there is no: My Jobs filter under JES? Define a new Filter as: <HLQ>.* Take all of the defaults for Filter definition
What if my JCL isn't colorized? See Cheat Sheet on File System Mapping
See: for File Manager product installation and documentation

13. Program Testing (Requires Debug Tool to be installed)
Compile your program with Debug Tool required: DD card for SYSDEBUG and compile options
Debug a program:
First, from the Debug Perspective discover your I/P address and listener port - by clicking the downward-pointing triangle, immediately to the right of the Debug UI daemon icon
Debugging a batch application:
Substitute the I/P address in the JCL //CEEOPTS DD card
Submit the job
Debug your code:
Click F8 to run to a breakpoint, F5 to step (execute) your statements one line at a time
To view the content of a variable - Hover over a field or look in the Variables or Monitors view
Use the Context Menu to:
Set break points
Add variable watch monitors
Run or unconditionally branch to a given line in your program
Terminate the session when finished - by clicking the red Terminate icon on the toolbar
Debugging an Online Program
Setup the DTCN properties for debugging an online transaction – See Cheat Sheet
From CICS or IMS DC (green screen) launch the transaction
Debug your code
FAQ
What happens if my job ABENDs?
You will be given the option to terminate or continue debugging
What happens when an online application returns to CICS or IMS DC (Message Switch)?
The 3270 data stream/screen (BMS or MFS map) is displayed. Upon <Enter> or PF-Key you can continue to debug
Can I backtrack (reverse the program execution flow)?
As of RDz v8.0 this feature is not available (it's only available with Green-Screen Debug Tool (running under TSO)
See: for File Manager product installation and documentation

14. Working with DB2 and SQL
1. Connect to DB2 (double-click on a connection) – see the Cheat Sheets to learn how to define a new DB2 connection
2. Explore your tables/views and their relationships:
Use the Data Source explorer to drill-down into your tables
Start from the Schema folder and drill-down (expand) folders for tables, views, etc.
Use the Overview diagram to see how your tables relate
Right-click over the Schema, and select Overview Diagram
From the Overview Diagram - select the tables
Click Go
3. Code and test SQL:
Right-click over the connection, and select SQL editor
Code your SQL using Content Assist (Ctrl+Spacebar)
Press F5 (or Right-click over the statement and select Run SQL)
Check out results in the Results tab
4. Analyze and Edit your DB2 test table values:
Right-click over the table
Select Sample Contents to see the value
...or...
Code SQL (see above) to filter the table
Right-click over the table, select Edit
Change values
Press Ctrl+S to save
View your saved table changes using SQL or Sample Values
See: for File Manager product installation and documentation

15. Working with VSAM/QSAM Test Data (Requires File Manager to be installed)
Access your file
Your ID – scroll to the bottom of the connection entries
A file created by someone else – Setup a Filter access the file
Double-click to open, or Right-click and select browse and use File Manager to edit the file
Navigate throughout the file:
Step (scroll) through the records in the file
Jump to a particular record – or to the top and bottom of the file
Re-sort the file – click the Sort icon
Modify record content:
Formatted view – Use the Browse button to associate a template file or copybook with a data file
Multi-row mode – Shows multiple records in the editor window
Single view – Shows one record (the current or selected record) at a time
Character view – the Character tab treats the records like rows
View the records in Hex – Click the Hex icon
Search – Right-click over a record and select: Find/Replace:
Search the file through logical fields within the records – using an associated copybook or template
Search throughout the entire file – search all bytes in each record by De-Selecting all fields in Find/Replace
Create a subset extract – see the File Manager Viewlet on the IBM Education Assistant
FAQ
When I double-click on a VSAM nothing seems to happen.
This type of behavior usually signifies that either File Manager is not installed/configured on your z/OS – or File Manager not at the proper release level to work with the version of RDz you are using
See: for File Manager product installation and documentation

16. ISPF 3.X Utilities - Working with Data Sets
From Remote Systems Explorer, the Context Menu (Right-click) has the following options:
Allocate Like - Creates a new data set using an existing Dataset's DCB and SPACE attributes Select a data set and Right-click to Allocate Like a new:
Library (PDS)
Sequential Data Set
VSAM files
To create new data sets from scratch – without basing them on an existing Data Set's DCB click: Specify characteristics (Advanced Allocation)
Rename, Delete, Compress, Search
Select one or more data sets - hold down the Ctrl key and left click to select multiple
Right-click, and from the Context Menu select your option
Create new PDS Member
Select the library you want to create a new (empty) PDS member in
Right-click, and from the Context Menu select Create New
Search - through one or more libraries
Select one or more data sets - hold down the Ctrl key. Left click to select multiple. The libraries can be in the same or in different LPARs
Right-click, and from the Context Menu select Search…
Use wildcard search patterns and/or Regular expressions (the | character allows you to logically "OR" multiple search criteria)
You can save your search query by clicking the small flashlight icon in the Remote z/OS Search view
Clone an existing PDS Member – Create a new PDS member from another PDS member in the same library
Expand the library you want to create a new PDS member in
Select the existing PDS member you wish to use as the new PDS member
Right-click, and from the Context Menu select Copy
Right-click on the library again. Select Paste – and rename the PDS member
Compare two source files
Expand the libraries that contain the source members you wish to compare - The libraries can be in the same or in different LPARs
Select the existing PDS member you compare. Right-click and select: Compare With > Each Other
Define a new GDG Model
Select the MVS Files icon
Right-click, and from the Context Menu select: New > Define Generation Data Group…
FAQ
What if a Context Menu option does not appear – example, I Right-click over a PDS and don't see Compress?
RDz will only provide allowable functions on a dataset. Your library is most likely a PDSE – and can't (doesn't need to be compressed)
See: for File Manager product installation and documentation

17. Advanced Development Techniques
UNIT
Advanced Development Techniques
Topics:
Control Flow Analysis
Data Flow Analysis
Reverse Engineering SQL
Editing Large DB2 Tables

18. Program Control Flow Analysis
Forward flow analysis (understand the Perform Chain starting from a given paragraph, and flowing forward in the PROCEDURE DIVISION)
Select your starting paragraph name inside the editor (anywhere in the Procedure Division)
Right-click and select: Open Perform Hierarchy
Note that, the Perform Hierarchy view can be moved to the top-right quadrant in RDz. This provides more vertical "screen real estate" and is better for large programs
Use the Perform Hierarchy view, to understand the Perform Chain
Perform nesting is shown as indented, hyper-linked paragraph names
To read the code in Performed paragraphs:
Use the Outline view
Or select the paragraph name (in the editor) and press F3
Backward flow analysis (Answering the question: "How did I get here, in my code?")
Click the small (Show Performer Hierarchy) icon on the top right of the view 
Use the Perform Hierarchy view, to understand what Perform and GO TO statements drive execution into your selected paragraph
Note that Show Performer Hierarchy, and the icon next to it - Show Performee Hierarchy) toggle between backward and forward flow analysis. This toggle persists (so you will need to click it – between modes of Control Flow analysis
FAQ
What if Perform Hierarchy is grayed out (disabled)?
This can happen if you have not (yet) selected a paragraph, or if your program contains enough syntax errors that the RDz parser can't understand your Procedure Division.
See: for File Manager product installation and documentation

19. Program Data Flow – or Impact Analysis
Data Flow Analysis refers to the processing of tracing values as they flow through program variables, in MOVE statements, Math, I/O, etc.
RDz provides two alternative methods that you may find efficient in doing these kinds of tasks:
Use multiple search windows
Find and then select your starting variable in the source
Open the Search menu and select: Search > Text > File
From the Search view:
Double-click a hyper-linked reference to see and position your cursor on the statement
When you find a statement that references a new variable that you must analyze:
Pin the current variable's search view, so that it persists 
Select the next variable in your source
Return to step 2 and iterate
Use a single search window and Regular Expressions
Press Ctrl+F to open the Find/Replace menu panel
Make sure Regular expression is checked
Enter the variable name and press the All button – to find all instances
Review and analyze the returned statements – compressed in the source view
If it turns out that another additional variables participate in the Data Flow:
Return to Step 5 and Add the additional variable names into the Find box, separated by | characters
Iterate from steps 5  7
Analyze results
See: for File Manager product installation and documentation

20. Reverse Engineer an SQL Statement
You can produce a visual diagram of SQL statements using the RDz Data Tools
Access and open a DB2 embedded SQL program
Use the Context menu (Right-click) and select: Filter view > Embedded SQL/CICS/DL1 to isolate your SQL statements
Select and copy one your SQL statements – typically a cursor DECLARE
Open the Data Perspective
In the Data Project view – either create use an existing, or create a new Data Development Project
Right-click inside the view and select: New > Data Development
Name the project (or leave the default name) and click: Next >
Select your connection and click: Finish
Expand the new project icon.
Right-click over: SQL Scripts, and select: New > SQL or XQuery Script
From the wizard select:
SQL Query Builder
Statement type: SELECT
Paste your previously copied embedded SQL statement into the top panel
Click into the panel and edit the code:
Remove host variables
A graphical view of your statement should appear in the middle panel
Note that, even though RDz's Data Tools support host-variables, there are number of COBOL embedded SQL constructs that are not supported
You may also test your SQL:
From the Context Menu
Select Run SQL
See: for File Manager product installation and documentation

21. Editing Large DB2 Tables
If your DB2 test table is too large to edit directly, you can use the following technique to modify row values:
Run a SQL Script to create a Result set that you wish to use as the basis for your editing and new values
Export the Results as: Plain Text (*.txt) and Comma Separated
Edit the text file produced:
Notepad works. Don't use any editor that adds special characters
Delete the column names header
Your new values will have to pass all of the standard DB2 (relational) data integrity checks:
Data type/Length and max value (for numeric columns)/Primary key uniqueness/Foreign key (referential integrity) checks
Save your new/edited tables values
From the Data Source Explorer
Select your table
Right-click and select: Data > Load…
From the Load wizard select:
File name (exported data)
Comma delimiter: Comma
Character string delimiter: None
Un-check: Replace data
Click Finish and check the Load status Message
View your new table data values
Use a SQL Script (Select statement) to verify your
See: for File Manager product installation and documentation

22. Part III – RDz Setup and Customization
UNIT
Part III – RDz Setup and Customization
Topics:
RDz Wizards, Setup and Configuration
Customize your Workspace Preferences

23. Setup a connection to your mainframe (z/OS)
From Remote Systems Explorer
Expand the New Connections icon and Double-Click z/OS…
Enter your host I/P address – or the logical name that resolves to an I/P address on your network. Example: zserveros.demos.ibm.com
Name the Connection and click Next >
Note that connection names must be unique
Enter your host port# for z/OS Unix files and click Next >
This is a value that typically a systems programming staff who installed RDz would give you
Enter your host port# for MVS files and click Finish
This is also a value that typically a systems programming staff would give you
Note that this only creates a connection. To connect (for the first time)
Right-click over your new connection and select Connect
Enter your TSO UserID and Password
Click Connect - After this first connection, you only need to expand your connection
FAQ
When I try to connect what kinds of errors could I get?
Three basic kinds:
Authentication errors – due to wrong ID/PWD
Connectivity errors – either your port settings are wrong, or there are network problems getting to z/OS
RDz listener failures – the RDz mainframe components may be offline. You will need to contact your systems programming staff, and ask that they be restarted
See: for File Manager product installation and documentation

24. Setup a connection to DB2 on z/OS
From the Data Perspective (from Remote Systems Explorer)
Right-click over Database Connections
Select: DB2 for z/OS as the database manager and enter Properties for your connection:
Location:
TCP/IP Location of the DB2 Server on z/OS (obtain from your DBA or Systems Programmer)
Host:
The IP Address of the z/OS mainframe for your DB2 system
Port:
The port number for DB2 on your z/OS mainframe
Do NOT check: Retrieve objects created by this user only
User name/Password
Your TSO logon credentials
Click Next and from the Filter wizard
Uncheck: Disable filter - and:
From the Drop Down box:
- Select a search pattern
- and enter a text string
Or check the Selection radio button, and check one ore more high-level Schema name(s) you wish to add to your Connection
FAQ
When I try to connect what kinds of errors could I get?
Two basic kinds:
Authentication errors – due to wrong ID/PWD
Connectivity errors – either your port settings are wrong or there are network problems getting to z/OS
See: for File Manager product installation and documentation

25. Create a filter (ISPF 3.4 Functionality)
Create a filter for datasets:
Filters are similar to ISPF 3.4 (DSLIST) functionality. They allow you to access files not "owned" by your TSO ID
To create a new filter:
Right-click over MVS Files or My Data Sets
Select: New > Filter…
Specify the search pattern for the Filter (like ISPF 3.4 – a combination of text strings and the asterisk * as a wildcard. Example: DDS0001.TEST.CO*
Enter a name for the filter – note that the named filter will appear in Remote Systems Explorer
To modify a filter – Extending it to additional datasets or changing its wildcard text
Select the filter
Right-click and select: Properties – then select Filter String
To change the existing filter string – overtype its wildcard text
To add an additional filter string (whose results are concatenated with other Filter string results):
Select New filter string
Specify the wildcard text
Click OK
Create a filter for batch jobs – to allow you to view results for batch jobs you did not submit:
Right-click over the JES icon and select: New JES Job Filter…
Specify the JES Job filtering pattern
FAQ
What rights do I have to datasets I didn't create accessed through filters?
The same rights you have when accessing the same datasets through TSO – all access privileges are governed by your authentication software: RACF, ACF-2 or Top Secret
If I delete a filter does it delete the underlying datasets? NO
See: for File Manager product installation and documentation

26. Setup a Local Property Group
A Property Group is a collection of specifications (mostly compile/link properties like SYSLIB, whether to preprocess for DB2, CICS, etc.) used by RDz to provide z/OS functionality (syntax checking, opening Copybooks, etc.)
To Setup or configure a Property Group for Local Workstation Projects
From the Property Group Manager view:
Expand LOCAL
Double-click the Property Group you wish to configure
Typically you will use the file produced by RDz when you create a new Local Workstation project. It's called: COBOL Sample Property Group
Select the language (either PL/I or COBOL), and from the language tab:
Specify SYSLIB:
Enter the fully-qualified directory in which your copy code is stored
To concatenate multiple directories separate each by a semi-colon
Specify EXEC SQL options – if your programs access DB2:
Check:  Source contains SQL statements
Select the connection to the DB2 system you wish to use
- Note that if you wish to connect from a Local Project to DB2 on z/OS you will need to install and
configure DB2 Connect. This is beyond the scope of these Cheat Sheets
Specify any SQL preprocessing options
Specify CICS options – if your source contains EXEC CICS statements:
Check the:  Source contains EXEC CICS statements box
Note that you must have IBM's TXSeries installed locally (on your workstation) in order to use this feature
See: for File Manager product installation and documentation

27. Setup a Property Group for z/OS (Remote) Assets
Property Groups for mainframe (remote z/OS) assets are more sophisticated than for Local Workstation projects. To configure them use these 3 steps:
Import a Property Group file as the default settings for a z/OS connection:
From the Property Group Manager view:
Select the Connection you want to work with
Right-click and browse to the Property Group file you wish to use – note that you could have more than one
Customize/Modify Property Group settings:
Specify the Categories you want to configure
Click the tab for your language (ex. COBOL, or PL/I) and from Settings tab check the Runtime Environments you wish to configure for (Example – does your program code contain: EXEC CICS or EXEC SQL statements)?
Still from the Settings tab, Click: Procedures and Steps. Expand the bottom PROC name – and select the step name (PL/I or COBOL). From this window specify:
Compile Option over-rides – typically you don't enter anything here
Listing Output Data Set – A listing dataset PDS (133 LRECL, etc) for compile listings to be placed in
Debug Data Set – A special PDS for members created for Debug Tool (LRECL=1024,BLKSIZE=27648)
Object Deck Data set – Your Object library (output from successful compile)
Copy Libraries – Your copybook and include libraries. Separate multiple by a space
Data Set Qualifier for Compile Errors – Enter a valid 8-byte MVS dataset name. Ex. ERRORCOB, ERRORPLI)
Additional JCL – typically you don't enter anything
Database Request Module Location (DBRM) – DBRMLIB PDS for your DBRMs (only shows if you checked DB2 runtime)
From the JCL tab:
Specify any custom JOB card properties
Specify your JCL Library – Where RDz will generate JCL to (this is an RSE Context Menu option for programs)
From the Link tab:
Linkage Editor Option over-rides – typically you don't enter anything here
Link Libraries – Your Object library – and any other Object or Load Libraries for static includes
Load Module Location – Named Load Library RDz generated JCL will point to inside Compile/Link JCL
Associate your Property Group with your MVS files in RSE
Right-click over MVS Files, or at the level of a PDS and select: Property Group > Associate Property Group…
FAQ
What does <HLQ> stand for? It stands for (resolves to) your high-level qualifier (TSO-ID) from your connection
See: for File Manager product installation and documentation

28. Change Default Workspace Properties and Settings
You may want to modify your shop's default RDz Workspace Properties This is similar to ISPF Option 0 – settings for TSO work
Access Preferences from:
Window menu
Preferences
From Preferences you can find and over-ride the following (commonly customized settings):
ISPF Editor (default selection)
Other LPEX editor preferences:
Tabs
COBOL number and column preferences
Colors - ISPF style editor colors vs. white background
Find Text - most guys prefer Incremental find dialog as a default
Additional Parser Associations
Column line indicator
BMS or MVS Map Editor Preferences
Large PDS Page (expansion) size
DTCN View setup defaults
Debug tool configuration:
Listener daemon port
CICS Debug configuration, etc.
File Manager - Editor data window size/step
SQL WORK:
Results and Table editor row max
SQL and XQuery editor templates
SQL editor templates
COBOL:
New boiler-plate program code
Statement templates (v8.0 and higher)
General (Eclipse settings):
Custom Key mappings
How long to keep Workspace Local History
Customized perspectives
Customized view colors,
See: for File Manager product installation and documentation

29. Reset or Change Your RDz Perspective
Perspectives are logical groupings of Views - and Views are like a single ISPF panel – a single-purpose function.
Just as on the mainframe where ISPF groups panels with similar functions under a high-level menu, RDz groups views that go together into a "Perspective" (Debug, Data, z/OS Projects, etc.)
To switch to a given Perspective from your current Perspective:
Pull down the Window menu
Select Open Perspective
Choose a Perspective from the list – or click: Other… and choose a Perspective
Note that you can check  Show all – to see a complete list
To reset your current Perspective to the IBM installation defaults – (useful if you've closed several views and want return all of them at once)
Select Reset Perspective
FAQ
What if I can't see a certain Perspective?
From the above, check  Show all – to see the complete list of RDz's perspectives
If the Perspective you're looking for is on that comes with a 3rd Party product, work with your I/T group, to be sure that the product is installed/configured correctly on your machine
See: for File Manager product installation and documentation

30. Open and work with Views
Views are like a single ISPF panel – a single-purpose function such as: Outline, Remote Systems Explorer, etc. Views are organized in Perspectives (previous topic)
Occasionally you may inadvertently close a view – or? You may want to open a view for the first time. To do this - from your current Perspective:
Pull down the Window menu
Select Show View >
Choose a View from the list, or:
Type a few characters of the View name – this will filter the view list
FAQ
What if I can't see a certain View?
If the View you're looking for is on that comes with a 3rd Party product – or simply is not part of the base RDz installation, work with your I/T group to be sure that the product is installed/configured correctly on your machine
How do I close a View? Click the X on the right-hand side of the View tab
How do I maximize a View? Double-click the View tab, or, Right-click over the View tab and select Maximize, or, Click the Maximize icon
How do I restore a maximized View (so I can see all of RDz's tools)? Double-click the View tab (this action toggles the view between maxi, or, Right-click over the View tab and select Maximize, or, Click the Maximize icon
See: for File Manager product installation and documentation

31. Terms and Vocabulary
Workspace – the highest-level folder on your workstation that holds all of all of your RDz preferences, workbench "state" information and any locally-stored files
Perspective – a collection of related Views for a particular task, such as: z/OS Projects, Debugging, Fault Analysis, CICS System work, etc. Perspectives are similar to ISPF higher level menus, such as =3 Utilities
View – a single tabbed window that represents one single development function (Perform Hierarchy, Program Outline, z/OS File Mapping, etc.). A view is similar to a single ISPF panel – such as 3.4 (DSLIST), 3.8 Outlist, etc.
Property Group – an ASCII file used by RDz that contains specifications for z/OS compile and link JCL (Library names, concatenation order for SYSLIB) etc. Property Groups allow you to do Syntax checking (Remote and Local) as well as opening Copybook members in the editor, etc.
z/OS File System Mapping – an ASCII file used by RDz that associates dataset names – and possibly member names within a data set to a given type of Workstation file (COBOL, Assembler, BMS, MFS, JCL, etc.). RDz uses z/OS File System Mapping to "know" which editor should be launched for any given z/OS file
Filter – A list of datasets that conform to a given search pattern, similar to ISPF 3.4 – except that RDz Filters persist, and can be a subset or superset of TSO files.
See: for File Manager product installation and documentation

32. Appendix – ISPF Cheat Sheets
UNIT
Appendix – ISPF Cheat Sheets
Topics:
z/OS – TSO – ISPF – RDz comparison
RDz Editor Hot Keys

33. RDz – Mainframe Comparison Chart ("Cheat Sheet")
TSO/ISPF
RDz – Integrated Development Environment
Mainframe – z/OS
PC – Windows – where the code is being developed
JCL
JCL. If doing offloading from z/OS, shell scripts – on AIX machines
Manually analyze code
RAA i
Edit Code - ISPF
LPEX or ISPF mode editor
Compile/Compiler Options
Syntax Check – and/or Build Application – Compiler options under RDz
Submit Job
Edit JCL and submit job, or just use the Context menu and Submit
Unit Test – DISPLAY/READY Trace, Xpeditor
Debug Perspective – Local Project
Integration Test – Xpeditor
Remote Systems – z/OS Debug Tool Integration
QA – Regression Test - WinRunner
Remote Systems Testing – and utilizing Rational Function Tester
ABEND-AID/IBM Fault Analyzer
RDz – Integrated Fault Analyzer
File-Aid/IBM File Manager
RDz – Integrated File Manager
PDS (library)
Project – or Folder Set
JES
Remote System / JES
Endevor/ChangeMan – or Your SCLM
3rd Party SCM utilizing RDz's CARMA feature; ClearCase utilizing native integration; SCLM utilizing the SCLM DT Perspective and/or Local History
ISPF Option 0
Preferences
ISPF Option 1 and Option 2
LPEX Editor
ISPF Option 3.1 (Library Utilities)
Remote Systems Explorer
ISPF Option 3.2 (Dataset Utilities)
ISPF Option 3.3 (Move and Copy)
ISPF Option 3.4 (DSList)
Filters and Context Menu in Remote Systems Explorer and LPEX Editor
ISPF Option 3.8 (Outlist)
Remote Systems Explorer – JES – My Jobs
ISPF Option 3.11  3.15 (Extended Search)
Search menu
ISPF Option 4 (Foreground)
Run
ISPF Option 6
TSO Command Shell – with some functional limitations (e.g. cannot issue Host Execs)
ISHELL
Remote Systems Explorer - USS files/filters + Context menu
OMVS
USS Command Shell
SPUFI/QMF
Data Perspective

34. RDz – ISPF Comparison Chart – PF-Keys
ISPF Editor
LPEX Editor
PF 1 = Help
F1, Help Menu
PF 2 = Split: Split the session (lets you use two functions of TSO at the same time.)
Ctrl/2 or Context Menu – Open New View – can open unlimited # of views
PF 3 = End
Ctrl+F4 / Ctrl + 0, or close the Content Area
PF 4 = Return
Close the Content Area
PF 5 = RFind (repeat last find )
Ctrl/F – and /<text> from LPEX command
PF = 6 RChange (repeat lst change)
Ctrl/N
PF = 7 Move Backward
PgUp key – or slider in window
PF = 8 Move forward
PgDn key – or slider in window
PF = 9 Switch between screens during a split session; goes with PF 2
Mouse – or Alt + Shift + Right/Left
PF = 10 Move left
Home key, or slider in window
PF = 11 Move right
End key, or slider in Window
PF = 12 Retrieve
For LPEX commands, the Up Arrow
Use ISPF Option 0 to customize PF-Keys
Use Preferences to customize and extend Function key behavior
The LPEX Context Menu can be accessed from the Right-mouse button – and from the Windows Menu key (on the keyboard between the right Alt & Ctrl keys)
It should be noted that with the LPEX editor, it is not necessary for most of the above functions to actually press Ctrl/Key combinations, as the functionality is available from a context menu (right-mouse)
In LPEX F1 gives you language-sensitive help (pressing F1 while the cursor is on a COBOL keyword will display help for that keyword).
To get LPEX help, enter the help command from the LPEX command line.

35. RDz – ISPF Comparison Chart – Primary Edit Commands
ISPF Editor
LPEX Editor
Home key – Jump to the Command Line
Escape key – jumps to the LPEX command line
AUTOSAVE/REC
Prompt for Save on exit, and Autosave (Preferences), and the asterisk – next to unsaved file names
BOTtom
LPEX command: bottom / Ctrl+End
CANcel
If have not saved, Close Content Area w/Save no
CHANGE – All – NEXT, CHARS, X, ALL PREFIX, FIRST, SUFFIX, LAST, WORD, PREV, [col-1] [col-2]
Supported using replaceText, Ctrl+F or the Search window: Change All, Next, PREV, Prefix and Suffix (with wildcards), Prev, Word, [col-1][col-2], P
Copy Member Name
LPEX command: Get filename
CREATE
Save file as…, or use Snippets View
FIND – NEXT, CHARS, X, ALL PREFIX, FIRST, SUFFIX, LAST, WORD, PREV, [col-1] [col-2]
Supported using findText, Ctrl+F, or the Search window: Find All, Next, PREV, Prefix and Suffix (with wildcards), Prev, Word, [col-1][col-2], P
Not supported: First, Last
HEX – Displays all lines in Hexadecimal
Display one individual lines in Hex
ISPF Macros
Not available – but can be re-written using Java for LPEX. Also, note that with the LPEX functionality some macro functionality may not be necessary
LOCATE
On the command line, type in the line number (no "L"), or use the Outline View
MODEL
Snippets and Templates (both options)
MOVE Member Name
LPEX Get command, in a different way, the Snippets View
NUMBER
LPEX command: number std (columns 7380), or number cob
PRINT – from ISPF 3.4
LPEX command: print, or Ctrl+P
PROFILE – are the changes made to your profile
Preferences
Replace Member Name
Snippets functionality
RESet
LPEX command: expandAll, or: action showAll, or Ctrl+W
Save
Ctrl/S or LPEX Save command
Sort
LPEX command: sort
STATS – updates statistics
Windows updates file statisticsautomatically
SUBmit
LPEX command: Submit, or edit JCL/Context Menu/Submit, or use Context Menu/Submit option
TABS
Can set margins in Preferences
TOP
LPEX command: top / Ctrl+Home
TSO SUB
LPEX command: submit, and edit JCL/Context Menu/Submit, or use Context Menu/Submit option
UNNUM
LPEX command: unnum
***Changes to Preferences are persistent, even if they are changed via LPEX commands.
Also you can write/modify User Profiles which customize LPEX settings (but this requires writing a Java class and a plug-in).

36. RDz – ISPF Comparison Chart – Edit Line Commands
ISPF Editor
LPEX Editor – ISPF Mode
A, An – After
A, An
B, Bn – Before
B, Bn
COLS – show columns
Columns always shown
C, Cn, CC – Copy
C, Cn, CC
D, Dn, DD
F, Fn – First (used with eXclude) F,
I, In – Insert lines
I, In
L, Ln – Last (used with eXclude)
N - Find excludes lines of code
M, Mn, MM – Move
Context menu
R, Rn, RR, RRn – Repeat lines
S, Sn – Show (used with eXclude)
Filter
TABS – used with TAB On
Set with Preferences
X, Xn, XX eXclude
X, Xn, XX
O, On, OO – Overlay
O, On, OO
TS, TSn – Text Split
Ctrl+<Enter>
<, <n, <<N Shift Data Left
<, <n, <<n
>, >n, >>n Shift Data right
>, >n, >>n
(, (n, ((, ((N – columns left – Used with COBOL
(, (n, ((n
), )n, )), ))n – Columns Right
), )n, ))n
I don't know what all the supported line commands are off the top of my head, but see the following help page: Developing > Developing COBOL, PL/I, Assembler, and C++ applications > Language Editors > System z LPEX Editor > z/OS extensions to the base LPEX editor > System z LPEX commands > ISPF LPEX commands.
The ISPF commands come from a number of different products/development teams, so the documentation is a bit convoluted, but the above page contains links to all the relevant documentation.

37. RDz – ISPF Comparison Chart – LPEX Editing Operations – 1 of 2
LPEX Editor
ISPF Editor
Refactor – Remove Noise Words: - IS, THEN, PROCEED TO
N/A
Multiple Line Comment/Uncomment
Persistent virtual margins – in the editor
Code completion (Content Assist)
Open Copybook
Open Declaration – of variable or PERFORM'd paragraph from anywhere in the Procedure Division
Perform Hierarchy
Refactor – wizard for intelligent variable name changes
Outline View
Filter View – Show only Divisions, SQL,CICS,DL/I, Code (no comments), etc.
COBOL, PL/I and HLASM keyword / language help
Show lines that have been changed during edit (before save)
Find and Change against multiple file types
Block Marking (Ctrl+Down, Ctrl+Up, Ctrl+Home, Ctrl+End)
Virtual 'A' and 'B' Column lines in the source code
Allocate Like
Remote System Filters
Side-by-side Compare and/or Restore from Local History
Close all split screens in one operation (context menu)
See file attributes and statistics at all times (in a View)

38. RDz – ISPF Comparison Chart – LPEX Editing Operations - 2 of 2
LPEX Editor
ISPF Editor
Wizard-driven approach to creating Web Services (WSDL files) from: CICS and IMS TM applications
N/A
Wizard-driven approach to creating, testing and deploying DB2 Stored Procedures
Copy files from one LPAR to another
Edit/Compile/Unit Test if the mainframe is offline
Syntax error – automatically select line with problem
See 46  76 lines of source at once
Templatized program development
Regular expression searches – including across Filtered files of different file types
Keystroke recorder (useful for repetitive tasks and online testing)
Bookmark and Tasks (both lines of source and filtered views)
Find "Last Changed" line of source code / Ctrl+J
Mark lines – including individual names
Find Marked Lines / Find named Marked Lines
Syntax errors as you type
Syntax check in the editor

39. Hot-Key Combinations – Part 1
RDz Hot Keys
Description
ISPF Equivalent
Ctrl+Home
Top of file
Max PF7
Ctrl+End
Bottom of file
Max PF8
Ctrl+2
Open same program in split-screen view
PF2 - then open the source member
Ctrl+0 (zero) …or… Ctrl+F4
Close edit session
PF3 (or CAN on the command line)
Ctrl+S
Save edit session
Save
Ctrl+P
Print current file
N/A
Ctrl+T
Make current line top line in the editor
PF7/PF8 with CSR as your paging option
PgUp
Page up one physical page of source at a time
PF7
PgDn
Page down one page of source at a time
PF8
PF7/PF8
Page up/down one page of source at a time
Up/Down –
Right/Left Arrows
Scroll one character at a time through your source:
Up/Down – Right/Left
Up/Down/Right/Left Arrows
Ctrl+PgDn
Page Right
PF11
Ctrl+PgUp
Page Left
PF10
Ctrl+L
Open Line Number feature
Ctrl+G
Filters out all COBOL code except the four divisions
Prefix area exclude
Ctrl+W
Show all filtered lines
RES
Shift+F10
Show the Context (popup) menu
Ctrl+Shift+L
Show the list of all Hot-Key Combinations
Escape
Cursor jumps to the command line

40. Hot-Key Combinations – Part 2
RDz Hot Keys
Description
ISPF Equivalent
Ctrl+F
Opens Find/Replace Dialog
Find/Change ISPF Commands
Ctrl+Z
Undo last change
UNDO (if Recovery On)
Ctrl+Y
Redo last change
N/A
Shift+Down Arrow
Select text from the current cursor position downward in the source file
Prefix Area Command: CC … CC PF7
Shift+Up Arrow
Select text from the current cursor position upward in the source file
Ctrl+Shift+Right Arrow
Select word
Shift+End
Select text from cursor position to end of line
Shift+Home
Select text from cursor position to beginning of line
Ctrl+A
Select all text in the source file
Prefix Area Command: C99999
Alt+U
Unselect selected text
Ctrl+C
Copy currently selected source lines
Prefix Area Command: C or CC
Ctrl+X
Cut currently selected source lines
Prefix Area Command: M or MM
Ctrl+V
Paste currently copied source lines
Prefix Area Command: A or B
Ctrl+J
Find previous edit change
Ctrl+Right
Locates cursor at the beginning of the next COBOL word
Ctrl+Backspace
Delete Current line
Prefix Area Command: D
Ctrl+D
Repeat Current line
Prefix Area Command: R
Ctrl+/ or Ctrl+\
Comment or Uncomment current line
Ctrl+Enter
Insert new line
Prefix Area Command: TS or I
Ctrl+Delete
Delete (Truncate) to end of line
Erase (EOF) key
F5 and F6
Find and Repeat Find, Change and Repeat Change
PF5 / PF6 F2
Delete COBOL word to the right of the cursor position