Scott Klement wrote:
The notion of making a 5250 program into a web service
is something I'm not familiar with, and definitely sounds
like a treacherous slope!
A treacherous slope? How about quicksand? May look solid at a cursory
glance. Before you know it, you're up to your neck in goo.
5250 and Web-service sound like contradictory terms when used in the
same sentence. One designed to respond to discrete requests such as
converting degrees centigrade to fahrenheit; the other for controlling
complex workflows.
5250 display files traditionally contain 4 - 400 record formats and one
5250 program may call other 5250 programs in a chain of programs that
open their own dislay files.
5250 and Web services? We're talking about different paradigms. Unless
of course, one considers HATS and Webfaced applications as "web
services".
Suppose we take a product like Zend 5250 bridge. After a connection is
established, 5250 screens are exposed as arrays of fields [including row
& column numbers, data types, display attributes, and conditioning
indicators]. How is that data useful except to emulate 5250 screens
with a lot of extra overhead?
Nathan.
As an Amazon Associate we earn from qualifying purchases.
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.