|
I have been looking at the IBM command FNDSTRPDM2 in QPDA designed for multi-file and multi-library string searches. I am really liking this command and I think it is a clever idea to use a list of libraries, files, and members to search using entries contained in a member in a source file. For example, LIB1 QRPGLESRC *ALL LIB2 *ALL *ALL Would search LIB1 for all members matching the string in file QRPGLESRC. Then LIB2 for all files and all members. I suppose you could use *all *all *all but you would probably want to submit to batch with SBMJOB for some of these that might take awhile. WDSC will have a popup search that will use this command for multi-file searches and I think this is a another step in the right direction. Again, we probably want to be aware of running this in batch. Search the WDSCI-L midrange archives for "FNDSTRPDM2" for a small discussion on this functionality. I think this command was added recently. Not sure when but I think at least V5R1 or earlier. Excellent! The only issue is that the help says that *LIBL and *CURLIB are options for the library but when I enter *LIBL or *CURLIB it says not allowed. Are there plans to make the command match the help? Also, I think this command is best submitted in batch due to how long it could take. Since QPDA is added to the library list when starting PDM, SBMJOB CMD(FNDSTRPDM2...) does not find this command even though QPDA is currently in the library list. The SBMJOB is using the job description of the user profile and QPDA is not in this library list. Should I add QPDA to my job description? Would it be better for the FNDSTRPDM2 or even FNDSTRPDM (from command line) to have a batch option that would submit itself to batch after doing an ADDLIBLE of QPDA? Thanks, Craig Strong
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.