Nablarch batches are divided into two types depending on the startup method:
In addition to this classification, the batches can be divided into the following three patterns by the input and output combination.
The combinations are as follows.
|FILE to DB||DB to DB||DB to FILE|
(Resident batches typically monitor the database, so there is no combination with FILE to DB)
FILE to DB
In FILE to DB batch, INSERT of files into temporary tables is performed without adding any business processes to the possible extent. This provides the following benefits:
DB to DB
DB to FILE
Although the DB is transaction-managed, file writing is not managed, so there may be inconsistencies when a failure occurs.
Combinations other than the above (FILE to FILE)
For example, a common batch process is to “match two files while outputting one file.” In this case, it means FILE to FILE, but this form is not used in Nablarch batches. After importing each file into the DB, the same processing can be performed by JOIN in SQL.
Although it is possible to use Nablarch batches to perform file processing such as matching and control breaks, which are common in mainframe batches, there are problems such as the complexity of batch programs and difficulty in determining how much to handle in a file and how much in a DB. Instead, using a combination of the above patterns will make each batch simpler, easier to design, and less likely to include bugs.
When performing FILE to DB or DB to FILE, moving or copying files in the batch process is not included.
The following batch processes are assumed to be implemented.
If the process fails in step 2, an operation to return the input file to its original directory is necessary before re-executing.
By moving and copying the files separately, the following advantages can be obtained.
Copyright 2020 TIS Inc.keyboard_arrow_up