RE: Max length of a VARYING field -- RPG400-L

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

Yes I see that.

-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 Steve Richter
Sent: Friday, May 11, 2007 3:02 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Max length of a VARYING field

On 5/11/07, Bob Cozzi <bob@xxxxxxxxxxxx> wrote:

Judging from the code you provided, performance would not change much from

what

you already have, your NextCommaSeparatedValue() routine returns a big old

2000

byte value.

it is email code. Just trying to code it for readability. make
believe the procedure is running on a quad core p5 selling for $8000
;)

it is the input InCsvString parm that would be the problem. When its
size is increased to varying(4)
d InCsvString 999999a const varying(4) options(*VarSize)

all callers that are varying(2) have to be mapped first to a
varying(4) so that the pass by reference can be satisfied. Same when
you keep the parm as varying(2) and call with a varying(4) variable.

-Steve

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.