RE: Replication and 4GL code

If you use asynchronous mode, i.e., DRINTERVAL not = -1 (see p. 25-11 in Admin. Guide), then you should see no impact at all when the secondary goes down. I *HIGHLY* recommend async mode for this reason, and also because you will probably take a performance hit, *even when everything is running OK*, if you run in sync mode. This is simply because every commit waits for the commit to happen on secondary before completing it on the primary -- basically, you have a 2-phase commit. And I would also recommend staying away from automatic failover, i.e., keep DRAUTO=0 (see pp. 25-17 thru 25-22 in the Admin. Guide). Might as well get used to that mode, anyway, since that is your ONLY "option" in IDS.2000!! HTH, Paul Mosser -----Original Message----- From: Cams [mailto:cmoore@fiscal.org.jm] Sent: Tuesday, September 26, 2000 1:18 PM To: informix-list@iiug.org Subject: Replication and 4GL code Hi there. We are planning to implement our application on version 7.31,UC3 with HDR enabled and the powers-that-be have a problem accepting how easy HDR is. So, the last question posed to the techies was "What happens to 4GL code in execution if and when replication has been interrupted?" I assumed they meant if the network link goes down or some other catastrophe such as that. Does anyone here have any experience to lend some enlightenment? Thanx, Cams -- ---------------------------------------------- Camille Moore DBA - Fiscal Services Ltd. (Jamaica) Sent via Deja.com http://www.deja.com/ Before you buy.