× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Ok. There are some misconceptions here.
You can ALREADY use the long names for tables, columns, etc in RPGLE. It's
been supported for a LONG time. Starting to actually use the long names
wouldn't break a darn thing. Unless you're in the camp that if it doesn't
fit on an 80 column card in the same punch spots then it isn't RPG.
In an effort to discourage the use of the short names I often obfuscate them
CREATE OR *REPLACE* TABLE Lookup_table for system name T00000001
(
Lookup_item for column C000000001 *VARCHAR*(*100*) ALLOCATE(*20*)
not null constraint Lookup_table_primary_key PRIMARY KEY,
*-- Item to lookup* Lookup_value_character for column C000000002
*VARCHAR*(*100*) ALLOCATE(*10*) with default null,
*-- Value of item (if character)* Lookup_value_integer for column
C000000003 *bigint* with default null,
*-- Value of item (if integer)* Lookup_value_decimal for column
C000000004 *decimal* (*25*, *5*) with default null,
*-- Value of item (if decimal)* Lookup_value_timestamp for column
C000000005 *timestamp* with default null,
*-- Value of item (if timestamp)* CONSTRAINT Lookup_table_has_a_value
CHECK (
*-- One, and only one, of the lookup result columns will have a value.*
(Lookup_value_character is not null and lookup_value_integer is null and
Lookup_value_decimal is null and Lookup_value_timestamp is null) or
(Lookup_value_character is null and lookup_value_integer is not null and
lookup_value_decimal is null and Lookup_value_timestamp is null) or
(Lookup_value_character is null and lookup_value_integer is null and
lookup_value_decimal is not null and Lookup_value_timestamp is null) or
(Lookup_value_character is null and lookup_value_integer is null and
lookup_value_decimal is null and Lookup_value_timestamp is not null))
)
RCDFMT T00000001R

Time to start using the System Catalog too:
https://www.ibm.com/docs/en/i/7.5?topic=reference-db2-i-catalog-views

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

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>) 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> 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> wrote:


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


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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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