Re: grep question - maybe

yeah. i started with fndstrpdm, but i have to build a cl for it to handles errors and such. i was hoping for a 1 stop shop.

it also seems grep doesnt like relational db's. when i run it over a flat file, it works fine. running it over PF with fields give me "not supported" message.

oh well, was worth a shot.

On 1/16/2016 2:35 PM, John Yeung wrote:

On Sat, Jan 16, 2016 at 1:56 PM, tim <iseriesstuff@xxxxxxxxx> wrote:

i have gotten this so far, but its not returning the information i know
exists:

DSPFD FILE(datalibray*ALL)
TYPE(*MBRLIST)
OUTPUT(*OUTFILE)
OUTFILE(TIM/ALLFILES)

db2 "SELECT '/QSYS.LIB/' || trim(MLLIB) || '.LIB/' || trim(MLFILE) ||
'.FILE/' || trim(MLNAME) || '.MBR' FROM tim.allfiles
WHERE MLSEU=' ' and MLFTYP='P'"
| grep 'JUDY'

Even supposing grep is the proper tool for this, you wouldn't want to
pipe a list of the file names to it, you would want to just issue the
grep command directly, with a wildcard in the file name parameter
(second positional parameter). It's designed to work with multiple
files in a directory as its "natural" workflow.

But as you're searching physical files rather than stream files, I
think the more appropriate tool is FNDSTRPDM. You can either issue
that as a CL command, preferably as part of a SBMJOB if you're looking
through a lot of files, or interactively in PDM.

John Y.