|
|
|
When the FD does not explicitly define a record size (using COBOL-specific syntax), xddgen determines the minimum and maximum record length by looking at the minimum and maximum record size of the various records layouts (level 01).
When COBOL does not specify a record length, the record is always fixed-length, but the records layout may have different sizes and so the generated XDD have different minimum and maximum lengths, which then (depending on how these are set) fail the check against the physical file record length causing a 4110 error (CALLBACK_2).
The logic has been changed so that, if the record length is not specified, it considers the record as fixed-length and uses the first record definition length as the "base length." It then checks each record size against the specified or calculated record minimum and maximum lengths and prints a warning if its size is outside of the expected range.
The XDD will be generated using the minimum and the maximum record lengths found in the various record definitions (schemas) as it always was.
If the XDD is going to generate information with different minimum and maximum record lengths (thus implying a vlen file) but the COBOL source did not specify the record as variable length, a warning message is printed. It is recommended to modify the COBOL source to resolve these warnings.
It was also identified that the size of COMP-4 for default AcuCobol configuration was not correct. The "binary-size" has been updated to the proper setting of "2-4-8" in acu.conf and acu-Ds.conf.
