Very close, but yes. When the routine hit asid 00E0, they compared favorably. In diagnosing this, it wasn't until I added the datatype() function to both the current loop asid and the lookup asid and they both came out as NUM did I figure it out. Duh.
I had long figured out that I could use strictly equals, but I wanted to get to the root cause. What do you win... Had you been siting over my shoulder and found the problem 1 hour prior to me sending my post to this list, you would have won a new car. Alas, as it is now, well.... you win squat. Both you and Mark Wheeler do get recognition from your peers that you are both REXX savvy and not to be reckoned with. How's that? Thanks, Todd. ----- Original Message ----- From: "Phil Smith III" <[EMAIL PROTECTED]> > > I bet it had to do with the fact that you were using "=" rather than "==", so 0E01 = 0000 ... > > What do I win? > > ...phsiii (Everybody gets bitten by this one once!) > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
