AsynchError
Synopsis
[Miscellaneous] AsynchError=n
n is either 1 (true) or 0 (false). The default value is 1.
Description
This parameter has been retained for compatibility, but should not be used when building new applications.
When AsynchError is enabled (n = 1), InterSystems IRIS® data platform processes can receive asynchronous errors.
If the server detects multiple asynchronous errors for a particular job, the system triggers at least one such error. However, there is no guarantee which error will be triggered. The possible asynchronous errors include:
-
<LOCKLOST> — Some locks once owned by this job have been reset.
-
>DATALOST> — Some data modifications performed by this job have received an error from the server.
-
<TRANLOST> — The server has asynchronously rolled back a distributed transaction initiated by this job.
Even if you disable a job receiving asynchronous errors, the next time the job performs a ZSync command, the asynchronous error is triggered.
During a transaction, InterSystems IRIS checks for pending asynchronous errors at each transaction start, commit, LOCK operation, and every network global reference. Since SET and KILL operations across the network are asynchronous, other instructions may be executed between the time a SET is generated and when the asynchronous error is reported.
Changing This Parameter
On the Compatibility page of the Management Portal (System Administration > Configuration > Additional Settings > Compatibility), in the AsynchError row, click Edit. Select AsynchError to enable this setting.
Instead of using the Management Portal, you can change AsynchError in the Config.MiscellanousOpens in a new tab class (as described in the class reference) or by editing the CPF with a text editor.
To change this parameter for a single process only (as opposed to instance-wide), use the AsynchError()Opens in a new tab method of the %SYSTEM.ProcessOpens in a new tab class. See the class reference for details.
