Re: Locking down SEU exit parameters

["Michael Ryan" <michaelrtr@xxxxxxxxx>]

That's a good idea Mark. My thought would be to load the information
into a subfile and let the user make changes. PITA for things like
wrapping and such, but it would work.

On 6/28/07, Mark S. Waterbury <mark.s.waterbury@xxxxxxx> wrote:
> 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
> >
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.