README for HP Neoview Release 2.4 Service Pack 2

New Control File Generator Option
When the Control File Generator creates a control file, by default, it populates the sources section
with a default data file named ./datafiles/nvt_datafile.dat. This example shows the
default data file in the sources section of a control file:
sources {
ACCT_src file "./datafiles/nvt_datafile.dat",
ACCT_tgt jdbc table NEO.USR.ACCT
}
The Control File Generator has a new optional argument, -srcfile, which allows you to specify
the names of data files of your choice. For example, if you specify -srcfile mydatafile, the
Control File Generator populates the sources section with the file name that you specified instead
of the default file name:
sources {
ACCT_src file "mydatafile",
ACCT_tgt jdbc table NEO.USR.ACCT
}
The source corresponding to the specified table now uses the file name that you specified instead
of the default file name.
The syntax of the Control File Generator now includes the -srcfile option:
java -jar/NVTHOME/utils/nvtControlFileGen.jar ...
-url URL_of_the_Neoview_server
-user username
-pw password
-sys system_name
[-cat catalog_name]
[-schema schema_name]
[-srcfile src-file-list]
[-file pathname]
[-temp template_file]
[-jobtype "load" | "extract"]
[-single "true" | "false"]
[-version]
[-help]
Optional Argument
-srcfile src-file-list
Specifies the names of data files to be used in the sources
section of a control file. The src-file-list is a
comma-separated list of file names. The number of file names
that you specify must match the number of tables that you
specify for generation.
If not specified, the name of the data file defaults to
./datafiles/nvt_datafile.dat.
For more information about the Control File Generator, see the Neoview Transporter User Guide
for Release 2.4.
Compression Option
Before Release 2.4 SP2, the Neoview Transporter used only the exploded rowset format while
creating rowsets for staging table and nonaudited loads. For example, if a column was defined
as VARCHAR(200), but most of the data was only 20 characters long, the Transporter would
expand all the data to 200 characters, padding the data with trailing spaces, even though most
of the data did not need to be expanded.
In Release 2.4 SP2, the Neoview Transporter introduces a new compression feature that uses a
run-length encoding (RLE) algorithm to compress data that is compressible, such as varchars,
during staging table and nonaudited loads.
12