Jeff, I looked through the html file and have couple comments.
1)I don't understand the line in the first paragraph "You can specify the GENERATED ALWAYS or GENERATED BY DEFAULT options when using the procedure to define identity column values". I haven't paid close attention to changes to SYSCS_UTIL.SYSCS_IMPORT_DATA, but I don't think it needs to know if it is dealing with GENERATED ALWAYS or GENERATED BY DEFAULT. In fact, from what I know, there is no way to specify to the SYSCS_UTIL.SYSCS_IMPORT_DATA procedure whether it is dealing with GENERATED ALWAYS or GENERATED BY DEFAULT.
2)IMHO, the information on GENERATED ALWAYS and GENERATED BY DEFAULT is not flowing very smoothly on the html page.
I like the format for GENERATED ALWAYS where we first give the create table sql and then 2 different forms of import files and how to use the import procedure to import from them. In addition to these 2 examples for GENERATED ALWAYS, I think it will be good to add another example where user is trying to import from a file with values for identity column data and import procedure uses that data for GENERATED ALWAYS. Such an import will fail for GENERATED ALWAYS. eg
CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'TAB1', 'C1,C2,C3,C4' , '1,2,3,4','empfile.del',null, null,null,0)
We should keep similar format for GENERATED BY DEFAULT. Show create table sql for it, and then show couple examples of import data file where the value is specified for the column or DEFAULT is specified for the column or the column values are not included in the import data file. And then for these various import files, show how data can be imported into the table with GENERATED BY DEFAULT.