Retries, Rowsetsize, Sorted – HP Neoview Release 2.3 Software User Manual
Page 53: Startseq, Retries rowsetsize sorted startseq
password
specifies the password to use when connecting to a JDBC, ODBC, or JMS data source.
•
password
specifies a plain-text password.
•
${referencename}
refers to a plain-text password in the plain property file. Transporter
automatically substitutes the corresponding password when it processes the control file.
•
$E{referencename}
refers to an encrypted password in the encrypted property file.
Transporter automatically substitutes the corresponding decrypted plain-text password
when it processes the control file.
The maximum length of any plain text password is 64 characters.
retries
retries = number
The default value is 3.
This option specifies how many retry attempts Transporter should make to establish a database
connection, open a JMS source, or open a named pipe on behalf of a job.
retries = number
can be zero or a positive integer.
The
option specifies how long to wait on each attempt.
rowsetsize
rowsetsize = number_of_records
The value must be an integer in the range from 1 to 100000.
This option specifies the number of records in each batch of rows Transporter exchanges with
the Neoview database.
If this option is not specified, Transporter chooses an optimized value based on the Neoview
SQL table or query.
sorted
sorted = true | false
The default is false.
For a load operation, this option specifies whether source files are sorted by the table’s primary
key. Transporter can improve performance and parallelism of certain database operations when
data is sorted by the primary key.
Errors can be returned if sorted is true and input data is not properly sorted.
For a load operation where the
is “insert”, if the
option is true, the sorted option must also be true, otherwise an error is returned.
This option is ignored for extract operations.
startseq
startseq = "sequence of characters"
startseq
, along with the
option, are specific to named pipe sources and
allow specification of start and end sequence records.
This is an optional feature to allow data synchronization between Transporter and your
applications.
The start and end sequence records are considered “substitute” records. Whenever one of these
records is written to the pipe (either by Transporter during an extract operation, or by the
application during a load operation), it is terminated by an appropriate record separator.
sequence of characters
should not contain a record separator.
retries
53