Polling
Sends data between two sites, usually a branch computer and the HO server. Polling consists of several programs working in unison to create, filter and process data to a store. The programs are controlled by commin. The parameters used with the programs are accessed/altered by comaad.
General Polling Process
- Transaction or File Maintenance record is created/altered
- Transaction or File Maintenance record changes are saved to a file
- File is filtered for certain transaction/record types
- File is sent to peer
- Peer filters file for certain transaction/record types
- Peer adds transaction/record changes into it's own database
Polling File Maintenance Records
When a new file maintenance record is added, a copy of the record (along with some extra information) will be placed in the "logfile" (log.dat). When you delete a record, an entry in the logfile will also be created. Altering a file maintenance record will create two entries in log.dat. One will be a snapshot of the record before the change and the other will be a copy of the record after the change.
XXaad creates entry(s) in log.dat
logmin reads entries from log.dat and only outputs certain record types into slog.dat. Effectively, logmin acts as a filter.
- slog.dat is sent to the other location
On the other end, logmin reads certain entries from slog.dat and outputs it to another file
On the other end, XXaad processes output file and applies changes.
Transactions
XXeat creates an entry in daytrn.dat
sen2post copies the entries from daytrn.dat, adds a bit of extra information and outputs it to sendtrn.dat
sendpost reads sendtrn.dat and outputs certain transactions to rsndtrn.dat
- rsndtrn.dat is sent to other computer
On other computer, sendpost reads in rsndtrn.dat, filters transactions and outputs to sendtrn.dat
On other computer, reclstr converts sendtrn.dat to daycomm.dat, which just a structurally the same as daytrn.dat
On other computer, XXpost will now add transactions to its transaction history file