Re: Search OS/400 Physical Files

Quoting Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>:

Shannon ODonnell wrote:

Yup

From: Dave Odom

Vern, et al,

I think what Shannon is looking for and I for sure am, is a native i5/OS
Search function that allows me to put in a character string or whatever and
*ALL libraries, if I so desire, and have it search ALL files in all
libraries, particularly source or physical files and have it function like
the Search function in Windoz. I have entered STRPDM, I have pulled up a
list of objects from all libraries, I have put in 25 in the option field of
the first on the list (shouldn't have to do this if I want to search all
objects in one or more libraries in the first place) and I pressed enter. I
get "Option 25 not valid". So, I then tried WRKF. I say all files, all
libs, PF. I get a list. I put in 25 in the option field of the first
file, I get "Specified option number not allowed". I have *ALLOBJ and am a
SECADM. So, I don't see ANYTHING that allows me to do a Windoz like search
on all objects for a character string or anything like it. What am I
missing?

This is another one of those discussion best left avoided simply because
they're rather frivolous, but maybe I can interject a teeny bit of sanity.

First, nobody I know of searches all of a Windows machine starting at
the root. Why? Because it takes forever.

So, are you really asking to search every file in every library on the
i? I doubt.it. Usually you're asking to search a few libraries. And
are you really asking to search physical files, or just source members?
Because searching physical files for a text string seems to me to be an
awfully rare occurrence, and one better suited to SQL.

So I'm going to limit my response to source searching. Searching a
library is damned simple, even from the green screen. Do a WRKOBJPDM,
limit it to objects of type *FILE, attribute PF-SRC. Piece of cake:

WRKOBJPDM LIB(&N) OBJTYPE(*FILE) OBJATR('PF-SRC')

Now, do a 25, F13, Enter. Type in your scan string. Done.

Now, if you *insist* that you want to search every file in every library
(and I reiterate that if this is something you do regularly, then you've
got much larger issue, but what the heck), then just use the search
capabilities of RDi. It will allow you to do a massive search, but be
warned it will take a while. But then again, search on a string
starting at root on Windows and let me know what day it finishes.

Okay, I'm done.

Joe


--

I have a simple CL that does DSPOBJD to a file, reads those records back and
runs FNDSTRPDM. Our sources are confined to a few libraries. There are
multiple DSPOBJD commands in the CL to build the list of files as needed. I
use this when I need to locate either a field reference in source or even a
comment.

John McKee