DataLoader/MX Reference Manual (G06.24+)

Running DataLoader/MX
DataLoader/MX Reference Manual—525872-002
3-8
Syntax of DataLoader/MX
did not redirect stdout, you used the -Q option, you can obtain more information
by rerunning the job without -Q.
-S=num-recs [<CSV[=out-file]>]
directs DataLoader/MX to print periodic status messages.
num-recs
is the number of input records that are processed between status messages.
<CSV[=out-file]>
if specified, causes messages to appear in a comma-separated value (CSV)
format suitable for loading into a spreadsheet for analysis or graphical display.
If =out-file is specified, the CSV status information is written to this file. If =out-
file is omitted, the status information sent to the terminal appears in CSV
format.
When you specify -S, if you open a DataLoader/MX process with the
#CMD.STAT qualifier, it prints the current statistics.
-T=num-recs [ <RESTARTFILE=restart-file [<{KEEP | PURGE}>]>]
directs DataLoader/MX to bracket records within HP NonStop Transaction
Management Facility (TMF) transactions. If a DataLoader/MX process fails within a
transaction, TMF backs out changes associated with records in the currently active
transaction and returns the database to the state it was in after processing the last
record in the last committed transaction. After resolving the problem that caused
the failure, you can restart the operation at that point. Information to facilitate such
a restart is put into restart-file.
num
is the number of input records per TMF transaction. If num is large, the
resources consumed by database changes associated with the records in the
transaction might hit a TMF limit, and the transaction could be aborted by TMF.
If num is very small, the TMF and DataLoader/MX costs per transaction are
excessive. Some experimentation is usually necessary to determine an
appropriate value for num.
restart-file
is the name of the restart file, which must be a Guardian file name.
DataLoader/MX generates a restart file with the name specified if the file does
not already exist. This file is an audited relative file with a record size of 20.
When DataLoader/MX successfully commits a transaction, it writes the last
number of records read from input to this file. If an error occurs, this file
contains the record number that was committed successfully. When
DataLoader/MX is restarted with this restart file, the previously processed