Re: MVC in RPG?

Mike,

That's so cool. That's what I've been wanting to do, also.

On one project, we had separated the DB functionality. In our case too much
business logic was placed in it. One thing that I noticed and would change
in the future is to not return the record format or it's address. The
record format should only exist in the service program containing the DB
procedures. Use procedures for retrieving each field or putting into each
field. Then when the record format changes, only the service program needs
to be recompiled and any other program or service program that needs the new
or changed field(s).

Create an instance. Besides the key fields include the "initial" program
that is called, especially if you maintian created by and changed by
information. Otherwise all the created by and change by program would be
the DB service program. That is also helpful for business logic as to where
to send error messages. (Include the module if you take program message
queues to that level.)

What are you using for modeling? Are you going to use data and process
modeling or object moduling?

MQueue