Changes between Version 1 and Version 2 of SchedTechManual/ServerChanges1_7

Timestamp:

Jul 10, 2012, 2:10:54 PM (12 years ago)

Author:

Sam Habiel

Comment:

--

SchedTechManual/ServerChanges1_7

@@ -4 +4 @@
 There are three issues:
 
-The interaction between transactions and locking causes a freeze in GT.M that looks like this:
+1. The interaction between transactions and locking causes a freeze in GT.M that looks like this:
 {{{
 GTM[******]: %%GTM-W-MUTEXLCKALERT, Mutual Exclusion subsystem ALERT - lock attempt threshold crossed for region /var/worldvista/globals/mumps.dat.  Process 17141 is in crit. -- generated from 0x00002B158FF975CD.
@@ -10 +10 @@
 The Scheduling GUI did a lock itself outside of the transaction in BSDX07, and Fileman did a bunch of locks internally inside the transaction.
 
-Cache users will fail with an UNIMPLEMENTED error if we use the full transaction syntax
+2. Cache users will fail with an UNIMPLEMENTED error if we use the full transaction syntax which is required on GT.M.
+
+3. Long running transactions present a problem to VISTA because unfiled transaction data can overwrite data not done via a transaction which is filed immediately. For example, in a transaction, Fileman creates records using the next available record number and files the data there. If two transactions do that at the same time that are not synchronized, we can overwrite the record; also, code outside of transactions will write the record first.
+
+Due to all of these reasons, I decided to completely remove Mumps Transactions from the Scheduling GUI code.