|
No - even as we have at least 2 or 3 developers who are using SDA on a
regular basis, we will go to
7.6 when the next hardware switch (leasing) is due.
We are using RDi - and the few guys who are still maintaining 5250
applications with 5250 tools can switch today.
But we are also in the process of switching to VS Code / Code4i as our
primary IDE. And even if there is no 5250 designer, the combination of
editing DDS code and having a preview of the resulting screens would be
enough for most of our work. More often I find myself editing the DDS
manually in the designer, because it's a bit tedious to do a simple
COLOR(WHT) in the designer GUI. Also a 5250 designer is in the works right
now, and I think it will be available later this year.
And I think Code4i might even be an option for /36 maintenance - we (the
community) just needs to create syntax highlighting for OCL and maybe
RPG/II - both shouldn't be so hard, as the groundwork is already done.
Kind regards,
Daniel
Am 24.07.2025 um 05:41 schrieb Richard Schoen <richard@xxxxxxxxxxxxxxxxxthis short sighted move or removing SDA and forcing RDI as an option or the
:
I’m just curious how many of you folks will stay at V7R5 because of
non-completed VS Code SDA alternative.
customers who are using it.
There’s no reason that SDA couldn’t have been left on the box for those
don’t think I can advise them to go beyond V7R5 unless they are planning to
We have a number of older customers using S/36 environment code and I
stop maintaining their green screen apps.
list
Interested in your thoughts.
Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
--
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.