TABLE — The name of the target tableBASE table.
TABLE-OWNER — The schema owner of the source DB2 table. Must match the value in the Punch File exactly.
DB2TABLE-NAME — The name of the source DB2 table. Must match the value in the Punch File exactly. This value is case-sensitive.
ORG — The tableBASE table organization. See valid values below.
METHOD — The tableBASE access method. See valid values below.
KEY-SIZE and KEY-LOCATION — The byte size and row offset of the key. Mutually exclusive with KEY-COLUMN. Both must be specified together on separate lines.
KEY-COLUMN — The name of a DB2 column to use as the table key. Mutually exclusive with KEY-SIZE and KEY-LOCATION. VARCHAR, DECIMAL, and SMALLINT column types are all supported.
VAR-LEN-LOC — Controls where the length prefix for variable-length columns (VARCHAR, VARBINARY) is stored in the row. The default value is ASIS, which leaves the prefix in line with the column data. Specifying ATEND moves all length prefixes to the end of the row.
NULL-IND-LOC — Controls where null indicators are stored in the row. The default value is ASIS, which leaves them in line with their associated columns. Specifying ATEND moves all null indicators to the end of the row.
Use KEY-COLUMN when the key column offset within the row is not known, or when defining a composite key from multiple named columns. To define a composite key, specify one KEY-COLUMN entry per column, listed in the intended sort order.
When KEY-COLUMN is used, ETL automatically determines whether the specified key columns are contiguous within the row. If they are not contiguous or are out of sequence, ETL relocates them to the beginning of the row in the order specified, duplicating those columns in the process. If the key columns are already contiguous and in order, no relocation is performed.
There should be one line per item starting in column 1. The value for each Keyword must begin in column 17.
Relocating both VAR-LEN-LOC and NULL-IND-LOC to ATEND produces a consistent row size and prevents variable-length prefixes from affecting key composition and sort ordering. When either option is set to ATEND, a COBOL copybook should be generated to accurately reflect the resulting layout.