Scott,

Your understanding of my question is correct. And yes, in a perfect
world, we would be given ample time to rearchitect our ancient 5250
applications, separating the business logic from the presentation
layer, rewriting that business logic into ILE procedures, etc. In
real life, we have to beg and plead for that time (knowing that the
fate of the i in our shop depends upon it), and it is rarely given to
us.

We have spent months rewriting some of our more complex green-screen
apps to make the business logic layer reusable. The time it takes
does not reflect favorably upon us. It's not our fault that the 5250
apps were written in the manner they were (many were written before
any of us even started working -- anywhere :) -- but we're the ones
that are forced to deal with them. If there were a good solution for
our problem, we could get applications up and running quickly, then
rearchitect the entire mess on the back end in our own time and at our
own pace. Not a great solution by any stretch, but one that would
greatly improve the situation we are in.

Thanks.
Mike E.


On Sun, Jun 29, 2008 at 2:09 AM, Scott Klement <web400@xxxxxxxxxxxxxxxx> wrote:
My understanding of the question was "does the IWS let me keep my old
code that writes to 5250 screens, and extract data from that 5250 screen
to make it into a web service"? I would consider that a treacherous
slope. Your code should be designed as re-usable, modular code. The
business logic should be organized into a set of re-usable service
routines. Those re-usable routines should be called as a web service.
(and possibly called other ways as well)

If you try to "screen scrape" your ancient 5250 applications that were
designed for a 5250 terminal, and not designed to be a web service, then
you are, in my humble opinion, heading down a treacherous slope.

Please understand that I'm in no way advocating the use of 5250 -- quite
the opposite.

Dave Odom wrote:
While I don't know specifically about the Integrated Web Services
server, getting off of 5350 and moving to GUI, of an appropriate
form, is the way to go to prevent the IBM i from becoming an even
greater anomaly in the IT world than it already is. As long as it
is perceived as an anomaly in the IT world at large it will rarely be
considered by the CxO level and its doom is certain and perhaps
quicker than you might think.
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.