Re: WDSC iSeries Search - was WDSCI-L Digest, Vol 7, Issue 245

Vern,

Yes, option 25 from WRKOBJPDM does a search on each individual
member--albeit much quicker than selecting option 25 on all the members
from WRKMBRPDM.

There is no option 25 on WRKLIBPDM. i.e., You have to drill down (option
12--work with objects) to the object level. Then you can specify option
25 on the source physical files. You would either have to do a subset
(17) to get down to the source physical files or page through the objects
and find them. That's the beauty of the search in WDSC or RDi (a.k.a.,
the workbench)--it will get down to the source files for you. However, it
currently ignores PF38-SRC files. We have lots of contemporary code in
our PF38-SRC files. It's just that our change management system was (and
still is) set up to use the old file names and we've never tried
converting them to PF-SRC.

The reason a search on a filter is so much slower, is that the workbench
has to resolve the members that you want to search. The 'iSeries search'
or Ctrl-H search is faster because it doesn't have to resolve the
individual members and individually submit a FNDSTRPDM command on each of
them. I think I checked into this a several releases ago. (Of course my
memory could be faulting me.)

Anyway, I asked to have a way to print the search results several years
ago--back when Violaine Batthish used to monitor the list and she put it
on some feature request list. I was pleasantly surprised to see a print
ability on the trial version of RDi that I looked at. I'm puzzled why
others don't have it now. Could it be only on RDi-SOA? That doesn't make
sense, but not having the print in WDSC doesn't make sense to me either.

Michael

wdsci-l-bounces@xxxxxxxxxxxx wrote on 09/01/2009 01:00:08 PM:

----- Message from Vern Hamberg <vhamberg@xxxxxxxxxxx> on Tue, 01
Sep 2009 08:24:15 -0500 -----

To:

Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] WDSC iSeries Search - was WDSCI-L Digest, Vol 7, Issue 245

There are several ways to run searches in PDM - from WRKOBJPDM it does
the entire file - from WRKMBRPDM it does individual members. Now perhaps

the search over an entire file ENDS UP doing individual members - not
sure about that. And I've not tried a search over a library in
WRKLIBPDM, to my best recollection.

Now maybe - guessing here - this is how these work differently from the
client, too - one could always check the job log of the QZRCSRVS or
whatever job for the client and see what it is trying to do.

Vern

blayman@xxxxxxxxxxxxxxx wrote:

Michael,
That is it. I would have never thought of that. If I do a

filter

search it does look in all the src files if I do a CTL-H search it

does

not. You would think they would be the same search. Thanks Bill

Bill




From:
MichaelQuigley@xxxxxxxxxx
To:
wdsci-l@xxxxxxxxxxxx
Date:
08/31/2009 10:31 PM
Subject:
Re: [WDSCI-L] WDSC iSeries Search - was WDSCI-L Digest, Vol 7, Issue

245

Sent by:
wdsci-l-bounces@xxxxxxxxxxxx



Bill,

I reported a bug several releases back that the search doesn't look at

PF38-SRC files--only PF-SRC. I was told it would be fixed in a future

release. As of WDSCi 7.0, it is not. Could this be why you're not

seeing

it search CL or DDS source?

Michael

wdsci-l-bounces@xxxxxxxxxxxx wrote on 08/31/2009 05:33:33 PM:

----- Message from blayman@xxxxxxxxxxxxxxx on Mon, 31 Aug 2009 15:
17:45 -0400 -----

To:

Websphere Development Studio Client for iSeries

<wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] WDSC iSeries Search - was WDSCI-L Digest, Vol 7, Issue

245

One thing I would in using CTL-H search I used a Q*SRC, *LIBL, all

members

and it did not search all of our source files only RPG and TXT and a
couple of others we don't have program source in. It never looked in

CL

or

DDS source, even though I expected it would. That could be why the

CTL-H

search is faster then the filter search, they don't look at the same
amount of objects. My 2 cents

Bill