lab02 rd power ibmi edit rpg

Rational Developer for Power Systems Software – Lab 2Maintaining an IBM i application using Remote Systems Explorer (RSE)

Lab 2 Exercises: Editing RPG applications using the LPEX editor

An IBM Proof of Technology

Catalog Number

© Copyright IBM Corporation, 2011

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM Software

ContentsOVERVIEW.............................................................................................................................................................4

LAB 2 EDITING RPG APPLICATIONS USING THE LPEX EDITOR...............................................................................62.1 OPENING SOURCE MEMBERS IN THE REMOTE SYSTEMS EXPLORER (RSE)..........................................................7

2.2 WORKING WITH THE LPEX EDITOR...............................................................................................................................222.3 SUMMARY..........................................................................................................................................................................79

APPENDIX A NOTICES..............................................................................................................................................................81APPENDIX B TRADEMARKS AND COPYRIGHTS...................................................................................................................83

Contents

IBM Software

Overview

This Lab is the second in a series of Labs that introduce Rational Developer for Power System Software (RD Power). The complete set of Labs show you how to edit, compile, and debug a sample IBM i application. The Labs also show how to use the RD Power Application Diagram Viewer, Screen designer, and Report Designer.

This series of Labs 1 to 9 teaches you how to maintain an IBM i application written in ILE RPG using the tools available in the Remote Systems Explorer.

The Labs 2 to 9 depend on the instructions in Lab 1. You should work through Lab 1 first to establish a connection to an IBM i server, then it is up to you whether you work on these Labs in sequence or pick one of the Labs that you are most interested in.

This Lab teaches you how to work with the tools and views in the Remote Systems Explorer (RSE) perspective that are available to update an IBM i application written in ILE RPG.

Learning objectives

Lab 2 has the following objectives:

1. Explore the views and tools in the Remote Systems Explorer (RSE) perspective.2. Customize the RSE perspective to fit your preferences for an editing environment.3. Use the LPEX editor to modify and work with ILE RPG source members.

Introduction

Before starting Lab 2 you should review the following requirements and information.

Skill level

Introductory

Audience

IBM i developer

System requirements

IBM Rational® Developer for Power Systems Software V8.0 with the RPG and COBOL Development tools for i feature and all software updates installed through the IBM Installation Manager.

IBM i 5.4, 6.1 or 7.1

Rational Developer for Power Systems Software – Lab 2: Editing RPG applications using the LPEX editor

IBM Software

Prerequisites

Basic Microsoft Windows operations such as working with the desktop and basic mouse operations such as opening folders and performing drag-and-drop operations.

It will also help if you understand DDS and ILE RPG.

This tutorial is divided into a number of Labs, each with its own learning objectives. You can choose to skip the Labs on Edit and Compile. You can go directly to this Lab if you are only interested in that part, however you need to complete LAB 1 to create a connection to an IBM i server. This connection will be used in in all of the Labs. Each Lab contains several lessons that should be completed in order for it to work as shown in the script.

Conventions used in this tutorial

• Bold font for user interface controls

• Mono-spaced font for user input and code blocks

• Italic font for variable names and glossary terms.

Icons

The following symbols appear in this document at places where additional guidance is available.

Icon Purpose Explanation

Important!This symbol calls attention to a particular step or command. For example, it might alert you to type a command carefully because it is case sensitive.

Information This symbol indicates information that might not be necessary to complete a step, but is helpful or good to know.

Trouble-shooting

This symbol indicates that you can fix a specific problem by completing the associated troubleshooting information.

Overview

IBM Software

Lab 2 Editing RPG applications using the LPEX editor

You need to complete LAB 1 before starting this lab.

Important! You should go through Lab 1 'Creating a connection and getting started with RSE' before you work on this Lab. Lab 1 contains the following information:

◦ How to start the product,◦ Which IBM i server to connect to, ◦ Which userid to use,◦ How to setup the correct library list for this lab,◦ and how to connect using your own PCOMM if

needed.

In Lab 2 you will do the following:

1) Explore the different ways that you can view source files to optimally display your application files for editing

2) Customize the LPEX Editor and explore the LPEX Editor’s language support features

Expected results

Upon completion of this tutorial you will know how to edit IBM i application source members from the Remote Systems Explorer perspective. You will also know how to customize the Remote Systems Explorer. This tutorial will prepare you for the next set of Labs where you will learn how to verify, compile and debug updates to your applications.


IBM Software

2.1 Opening source members in the Remote Systems Explorer (RSE)

This module teaches you about how to open source files so that you can edit them using the Live Parsing eXtensible editor (LPEX editor). You will explore the different ways that you can modify the editor view to optimally display your application files within the RSE perspective. You will also learn how to edit and navigate through a source member using the editor outline view.

__1. Explore the different ways that you can view source files to optimally display your application files for editing

__a. Open a member for edit from the Table view or the Remote Systems view

__b. Open another member for edit and multiple views

__i. Switch from one edit session to another

__ii. Maximize the editor space and view one member at a time or two side by side

__iii. Open multiple views of the same source member

__c. Display a structural outline of items defined in a source member

2.1.1 Opening a member for edit from the Table view or the Remote Systems view

You are going to use the LPEX Editor to edit the member MSTDSP found in the QDDSSRC source file.

Using the IBM i connection you created in Lab 1:

__1. Expand library RSELABxx if it is not already expanded.

__2. Expand file QDDSSRC in library RSELABxx.

__3. To open the file from the Remote Systems view for editing you can choose one of these methods:

__a. Double-click member MSTDSP in the QDDSSRC source file.

__b. or Right-click on the member select Open With > Remote Systems LPEX Editor from the pop-up menu.

This locks the member on the host and opens it in the local Remote Systems LPEX Editor. After you are done making changes you can save the member using either the File > Save menu option or the Ctrl+s keyboard shortcut. The locks on the member are released when you close the editor.

Lab 2

IBM Software

__4. To open the file from the Object Table view: (You can close the file and reopen it this way if you like.)

__a. Right-click the QDDSSRC source file and select select Show in Table from the pop-up menu.

This will open the Object Table view.

Once in the view you can right-click on the MSTDSP member and get the same pop-up menu actions as you would see in the Remote Systems view. Double-clicking on a member will open the member for editing in the Remote Systems LPEX Editor.


IBM Software

Troubleshooting: If the wrong pop-up menu is displayedSome entries in the Object Table view are editable and are selected for edit when you click on them. These entries will have their own menu items when you select them that apply to the cell that your are editing instead of the row that you are working with. You need to right click when you select the row or right click on the Attribute cell SRC which is not editable for the Open With menu to be displayed.

The Remote Systems LPEX Editor opens built into the workbench, with rich editing functions. It is IBM i aware and a superset of SEU. The syntax checker is ported from SEU, and the reference manuals are built-in and F1 cursor sensitive.

Lab 2

IBM Software

Tip: To open i Series members quickly, you can use the keyboard shortcut Ctrl + Shift + A, or right-click IBM i Objects and select Open Member, without the need to drill down through your IBM i Objects subsystem to find the member.

2.1.2 Opening a second source member and multiple views

Next let’s open a second member in the editor. To open a second source member:

__1. In the Remote Systems view, double-click member PAYROLL in the QRPGLESRC source file.


IBM Software

You can easily switch between the two edit session

__2. Click on each tab to switch from one edit session to another edit session.

Lab 2

IBM Software

You can easily maximize the view:

__3. Double-click the MSTDSP tab to maximize the Editor window.

__4. Double-click the MSTDSP tab again to return the view to its original size.

Tip: You can also switch between files that are open in the editor view by pressing Ctrl + F6.

You can also view the members side by side:

__5. Click on one of the tabs and drag it to the right side of the edit area. You will see this icon as

you drag it:

__6. Let go when you see a box and arrow on the right half of the edit area.

You can maximize and minimize the views in this mode as well by double clicking on one of the tabs. But you will notice that the two members in this case are always viewed side by side.


IBM Software

To return to the tabbed view so that each member can be viewed separately:

__7. Click on one of the tabs and drag it to the left tab or tab area. You will see this icon as you drag

it:

__8. Let go when you see a box and folders icon in the tab area.

You can open multiple views of the same source member while editing in the Remote Systems LPEX editor. To open multiple views of your RPG source:

__9. Double-click the PAYROLL tab in the editor to maximize the Editor window.

__10. Right-click this source in the Editor view and click View > Open new view.

Tip: You can open a maximum of five views of the same source.

Lab 2

IBM Software


IBM Software

__11. Right-click in one of the source views and select View > Next view or View > Previous view to navigate among the views.

Tip: Any changes made in one of the views will automatically update all other views of the same source.

__12. Scroll down and place the cursor at line 33 in the left view of the Payroll source.

__13. Press Enter.

Lab 2

IBM Software

A new line is inserted in both views and since the previous line is a D-spec, the new line is also marked as a D-spec.


IBM Software

__14. Define a new variable, as shown in the screen shot below, with length 10:

Now, in the view on the right, you can start using the new variable while being able to maintain your view on the left on the definition of the variable.

Lab 2

IBM Software

Another nice feature is the ability to change the way the views split. If you don't like the vertical split, you can specify to split horizontal instead. Lets try that:

__15. Right-click a source view and select View > Horizontal split to change from a vertical split of the views to a horizontal split of the views.


IBM Software

Here is how your edit view should look now:

If you want to close the extra views:

__16. Right-click the source view that you want to close: RSELABXX/QRPGLESRC(PAYROLL): 2.

__17. Select View > Close view.

Tip: This option is not available on the first view.

You have opened another member for edit and seen multiple views of members.

Lab 2

IBM Software

2.1.3 Using the Outline view of a source member

The Outline view acts as an excellent resource when you want to navigate through RPG, COBOL and DDS source in the Remote Systems LPEX editor. The Outline view displays a structural outline of items defined in the file that you currently have open in the Remote Systems LPEX editor window. With the editor active, you can expand the file structure and click various elements in the Outline view, in order to jump to that location in the source itself.

To see an Outline view of your RPG source:

__1. Click the PAYROLL tab in the editor and click Refresh on the Outline view toolbar.

Tip: If you have closed the Outline view previously, you can reset the perspective by selecting Window > Reset perspective from the workbench menu or Window > Show view > Other then expand General and click Outline in the Show view dialog.

The Outline view contains your source program in a tree view without the lines containing logic.


IBM Software

Now you want to see more details of your source member.

__2. Expand Files.

__3. Expand the MSTDSP workstation file.

__4. Expand the EMPSEL record format.

__5. Expand EMPNO.

This will display all of the source line numbers where the EMPNO field is used and (M) indicates that the field is modified at that location.

__6. Click on the 187(M) line number in the Outline view.

This will position the source editor accordingly.

Tip: Clicking a field or a variable in the Outline view will position the editor to its definition.

__7. Click the PAYROLL tab to get the PAYROLL editor window in focus for the next lesson.

You have displayed an outline of a source member while editing RPG or DDS source files.

Lab 2

IBM Software

2.2 Working with the LPEX editor

This module teaches you how to edit an RPG source member and learn about some of the Remote Systems LPEX Editor’s language support features and customization options.

Learning objectives

__1. Customize the LPEX editor

__a. Change the default settings of the LPEX Editor Parsers.

__b. Change the color settings and font used by the Editor.

__c. Change the default behavior of the Enter key.

__2. Explore the LPEX Editor’s language support features while editing an RPG source member

__a. Use SEU commands to edit source.

__b. Undo and redo source changes.

__c. View language sensitive help for the MOVE operation code.

View a list of all help contents.

Limit the search of help to specific documents.

Search the help.

__d. Request a prompt for a specification line.

Display context sensitive help for any field in the IBM i Source Prompter.

__e. View the beginning and ending of constructs in your source.

__f. Use the Find and Replace window to search for an item in your source.

__g. Filter or subset your source.

__h. Filter lines based on line type.

__i. Search through members in a source physical file.

__j. Compare different versions of a program and identify the differences.

__k. Syntax check source by line.

View help on syntax errors.


IBM Software

Introducing the LPEX editor

Your program editing tasks are simplified with the Remote Systems LPEX Editor. The editor can access source files on your workstation or your IBM i system directly. When a compilation results in errors, you can jump from the compiler messages to an editor containing the source. The editor opens with the cursor positioned at the offending source statements so that you can correct them.

Here is a list of some of the basic editor features that you would expect in a workstation editor:

Cut, copy, and paste.

Block marking of lines, characters, or rectangles with copy, move, and delete operations.

Powerful find and replace function.

Unlimited undo and redo.

In addition there are a few additional functions that you may not have seen in a workstation editor:

Token highlighting where different language constructs are highlighted using different colors to help identify them in a program.

SEU-like format-line rulers to show the purpose of each column for column-sensitive languages like RPG and DDS. These rulers can automatically update themselves to reflect the current specification.

SEU-like specification prompting for CL, RPG, and DDS.

Sequence numbers, which allow SEU-style commands in the prefix area.

Intelligent tabbing between columns for column-sensitive languages.

Automatic uppercasing for languages that expect uppercase.

Settings for column-sensitive languages that simplify text insertions and deletions.

Online language reference.

2.2.1 Changing the default editor settings

The LPEX Editor has predefined settings, but it also has an associated preferences page containing settings that you can modify. The name of the general preference category is LPEX Editor, but there are also settings that can be made that are specific to IBM i parsers and those are made in the Remote Systems LPEX Editor preference category.

You will change the default settings of Remote Systems LPEX Editor and IBM i Parsers as well as the general LPEX Editor Appearance and User Key Actions.

LPEX provides special support for insertion and deletion in column-sensitive languages.

Lab 2

IBM Software

When column-sensitive editing is selected, each column is considered as a separate entry space. For example, in a RPG source member, if you insert or delete characters from a string in the Factor 2 entry, the Result field entry will not move. The default editor preference has column-sensitive editing set as off. You can switch this support on by going to the workbench preferences window.

To set column sensitive editing:

__1. In the workbench menu, click Window > Preferences from the workbench menu.

The Preferences window opens.

__2. In the left pane of the Preferences window, expand Remote Systems.

__3. Select Remote Systems LPEX Editor.

The right pane allows you to set preferences for this feature.

__4. In the right pane of the Preferences window, select the Column sensitive editing check box.

When selected, each column is considered as a separate entry space.

__5. Click the Apply button.


IBM Software

To enable or disable autosave while editing source in the Remote Systems LPEX Editor, select or de-select the Autosave check box in the preference dialog.

By default, autosave is enabled and the value for the minutes is set to 5. You can specify a value between 1 and 60 minutes.

Note: The Autosave action will perform a local backup onto the workstation disk. It will not remotely save the member onto the IBM i server. Use the Save or Save as actions to save the member back onto the IBM i server.

Lab 2

IBM Software

We will change one other preference entry that users like to change. Adding the previous specification type to a new line when editing RPG source is not liked by all users. Here is how to change this behavior:

__6. Expand IBM i Parsers under Remote Systems and Remote Systems LPEX Editor.

__7. Select ILE RPG.

__8. Clear the Repeat previous specification type check box.

__9. Click OK on the Preferences window.

__10. Return to the Editor window.

This preference must be cleared if you want to change the Enter key behavior in the general LPEX editor preferences.


IBM Software

2.2.2 Changing the editor appearance

Other interesting preference settings are located under LPEX Editor. You can use the link at the top of the page to quickly jump to the LPEX Editor preferences. Appearance allows you to modify color settings and font used by the Editor.

To change the editor appearance:

__1. In the left pane of the Preferences window, expand LPEX Editor.

__2. Select Appearance under LPEX Editor.

__3. In the right pane under the Styles list, select formatLine.

__4. Change the Foreground color to dark green.

__5. Change Font to 12.

__6. Change Background color to light green.

Lab 2

IBM Software

Notice how your changes are reflected in the sample edit view.

Change the current line appearance to make it more visible when editing:

__7. Select currentLine under the Styles list.

This option highlights the line that the cursor is on. The option applies to all source files opened in the editor area.

__8. Change the Background color to light yellow.

__9. If you don’t like the changes you made, you can click Restore Defaults to return to the original settings.


IBM Software

2.2.3 Changing the Enter key behavior in the editor

To modify the default behavior of the Enter key:

__1. Expand LPEX Editor if not already expanded.

__2. Select User Key Actions.

The LPEX Editor has a predefined behavior for the Enter key to always add a new line and not split the line when the Enter key is pressed. To change this default behavior and have the Enter key split the line, use the following instructions:

__3. Type enter in the Key field.

Tip: The Key and Action fields are case sensitive. Make sure that the values typed in the Key and Action fields are exactly as shown.

__4. Type splitLine in the Action field.

Tip: Use the drop down list to select the value.

Lab 2

IBM Software

__5. Click the Set button.

Next let’s see the results of the customization.


IBM Software

2.2.4 Testing the editor customization

Notice that now the line the cursor selects gets highlighted with the color that you set in the preference setting for highlight current line if you kept the setting.

__1. Move the cursor to line 27, column 10.

__2. Make sure the editor is in Insert mode. If the status area shows Replace, press the Insert key.

__3. Press the space bar 3 times.

Notice that only the file name is shifted but none of the other columns to the right are effected.

__4. Press the Backspace 3 times. Once again the file name is shifted but no other columns are effected.

Next let’s see the results of splitLine.

__5. Position your cursor on line 32, in the middle of the comment text.

__6. Press the Enter key.

Lab 2

IBM Software

Troubleshooting: You may notice that splitLine does not work if you did not turn off the Enter key preferences for the ILE RPG Parser. To do this go back to the preferences page.1. Expand Remote Systems > Remote Systems LPEX

Editor > IBM i Parsers.2. Click on ILE RPG to display the preference dialog

for this language.3. Un-select the Repeat previous specification type

check box.4. Click the OK button.

The text to the right of the cursor is moved to the next line.


IBM Software

You have changed some of the default editor settings and seen the results of the changes.

Feel free to change the preferences to your preferred settings.

2.2.5 Using SEU commands in the LPEX editor

You can configure the LPEX Editor to adopt the keyboard and command personalities of many popular editors. Most editor profiles differ only in the keys and commands used to perform various editor tasks. Some base editor profiles, listed below, also add prefix information and a command area at the start of each line:

ISPF SEU XEDIT

The editor recognizes prefix commands used by these editor profiles. Depending on which profile you are using, you can enter SEU, XEDIT, or ISPF commands when the prefix area is active.

If you are an SEU expert you will appreciate the ability to use SEU commands.

To enter SEU commands:

__1. Move the cursor into the gray sequence number area (prefix area) to the left of the edit area.

__2. On any sequence number type dd.

__3. Go down a few lines and type dd again and press Enter.

Notice that the lines have been deleted.

Lab 2

IBM Software

__4. Now type i5 in the sequence number area.

__5. Make sure the cursor is within the sequence number area.

__6. Press Enter.

Five new lines are inserted.

Tip: If you press F1 in the prefix area you will get help on all of the Prefix commands that can be used wiht the seu base profile.

You have learned how to use SEU commands in the editor.

2.2.6 Requesting undo and redo operations

The editor records each set of changes you make to a file in the Editor window. The number of changes made since the last file save is displayed on the status line. If you want to undo a set of changes made to a file you use the Undo operation. You can also cancel the effects of an Undo operation by using the Redo operation.

Now you are going to undo some of the changes you just made to the file. Then you will cancel the Undo operation by using the Redo operation. Finally you will reload the source so that it is back to its original content.

__1. Click Edit > Undo from the workbench menu.

Notice that the 5 new lines disappear.


IBM Software

__2. Press Ctrl + Z to undo the last change.

Ctrl + Z is a shortcut for Edit > Undo.

Notice that the deleted lines that were deleted using Edit > Undo reappear.

__3. Click Edit > Redo from the workbench menu.

Notice that the lines are deleted again.

At this point you will reload the source from the IBM i server to make sure that it is back in its original form.

__4. Click File > Close on the workbench menu.

Tip: You can also click the X on the PAYROLL tab.

Lab 2

IBM Software

A Save Resource dialog opens asking if you want to save the latest changes.

__5. Click No.

__6. In the Remote Systems view, open the PAYROLL member in the QRPGLESRC file by double clicking on it.

You have learned how to undo and redo changes that you made to a file.

2.2.7 Invoking language sensitive help

Inside the editor, there is cursor-sensitive language-reference help available.

This help is invaluable if you cannot remember the order of fields in an RPG specification or the allowed values for a variable field. This help is available from the LPEX Editor window.


IBM Software

To receive language sensitive help, press F1 in an Editor window. If the cursor is on an operation code, you receive help for that operation code; otherwise, you receive help for the current specification.

To access language sensitive help:

__1. Position the cursor over the MOVE operation code in line 112 of the ILE RPG source.

Tip: To jump to a specific line, type the number into the editor's command entry line and press Enter.

__2. Press F1.

Language-sensitive help for the MOVE operation code appears in a Help window. Text marked in blue in the Help window contains links to detailed information about the topic.

Lab 2

IBM Software

__3. Click the link Date Data Type.

The Help page for Date Data Type is displayed.


IBM Software

__4. Explore the Help window to see what else is available. Close the Help window.

__5. Select Help > Help Contents on the workbench menu.

Lab 2

IBM Software

You can see the help that is available in the product.

To locate the language reference information for ILE RPG, in the left pane of the Help window:

__6. Expand Reference.

__7. Expand Rational Developer for Power Systems Software.

__8. Expand Language reference.

__9. Expand IBM i programming information.

__10. Expand High-level languages.

__11. Expand ILE RPG.

__12. Expand Language Reference.

Having the latest version of the manuals at your fingertips will make it easier to find programming information. There is also the option to search the help by specifying a search string. By default, the complete help will be searched.

You can limit the search scope to specific documents in order to avoid getting search results from all the documentation in the workbench.

__13. Click Search scope. The Select Search Scope dialog opens.

__14. Select Search only the following topics radio button.

__15. Click New.


IBM Software

__16. In the List name field, type MyList.

__17. Select the Reference check box to limit the search to this help area.

__18. Click the OK button on the New Search List dialog.

The Select Search Scope dialog reopens with MyList selected in the topic list.

__19. Click OK on the Select Search Scope dialog.

__20. In the Search field, type chain for example.

Lab 2

IBM Software

Searching requires a help index and it takes a bit of time to create the index in your workspace. If you don't want to wait for the index to be build, skip this step.

__21. Click GO.

The search results from the selected topic area display.

You have accessed language sensitive help.


IBM Software

2.2.8 Prompting language specifications

Now back to editing the source code, let’s look at prompting and more.

Instead of entering or changing code directly in the Editor window, you can use prompts. When you request a prompt for a specification line, a window appears where you can enter or change that line using entry fields.

To access prompts:

__1. Return to the workbench.

__2. In the Editor window move your cursor to the D-spec on line 33.

__3. Press F4. You can also click Source from the workbench menu and then click Prompt.

You see the Source Prompter at the bottom of the workbench. The Source Prompter shows the specification line broken down into its individual fields.

Lab 2

IBM Software

On the Source Prompter toolbar you can use the two push buttons to:

Disable source prompt view - toggles the display of the source prompt view.

Change to insert mode - allows you to enter and insert a new specification instead of displaying the data on the current source line for edit.

To display context sensitive help for any field in the Source Prompter:

__4. Tab to the Keywords field.

__5. Press F1 to see help for this field.

The Help window with help for the D- spec keywords opens. If it doesn’t appear automatically, you might have to bring it to the foreground by clicking on its icon on the Windows taskbar.


IBM Software

You will see words in the help that appear in a different color than the regular text. These are help links and they show that there is additional help available on that word or phrase.

__6. Click on any link to see specific help for that item.

__7. Close the Help window.

2.2.9 Indenting source

When editing ILE RPG source, it can be difficult to determine the beginning and ending of constructs. The RPG Indentation view allows you to see your source with constructs in an indented mode.

Lab 2

IBM Software

To indent source:

__1. Click on the editor tab for the PAYROLL member to make it active.

__2. Click Source > Show Indentation on the workbench menu.

You see the RPG Indentation view below the edit dialog.

You can display the RPG Indentation view as a full view:

__3. Double-click RPG Indentation tab

__4. Go to line 150.


IBM Software

The line shown on the status bar is the cursor position. In the Indent view you see some nested conditions with indented lines. As you will notice this helps to recognize the beginning and ending of these conditions.

Tip: The RPG Indentation view is Browse mode only and cannot be edited.

Lab 2

IBM Software

__5. Click the X in the top right corner of the Indentation view to close it.

__6. Double-click any of the tabs to show the editor again.

You have used the RPG Indentation view to see the beginning and ending of constructs.

2.2.10 Finding and replacing text

The LPEX Editor also has a powerful find and replace text feature. You use the Find and Replace window to search for an item. You can search for a word, a partial word, or a sequence of such. You can also enter a pattern you want to match, provided that the pattern follows the rules of regular expression. You can replace the found search item. If the entered text or pattern is found, the cursor moves according to your chosen search direction, either to the next or previous occurrence of the search item. It replaces the found text according to your selections.

To find and replace text:

__1. Click anywhere in the editor to give it focus then press Ctrl + Home to go to the top of the file.

Tip: When you press Ctrl + Home to go to the top of a file or Ctrl + End to go to the bottom of a file, a quick mark is set at your cursor position. This allows you to return to that line by pressing Alt + Q. Ctrl + Q will set a quick mark.

__2. Click Edit > Find/Replace from the workbench menu or press Ctrl + F.

The Find/Replace window opens at the bottom of the Editor window.


IBM Software

At the bottom of this window, you will notice that you have some options to select from. For example, you can search only in certain columns. You want to find the first occurrence of BEGSR.

__3. In the Find field, enter BEGSR to find the start of a subroutine.

__4. Make sure the Replace field is blank.

You would use this field for text replacement.

Lab 2

IBM Software

The Editor moves the active line to line 52, which contains the first BEGSR phrase in the file.

__5. Click Next to go to the next location of BEGSR in the file.


IBM Software

__6. Click in the Editor window to close the Find/Replace window.

Lab 2

IBM Software

You have searched for a string in your source using the Find/Replace window. Next let's do some filtering.

2.2.11 Filtering lines by string

The editor allows you to filter or subset your source so that you see only lines containing a given string. Filtering lines makes it quick and easy to find lines without having to scroll through your source.

To filter source by string:

__1. Double-click the variable EMPAPL in the Editor window in order to select it.

__2. Select Edit > Selected > Filter Selection from the workbench menu.


IBM Software

Lab 2

IBM Software

A compressed source view is shown. It only displays the lines that contain the string EMPAPL. Plus signs in front of the line numbers allow to expand the source lines following the line containing the string.

The number of occurrences is shown at the botton of the editor view.

To expand the section of source after line 79 up to the next occurrence of the string:

__3. Expand line 79.


IBM Software

This expands the section up to the next instance of EMPAPL.

Now you want to show the entire source again:

__4. Click Edit > Show all from the workbench menu, or right click in the editor and select Show all from the context menu, or press Ctrl + W.

The entire source member is displayed again.

You have filtered your source so that you see only lines containing a given string.

2.2.12 Filtering lines by type

To help you navigate quickly through your ILE RPG source, the editor allows you to filter lines based on the line type. Imagine you want to see where all the subroutines are defined in your source.

To filter lines by type:

__1. Right-click in the Editor view for the PAYROLL member.

__2. Click Filter view > Subroutines in the context menu.

Lab 2

IBM Software


IBM Software

All source lines containing the BEGSR or ENDSR operation codes are displayed allowing you to move quickly and easily to the desired subroutine in your file.

Lab 2

IBM Software

__3. Expand the subroutine declaration for CHGCDE (line 444) to show all lines in this subroutine.

Now you could work with the source inside this subroutine.


IBM Software

__4. Right-click in the Editor window and click Show all on the context menu to show all lines in the edit view again.

You have filtered lines in your source by line type.

2.2.13 Searching multiple files

If you would like to search through the members in a source physical file or through the files in a local directory, you can use the Search tool. The Multi-File Search utility allows you to search for a particular string of text in many members on the host. This function can also be used on local files.

You need to change the current library for your RSE job to your development library so the results of the SEARCH are placed in this library and not into the default current library.

To change the current library:

__1. In the RSE view, right click on the Library List filter.

__2. Click on the Change Current Library action.

Lab 2

IBM Software

In the Change Current Library dialog:

__3. Type in the library name RSELABXX.

__4. Click the OK button.

You are done setting the current library. RSELABxx now shows a decorator (a little green star) that indicates this is the current library.

To search multiple files:

__5. Click Search --> IBM i on the workbench menu.


IBM Software

The Search window opens.

__6. In the Search string field, type ENHRS.

The Connection field should contain your IBM i server name, otherwise enter it there.

__7. Under Target in the Library field, type RSELABXX.

__8. Under Target in the File field, type QDDSSRC to search all members in this source physical file.

__9. Under Target in the Member field, select *ALL.

__10. Click Search.

Lab 2

IBM Software

The Multi-File Search window lists all the lines in all the files that reference ENHRS.

__11. Double-click the last line in the list at

A ENHRS 3 1 TEXT(’EMPLOYEE NORMAL WEEK HOURS’)


IBM Software

The member REFMST is automatically loaded into the editor and the cursor is placed on the correct line.

__12. Click the X in the REFMST tab to close the REFMST file.

You have searched through members in a source physical file.

2.2.14 Comparing files using the Remote Systems Explorer

If your product undergoes many changes, you will find the Compare utility useful. It allows you to compare different versions of a program and find the differences.

Using the compare utility in the workbench you can view the differences between two files by comparing them. You can compare different files and you can compare versions in the workbench with versions in the repository or with the local edit history.

Lab 2

IBM Software

After a comparison is carried out, the Compare Editor opens in the editor area. In the Compare Editor, you can browse through all the differences and copy highlighted differences between the compared resources. You can save changes to resources that are made in the comparison editor.

Tip: Make sure all lines show in the source before starting the Compare tool.

First let’s setup some preferences to get the best results from the Compare tool:

__1. Click Window > Preferences from the workbench menu.

The Preferences window opens.

__2. In the left pane of the Preferences window, expand LPEX Editor.

__3. Click Compare under LPEX Editor. In the right pane of the Preferences window make sure that the Ignore all blanks check box is selected.

__4. Click OK in the Preferences window.


IBM Software

Back in the Editor window of the PAYROLL member:

__5. Double-click the PAYROLL tab to show the edit view in full screen mode.

__6. Click Edit > Compare to file on the workbench menu.

The Compare window opens.

__7. Expand your connection.

__8. Expand *LIBL.

__9. Expand RSELABXX.

__10. Expand QRPGLESRC.

Lab 2

IBM Software

__11. Select member PAYROLLG.

__12. Click OK.

The editor now will show the differences of these two members PAYROLL and PAYROLLG.

You can move from mismatch to mismatch by right-clicking the source and selecting Compare > Next Mismatch, or by using Ctrl + Shift + N.

Mismatches in PAYROLL and PAYROLLG are highlighted in different colors so that you know where the mismatched lines are in each file.


IBM Software

__13. Click Ctrl + Shift + N to find the next mismatch.

Lab 2

IBM Software

Next, end the compare session:

__14. Right-click the source and select Compare > Clear.

You have compared different versions of the program and found the differences.

There is a second compare tool that provides a different user interface. It is the built-in Eclipse compare tool. You can decide which of the two tools you prefer and use in your day-to-day work.

This tool is not based on the editor so you actually invoke it in the RSE view.

__15. Select the PAYROLL member in source file QRPGLESRC in library RSELABXX.

To select a second member to compare with:

__16. Press the CTRL key then select member PAYROLLG in the same source file.

__17. Now right click and select the Compare with > Each other actions on the content menu.


IBM Software

Lab 2

IBM Software

The compare editor displays. It is best to maximize this view:

__18. Double-click on the Compare editor tab.

You see both members side by side. The differences between the members are marked by markers in the right side bar. The tool buttons allow you to position to next or previous line that has a difference.

The editor is positioned at the first difference. In order to position it to the next:

__19. Click on the Next Difference button.


IBM Software

Lab 2

IBM Software

You can now see the next line that has differences.

To close the Compare Editor:

__20. Click the X on the Editor tab.


IBM Software

Let's have a look at the syntax checker.

2.2.15 Checking syntax

One of the powerful features that the LPEX Editor shares with SEU is its ability to syntax check your source. Syntax checking can be done either when the cursor leaves each line of source. It can also be done all at once on either the currently selected source or on the entire source member.

Lab 2

IBM Software

Now you will create a syntax error and watch for the prompt to correct it. To syntax check the file:

__1. In the PAYROLL Editor window, move the cursor to line 211 by either typing the line number in the sequence number column or scrolling down.

__2. Append an X to the EXSR op-code to make it EXSRX.

__3. Move the cursor off of the line.


IBM Software

An error message appears to draw attention to the error.

__4. Move the cursor onto the pink error message.

__5. Press F1.

Lab 2

IBM Software

This opens a window with second level help for the error.

__6. Close the Help window.

__7. Change EXSRX to EXSR to correct the error or you can use Edit > Undo to undo the error.

__8. Move the cursor off the line you just fixed.

The error message is automatically removed from the editor.


IBM Software

Tip: You can toggle automatic syntax checking. Click Window > Preferences from the workbench menu and then expand Remote Systems > Remote Systems LPEX Editor > IBM i Parsers. In the left pane of the Preferences window, select the language you want to change the settings for and then select or de-select the Automatic syntax checking check box. Click OK.

Tip: You can syntax check the whole source member currently in the editor by clicking Source > Syntax Check All.

Lab 2

IBM Software

2.3 Summary

Now you are ready to use the Remote Systems LPEX Editor to edit the source members.

Congratulations!

You have successfully completed Lab 2: Editing RPG applications using the LPEX editor.

Feel free to explore all the Labs 1 to 9 that are available.

More information and material can be found at:

RPG CAFE at: http://www-949.ibm.com/software/rational/cafe/community/rpg

Look for the RD Power hub on the RPG CAFE page or at:

https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityview?communityUuid=49773f8f-a20d-4816-86f2-44a2d862dbc1


http://www-949.ibm.com/software/rational/cafe/community/rpg



IBM Software

The Rational Developer for Power Systems Software product page at:

http://www.ibm.com/software/rational/products/rdp/

The Rational Developer for Power Systems Software support page at:

http://www.ibm.com/support/entry/portal/Overview/Software/Rational/Rational_Developer_for_Power_Systems_Software

IBM User Communities at: http://www.ibm.com/community/

The IBM Education Assistant Web site integrates narrated presentations, demonstrations, tutorials, and resource links to help you use IBM products successfully. The IBM Education Assistant Web site is located at: http://www.ibm.com/software/info/education/assistant/

Enjoy working with Rational Developer for Power Systems Software!

Lab 2

http://www.ibm.com/software/info/education/assistant/

http://www.ibm.com/community/



http://www.ibm.com/software/rational/products/rdp/

IBM Software

Appendix A Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.


IBM Software

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. All references to fictitious companies or individuals are used for illustration purposes only.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Appendix

IBM Software

Appendix B Trademarks and copyrights

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

IBM AIX CICS ClearCase ClearQuest CloudscapeCube Views DB2 developerWorks DRDA IMS IMS/ESAInformix Lotus Lotus Workflow MQSeries OmniFindRational Redbooks Red Brick RequisitePro System iSystem z Tivoli WebSphere Workplace System p

Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. See Java Guidelines

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.

IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.

Other company, product and service names may be trademarks or service marks of others.


© Copyright IBM Corporation 2011

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 and ibm.com are trademarks or registered

trademarks of International Business Machines Corporation in the

United States, other countries, or both. If these and other IBM

trademarked terms are marked on their first occurrence in this

information with a trademark symbol (® or ™), these symbols

indicate U.S. registered or common law trademarks owned by IBM at

the time this information was published. Such trademarks may also

be registered or common law trademarks in other countries. A current

list of IBM trademarks is available on the Web at “Copyright and

trademark information” at ibm.com/legal/copytrade.shtml

Other company, product and service names may be trademarks or

service marks of others.

lab02 rd power ibmi edit rpg

Documents