×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I believe the date/time can limit a search; a quick test seems to
support that. So to limit a job name search, optionally pre-search the
history for the job [start &] stop time, and limit the search of the
receiver data by at least the job end date/time, using TOTIME() to
prevent the DSPJRN from searching past what would obviously be the last
possible entry from that job. Of course the same scanning issue exists
for the DSPLOG, but hopefully for fewer entries; e.g. only 65K --
QHSTLOGSIZ should IMO be set to the max on all systems.
If multiple searches will be made, but either a full copy of the
ENTDTA is not desired or only of interest in an actual DSPJRN, then an
OUTFILE of the DSPJRN minimizing the Entry Data Length could be used to
lookup start and end sequence numbers to be used on the DSPJRN. Maybe
better, to find/use start and end times, since my quick test did not
seem to show good benefits for sequence numbers as compared to time.
Optionally having indexed the common lookup fields to make that search
even faster, but at least SETOBJACC and parallel scan is available for
database files.
Regards, Chuck
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.
midrange.com
