Re: %scan not working as I'd expect...

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

hi Bryce,

'Criteria' can't possibly contain 'HOSPITAL' as you suggest, because 
Criteria is 30A, not 8A.  So more likely it contains 
'HOSPITALbbbbbbbbbbbbbbbbbbbbbb' (where 'b' indicates a blank)

However name1 doesn't contain 'HOSPITALbbbbbbbbbbbbbbbbbbbbbb', it
'**MY EXAMPLE HOSPITALbbbbbbbbb'.  there aren't enough blanks following 
'HOSPITAL'

If you change name1 to be 51A, it'll successfully find the string, 
because now there are enough blanks.  Alternately, you could trim the 
blanks off of 'Criteria':

    pos = %scan(%trimr(Criteria): name1);

Or you could use a VARYING field, and not assign the blanks to begin with.



On 11/3/2010 10:55 AM, Bryce Martin wrote:
> I'm trying to use the %scan bif and it doesn't seem to be working.  I must
> really misunderstand how it works or something....
>
> short example....
>
>       D Criteria...
>       D                               30a             //parameter for my
> procedure.
>
>       D name1...
>       D                 s             30a
>       D pos...
>       D                 s             10i 0
>        /free
>          ....some sql code to populate name1.
>
>             pos = %scan(Criteria : name1);
>
>          ....some more code later on
>        /free
>
>
> I'm using a SEP to debug this.  When the %scan is performed the value of
> pos is being returned as 0.  Criteria = HOSPITAL, name1 = '**MY EXAMPLE
> HOSPITAL'
>
> Why is pos = 0?  HOSPITAL is CLEARLY in there...  shouldn't it return the
> position on the H?  Which in the real data for my first record I would
> expect to be position 19.  In this example I would expect it to return
> position 14.
>
> Am I missing something?