Re: conversion to ILE

["David Morris" <dmorris@xxxxxxxxxxxxx>]

Rob,

Depends on how you do it.  OPTIONS(*VARLEN) could speed up what
 you are doing.  If you are on V4R2 Varying makes a huge difference.  I 
converted our string routines to use Varying when V4R2 came out and it 
made a big improvement.  If you combining CONST and VARYING you 
get ease of use, flexibility, and speed.  The biggest drawback is that CL 
calls have to append the length manually.  Also the older (non-free format 
opcodes like xlate don't automatically set the result length.)

David Morris

>>> Rob Berendt <rob@dekko.com> 04/21/99 07:44AM >>>

...Be careful about generic string handling routines.  They can be a real 
performance 
killer.  I tried making a 'caps' procedure.  The procedure supported strings up 
to 
32,702.  It used the xlate function to do it.  You could do the following:
eval field = caps('abc')
However that took a LONG time to run because it had to check all 32,702 
characters.  
Better to do the xlate function in your own program...

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *