Re: SEU Search options

John

Try prompting opt 25 once with the OPTION parameter set to *DSP.

The next time you do it, that OPTION should be there. Then change OPTION to *NONE and set PRTRCDS to *ALL and PARM to *EVENTF.

Then do a 25 again and see what you see.

You might do the same kinds of thing with a mix of opt 25 and FNDSTRPDM from a command line.

Vern

On 3/4/2015 9:55 AM, John Yeung wrote:

On Wed, Mar 4, 2015 at 7:03 AM, CRPence <CRPbottle@xxxxxxxxx> wrote:

The feature is PDM, and AFaIK [and seems confirmed by testing that] the
effect is also\therefore the PDM. The /same/ effect is seen after having
performed a Find String Using PDM (FNDSTRPDM) request from a command-line
invocation;

I have no reason to doubt you, but I have not observed the same behavior.

When I invoke FNDSTRPDM at the command line, it doesn't affect the
parameters that show up when I subsequently use option 25 from PDM
(working with members).

In fact, that is the very reason I altered my workflow years ago to
sometimes use option 25 and sometimes use the command directly.
(Typically, I will use option 25, repeated down the list with F13,
when I want to view matching members interactively; and use the
command directly when I want to print a list of matching members.)

It's certainly possible that the system I'm using is configured
differently than what other folks have. We're on 7.1. I'm happy to
answer other questions if folks tell me how to get the information
from my system (like what's the proper parameter for DSPSYSVAL or
whatever).

John Y.