Using Filters in the Remote Systems LPEX Editor

April 7, 2004 Hey, Ted

I have recently started to use the WebSphere Development Studio client (WDSc) LPEX editor to maintain RPG programs, and so far I am enjoying the experience. I would like to share a tip with readers of Four Hundred Guru who, like me, are working their way through the LPEX learning curve.

–Lynn

When editing with SEU, I often use the X and XX line commands to exclude lines that I do not wish to see. After issuing these commands, I can use SEU’s Find command or the Find/Change Options menu to display selected lines. LPEX has additional filtering capabilities that put SEU to shame.

One technique I have found helpful is to find all instances of a text string. Drag the mouse across a section of text to highlight it. Right-click and choose “filter selection” from the pop-up menu. LPEX displays only the lines that contain the selected text.

Another way to filter lines is by function. Right-click the editing session and choose “filter view” from the pop-up menu. A second pop-up menu allows you to select from the following options:

• By date: Display lines that were modified before, on, or after a certain date, or between a range of dates.

• Code: Display only executable code. Comments are not shown.

• Comments: Display comments only. Executable code is not shown.

• Control: Display program-control commands, such as do loops, if groups, and calls to subroutines.

• Procedures: Display beginning and ending lines of subprocedures.

• SQL statements: Display SQL statements only.

• Subroutines: Display BEGSR and ENDSR op codes.

LPEX places a small box with a plus (+) sign in it immediately before the sequence number of each displayed line. Clicking the plus sign displays the hidden lines that follow.

To remove the filter and display all lines, right-click the source member and choose “show all” from the pop-up menu.