| Exchange scheme designers information |  |
| In the Table Relations (Import) (daxch0121s000) session you can enter a name of a session or 4GL program in the Program Name field. If you want to overrule the generated script, you can program the exchange script yourself. If you want to create your own script, you can use the following information which describes the interface between the Import Data (Non-Regular) (daxch0223m000) and Import Data (on a Regular Basis) (daxch0224m000) sessions. Program Interface From the above mentioned sessions the following variables are passed as parameters to the session or 4GL program:
arg | type | description
1 | domain daxch.cxch | exchange scheme
2 | domain daxch.cbat | batch
3 | domain daxch.batl | batch line
4 | domain daxch.txch | exchange type: (non-)regular ex- or import
5 | long | current run number
6 | long | current try number
7 | long | processing company: the company data is exported from or imported to
8 | long | startup company: the company the Exchange (XCH) module is running in
9 | domain daxch.redo | processing type (new run, restart, reprocess or continue)
10 | domain daxch.yesno | reprocess error rejected records?
11 | domain daxch.yesno | reprocess condition rejected records?
12 | domain daxch.yesno | wait for <CR> with messages?
13 | string | calling program: daxch0227
Note Do NOT import the form variables: adat.f, adat.t, atim.f, atim.t. They can and will differ from the actual audit interval, for example in a job. It is assumed that the log file is updated by the subprocess (in company process.comp) and that the variable stop.processing is exported to the parent process (by the subprocess) if necessary. Refer to session Predefined Functions/Variables (daxch0510s000) for information on how to update the log file. If processing type = new run, then try number = 1; otherwise try number > 1. If processing type = reprocess, then at least one of argument 10 and 11 will be yes, otherwise both will be no. |