RE: lack of usable new OS features

["Steve Richter" <srichter@xxxxxxxxxxxxx>]

I agree with Konrad. Especially his use of the word "useable"

Here are what I consider useable features that could be added to os400:

journal the ifs
journal data areas
in fact, journal all stream file structures: user space, data area, stream
file. where the journal entry contains: start location, change length,
before and after change value.
triggers on changes to a stream file, dtaara, usrspc.

The purpose being to enable full system mirroring.  This provides real high
availability to your web serving iseries.

On the HA and mirror front, enhance triggers. Allow a trigger program to
redirect the update io to the replication master system. ( To keep files on
two or more systems in sync there are scenarios where you want to redirect
all file chgs to a replica master, then back out to the replica viewer )

Out of the box tight, auto config, built in connectivity between iSeries
systems and partitions.

A job running on one system or partition should be able to call directly
into a pgm on another system, then return back just like calling a pgm on
the same system.

Add system name to object name qualification on all commands. Same as on a
pc: _\\system\library\object. Enable all object cross system/partition
support implied by this naming extension.

Start work now on a common language runtime for all ibm platforms and linux.
Use and extend the JVM if that works. All iSeries languages and APIs must
call down to this CLR. Same for the mainframe. Maybe call it "MI". The
objective being the ability to run an iSeries program on any IBM platform.

Fix the performance failings of the host servers. Publish a "host servers
inteface reference manual".

Job name and user name should be able to be changed in flight.  Or at least
provide an "aka" name. This way a host server job that is running remote
calls from a pc can have a meaningful job and user name.

Fix the performance and connectivity problems of NetServer. If a user can
telnet to the iSeries, they should be able to see and access it in their
network neighborhood.  Response time when accessing an iSeries in NN should
be the same as a comparably remote pc.

See the iSeries as an NT competitor. The benchmark being a VB program that
uses ODBC, ADO and file serving access to a server should see comparable
performance from an iSeries as from a PC server.

Long object name support, a common set of APIs for database io, scrap ile
and all those who proposed it, a byte data type so that there is a chance of
converting the system to unicode, open database and IFS files in CL, web
page APIs and commands so a cl pgm can serve a web page, ...


Steve Richter
AutoCoder, LLC