RE: what was the single mgmt decision made in mid-1990s. period

You are right.

Scott Klement wrote a couple of articles on modular and MVC programming.
A concrete example of MVC was in February 2007 System i News: "Pattern
Recognition: Ease Modern RPG Programming".

One of the "problems" is when MVC is written for "simple" or "trivial"
examples, there appears to be a lot of extra code, both in terms of LOC
and number of objects, as compared to the traditional display program.
Many people see "more code" and "extra effort" for "a simple example"
and shy away from it. If however they look to either A) larger
applications with potential duplicated logic (such as validation), or B)
multi-interface applications (5250 vs browser vs client) then the extra
effort and code becomes much smaller and insignificant compared to the
gains.

--Loyd

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Perkins
Sent: Tuesday, February 17, 2009 3:47 PM
To: Midrange Systems Technical Discussion
Subject: Re: what was the single mgmt decision made in mid-1990s. period

IMHO, we as developers need to change the way we design programs.
Validation
for green screens needs to be moved to either a separate program or a
service program. No more huge programs that display data, update data,
write
data, etc. It needs to be separated.

James R. Perkins