Re: 7.6 and SDA ?

We’ve had this discussion ad-nauseam before. Like in all cases, the answer is “it depends”.

If you are on an single system with a moderately (or less) educated/trained administrator, the need for SEU (or a likewise replacement) goes up quite a bit since the experience will not match the needs of a crisis. On the other hand folks like Rob, where the experience and technical levels are quite high there are work arounds to not having SEU. Since it’s likely that communications and such are down in an emergency, VSCode etc. will not work, you need something on the system directly.

There is a solution staring most folks in the face, Open Source. There are about 3 or 4 excellent editors in the open source stack available for use. Get a group together to modify one of those to recognize source physical files and go for it. (You could also use /qsys.lib/qgpl.lib/qclsrc.file/mymbr.mbr to open them but that’s a bit of an ask) Instead of complaining that SEU is going away (It’s not at this moment) build a better solution!

Another thought, VSCode is very transportable, why not build a version that runs directly on IBM i ? Add Richard’s CL prompting to it and you’re 90% there……..

As far as SDA is concerned, IBM has been warning you for years, start listening………

I’ll shut up now.

Jim Oberholtzer
Agile Technology Architects

On Feb 17, 2026, at 6:57 AM, Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello Rob,

Am 17.02.2026 um 13:19 schrieb Rob Berendt <robertowenberendt@xxxxxxxxx>:

"need" is not a word open to opinion.

I have not used the word "need" anywhere in my reply.

Is SEU "needed" to edit a CL program in a crisis situation? If you were tasked in such a situation to work on a system without SEU would you reply to IBM that you couldn't do it? Or would you find a way?

Of course I would find a way. But why do you suddenly add a crisis situation scenario? My sole point was to make you aware that "not using SEU" isn't an option for everyone, for various reasons, which might even appear minor to you.

:wq! PoC

--
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.