ON DB_CHANGE action
Related pages:
ON DB_CHANGE tableIdent GOTO [procName [PRTY prtyIdent]| NONE]
tableIdent | in | Identifier of the object of the Table type. |
procName | in | Name of RPC procedure in ESL script. |
prtyIdent | in | Optional identifier of the Int type. A priority when calling RPC. |
RPC PROCEDURE ProcName (IN INT _dbTable, IN INT _actionId) END ProcName
The value of formal parameter _actionId can be one of the following options:
_actionId | 0 | Monitoring of the table has started successfully. |
_actionId | 1 | Initialization of table monitoring failed because of one of the following reasons:
|
_actionId | 10 | D2000 DbManager is executing the action DB_REFRESH_TABLE or a structure definition configured on object of Table type has been saved. |
_actionId | 11 | D2000 DbManager has finished the operation DB_*, DBS_* PG_* or some operation has been executed over the table from process D2000 HI by user interface. If the modification are executed within the database transaction (DB_TRANS_OPEN ...), D2000 DbManager generates a message about the change of table when the changes are being confirmed (DB_TRANS_COMMIT). |
_actionId | 12 | The table has been deleted from configuration of application. |
_actionId | 13 | The active instance of the D2000 DbManager process changed its status to passive or in redundancy the D2000 Server to which the D2000 DbManager process is connected changed its status from HOT to SBS. It is necessary to re-register at new active instance of the D2000 DbManager process via action ON DB_CHANGE. Note: When switching the active instance or during D2000 redundancy switch (when the D2000 DbManager process becomes passive), all the transactions are closed, all database operations are terminated and all handles are invalidated. Therefore it is necessary to repeat all of the initialization sequences of scripts on a new active instance (opening the databases, tables etc.). |
Related pages:
Pridať komentár