Re: %trim and %trimr Not Working on a 32767A Field

So Scott... are you saying to use varying then?

On 10/13/06, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> wrote:

WARNING you are using *VARSIZE in an unsafe manner.  You are risking
accessing other areas of memory that you shouldn't be.  That can
potentially crash your program, but most of the time you'll just end up
with extra garbage in the parameters.  *VARSIZE is a dangerous option,
make sure you understand how it works before using it!

This would be much worse if you were changing the variables.

Whenever you use *VARSIZE you must also pass the LENGTH of the variable as
a separate option, or get the length from an operational descriptor.  Then
you have to write your code in a special manner that ensures that you only
refer to the length passed in.

When you use *VARSIZE, the procedure doesn't know how long the data
actually is.  It thinks it's always the maximum size (the size defined on
the D-spec) and when you pass something shorter, it tries to just "keep
reading" and goes beyond the end of the variable into other areas of
memory.

--
Scott Klement  http://www.scottklement.com

On Fri, 13 Oct 2006, Mike wrote:

> Just as the subject says. I am wring a subproceedure that can take in
any
> length of field. I am trying to trim down the field to the proper size,
but
> it isn't. Here is the code:
>
>     P SendBatchEmail  B                   EXPORT
>     D SendBatchEmail  PI
>     D  fromAddress                 100A   CONST
>     D                                     OPTIONS(*VARSIZE)
>     D  toAddress                 32767A   CONST
>     D                                     OPTIONS(*VARSIZE)
>     D  ccAddress                 32767A   CONST
>     D                                     OPTIONS(*VARSIZE)
>     D  bccAddress                32767A   CONST
>     D                                     OPTIONS(*VARSIZE)
>     D  subject                   32767A   CONST
>     D                                     OPTIONS(*VARSIZE)
>     D  body                      32767A   CONST
>     D                                     OPTIONS(*VARSIZE)
>
>      /free
>
>        cmd = 'SBMJOB CMD(CALL PGM(BATCHEMAIL) ' +
>              'PARM(''' + %trim(fromAddress) + ''' ''' +
>                          %trim(toAddress) + ''' ''' +
>                          %trim(ccAddress) + ''' ''' +
>                          %trim(bccAddress) + ''' ''' +
>                          %trim(subject) + ''' ''' +
>                          %trim(body) + ''') JOB(SNDEMAIL)';
>
>        ExecClCmd(cmd);
>
>      /end-free
>     P SendBatchEmail  E
>
> After the assignment to cmd, it contains "SBMJOB CMD(CALL
PGM(BATCHEMAIL)
> PARM('me@xxxxxxxxxxxxxxxxxx' 'me@xxxxxxxxxxxxxxxxxx
> ..." A ton of spaces and no ending quote mark. Any ideas? I am sure I am
> doing something stupid, I just can't see it.
>
> --
> Mike Wills
> Blog - http://mikewills.name
> Podcasts - http://theriverbendpodcast.com
> --
> This is the RPG programming on the AS400 / 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.
>
--
This is the RPG programming on the AS400 / 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.