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



Regarding part 1:
Would specifying *USRLIBL to QUSLOBJ instead of *ALLUSR work?

Elvis

Celebrating 10-Years of SQL Performance Excellence
http://centerfieldtechnology.com/training.asp

-----Original Message-----
Subject: Is there an alternative to FNDSTRPDM?

Hi Folks,

This is a two-parter.

I'm trying to write some utilities to find hard-coded values in places
like data areas, files, etc.

1. I'm sort of happy with my utility for data areas. I'm using QUSLOBJ
to list *ALL in *ALLUSR of type *DTAARA. Then using QWCRDTAA to retrieve
the data area data and search for my string. No problem.

What I would prefer to do is to use my library list instead of *ALLUSR but
I only want the user libraries in my library list. Is there an API to
determine if the library is a user or system library or do I have to
hard-code the list of libraries found in the "Object (OBJ) - Help"?

2. I'm not sure what to do for *FILEs. I'm using QUSLOBJ to list *ALL in
<lib-parm> of type *FILE. Is there an alternative to FNDSTRPDM? When I
use system(FNDSTRPDM...) it produces a spooled file for every file and
it's just not manageable. I'm looking for an API similar to QWCRDTAA that
will retrieve the data so I can search it and only report the ones where a
match is found.

Any suggestions would be most appreciated.

Thanks,

Glenn Gundermann


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.