Regular and non-regular data exchange
You can import and export data in LN on either a regular or a non-regular basis. A regular data exchange refers to a run that is scheduled on a regular basis. A non-regular data exchange is one that you run on demand, on an as-required basis. The results of both types are the same, but are used differently, depending on the situation and your business needs.
The sessions that you use for regular or non-regular data exchange are the following:
- Import Data (on a Regular Basis) (daxch0224m000)
- Import Data (Non-Regular) (daxch0223m000)
- Export Data (on a Regular Basis) (daxch0234m000)
- Export Data (Non-Regular) (daxch0233m000)
Non-regular data exchange is useful when critical data has changed that must be updated, or if not all of the data has changed and you want to update only the changed data. You can also use Non-regular data exchange if you want to test an exchange scheme before you approve the scheme for regular data exchange. For a non-regular data exchange, you can select a range of batches or a range of batch sequence numbers to import. The data exchange is restricted to these ranges.
You can use Regular data exchange if you want to maintain several sites whose data changes periodically. Regular data exchange is also useful in multisite situations in which it is critical that no run is lost, overwritten, imported twice, or imported in the incorrect order. Only complete exchange schemes can be imported and exported in a regular run, which ensures that no part is missed.
Regular data exchange uses the run number. The run number is unique and consecutive for a combination of exchange scheme and exchange type and is based on the contents of the log table. Each redo is stored under a new try number, which is unique within a run number, exchange scheme, and exchange type combination.
Regular and non-regular data exchange differ in where they place the physical ASCII files. A non-regular data exchange places the data in the sequential file directory, named at the exchange scheme level, in a file named in the Table Relations (daxch0531m000) session.
A regular data exchange builds an extra directory for each run of an export to retain a history of all exported files.