Re: Find/Replace in multiple source members

That's just a bug Greg - have you reported it? It is hardly a product design deficiency.

And I'm nowhere near convinced that paging though putting 3s against source members etc. is any easier than selecting multiples and drag/drop onto the target file.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Apr 13, 2018, at 10:23 AM, Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Matt,

I was almost there yesterday... I was out in my "workspace" looking for the members from my member filter. I was going to use Notepad++ to find/replace.

It really shouldn't be this hard. There are several things that a just easier/quicker in PDM still - this included. Try copying source members to another source file... any that have an apostrophe in the description will fail to copy.

Greg

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Tyler, Matt
Sent: Thursday, April 12, 2018 6:02 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Find/Replace in multiple source members

Greg, What I do is the following but it takes bit more set up but once you have the steps down its becomes easy the next time you need to replace a lot of source.

0. You will need to check out ALL source to be modified, so you may want to do these steps twice, once to get a list again to replace the source code.
1. search for all members to change by using a rough search match condition, e.g., get as many possible matches just to ensure you cover your bases.
a. It does not matter if you use IBM or iSphere search at this point but with iSphere you better your chances of correct matches if you know regular expressions.
2. Open all or as many as you feel RDi can handle for you at one time. No need to keep them open just down load them. This loads the local source edit cache. Close all opened members.
3. Open search again but this time use the "File Search" tab. Place the same search criteria you used before or make it more specific if you used a broader search. In the Scope section create a "Working Set" by clicking on the Choose button. Then click New. Select the type of resource and select next. Scroll to the "RemoteSystemTempFiles" project and expand. Keep expanding until you find the folder that references your server source library where you have the code checked out for change. We use an IASP so I also have to expand the reference to that. Name your work set then click Finish.
4. Select that work set from the list.
5. Ensure the radio button is set on the "Working Set" item. Then activate the search.

Once it's done you get another list. From this list you can select entries to perform search and replace over (only if you have the members checked out from production source). The search and replace opens the member from the local cache and updates the code. You should be able to just save all and have the source pushed back to the server. Not the best but it's better than the refactor open added to RDi especially when you have dozens and dozens of source members to modify.

** Note
I have yet to follow these steps on version 9.6.0.1 but I see no reason they won't work still.
If you use iSphere search you can save the results as a RSE filter. Then create a User option that performs your CMS check out if it's one that resides on the IBM I (we use Rocket Aldon LM(i)).


-Matt

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.