|
First, you CAN'T run a FNDSTRPDM across multiple source files; you have
to
run it across each one individually. You can bring up the source members
in
WRKOBJPDM and do a 25 on each one, but then you have to search every
member
in the file. Is that what you do? Or do you search the files
individually?
Do you do your WDSC search one file at a time as well? Or do you use a generic file name? Because the generic file lookup takes a little while. I'm just trying to get an idea of if you're comparing apples to apples.
Joe, In PDM when I am trying to determine the scope of a proposed change, I use WRKOBJPDM to display a list of source files, and put option 25 in the option fields of the selected source file(s), and submit the search to batch. That produces 2 reports, one showing the lines that match the search string, and the other showing the names of the source members with matches. Often I am more interested at this point with the number of source members found with matches, just to get a handle on the scope of work. While this is searching I'm doing other things. I just ran a search in RSE, using Find String on a list of selected source files. This is not the way I did it in the past, and this produces a list that appears to be much more useful. I don't know what search function I was doing in the past, but WDSC was copying individual source members from the I5 to perform the search. Perhaps I was selecting all of the members in the file, and not the file itself. Thanks for the time, Joe. This will take some investigation. However the lack of a report still keeps me tied to my PC, and make the list difficult to share. Steve Steven Morrison Fidelity Express 903-885-1283 ext. 479
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.