RE: Application development tools (was: no subject)

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
And how many of these SEU users would lie to their employers that they
need SEU to continue editing?  And not tell their employers that they've
already paid for Code when they've purchased PDM and the compilers?

Or would they be honest enough to say:

These are the ways we can continue to edit programs,
1)  Use EDTF.
2)  Use a mapped drive, ftp, or some such thing, and use NOTEPAD.
3)  Use Code, which we paid for when we purchased PDM and the compiler(s).
4)  Use a third party editor, cost = ?
5)  Use this separately licensed SEU product, cost = ?

And which option do you think management would go for?

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




Buck Calabro <Buck.Calabro@commsoft.net>
Sent by: midrange-l-admin@midrange.com
07/24/2002 09:13 AM
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Fax to:
        Subject:        RE: Application development tools (was: no subject)


>However, with the security offered by licensing,
>...don't you think that the pirating scheme
>has little chance of life?

So very few developers have moved to Code/Flex/Studio and so very many use
SEU/PDM exclusively that I think this will cause widespread hacking of the
iSeries licensing scheme.  I don't think there's another licensed program
that more people want and use than PDM/SEU.  That includes Client Access.
Look at how many requests we see for free/low cost emulators!  People are
willing to leave the IBM fold for everything except SEU.

Here's my rhetorical question:  If IBM were to offer support for SEU (say
SQL prompting), paid for by direct subscription costs and not buried in
the
WDSc umbrella, how much would the SEU users be willing to pay?  IBM will
probably support SEU if they can demonstrably make money doing so.
  --buck
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.