|
|
|
ctntfy reads input file ctntfy.in, which contains a list of servers and files to monitor.
Below is an example of an input file showing three servers and two files to monitor and their corresponding target files to update.
;Server id Server name
1 FAIRCOM1@localhost
2 FAIRCOM2@localhost
3 FAIRCOM3@localhost
;Source server id Source file Actions Target server id Target file
1 vcusti ADU 2 vcusti
1 custmaster.dat ADU 2 custmaster.dat
1 vcusti ADU 3 vcusti
1 custmaster.dat ADU 3 custmaster.dat
2 vcusti ADU 1 vcusti
2 custmaster.dat ADU 1 custmaster.dat
2 vcusti ADU 3 vcusti
2 custmaster.dat ADU 3 custmaster.dat
3 vcusti ADU 1 vcusti
3 custmaster.dat ADU 1 custmaster.dat
3 vcusti ADU 2 vcusti
3 custmaster.dat ADU 2 custmaster.dat
ctntfy creates a thread for each entry in the list of files to monitor. Each thread connects to the source and target server and opens the source and target files, then enables monitoring of the source file and reads queue entries as they arrive and processes them. The add processing has been verified to work with non-TRANPROC and TRANPROC files.
This example doe not hand delete and update requests as changes to the queue information must be provided for the utility to be able to find the record to delete or update in the target file. A suggestion for how this can be accomplished is the following: if a key that does not allow duplicates is available, include with a delete or update queue entry the key number and key value that can be used to find the record to delete or update in the target table.
