Difference between revisions of "WDSC tips/Find"

From MidrangeWiki
Jump to: navigation, search
m (fix link)
m (fix link)
Line 17: Line 17:
===Find Tips ===
===Find Tips ===
original post [http://archive.midrange.com/wdsci-l/200702/msg00067.html]
original post [http://archive.midrange.com/wdsci-l/200702/msg00067.html]
Check [[WDSC tips/Editor#Editor Commands|Command line find]] 
Check [[WDSC Find Tips]]
Check [[WDSC Find Tips]]

Revision as of 00:06, 13 June 2008

Scan for a date when source lines were changed (like F14 in SEU)

original post [1]

  • You could issue the "locate sequenceText" command (in the command line at the case of the RSE editor or press ESC to enable command line), then invoke it repeatedly from the LPEX command line (UP arrow key, Enter).
  • example locate sequenceText 071201 to 071231
  • You can filter by date. Right-click in the source and you can filter by date. ref [2]

Locate is an Editor command.

There is more find info at WDSC Find Tips

Return to #TOP

Find Tips

original post [3]

Check Command line find

Check WDSC Find Tips

Check Searching for text

  • In WDSC
  • Click Help,
  • Click Help contents
  • Search on 'Regular Expression Grammar',
  • click on 'Regular Expression Grammar to see ALL the codes.
  • This is very useful when you tick the 'Regular Expression' check box in the LPEX Editor EDIT,Find/Replace.

eg. To find all lines that have BEGSR or EXSR or ENDSR type BEGSR|ENDSR|EXSR into the find box , make sure the 'Regular Expression' checkbox is ticked then click on ALL. You will see the calling structure of the subroutines. (This does not work with procedure calls)

Return to #TOP

Find Field usage (for SQL where OUTLINE doesnt work)

original post [4]

  • To see where a field is used,
  • double click (select) the field name,
  • then right click, Selected->Filter Selected.
  • If you're command-line oriented, you can do the same thing with 'findText all field_name'
  • Ctrl-W to go back to the normal view or 'expandAll on command-line

Return to #TOP