<--- Back to Details
First PageDocument Content
Office work / Paper / Z notation / Business / Software / Computing / Transaction server / CICS Universal Client / CA/EZTEST / Transaction processing / IBM software / CICS
Date: 2011-06-19 18:54:25
Office work
Paper
Z notation
Business
Software
Computing
Transaction server
CICS Universal Client
CA/EZTEST
Transaction processing
IBM software
CICS

Microsoft Word - cicsschematics.1.doc

Add to Reading List

Source URL: www.sysed.com

Download Document from Source Website

File Size: 333,75 KB

Share Document on Facebook

Similar Documents

Response times in Client-Server Systems A.J. Field* , P.G. Harrison*, J. Parry† Abstract. Response time is the key performance measure in on-line transaction processing systems and other client-server architectures. No

DocID: 1sW4Z - View Document

Computing / Java enterprise platform / Computing platforms / Java specification requests / Transaction processing / Java Platform /  Enterprise Edition / Enterprise JavaBeans / Distributed transaction / Application server / Java Transaction API / Java EE version history

CNT in JOTM DUSART Doriane June 10thUniversité de Valenciennes

DocID: 1rbN7 - View Document

Software / Computing / Extensible Storage Engine / Proprietary software / Common Gateway Interface / Apache HTTP Server / Database / File system / Distributed computing architecture / Relational database management systems / Apache Hive

Managing Versions of Web Documents in a Transaction-time Web Server Curtis Dyreson, Hui-Ling Lin, and Yingxia Wang Washington State University School of Electrical Engineering and Computer Science Pullman, WA, USA

DocID: 1qu08 - View Document

Software / Computing / Data management / Password / Security / Database transaction / Microsoft SQL Server

IPASONLINE features SDFIT

DocID: 1qmxz - View Document

Computing / Software / Transaction processing / Data management / Concurrency control / Databases / Isolation / Snapshot isolation / Snapshot / Microsoft SQL Server / Book:Non-Relational Databases

Background Patient B’s custom application had slowed down as their data grew. They’d tried several different relief efforts over time, but performance issues kept popping up – especially deadlocks. They wanted a pe

DocID: 1qkBp - View Document