Although The Evans Group no longer consults, the web site lives on!
The implementation of the Open Transaction Environment (OTE), and the accompanying requirement for threadsafe programming, marks a radical change in CICS capabilities. When first announced, threadsafe was implemented primarily for the significant CPU savings achievable with CICS/DB2 transactions (customers report up to 30% reduction in CPU for some CICS/DB2 applications.) Now, a second wave of threadsafe implementers are finding significant advantages in converting non-DB2 applications to threadsafe, including:
However, some users have suffered transaction abends
and even data corruption if non-threadsafe programs are allowed to
run in the OTE. Exercise caution and conduct thorough research when
considering a threadsafe conversion.
CICS TS 4.2 (with IMS r12) now uses an OpenAPI TRUE, meaning that CICS/DLI programs can now take advantage of the OTE. Russ has an article in ETJ detailing some of the implications of this enhancement.
Russ has also written two introductory articles on CICS and Threadsafe for Technical Support, the journal of NaSpa, and recently published a series of articles in Enterprise Tech Journal on the subject.
For detailed information about what threadsafe is, how to use the OTE, and how to convert non-threadsafe programs to be threadsafe compliant, download the latest versions of the presentations Russ has developed:
Russ has written a number of articles for peer reviewed journals on the subjects of Threadsafe: