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



The fist two bytes of a VARCHAR field store a short 2-byte integer
containing the current size of the string in the field.

Why are you writing I-specs in the first place?

Charles

On Thu, Jan 14, 2016 at 3:21 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I have a DDL-described PF with these columns:
ID integer
TEXT varchar(40)
...

I'm trying to do I-specs for these but I'm having trouble. DSPFFD shows:
ID buffer length 4 buffer position 1
TEXT buffer length 42 buffer position 5

So I did these I-specs:
I I 1 4 0ID
I A 5 46 TEXT

ID seems fine, but TEXT is acting weird. In debug, TEXT shows a blank
space before the value which doesn't go away if I trim the field. That
makes me think there's some non-displayable character there. I've never
defined an INTEGER or a VARCHAR on an I-spec, so I assume I messed
something up.


Any ideas?
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx 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.