|
If most source members were already converted to HTML into the IFS, would using a search engine be that much faster than using FNDSTRPDM2 or FNDSTRPDM to search for strings? Would we be using the memory of the iSeries like FNDSTRPDM or the PC memory? Would this tie up the PC or possibly the iSeries for quite awhile or is it even more more efficient? Could we have a job that runs every morning to convert any new or changed source members to HTML and then search HTML objects for any deleted members in QSYS.LIB and delete those HTML members (keep in sync)? My initial reaction to all this was that I didn't see how searching HTML would be faster than searching members directly. I am now reminded of how fast searching for strings occurs on this midrange list and how Mark Phippard is sharp. Does anyone know of a way or free utility to convert source to HTML (or how it would look)? How would we go about indexing the source code and using the web interface. I don't think I have the time or confidence to try something new soon but I would like some help in thinking about this for the future. If it is faster, then maybe WDSC can consider exploiting this method, assuming with some setup and more storage of course. Is the web engine we are talking about the iSeries Webserver Search Engine? Seen here: http://www-1.ibm.com/servers/eserver/iseries/software/http/services/search.html How might this be used? Any insight or comments would be greatly appreciated. Thanks, Craig Strong ** Mark wrote: If fast member searches are that critical why not do something like convert your source to HTML when it is put into production and place it in the IFS. Then use a search engine to index the source code and provide a web interface for searching your source? I do not know if anyone has written any wholesale utilities to convert source to HTML, but the LPEX editor within WDSC can do it. Mark
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.