Highlighted
Absent Member.
Absent Member.
4901 views

Comp-X behavior

We have a variable defined as Pic X(5) Comp-X. This is able to handle 13 digits, which it does. However, whenever we move this value to a alphanumeric field, which is defined as Pic X(13), the high order digit is dropped and the field contains 12 digits and a space. If we would move the comp-x field to a numeric field, that is defined as Pic 9(13), and then move this to the alphanumeric field it moves all 13 digits correctly. There seems to be a bug in the way that Micofocus moves the comp-x field to alphanumeric. Is there a compile setting that must be used to get the correct behavior?

0 Likes
4 Replies
Highlighted
Absent Member.
Absent Member.

RE: Comp-X behavior

This is not a bug.  PIC X(5) COMP-X only handles 12 digits fully; because it's binary, it partially handles the thirteenth digit, but cannot handle a number 9999999999999 (13 nines).  Its maximum value is 1099511627775 (a 12-digit number) with the value h"FFFFFFFFFF" (10 hex-digits).  Thus the compiler assigns a digit-length of 12.

In the latest versions of Visual COBOL, what you want could be described as Pic 9(13) Binary(5).  This describes a 13-digit item in a 5-byte binary item.  Moves using this as a sending item will move a 13-digit number to an alphanumeric item.  As described above, the 13-digit item cannot contain a value greater than 1099511627775, that is, not all 13-digit values are possible.

This sample program:

      01 Digits12      PIC X(5) COMP-X VALUE 1099511627775.

      01 Digits13      PIC 9(13) BINARY(5) VALUE 1099511627775.

      01 Alpha13       PIC X(13).

          move digits12 to alpha13.

          display "alpha13 from digits12 = """ alpha13 """".

          move digits13 to alpha13.

          display "alpha13 from digits13 = """ alpha13 """".

when run, displays:

       alpha13 from digits12 = "099511627775 "

       alpha13 from digits13 = "1099511627775"

0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Comp-X behavior

The value 1099511627775 is 13 digits. There is no problem in moving the Pic X(05) Comp-X to a numeric 9(13) field. Also Acucobol has no problem with dealing with the field defined this way. Micro Focus is off by 1 byte in all comp-x lenghts from 1 to 8. Is a field defined as Pic 9(13) Binary(5) equivalent in lenght to a Pic X(05) Comp-X?

0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Comp-X behavior

Yes, the value 1099511627775 is 13 digits, but the type of the data item described by Pic X(05) Comp-X is 12 digits, and that is what is relevant in a move from numeric to alphanumeric.  Micro Focus is not "off by 1 byte" except by your interpretation and even then it would be off by 1 digit (not byte).  

Yes, the length of Pic 9(13) Binary(5) is 5 bytes (that's what the 5 in parentheses following Binary means), just like a Pic X(05) Comp-X (where the Pic X(05) specifies 5 bytes).  The problem with Pic X(05) Comp-X is that for COBOL purposes, a digit-length must be implied and Micro Focus chose the digit length that would always fit.  How ACUCOBOL chose to resolve the difference between binary representations and decimal representations in a decimal language such as COBOL is not relevant to the argument, only to an observation that this represents another ACUCOBOL vs. Visual COBOL compatibility issue in the subtle area of automatic conversion from binary to decimal to alphanumeric.

0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Comp-X behavior

Sorry I meant off by 1 digit. Acucobol is relevant since that is what we are trying to convert from. Another reason not to convert.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.