Re: SEU vs. RDi vs. ? (PRIVATE REPLY)

Hi, again, John:
>>>---> private reply "off-list" <---<<<

One more clarification of something I mentioned in my last reply ...

By having a small P05 development system (model 515 or 520) you can license the development tools,
WDS/400 (5722-WDS) at a far lower cost, than what they would cost on a larger system (P10 or P20 etc.) -- so the idea is, you would not license the compilers or development tools AT ALL on the larger production system.

You would do all your development on the development box, and then send the compiled objects over to the production system. There are several ways to do this. Ideally, you may want to consider purchasing a "change management" package to assist with this process. Do you currently use ChangeMan or Endevor or any other change control products on the mainframe? Or at least, something like CA-PANVALET or CA-LIBRARIAN?

Regards,

Mark S. Waterbury

> McKown, John 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.