|
When you advocate for 5250, you're advocating for a terminal emulator on
the client and "interactive" sessions on the server. In most cases you're
advocating for SEU and PDM (or their RDI equivalents). You're generally
advocating for RPG as a language. I'd bet that in most cases, the 5250
advocates have NOT seriously explored alternatives. Therefore, they don't
know how to create and deploy alternatives to 5250.
Have you learned HTML, CSS, and JavaScript? Do you understand a browser's
DOM (document object model), and do you know how to reference it from
JavaScript? Do you know how to configure the IBM i HTTP server? Have you
explored HTTP options for managing user authentication, authorization,
access to menu items, and sessions?
Whatever language environment, application architecture, run-time framework
you have settled on, is the one you advocate for. Notwithstanding its
weakness and pitfalls.
On Thu, Jan 2, 2020 at 3:25 PM Booth Martin <booth@xxxxxxxxxxxx> wrote:
We do not disagree. It isn't useful to "push" any single Messianic
solution on to users. On the other hand, 5250 is certainly a viable
choice, one of many. Saying 5250 is dead serves no purpose. It's here.
it's been here, and it's going to continue to be here for a long time
to come.
It's one of our tools. Refusing to learn and use the enhancements
speaks ill of our professionalism. We have sortable subfiles.
first-rate filtering, push buttons, scroll bars, drop down boxes, check
boxes, and radio buttons. They work, users understand them, and they
improve the 5250 user experience significantly. F-keys, *MORE,
confirmation sub files, and explaining the difference between the Enter
key & the Record Advance key can be easily abandoned. A 5250 shop can
easily sllde into these enhancements and at least get their shop out of
the 1990s, this is not a heavy lift.
in my opinion.
On 1/2/2020 3:31 PM, Raul Jager wrote:
This is also My opinion. By pushing the 5250 we will do a disservice to--
our favorite platform.
I use 5250, but it is a very bad idea to push it to my users.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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.