Re: RNF7535: varchar not compatible with options(*varsize)?

Yes - although varchar may still be a good choice depending on how the string is built and how else it is used.

For example:

for i = 1 to 1000000;
varchar += %char(i) + ',';
endear;

for i = 1 to 1000000;
char = %trimrR(char) + %char(i) + ',';
endear;

The first case will run in a hundredth (or less) of the time taken by the second fixed char version.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Mar 30, 2018, at 2:14 PM, Dan <dan27649@xxxxxxxxx> wrote:

Gentlemen, thanks for all of the replies. I probably won't get back to
this project until next week, but I wanted to acknowledge your
contributions. It's apparent I still have much to learn about this type of
stuff.

The biggest concern was, if I didn't use varchar, I'd always be passing
16MB of data to Qc3CalculateHash. 95% of the time, the length of the data
to be hashed won't exceed 100KB, but those outliers kill ya, so I
accommodate the max. Do I understand correctly that, by specifying
%addr(DataToHash:*DATA), that no data is being copied, but simply the
address of that data is passed to Qc3CalculateHash? If that's the case, I
wouldn't need to worry about defining DataToHash as varchar; just define it
as char. Do I have that right?

- Dan
--
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: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD