|
That one off was a variation of PL/1 if I remember it correctly.
iBM Changed to C about 6.1?
Again my memory is fading.
Jim Oberholtzer
Agile Technology Architects
On Jul 25, 2025, at 5:38 PM, x y <xy6581@xxxxxxxxx> wrote:sense
IMO, Patrik's explanation is exactly right. IIRC, there was a one-off
language used to develop System/38's CPF and utilities; it would make
that SDA was built using that tooling. With the move to RISC and thegreat
emphasis on secure software, it's likely parts of the SDA app would notget
through a code review or a systems assurance test today. Hence, IBM'scustomers
trying to kill SDA because key components are borderline unusable.
Meanwhile, IBM is whistling by the graveyard hoping thousands of
and applications developers don't miss it.would
But here's one big problem with Patrik's scenario: why hasn't SEU been
end-of-life'd? It likely uses the same development framework and one
think it suffers from the same ailments as SDA. SDA appears to be theIBM
stalking horse to gauge customer reaction to killing off ADTS and PDM.
Hey IBM: how about inviting a couple of user Big Brains, folks with no
history as an employee or contractor, to your dev locations and show thembut
what tools you use in your labs? That would pull back the kimono a bit
it ignores one area: interactive development. Do you have any apps otherharder
than SDA and SDA that use *DS4 mode? Interactive app development is
than you think; how many on the lab staff have built and managed aand
real line-of-business application? A tactical solution is to kill SDA in
the expectation/hope/bet that a VS Code plug-in will provide a better and
cheaper solution but the unintended consequence of that is leaving RDi
Merlin behind in favor of VS Code.surroundings
Some favoring euthanizing SDA and SEU point to the importance of adopting
modern development practices supported by modern development tools. But
conflation isn't the answer: great art--paintings, shotguns, a garden,
wooden boats, software applications--can be created in humble
with low-tech tools (one notable exception: fancy web pages areessentially
beyond human comprehension and require a robust tool to keep track ofaid
everything). Applications developed in a steel-and-glass monolith aren't
inherently better but there's no question that modern dev tools greatly
the development process. Colorizing tokens, RDi's CTRL+2, and RDi'sALT+Z
provide measurable productivity increases but they don't contributewrote:
directly to the product.
And that other thing about the OS being green-screen...well, yes. What's
notable about that truth is the lack of movement by IBM. That suggests
resources are directed to other areas. There are changes coming and it's
just a matter of time; IBM's Merlin may signal how we develop in the
future. Pardon me while I check my life expectancy chart.
On Fri, Jul 25, 2025 at 8:10 AM Patrik Schindler <poc@xxxxxxxxxx>
midrangelist@xxxxxxxxxxxxxx>:
Hello Gavin,
Am 25.07.2025 um 14:56 schrieb Gavin Inman <
toeliminate 5250.
If you want to push your remaining dedicated base off a platform IBM,
Matches my thinking. When I started exploring the system as a
retrocomputing hobbyist in 2007 and soon after found it extremely easy
GUIwrite full screen text UI applications — compared to Libcurses on Linux.
Sadly, TUIs are (outside of nerd niches) generally considered outdated
nowadays, and the limitations of the 5250 forms based approach limits
possible interactions with the user even further. Everything has to be
text.and clickable, despite the fact that requested information is still
listMostly.
But then, I'm not a commercial user, and consider myself being part of
that nerd niche mentioned above.
:wq! PoC
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
relatedTo 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@xxxxxxxxxxxxxxxxxxxx for any subscription
listquestions.--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxrelated questions.
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@xxxxxxxxxxxxxxxxxxxx for any subscription
--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.