MUPIP LOAD needs to warn if zwrite/go format extract file is missing 2-line header
Final Release Note
Description
Below is an example demonstrating the issue. The extract file x.zwr
has 3 lines of data but is missing the 2-line header that each zwrite/go extract file usually has. The user created such an extract file by mistake.
$ cat x.zwr
^x(1)="1"
^x(2)="2"
^x(3)="3"
$ mupip load x.zwr
^x(1)="1"
^x(2)="2"
Beginning LOAD at record number: 3
LOAD TOTAL Key Cnt: 1 Max Subsc Len: 6 Max Data Len: 1
%YDB-I-LOADRECCNT, Last EXTRACT record processed by LOAD: 3
$ yottadb -direct
YDB>zwrite ^x
^x(3)=3
As you can see above, only ^x(3)
got loaded. ^x(1)
and ^x(2)
did not. They got treated as the 2-line extract file header and skipped.
It would be better to issue an error if the 2-line extract file header does not conform to a valid header. The current behavior of silently skipping the first 2 lines would confuse the user as some of the data that they tried loading did not get loaded and the user has no clue.
Draft Release Note
Edited by Narayanan Iyer