sdsGetTransactions(transactions: JadeDynamicObjectArray input);
The sdsGetTransactions method of the JadeDatabaseAdmin class, valid only at secondary database systems, creates and populates an SDSTransaction dynamic object for each active transaction that is currently being replayed or isolated on the executing secondary system and returns these transaction dynamic objects in the transactions input array.
The SDSTransaction instances returned in the transactions array have a name attribute value of SDSTransaction and type attribute value of SDS_TransactionType (4).
The transaction dynamic attributes are listed in the following table.
| Name | Type | Description |
|---|---|---|
| startTime | TimeStamp | Time at which the transaction started |
| status | Integer | Transaction status (see the following table) |
| statusText | String | Descriptive text that is displayed for the transaction status |
| transactionID | Decimal | Identifier of the transaction |
| userName | String | Name of the user |
The values of the transaction status attribute represented by one of the
| Global Constant | Integer Value |
|---|---|
| SDS_TranNormal | 1 |
| SDS_TranInterrupted | 2 |
| SDS_TranDeferred | 3 |
| SDS_TranWaitingAuditCommit | 4 |
| SDS_TranReadyToCommit | 5 |
| SDS_TranPrepareToCommit | 6 |
| SDS_TranReadyToAbort | 7 |
| SDS_TranInDoubt | 8 |
The only value of interest to most users is SDS_TranInterrupted. When there are active transactions in an interrupted state, read-access to persistent objects is not permitted. See also the sdsEnableReadAccess and sdsEnableReadAccessAt methods, earlier in this chapter.
The caller is responsible for deletion of these transient dynamic objects. Deletion is best achieved by purging the array when the entries have been processed.
A runtime exception is raised if this method is called for a Relational Population Service (RPS) node.