Re: Will IBM ever expand system object names?

Javier


It seems obvious it should be easy - but the internal structure of object names is not something to change without handling the implications of that change - hence, the cost of people and time.


The actual system objects of SQL objects still use the internal structure - you get to name your own 10-character "system" name for the long-named tables and all. So under the covers, these all still use the 10-character naming, whether created by your or generated. All the MI instructions that deal with objects, they use a structure with elements that are CHAR(10), plus a couple other attributes, at least. There are at least a context (MI name for library) and object.


Maybe you can build a case to support adding something like how SQL names are handled - maybe it's an internal additional attribute on the internal object type, I don't know. It was worth it with SQL due to a need for compatibility, perhaps, with other SQL products - it's harder for me to see how it is worth the time, as there isn't much I see that relates to non-IBM i systems for this to help.

Regards
Vern


On Wed, 29 May, 2024 at 12:02 PM, Javier Sanchez <javiersanchezbarquero@xxxxxxxxx> wrote:


To: midrange systems technical discussion

Having long names with SQL did not cause any issue. It rather came to
ease many compatibility issues.
Why would an expansion in system object names cause headaches? Without
SQL, it could bring other benefits at the RPG level, i.e., as with external
data structures that are read from a table/file definition and get the
alias as the node name when qualified.

Like I said at first, hopefully with SQL we may have this functionality,
even for user profile names. Now, this is only a small survey, and the
opinion of the experts is good to know :-)

JS

El mié, 29 may 2024 a las 9:54, Jim Oberholtzer (<
midrangel@xxxxxxxxxxxxxxxxx<mailto:midrangel@xxxxxxxxxxxxxxxxx>>) escribió:

An earlier post lamented that user names should be longer.
OK, Use the built in LDAP server or any other kerberos server. Now you
have the luxury of single sign-on if you wish, usernames that are stupidly
long, and a world of other benefits. Sure it comes with an administrative
cost but IBM does not need to spend money on things that are already there,
albeit not quite so easy as the QSYS version.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Wed, May 29, 2024 at 10:45 AM VERNON HAMBERG Owner via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>> wrote:

Be sure to search Ideas first - seems I've seen this already when
reviewing in a CAAC meeting.


As Jon said, there are reasons not to, it would be a tremendous cost.


Cheers
Vern


On Wed, 29 May, 2024 at 10:09 AM, Diego E. KESSELMAN <
diegokesselman@xxxxxxxxx<mailto:diegokesselman@xxxxxxxxx>> wrote:


To: midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>

You should create an IBM Idea

On 29/05/24 07:18, Javier Sanchez wrote:

With SQL objects this is already possible, and sometime in the future,
maybe we will be able to do everything using only SQL, which would be
fantastic.

What about in the meantime we could have expanded the current 10-char
system object name length to something longer?

This is one item on my wish list, and I could also consider including

the

underscore character as a valid starting one for such names.

JS

--
Saludos/Regards

Diego E. KESSELMAN

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx><mailto:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto: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<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx><mailto:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto: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<mailto:support@xxxxxxxxxxxxxxxxxxxx><mailto:
support@xxxxxxxxxxxxxxxxxxxx<mailto: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<mailto: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<mailto: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<mailto: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<mailto: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<mailto: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<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.