On Wed, Oct 3, 2018 at 2:13 AM Don Brown <DBrown@xxxxxxxxxx> wrote:
how did you retain the investment in the existing program
logic.
You probably have logic that validates data before storing it, or returning
error messages for data that doesn't qualify. You may have logic that
ensures referential integrity or implements rules pertaining to database
transactions and maintenance. For that type of logic, I recommend placing
that behind DB update and write triggers. You may be able to cut and paste
that type of code. You can read about our approach at:
http://rd.radile.com/rdweb/info2/ibmiapp04.html
Frankly a lot of 5250 application logic should be replaced. Web
applications follow a request-response cycle, as opposed to the display
file record write-record read paradigm.
The approach we took was to develop robust web application templates that
cover inquiry and maintenance operations for perhaps 80% of database
tables. We also wrote a code generator that we can apply to any DB file. We
sometimes crank out several DB maintenance applications in a day. So I
recommend wholesale replacement of just about all 5250 applications.
Using this approach, we were recently awarded a contract to deploy our K-12
student information system throughout an entire state. We have just 2
developers on staff, who beat out competitors who employ hundreds of
developers.
midrange.com
