Re: Web apps on the AS/400

[jpcarr@xxxxxxxxxxxx]

Leif said
<SNIP>
not really. Subroutines can have states too, either by having the state
information
in a parameter passed to them or simply by not deactivating themselves.
Maybe it is because you come from an RPG background that you can't see
this. If you have worked with COBOL you would be used to your subroutines
having state as that is the default. The classical case is a COBOL program
acting as a file I/O handler. The COBOL program encapsulates access to
a "file" which could be either an SQL table, a data area, a "normal"
database
file, or stored on another system. You call the "file I/O" handler with an
operation code (a "method"). It does the operation to its internal state
(its opened file) causing communication with the external world. This
is a technique used by COBOL programmer for at least the last 35 years.
The file managed by the COBOL program becomes an object, e.g.
a customer. There is absolutely no conceptual difference here.
<SNIP>

You're right Leif,   I teach this at my "External I/O routines using SQL"
session at COMMON.
Great technique

John




+---
| 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
+---