Re: SEU and V7R1.

Hi Raul

I guess I don't think IBM will go back. However, they do have a "new"
product, Application Management Toolset. There was an announcement of
this in April 24, 2012 - here is part of the description.

*IBM Rational Application Management Toolset for i*

To meet a common need of IBM i system administrators and advanced users,
this new offering features simple, per-processor licensing at a price
every company can afford.

IBM Rational Application Management Toolset for i provides IBM i system
administrators and other advanced users with a lightweight set of tools
for the common tasks of working with library file system objects and
scripting with Command Language (CL).

Functionally, Application Management Toolset for i is a subset of the
venerable Application Development Toolset (ADTS), which is sold as part
of WebSphere Development Studio for i 6.1 or as part of Rational
Development Studio for i 7.1. Two of the key components of ADTS are
Programming Development Manager, commonly known as PDM, and Source Entry
Utility, commonly known as SEU.


Now I don't know if THIS version will support the new stuff in CL. I do
know that it will not support editing RPG of any type.

This does show that IBM are listening to users. And that they will
probably not change the direction as to languages other than CL.

Here's a link to the announcement -

http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=897/ENUS212-114&infotype=AN&subtype=CA&appname=wwwsearch

That's all I know - everything CAN change, of course.

Vern


On 6/18/2013 7:49 AM, Raul A. Jager W. wrote:

There used to be a "long-established policy" about charging extra for
interactive capability, it is gonne in the newer models. I think IBM
will revert the SEU policy.

Vernon Hamberg wrote:

Alan

If you have to use SEU, you can ignore the syntax errors when you exit
SEU. The compiler still knows about the new stuff.

As someone else said, this is a long-established policy - hey, when did
6.1 come out?

HTH
Vern

On 6/17/2013 5:48 PM, Alan Campin wrote:

I can't believe this has not come up before. Maybe I am blind.

Looking at the articles on the new V7R1 features that Kurt sent out I see
this gem!

Here's what's really interesting: SEU's syntax checking has been frozen at
the 6.1 level! That means that SEU will not recognize any of the 7.1
enhancements and will detect these new features as errors.

This is a disaster!

Both my current company and the previous company have refused to buy the
RDI tools and at $1,660 bucks I am not too surprised! Unless you work in a
shop where they will spend the $1700 bucks per developer plus maintenance
you are effectively locked out of using V7R1 features unless we turn off
syntax checking. A big reduction in productivity.

Anybody know of any efforts to get checking turned back on in V7R1?