Back | Forward

The header record format is always the same regardless of the type of batch processing to be performed (insert/modify/delete). Output files are always opened in append mode; it is possible to collect the results from several batch processing runs in a single file or single pair of files. However, two batch processes that run concurrently cannot write to the same output file (or files) because the files are not open for sharing.

• If you provide only a single output file for data import, it will contain both error messages and the data for any transaction that FASuite could not process because of an error.

• Assuming that FASuite is to write the output file in the working directory and is to name it import_1.out, the header record would look like the following example:

•  ./import_1.out<newline>

• If the batch processing consists of data import, the header record may optionally contain the name of a second output file.

• If you provide two file names for data import, the first file contains error messages and the second file contains the data for any transaction that FASuite cannot process because of an error. This feature makes it easy to resubmit only the transactions that FASuite rejects, after you correct the reported errors and prepend the two header lines to the second file.

• If you provide a second file name, you must separate the names with a semicolon (;). Assuming that FASuite is to write errors to import_1.err and rejected transactions to import_1.rej and both files to the working directory, the header record would look like the following example:

•  ./import_1.err; ./import_1.rej<newline>