Re: Will IBM ever expand system object names?

Where would you store the relationship between the 10 char name the system would have to create and the long name? Would you allow calling by the short name? That would match the way SQL names work. Either way it slows down calls.

Just to give a tiny example of the work needed. Think of all the APIs that accept a 20ch compound name. How big are you going to make the new names? 30? 40? They can't be arbitrary because such APIs have to split the components. Unless you include a separator? Now you have extra logic to test for its existence. Then there are edge cases such a 20 char field with a five char library name and a 14 long object. even the length of the field doesn't tell you how to process it.

The amount of testing alone would be massive. And for what? Seriously, what _real_ benefit does one get from this?

Sorry - I just think it would be a massive waste of $s with little or no payback.


Jon P.

On May 29, 2024, at 1:34 PM, Javier Sanchez <javiersanchezbarquero@xxxxxxxxx> wrote:

What if this existed?

CRTBNDRPG PGM(MYPGM) LONGNAME(MYLONGPROGRAMNAME) .....

and at some point you just like:

CALL LONGPGMN(MYLONGPROGRAMNAME)

And this would work for new applications. Why not?


El mié, 29 may 2024 a las 11:19, James H. H. Lampert via MIDRANGE-L (<
midrange-l@xxxxxxxxxxxxxxxxxx>) escribió:

On 5/29/24 10:01 AM, Javier Sanchez wrote:

Why would an expansion in system object names cause headaches?

It would break a great deal of software that uses record-level access.

Every single system API that deals with objects in the QSYS.LIB file
system assumes that a fully qualified object name in that file system
consists of a 10-character library name, a 10-character object name, a
10-character member name, for database files, and a 10-character object
type, for APIs that deal with multiple object types.

The same is true for CL commands.

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

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