Re: 20 years ago

Reeve,

I think that your analysis is very good and true - IBM wanted to sell Websphere and everything left and right of that path was left to die, or better got no more updates because backwards compatibility was and still is a holy cow.

And I made my peace with what happened - but I still think, that

A) a good, fast and easy to use open source web framework for ILE languages would be really nice, and

B) some final extensions to the 5250 data stream and DDS would be really nice - like dynamically selecting the screen (e.g. for mobile scanner devices that mostly still run 5250) or some HTML elements (like hyperlinks embedded in screen constants or fields) - and of course the extension of iACS to support all that

Well dreams of a developer who is still developing 5250 screens in 2022 because the client wanted to switch back from a GUI product to “green screen” because they find it more user friendly and much more performant.

Just my thoughts
Daniel

Von meinem iPhone gesendet

Am 17.08.2022 um 23:04 schrieb Reeve <rfritchman@xxxxxxxxx>:

Chris, I understand why: a non-text interface is hugely more flexible and
the constraints of the 60's and 70's (kilobit data lines, limited RAM,
limited developer tools) are gone. The development work that led to the
System/38 wouldn't have been possible or made sense if some in IBM hadn't
recognized that data speed, memory, and CPU performances were going to
increase at a staggering rate. I used 3270's for CCP and did crazy stuff
to get good response time on 4800 BPS dial-up lines. Advancements in the
hardware domain is the big reason the efficiency of a text-based display is
no longer a factor.

Second reason: IBM wanted to sell Websphere. The 5250 market was hammered
by 3rd party hardware; Websphere is soft and licensed--you can't go wrong
if you're the licensor. Don't forget follow-on hardware!

Third reason: by charging for interactive seats, IBM somehow made 5250 look
better than before.

The conspiracy theorist in me thinks factions in IBM blocked additional
development in Open Access for RPG to prevent native handling of HTML *without
requiring 3rd party applications*. I realize 10,000 vendors are now typing
emails of protest--but my 5250 support came bundled with the compiler and
OS; why shouldn't full HTML as well, with comparable tools, utilities, and
compiler features? Customer satisfaction with the platform would be
higher, there'd be new blood in the developer community, and IBM would have
a fiercely loyal customer base willing to pay premium rates. IBM invented
the midrange market *and they killed it*. I guess it was...too old (a dig
at IBM's age discrimination troubles).

As a vendor, I'm seeing little consensus WRT modernization (specifically,
the UI) technology approaches. Some are enamored with Python, others like
a Windows-centric approach, and a few think the world of 4GL and 5GL
products. There are even those who want to convert RPG to Java, and I wish
them a long and happy life (their professional life is going to be long and
it will not be happy). I've made my choice, and it's to focus on the
application functionality and build interfaces that support alternate
UI's. It's my choice as of today!

Having standards put in place by IBM--like 5250 and 96-column cards--makes
budgeting easier (the price may be high but you'll be confident you have
them right). It reduces the breathtaking variations we see in satisfaction
with modernization projects (granted: a weak base system will not modernize
well and coupling application reengineering with a new UI is high risk).
"Blue handcuffs"--we complained but they worked.

For me, having IBM provide a native HTML interface would remove the
technology selection challenge (and the cost and the time) and would allow
me to do what I do best: deliver high-function, low-cost business
applications. A UI with a full color palette, variable fonts, and
unlimited screen size, all thanks to HTML, would make it fun to code for 60
hours a week.

The best path looks like starting with the HTML up front, building
interactive applications, and using the AS/400 family as database and batch
servers--they're the bots for HTML's Jedi warriors. This approach protects
much of your investment from IBM's business plans, which the prudent
business person will do.

Just saying.

On Tue, Aug 16, 2022 at 3:02 PM Hiebert, Chris <chris.hiebert@xxxxxxxxxxxxxx>
wrote:

I've always found it strange the IBM has resisted any updates to the
Display File spec, or even the 5250 data stream in general.


Although we can use DSPATR(&FIELD), then load the field is all the
attributes you want, and get rid of indicators all together.

A DSPATR(&DSPATR02A)
A DSPATR02A 1A P


RPG Procedure parses the input color and attribute and sets the DSPATR
value accordingly.

Dspatr02A = Rtndspatr('TRQ':'RI');
Dspatr02A = Rtndspatr('WHT':'UL');


--
Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.

From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Gad
Miron
Sent: Tuesday, August 16, 2022 11:33 AM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: 20 years ago



Speaking of DSPFs



Some 20 years ago (st. Peppers) I had the notion to ask IBM to let us use

Field attributes indicators in DSPFs in a more straight forward (and self

explanatory) way.

This by adding all 7 attributes of each field ( HI RI CS BL ND UL PC) to

the INDRADA area



Then we could write in the RPG program like this:

FIELD1.PC = *ON (Set on Position cursor for FIELD1)

FIELD2.RI = *ON (light up Reverse Image for FIELD2)

you get the point...



This method will also help with the limited number of indicators.



But, as I have been coding less and less during that time I kind of

dropped it.



BTH, I know that one can map names to each indicators and use named

indicators

But if IBM were to add a built-in support for this feature it would have

standardize all

reference to these field attribute and not leave it to the (lazy , like me)

programmer.



Just a flash-back



Gad
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com