MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » November 2002

Re: Finding members



fixed

Here is what you do:

    DSPFD FILE(*ALL/*ALL) TYPE(*MBRLIST) +
        OUTPUT(*OUTFILE) OUTFILE(yourlib/ALLMBRS)

Then, if you have Query/400 installed, you can just run:

    RUNQRY QRY(*NONE) FILE(yourlib/ALLMBRS) +
        RCDSLT(*YES)

Then, select records using a "pattern" such as:

    MLNAME    LIKE    '%ABC%'

Or whatever other member name "pattern" you are looking for,
such as "ABC%", etc.

Or, you can use SQL (eg. STRSQL) to query this "outfile", as in:

SELECT MBFILE, MBLIB, MBNAME, MBUPDD, MBUPDT
    FROM yourlib/MBRLST WHERE MBNAME LIKE '%ABC%'

You get the idea?

Depending on whether you use TYPE(*MBR) or *MBRLIST,
you would use field names MLNAME, MLFILE, MLLIB, etc.,
instead of MBNAME, MBFILE, etc.

So, OS/400 does have a capability to "search" across all libraries,
or only all user libraries, etc.; you just have to learn how to use the
tools! :-)

----- Original Message -----
From: "Joe Lee" <LeeJD@ah.org>
To: <midrange-l@midrange.com>
Sent: Thursday, November 07, 2002 4:31 PM
Subject: RE: Finding members


> The thing that's always bugged me is that while there are system files
> that contain all sorts of information about the objects on the system,
> even down to a list of all fields in all files on the system, there is
> no file that contains a list of the members on the system. That said it
> is a relatively simple matter to write a program that reads through the
> QADBXREF file in QSYS and run a CHKOBJ for the member for each source
> file on the system. It is also possible though slightly more difficult,
> and much more time consuming to create a program that will look for
> members with wildcards in their names.
> Joe Lee
>
>
> >>> Booth@MartinVT.com 11/07/2002 15:13:07 >>>
>
>  Aside from all of the other suggestions (which are good ones) there's
> a
> mix-up on files and members.   A member is not a file.
>
> "Members" is one of IBM's wonderfully great ideas that fell flat.  We
> have
> to live with the consequences but the consequences are minor.  You've
> hit on
> the worst consequence - how does one find a member?  Members are hard
> to
> find because they are not objects like files and libraries and
> programs.
>
> On the AS/400 I think its easier to think of things as being in object
> bags
> instead of on  an object tree.
>
>
> ---------------------------------------------------------
> Booth Martin   http://www.MartinVT.com
> Booth@MartinVT.com
> ---------------------------------------------------------
>
> -------Original Message-------
>
> From: midrange-l@midrange.com
> Date: Thursday, November 07, 2002 05:41:51 PM
> To: 'midrange-l@midrange.com'
> Subject: RE: Finding members
>
> Thanks Bonnie...however, the file (as it's called on the hp) would
> actually
> be a member on the iseries (MYLIB/MYFILE), and if my understanding is
> correct (and that's truly said with caution), then you would not see
> the
> member if you were using the WRKOBJ command...?
>
> Ray Shahan
>
> "Life is what happens while you're busy making other plans", John
> Lennon
>
> > -----Original Message-----
> > From: Bonnie Williams [SMTP:WilliamB@ccsd15.k12.il.us]
> > Sent: Thursday, November 07, 2002 4:09 PM
> > To: midrange-l@midrange.com
> > Subject: Re: Finding members
> >
> > To find a file named MYFILE anywhere on the system, type:
> > WRKOBJ OBJ(*ALL/MYFILE)
> >
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact