Preface
Originally, IBM® CICS® employed a single task control block (TCB) to process, for example, application code, task dispatching, terminal control, and file control that run on the application or quasi-reentrant (QR) TCB. Over time, IBM added specialized TCBs to CICS to help offload management tasks from the overcrowded QR TCB. Virtual Storage Access Method (VSAM) subtasking, the IBM VTAM® High Performance Option, and asynchronous journaling were implemented on separate TCBs. The IBM DB2® and MQ Series (now called WebSphere® MQ) attachment facilities also employed TCBs apart from the application TCB. Distributing processing among multiple TCBs in a single CICS address space is not new. However, customers and ISVs had little control over ...
Get Threadsafe Considerations for CICS now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
