The search http://vm.marist.edu/htbin/wlvindex?cmspip-l#search isn't
turning up anything (and I mean ANYTHING!)... looks broken.

Maybe I'm just having a bad day (probably), or maybe the doc is a little
weak (maybe).

In a stream of records with real device addresses (the usual hex, from
0000-FFFF) in them.  I'd like to select those within a certain range.
The records (from a CP directory) look like (where vdev and rdev are the
hex address within the 0000 to FFFF range):

_userid_ DEDICATE vdev rdev

I was using:
...
'| SPECS W1.3 1 PAD 0 W4 NW.4 RIGHT' , /* Ensure 4-digit hex number for
X2D   */
'| SPECS W1.4 1 W4 X2D NW' ,           /* Convert rdev to decimal for
compare */
'| PICK W4 >==' loDevNum ,
'| PICK W4 <==' hiDevNum ,'
...

That X2D conversion works "as expected" in rexx.  E.g. FFFF = 65535
But with SPECS X2D, FFFF = -127
Obviously, it's respecting the high order bit.
High astonishment factor.  Makes me wonder what older pipes I've written
using this
type of conversion which will eventually fail?

I must have missed the doc in the Piper's manual that explains this
(it certainly wasn't in the SPECS doc).  To be fair, it does state:
"Note that the REXX name for a conversion function can be misleading:".
Where should I look for the doc?

And... is there a better way to do this?

Maybe tomorrow won't be another bad day...

Mike (relapsing back to plumber's apprentice) Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not necessarily
represent the opinions or
policies of Hewitt Associates.




The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail.

Reply via email to