RE: Locking down SEU exit parameters

["Holden Tommy" <Tommy.Holden@xxxxxxxxxxxxxxxxx>]

Use DSPF instead...then you KNOW they can't screw anything up!!! 


Thanks,
Tommy Holden


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jonathan Mason
Sent: Thursday, June 28, 2007 8:30 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Locking down SEU exit parameters

Hi Mark

Why is it that the obvious solutions are the ones we never consider.
What a
fabulous idea, go to the top of the class.

I've used EDTF in the past for IFS files but had never considered it for
database files.  Perfect.

Thanks

Jonathan

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S. Waterbury
Sent: 28 June 2007 13:47
To: undisclosed-recipients:
Subject: Re: Locking down SEU exit parameters

Hi, Jonathan:

How about this, since it is just a "text" member they are editing ...

Use the EDTF command instead of STRSEU ... e.g.:

     EDTF FILE(ISS/QTXTSRC) MBR(XYZ) 

EDTF, although originally for stream files, can also edit source phyical

file members, and has only F2=Save, F3=Save/Exit, and F12=Exit, with no 
opportunity for the end user to change the member name, etc.

Regards,

Mark

> Jonathan Mason wrote:
> Does anybody know if it is possible to lock down the parameters shown
on
the
> SEU Exit screen?  
>
> I have a requirement where I need to invoke SEU so that the users can
> perform some text editing on a specific TXT member and I am concerned
that
> the user may change the member name, source file or library when they
exit
> out of SEU.
>
> Ideally I would like to be able to prevent the parameters from being
> overridden (in a similar manner to command prompting using "?-" etc)
or
> alternatively find a means of identifying the source member, file and
> library specified on the Exit screen.
>
> I thought about using an exit program, but could only find
QIBM_QSU_LCMD
> which relates to SEU line commands.
>
> Any ideas?
>
> Thanks
>
> Jonathan
>