Re: Setting A Hex Value in COBOL

In article <2Fs7i.159356$oS7.144347@xxxxxxxxxxxxxxxxxxxxxx>,
William M. Klein <wmklein@xxxxxxxxxxxxxxxxx> wrote:

[snip]

If one wants to be "totally safe" it is NEVER a "good
idea" to put a 3 (decimal) digit value into a field defined with "PIC 9(2)" -
regardless of USAGE (unless using an implementer defined usage that SAYS
this is
OK, such as COMP-5 or COMP-X in some compilers).

I believe that the original poster specified that the target of the +229
VALUE clause was an S9(4) COMP field which had been REDEFINED into two PIC
X fields.

DD

.

Relevant Pages

  • Re: Setting A Hex Value in COBOL
    ... regardless of USAGE (unless using an implementer defined usage that SAYS ... VALUE clause was an S9COMP field which had been REDEFINED into two PIC ...
    (comp.lang.cobol)
  • Re: moving data from one place to another in a text file
    ... >> If it works on 90% of existing compilers AND is supported by the ... >> current standard, it qualifies as general in my thinking. ... Pretend this is one of the English Usage debates. ... allocation is common usage; someone else quotes The Book saying ...
    (comp.lang.cobol)
  • Re: Critique my assignment please
    ... of what you yourself are writing. ... Nobody knows how 99% of the implementations work. ... teeny-tiny fraction of the available C compilers. ... with related tools because of the wide usage. ...
    (comp.lang.c)
  • Re: What does "*" mean in "int main(int argc, char *argv[])"?
    ... >Unfortunately, there are some compilers that, incorrectly, accept 'void ... The incorrect part isn't that they accept it but that they fail to issue ... This compiler supports the usage of 'void main' as an extension. ...
    (alt.comp.lang.learn.c-cpp)
  • Re: Just want to know why
    ... "Dan Pop" wrote in message ... the usage of such compilers is not necessary. ... I am stuck with one of them at work. ...
    (comp.lang.c)