If you use an XAE Type 1 database to store AutoEdit variables, the variables are stored both in the Extended Common Service Area (ECSA) and using the Coupling facility.
The advantage to this method of storing AutoEdit variables is that resolving the variables from the originating, owning, machine (from ECSA) is not costly in terms of performance.
The disadvantages to this method include the following:
More resources are used than when using a standard AutoEdit database. This is because in addition to writing the variable contents to ECSA, the variable has to be updated in a List structure in the Coupling facility.
Resolving variables from a machine other than the originating, owning, machine is more costly in terms of performance, because the list in the Coupling facility must be read instead of resolving the value directly from ECSA.