The Effect of Locks on Requests - IBM CICS Interface for Teradata

IBM CICS Interface for Teradata® Reference - 20.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
IBM CICS Interface for Teradata
Release Number
20.00
Published
October 2023
Language
English (United States)
Last Update
2024-03-18
dita:mapPath
nmw1695364801820.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
axu1470436513048
Product Category
Teradata Tools and Utilities

Locks held by a transaction, until a transaction is committed or rolled back, can block the progress of other requests in CICS or in any other system operating against the database.

Therefore, to maximize request concurrency, transactions should be committed or rolled back as soon as possible so that locks on database objects can be released as soon as possible. It is particularly undesirable to hold locks while awaiting terminal input because of the relatively long duration of a terminal wait.

Conversational and pseudo-conversational applications should be written to minimize lock duration, the length of time a lock is held, by using frequent commits.