Top
NetCOBOL V11.0.0 Release Notes
FUJITSU Software

2.2.5 Interchangeable information regarding bug fixes

Here, it explains bug fixes corrected by NetCOBOL V10 or later version in which the operation of the NetCOBOL development environment changes in the following tables.

Table 2.2 Interchangeable information on bug fixes of NetCOBOL Runtime Environment

No.

V/L(*)

P number

Content

1

V10.1.0

PG97090

The problem of not correctly replacing the alternative character specified for argument-2 was corrected when there was no national character corresponding to the character converted by the NATIONAL-OF function when the COBOL program was executed under the following conditions.

  1. It is a program compiled using compiler option RCS(UTF16,BE).

  2. And, the NATIONAL-OF function is used.

  3. And, Argument-2 is specified for the function of No.2.

And, data that is not alphanumeric characters is specified for argument-1 in No.2 above, and the code conversion error (there is no corresponding National character) occurs internally.

2

V10.1.0

PG76651

When all of the following conditions are met while executing a COBOL program, a size comparison of national items varying in length (national language edited item, including the intrinsic function) was incorrect.

  1. Compiler option RCS(UCS2,LE) or RCS(UTF16,LE) is specified.

  2. And, there is a size comparison of National item and National item or National language character constant.

  3. And, at least one side is an item with the ANY LENGTH clause is specified or reference modification.

  4. And, the length of the compared targets differs.

3

V10.1.0

PG87250

Under the following conditions, the MOVE result by internal Bool item is incorrect.

Note: The move result is different according to the state of the area allocated just behind the sending data item.

[Condition 1]

  1. Move from internal Boolean item to internal Boolean item.

  2. Data start position (*) of the sending data item is different from data start position of the receiving data item.

  3. [a] + [b] > 32, or [c] + [d] > 32

    a: Data start position (*) of the sending data item

    b: The length of sending data item or the length of receiving data item, whichever is smaller.

    c: Data start position (*) of the receiving data item

    d: The length of receiving data item

  4. The receiving data item is subordinate to the group item.

  5. Data start position of the receiving data item is not one byte alignment of the group item in 4.

  6. "Bit length of sending data item" < " Bit length from bit data starting location on the receiving side to the first byte boundary "

  7. Bit data of sender data item is outside the byte boundary or Byte boundary exist between the start position of the sender’s data item of paragraphs 6(*) (bit length till the byte boundary of the first recipient).

*: relative bit position in byte

Example of Condition 1

        DATA DIVISION.
        WORKING-STORAGE SECTION.
        01 DATA1.
          02 DATA1-1 PIC 1(5) BIT.
          02 DATA1-2 PIC 1(4) BIT.
          02 DATA1-3 PIC 1(7) BIT.
        01 DATA2.
          02 DATA2-1 PIC 1(1) BIT.
          02 DATA2-2 PIC 1(32) BIT.
        01 ANS-DATA  PIC 1(32) BIT VALUE B"1111".
        PROCEDURE DIVISION.
             MOVE X"FFFF" TO DATA1.
             MOVE DATA1-2 TO DATA2-2.
             IF DATA2-2 = ANS-DATA
               THEN DISPLAY "OK"
               ELSE DISPLAY "NG"  *> B"11111110-00000000"
             END-IF. 

[Condition 2]

  1. Move from internal Boolean item to internal Boolean item.

  2. The sending data item or the receiving data item is referred by the subscript.

  3. " The length of receiving data item " > 1

  4. It is either the following.

    • "The length of sending data item" > 1

    • The receiving data item is referred by the subscript.

    • " The length of receiving data item " > 25

  5. There is not the data starting location of the receiving data item on byte boundary.

  6. "Bit length of sending data item" < " Bit length from bit data start position of first byte of the receiving data item

  7. The bit data of the sending data item overlaps the byte boundary, or there is byte boundary between from start position of the sending data item to "Bit length from bit data start position of the receiving side to the first byte boundary" in 6.

Example of Condition 2

        DATA DIVISION.
        WORKING-STORAGE SECTION.
        01 DATA1.
          02 DATA1-1 PIC 1(5) BIT.
          02 DATA1-2 PIC 1(4) BIT.
          02 DATA1-3 PIC 1(7) BIT.
        01 DATA2.
          02 DATA2-1 PIC 1(10) BIT OCCURS 5 TIMES.
        01 ANS-DATA  PIC 1(10) BIT VALUE B"1111".
        01 CNT        PIC 9 VALUE 2.
        PROCEDURE DIVISION.
             MOVE X"FFFF" TO DATA1.
             MOVE DATA1-2 TO DATA2-1(CNT).
             IF DATA2-1(CNT) = ANS-DATA
               THEN DISPLAY "OK"
               ELSE DISPLAY "NG"  *> B"11111110-00000000"
             END-IF. 

*: V/L is a scope where the bug exists.