Locking down SEU exit parameters

I wrote an RPG program that provides the ability to edit a text member
with Add, Delete, Copy, Move features not unlike SEU, but it has none of
the other features. Should be just what you need.

You can call it in browse or update mode and the name of the library,
file and member must be set using your own code before you call it.

I send that with some software so that users can change an INI like
member containing tailoring variables when they don't have SEU on some
minimum in-store machines.

If you are interested send me an email about how I can get the code to
you.

Regards
Steve Moland
Access Paths Inc
12 Parmenter Rd Unit C4
Londonderry NH 03053
603 845-0190 Ext 2
steve@xxxxxxxxxxx

message: 10
date: Thu, 28 Jun 2007 10:56:48 +0100
from: "Jonathan Mason" <jonathan.mason@xxxxxxxxxxxxxxxx>
subject: Locking down SEU exit parameters

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