commit control for an interactive web app, is this feasible

Basically I am webifiing an ILE suggested retail maint program (one "big"
program - when looked at from a html perspective)
I have done enough on our AS/400 now to realize how each painting of the web
page even if the same program can have
different job numbers (a new "copy" is called with each i/o to the web)

So, from a philosophical viewpoint, looking at an app that is really cool
and they still do need the commit control, though
they may have been in and out of a few programs to play with srp's, will
commit even work - I can start it with *job or
*actgrp(which I already know would be the only way it could even possibly
work), but - we are on V4R5 -
does that work in this environment; I will be splitting the one program up
into about 10 cgi's
plus the other pgm calls it does based on command keys will be split out
too, all for me is very doable, with the exception
of an uneasy, mis-understanding of commit control with regards to html
coding.  To our full site is hosted on the AS/400 for
customers, including order inquiry, sales data, price books, flyers, and
some other fluff.

Or will I be forced into my old days of commit control via a "work" file?

*side note, I seemed to have lost getting messages, I have re-signed up, but
we have switched ISP and e-mail hosts (AGAIN)
so I have lost many messages, and I am not sure if they can handle be being
on the list yet - if they stay up for any amount
of time for the rest of this week.


TIA for clarification.


Mark A. Manske
Minter-Weisman
Sr. Project Lead
http://www.minter-weisman.com
[mailto:mmanske@minter-weisman.com]




+---
| This is the WEB400 Mailing List!
| To submit a new message, send your mail to WEB400@midrange.com.
| To subscribe to this list send email to WEB400-SUB@midrange.com.
| To unsubscribe from this list send email to WEB400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---