vgobiraj
3rd January 2002, 20:05
Is there any way(other than using AFS) to execute an exchange scheme using Baan 4GL/3GL code.


Thanks

toolswizard
11th January 2002, 21:35
If you have source code you could make a customized version of script tuxch0234 which does the acutall running of the exchange script (program).

You may even be able to call the import/export session itself to do the run.

You can also run it as a batch job.

Please describe what you are attempting and I can be more specific in helping you.

vgobiraj
12th January 2002, 22:37
Thanks for ur input.

We don't have source code.

My requirement is to closely monitor the export.

e.g. Ensure that there was no error and the data file is created.
(capture the run number check the log...etc)


So my idea was one 4GL script, which can invoke the exchange
scheme and then check/monitor the status of the export.

isimeon
14th January 2002, 11:51
wait.and.activate("tuxch0223m000", arg1, ... ,arg9)

Arguments for regular import:
1. exchange scheme from
2. exchange scheme to (optional argument, default is equal to exchange
scheme from)
3. quit on stop condition: 0 = no, 1 = yes (optional argument, default is
no)
4. type of processing: 1 = new run, 2 = restart, 3 = continue (optional
argument, default is new run)
5. import/export company (optional argument for overruling the company
specified in the batch(es), if this argument is not given, the batch
company will not be overruled)

Arguments for regular export are the same, only argument 3 is missing.

Arguments for non-regular import:
1. exchange scheme from
2. exchange scheme to (optional argument, default is equal to exchange
scheme from)
3. batch from (optional argument, default is minimum value)
4. batch to (optional argument, default is equal to batch from)
5. batch sequence number from (optional argument, default is minimum value)
6. batch sequence number to (optional argument, default is equal to batch
sequence number from)
7. quit on stop condition: 0 = no, 1 = yes (optional argument, default is
no)
8. type of processing: 1 = new run, 2 = restart, 3 = continue (optional
argument, default is new run)
9. import/export company (optional argument for overruling the company
specified in the batch(es), if this argument is not given, the batch
company will not be overruled)
Arguments for non-regular export are the same, only argument 7 is missing.

Note:
- If an optional argument is specified, all previous optional arguments
should also be specified.
- 'Wait for <cr> with messages' will be set to no.


After export/import you can check xch tables.

toolswizard
16th January 2002, 01:14
Why not let the exchange scheme report on itself. In the stop condition you could check the different error fields for greater than 0. If it is email your self or print the log, or email the log to yourself. The choice is yours. There are a number of variables and functions available to you. You can also create your own error report right inside of exchange and send that to yourself.