Re: SEU Search options -- WDSCI-L

Hi Greg

I suspect nothing is quite so simple as we might like.

A further step you could do in PDM is 25 F13 and then put the parameters you want to set on the command line - they will apply to every evocation of the FNDSTRPDM command.

so you could have a User Option that runs FNDSTRPDM, then F13, then instead of an F4, put things like OPTION(*DSP) on the command line, or PRTRCDS(*NONE) or PARM(' ')

Opt 25 is not promptable (F4 gets an error message), so you'd need the user option that is built around FNDSTRPDM - here's my example for working running it from
WRKOBJPDM - FNDSTRPDM FILE(&L/&N) MBR(*ALL)
- and on the command line,
string('v') option(*dsp) parm(' ')

There are other possiblities, and you need a different user option for running it over WRKMBRPDM

HTH
Vern

On 3/4/2015 3:37 PM, Greg Wilburn wrote:

I can see where a UDO would be a descent work-around. Just tough after 15+ years of "25 <F13>"... I did lose some of those when we upgraded from an old 5.4 box to a new 7.1 box.

I just don't understand why RDi has to mess with the settings at all. In fact, I can recreate the scenario where it does NOT change the find parameters in PDM. If I'm actually in PDM on the green screen when I do a Text Search in RDi, nothing changes in PDM option 25.

So why not just "tell RDi" that the user profile is in PDM?

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Wednesday, March 04, 2015 2:44 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] SEU Search options

Good point - the existence of this easily-obtained plug-in mitigates
against IBM making a change - and that's fine. They have to use limited
resources wisely, just as all the rest of us do.

Now Edmund, do NOT listen to me!! :)

Vern

On 3/4/2015 12:29 PM, Jon Paris wrote:

Slightly off kilter question.

Why with the advent of iSphere with its waaaaayyyyyy faster search speeds and more flexible options is anybody still using the built-in search? I have't used it once since I installed iSphere.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Mar 4, 2015, at 1:25 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote:

Ah I did miss that he said PDM - yes, doable, but I sometimes use the *CHG option, sometimes the *DSP, sometimes case-sensitive, sometimes not - I know I could prompt a user option, too, so maybe this would be enough of a workaround. We'll see if Greg thinks so.

I've no problem with leveraging something like FNDSTRPDM in RDi, just that it still would be good if it had no side-effect on my use of the command in PDM.

Later
Vern

On 3/4/2015 12:15 PM, John Yeung wrote:

On Wed, Mar 4, 2015 at 1:03 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote:

[Re: Doug's suggestion of defining one's own PDM options]

maybe, but i only use opt 25 in PDM on green screen - it doesn't get around
the issue that I can see to add a UDO (new acronym?). And I just don't like
having the *EVENTF parm and the PRTRVDS set to Y in the opt 25 PNLGRP, etc.

But tell me more that i'm not seeing!

I can't be sure, but I think what Doug is suggesting is to change your
workflow on the green screen. That is, for now you have to accept
that searching from RDi is going to affect the parameters for Option
25. So don't use Option 25. Instead, use your own custom PDM option
that has some of the parameters prepopulated the way you like them.
If you have a few different usage patterns, you may want to create a
few different custom options to accommodate them.

John Y.

--
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: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.