Strip is not required at all here (parse splits in words; except for the last one, but the . following "w11" makes w11 is without blanks too). And uppercasing can be done in PARSE too, hence parse upper var cmdtrap w1 w2 w3 w4 w5 w6 w7 w8 w9 w10 w11 .
2010/5/31 Tony Thigpen <t...@vse2pdf.com> > Try changing: > cmdtrap = strip(data.1) > to > cmdtrap = upper(strip(data.1)) > > Tony Thigpen > > -----Original Message ----- > From: Berry van Sleeuwen > Sent: 05/31/2010 05:14 AM > > Hello listers, > > > > We have a rexx exec called by PROP when an event occurs. But it didn't > give > > us the result we were expecting. I have changed the exec now, hopefully > it > > will be good. But still, why didn't the exec work the way I expected? I > have > > tried to replicate the result but was not able to. > > > > Exec PR_VSRVD looks like: > > > > Address Command > > 'PIPE (end \) stack | stem data.' > > If data.0>0 Then Do > > cmdtrap = strip(data.1) > > parse var cmdtrap w1 w2 w3 w4 w5 w6 w7 w8 w9 w10 w11 . > > If w1 = 'DMSFRO159E' & w2 = 'INSUFFICIENT' & w10 = 'FROM' Then DO > > < do some stuff here > > > End > > End > > > > Now I would expect the "IF" statement to trigger if w1, w2 and w10 are > like > > above. But looking at the trace: > > > > *-* IF W1 = 'DMSFRO159E' & W2 = 'INSUFFICIENT' & W10 = 'FROM' > >> "DMSFRO159E" > >> "DMSFRO159E" > >> "1" > >> "INSUFFICIENT" > >> "INSUFFICIENT" > >> "0" > >> "0" > >> "FROM" > >> "FROM" > >> "0" > >> "0" > > > > When testing the same thing manually all compares are "1" and the do-end > is > > triggered. > > > > What could be the cause of this? Could PROP or something else in OPERATOR > > cause the exec to behave differently? > > > > Note, this is on VM 2.2, CMS level 13. (And before anyone notices, Yes I > > know, there is no point in comparing w2 and w10 since w1 is actually that > > message so the new exec only triggers on w1.) > > > > TIA, Berry. > > > > > -- Kris Buelens, IBM Belgium, VM customer support
