× 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.



Dan

I agree, speed can be an issue. There must be a mapping, among other
things, that slows things down between the IFS and the native library
system. I wonder if the *TYPE2 IFS directory attribute can speed things up
for QSYS.LIB file system access.

I don't know what's with FNDMBR - 5 years ago, when I first used it, it was
pretty fast. YMDV (your mileage DID vary)

Cheers

Vern

At 06:43 AM 11/8/02 -0800, you wrote:
Well, that was my first brush with qshell. (Finally working on a box
that's on a supported release!)  Kinda neat.  The wildcard function is
full-featured, i.e. stuff like '*R22*' finds R22 anywhere in the member
name.  I guess PDM does that too, doesn't it?

Still, the find without a specific library named took quite awhile.  A
DSPFD *ALL/*ALL TYPE(*MBR) ran faster than STRQSH CMD('/usr/bin/find
/QSYS.LIB/ -name ''FSM*.MBR''').  If you have a logical on the outfile
like the one I described yesterday, the find capability is really fast.

I checked out the FNDMBR utility you mentioned.  Holy cow.  That thing
locked up my screen for thirty minutes.  If you exit and try it again,
it has to rebuild the whole thing.  I dunno, we don't have enough
activity creating, moving, and deleting source members that merits
having to rebuild the member list every time we use a utility like
this.

Dan


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.