Re: SEU vs. RDi vs. ?

["Michael Ryan" <michaelrtr@xxxxxxxxx>]

Realize that SEU is much more similiar to ISPF than RDi. Not that the
RDi is a bad thing, but you'll need to learn it...just like the i
programmers that have made the change to RDi or WDSc.

On Fri, Dec 5, 2008 at 10:29 AM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
> Definitely go with WDSCi, or it's replacement RDi.
>
> At IBM i 6.1, you have to choose between SEU and RDi.  They are both per seat.
>
> Get an RDi license for your developers and a couple of SEU ones for
> quick emergency fixes while the system is in a restricted state.
> Although honestly, you can do with SEU.  Given that the EDTF command
> will edit source members.
>
> HTH,
> Charles
>
>
> On Fri, Dec 5, 2008 at 10:06 AM, McKown, John
> <John.Mckown@xxxxxxxxxxxxxxxxx> wrote:
> > Sorry if this is a rehash. I am revising a document that we created a
> > number of years ago when we looked at converting from the z to Windows
> > or an iSeries. We did neither, basically because management wanted
> > Windows and we totally shot the proposal full of holes.
> >
> > Anyway, one of our questions on the i was about program development. On
> > the z, we use ISPF, which has a number of utility functions and as best
> > as I can tell, the editor is similar to SEU. Anyway, the answer from the
> > vendor was that we should use SEU for program development and that it is
> > bundled with the iSeries. Is this still a good recommendation? Can SEU
> > be used effectively for program development, or would you recommend RDi
> > or something else?
> >
> > Many thanks.
> >
> > John McKown
> >
> > Systems Engineer IV
> >
> > IT
> >
> >
> >
> > Administrative Services Group
> >
> >
> >
> > HealthMarkets(r)
> >
> > Administrative Services Group
> >
> > 9151 Boulevard 26 * N. Richland Hills * TX 76010
> >
> > (817) 255-3225 phone * (817)-961-6183 cell
> >
> > john.mckown@xxxxxxxxxxxxxxxxx * www.HealthMarkets.com
> >
> >
> >
> > Confidentiality Notice: This e-mail message, including any attachments,
> > is for the sole use of the intended recipient(s) and may contain
> > confidential or proprietary information. Any unauthorized review, use,
> > disclosure or distribution is prohibited. If you are not the intended
> > recipient, please contact the sender by reply e-mail and destroy all
> > copies of the original message.
> >
> >
> >
> >
> > --
> > 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.
> --
> 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.