Re: Is there an alternative to FNDSTRPDM?

V5R4M0
TIA
Guy




"SJL"
<sjl_abc@xxxxxxxxxxx To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> cc:
Sent by: Subject: Re: Is there an alternative to FNDSTRPDM?
midrange-l-bounces@m
idrange.com


12/17/2007 01:25 PM
Please respond to
Midrange Systems
Technical Discussion






Guy -
What version of the Operating system are you on?
- Steve

----- Original Message -----
From: <GUY_HENZA@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Saturday, December 15, 2007 11:01 AM
Subject: Re: Is there an alternative to FNDSTRPDM?

Steve

I just got a project to search and document all OVRPRTF commands. I sure
could use your program. Please email it to me at
guy_henza@xxxxxxxxxxxxxx

Thank you,

Guy



Glenn -

I assume in (2) that you are searching source code.

A few years back I created a command called FNDSTR that lets you specify
multiple search strings at a time for searching source members, but
currently it can only search one source file at a time by specifying a
specific
member name or *ALL members.

The main program is old RPG/400 code but it works well for me and I now

use

it instead of FNDSTRPDM since my command allows you to specify multiple
search strings (up to 20 25-byte search arguments) in one search pass
whereas FNDSTRPDM only allows one search argument.

It produces two simple reports:
One report shows a list of the source members in which the search strings
were found, the other report shows the member name, source statement
number,
and source statement containing the search string.

I can save the command and its related objects off to a save file and

send

it to you, if you are interested in trying it out.

BTW, it wouldn't be very difficult to modify it to search multiple source
files as well, by turning the SRCFILE parameter into a list parameter,
changing the CPP to process a list of source files instead of a single
source file as it currently does.

Regards,
Steve

----- Original Message ----- From: "Glenn Gundermann"

<ggundermann@xxxxxx>

To: <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, August 29, 2007 3:44 PM
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
ggundermann@xxxxxx
Cell: (647) 272-3295
--