RE: Separating I/O from business logic

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

No duplication.  Once the rules are in a separate module, you use that
module in the server program.  I have only one program that holds the
business logic.  I have defined a way to transition from one large program
that does all to separate callable programs, to separate ILE modules if that
is the direction they want to go.  Finally to Client/Server.  Read again
Ken!


Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Ken.Slaugh@cm-inc.com [mailto:Ken.Slaugh@cm-inc.com]
Sent: Monday, November 20, 2000 8:11 AM
To: MIDRANGE-L@midrange.com
Subject: RE: Separating I/O from business logic



Chris,
     Your method requires that the business rules be duplicated. Thus
maintained twice in the future. Don't make your life more difficult than it
already is.

     Use the existing display file enabled program. Just simply change the
workstation file to USROPN. Put an indicator on the new OPEN and CLOSE
statements and use the indicator to control the client/server modal.

     Instead of using DataQs directly, pass the I/O in *entry plist
parameters. Then write a driver program, using DataQs or Sockets, to call
the original application program and send/receive the data.

Ken Slaugh  (707) 795-1512 x118
Chouinard & Myhre, Inc.
AS/400 Professional Administrator/MSE
Client Access Specialist
http://www.cm-inc.com/
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---