Certainly some good points about the developer community not pressing however many (most?) of those not pressing have gray hair. They know the days to retirement number better than they know web services. They don't want to learn Free form or RDi or SQL or.... So that's one component of the problem.

They there are the IT shops who forbid moving forward. I wrote a FREE program that called APIs to do dynamic LPAR stuff back in the POWER4 days. (Pre-HMC). They customer told me to take it back and write it fixed form. I Lied and said "can't be done." If they wanted the function it came in FREE. I got thumbs up from two developers at the back of the room. :-) Management was not amused but accepted it.

But then you say: "Get rid of single level store." And i scratch my head because that is a key building block of the entire system! Get rid of that and you've truly gutted the system.

I can't disagree with removing limits and making more things consistent and more widely available. Many of those are good but remember there are only so many dollars available for enhancement. Recently the available number of SQL functions for us Admins is off the rails! This is a good thing!! And the system itself moves forward with more capability and capacity, it's really not standing still.

Have you entered RFEs for all your requests? That's the best way to get IBM to see these needs and if people vote for them that's the way for IBM to actually act upon them. If you have created them publicize them!! If not, go forth and RFE!!

- Larry "DrFranken" Bolhuis

www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 3/20/2019 2:23 PM, Steve Richter wrote:
and my complaint is with the programmer community which does not press IBM
to improve the system. So much could be made better. Get rid of ebcdic and
replace with UTF-8. Embrace javascript everywhere on the system, all the
APIs consume and return JSON. No more 16 meg user space size limit. Forget
single level store - does not apply because jobs, apps, users have to be
siloed from each other. SQL debugging is needs a lot of work. And the
debug experience, from the browser, to the node.js or PHP server, to the
application code on the system should be seamless. ILE service programs
should never return a signature violation - system should just find the
procedure being called by its name. The 10 character name limit - come on
people, why accept that? SQL procedures and functions need to be used
interchangeably with ILE procedures and RPG programs. Spooled output of a
job and output queues are a great way to store output. Expand the concept
to output to a folder like structure and allow multiple file types. ( a job
produces a PDF file and it is stored in the folder structure of the output
of that job. ) ILE needs a garbage collector. When a job bombs, the call
stack should not go away. It should be stored on disk and not garbage
collected. CL commands are terrific. Expand their use to enable a CL
command to call an ILE procedure or SQL procedure. And support all the
data types of the parameters of the executable being called.

On Mon, Mar 11, 2019 at 3:25 PM Bob Cozzi <bob@xxxxxxxxxxxx> wrote:

Curmudgeons day was Jan 29...
But for me, it is everyday.

IMHO AS/400 and 'iSeries" were better names than the non-name nomenclature
"i" as it was given when officially announced or "IBM i" which was adopted
years later. (I can go to the video if you doubt my statement about the
name), in fact when I get into discussions about "AS/400 v IBM i" I say,
well, IBM said it is called "Just i" so that's what I call it "just i".

But regardless of how many times we wasted our time with this name-gate
debate, IBM doubles-down on it. No one has the guts to go up to the IBM VP
in charge and say: Hey, we should call it "IBM Blue" (or insert your
favorite trademarkable and google searchable unique brand ID here).
(Sidebar: I have suggested "IBM Blue" circa 2001 to IBMers and they said
it was a great idea. Then they joked and said how about "Green OS", which
today would probably be a very popular name, actually.)

So at the end of the day, they have a no-name system, that no one cares
about (I know, I know, there are 2-dozen or so "insiders" who do care, but
that is still statistically no one), a name they have rarely promoted and a
name a large percentage of their own customers who run that operating
system don't even know the name of. Today "IBM i" is a cash cow for that
shrinking group of individuals and VC firms. You get the same group of
people anointed as "IBM Champions" year after year, save a few new
deserving ones, you get the same group of Speakers at every event
world-wide, and you get people talking about integrating things into their
workflow "over the next few years" that should have been integrated decades

This is NOT a failure on the community for calling it "AS/400" instead of
just i.
This is NOT a failure on the part of the technical capabilities of
CPF/XPF/"OS/400"/"i", it has always been the best at what it does at a
majority of things, But it is not a pretty system to use (green screens).
Some AIX/Linux/U*ix functions are better on those other operating systems.
Also Windows is sexy, Mac OS X was sexy and mobile isn't doing green screen
(save "Mocha") anytime soon.

No, it isn't us or the community at large that is failing the IBM Power
System running the IBM i operating system, it is in my opinion, a huge
failure on the "owner" of this platform. It started back in the mid-1990s
when someone at IBM sat in a meeting and killed a native GUI for OS/400 (as
it was called back then). We now have solid state drives, mobile devices
and an Internet with crazy fast speeds in most countries outside of North
America. All those things were overlooked in the short-sightedness of
whomever made the decision for a non-GUI interface.

But hey, the "owners" of the platform are nearing their retirement too, so
do they really care?

-Bob Cozzi

This is the Consulting on the IBM i (AS/400 and iSeries) (Consult400)
mailing list
To post a message email: Consult400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/consult400
or email: Consult400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/consult400.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.