Re: 5250 to Web Interface / Application Modernization

Jon,

It appears that you may be spread a little thin by being engaged in several
conversations all at once on this list, and you're probably busy with work
too. You're way off base in regard to thinking that my perception of what
OA can and cannot do, being slewed by 5250 thinking. I've looked deeply
into OA.

In regard to the purpose of this thread, is it really relevant what is
"possible" with OA?

Moreover, OA web applications implement the display-file write-read
paradigm. The format of the display file may have changed. That's up to the
creativity of the people who designed the OA handler. The Workstation Data
Management function has effectively moved off the IBM i, and has been
replaced by something comparable that is running in the browser in some
cases, or running on an intermediate platform in other cases. Again, how
that works is up to the creativity of the people who design the OA handler.

With OA, the normal client-browser request-response cycle has been swapped
out in order to accommodate the display-file write-read paradigm. That
definitely comes back to bite.


On Tue, Apr 9, 2019 at 2:03 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

" But you give up the ability to respond to any type of event that may
occur at any time within web browsers."

No - you don't have to. Many of the limitations we perceive with 5250s
are imposed by Workstation Data Management. But using OA WDM is not in play
- so neither are the limitations.

I'm not saying that completely designing a new modern UI should be done
with an OA handler approach - although I've seen it done very very well.
But your perception of what it can and cannot do is slewed by 5250 thinking.