On Mon, 23 Jul 2007 10:24:12 -0500, Paul Gilmartin <[EMAIL PROTECTED]> wrote:
>On Mon, 23 Jul 2007 08:23:38 -0600, Steve Comstock wrote: >> >>Depends what you mean. >> >>x'FACE' is a hexadecimal number, right? (= 64206 in decimal, >>if an unsigned number). >> >>c'FACE' is one way of representing it in EBCDIC >> >>So you want to convert c'FACE' to x'FACE'? >> >>Or are you talking zoned decimal, packed decimal, >>or floating point numbers? >> >>Give us some info on the parameters that bound your >>problem. >> >There's a pervasive ambiguous and careless usage in this area. >One of my favorite (not!) examples is: > > Title: z/OS V1R7.0 MVS Assembler Services Reference ABE-HSP > Document Number: SA22-7606-07 > >91.0 ENQ -- Request Control of a Serially Reusable Resource > * 91.1 Description > 91.1.8 Parameters > > qname addr > Specifies the address of an 8-character name. The name can contain any valid > hexadecimal character. ... > >OK. The adjectives "valid" and "hexadecimal" appear to be restrictive -- It's >pretty hard to expand the scope of "any". I'd infer that some characters are >not valid, ... >The meaning would be clearer if the two adjectives were omitted and it >simply said "any character". >... Better written documentation points to a code page or other specific definition of "valid character". In any case, the word "hexadecimal" as they used it makes no sense. "Binary" would have been just as meaningful (or meaningless). Pat O'Keefe ---------------------------------------------------------------------- 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
