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



Dang Bob! That's not half bad...


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob Cozzi
Sent: Friday, May 11, 2007 1:43 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Max length of a VARYING field

I like this:

D myOldVarrying S 256A Varying
D myNewVarlen S 256A Varlen(2|4|8)

Where VARLEN defaults to an int4 but 2, 4 or 8 byte integer "lengths"
prefix can
be specified.
That way I can switch to VARLEN and have it default to 4, but VARLEN(2)
provides
a clear indication of something that should remain at the old variable
length
limit.

-Bob Cozzi
www.i5PodCast.com
Ask your manager to watch i5 TV



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On
Behalf Of Barbara Morris
Sent: Friday, May 11, 2007 12:26 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Max length of a VARYING field

Keith Carpenter wrote:
Barbara Morris wrote:

I'm all for the increased size, but...

I hope there will be an option to retain the 2-byte prefix for
backward
compatibility. If not, this could become an infamous gotcha where if
someone compiles 1 module/program they end up having to fix a whole
series of programs.


Well, there won't be an option because the default will remain at 2.
You will have to code something extra to get a 4 byte prefix.


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.