The BIND TRANSACTION STATISTICS statement defines the beginning of a transaction for the purposes of collecting transaction statistics. The system allocates a block of storage in which to accumulate these statistics. Because this block is owned by the logical terminal associated with the current task, the BIND TRANSACTION STATISTICS statement cannot be used with nonterminal tasks.
Note: If a transaction statistics block (TSB) is already allocated for the logical terminal associated with the current task, the BIND request clears the block and writes any previously accumulated transaction statistics to the log file.
When a BIND TRANSACTION STATISTICS request is issued, the system assigns the transaction a 40-character identifier; the first 32 characters are the identifier of the signed-on user (if any) and the last eight characters are the identifier of the logical terminal associated with the current task.
►►─── BIND TRANSACTION STATISTICS; ───────────────────────────────────────────►◄
The following example illustrates the BIND TRANSACTION STATISTICS statement:
BIND TRANSACTION STATISTICS;
Upon completion of the BIND TRANSACTION STATISTICS function, the ERROR_STATUS field in the IDMS DC communications block indicates the outcome of the operation:
The request has been serviced successfully; any existing transaction statistics block was written to the log file before being cleared.
Storage for the transaction statistics block is not available; to wait would cause a deadlock.
A new transaction statistics block has been allocated.
Either the parameter list is invalid or no logical terminal element (LTE) is associated with the issuing task.
The collection of transaction statistics or task statistics has not been enabled during system generation.
|
Copyright © 2014 CA.
All rights reserved.
|
|