Addressing OLTP Solutions with CICS: The Transaction Server ... - Ibm

More documents

Recommendations

Info

design. The process of composing a software blueprint, showing how to build from the requirements specification document. Design often includes module decompositions, data structure definitions, file format definitions, and important algorithm descriptions. distributed processing. Distributed processing is an application or systems model in which function and data can be distributed across multiple computing resources connected on a LAN or WAN. See client-server computing. DPL. Distributed program link. Provides a remote procedure call (RPC)-like mechanism by function shipping EXEC CICS LINK commands. In CICS/6000, DPL allows the linked-to program to issue unsupported CICS/6000 function shipping calls, such as to DB2 and DL/I, and yields performance improvements for transactions that read many records from remote files. DTP. Distributed transaction processing. Type of intercommunication in CICS. The processing is distributed between transactions that communicate synchronously with one another over intersystem links. DTP enables a CICS application program to initiate transaction processing in a system that supports LU 6.2 and resides in the same or a different processor. E ECI. external call interface. An application programming interface (API) that enables a non-CICS client application to call a CICS program as a subroutine. The client application communicates with the server CICS program, using a data area called a COMMAREA. Encina. Enterprise computing in a new age. A set of DCE-based products from Transarc Corporation that are available on the RISC System/6000. The Encina family of online transaction processing products includes: • Encina Toolkit Executive • Encina Server • Encina Structured File Server (SFS) • Encina Peer-to-Peer Communication Executive (PPC). EPI. External presentation interface. An application programming interface (API) that allows a non-CICS application program to appear to the CICS system as one or more standard 3270 terminals. The non-CICS application can start CICS transactions and send and receive standard 3270 data streams to those transactions. environment. The collective hardware and software configuration of a system. 180 CICS for AIX as the Transaction Server F file server. A centrally located computer that acts as a storehouse of data and applications for numerous users of a local area network. G GUI. Graphical user interface. A style of user interface that replaces the character-based screen with an all-points-addressable, high-resolution graphics screen. Windows display multiple applications at the same time and allow user input by means of a keyboard or a pointing device such as a mouse, pen, or trackball. H heterogeneous network. A local or wide area network comprising hardware and software from different vendors, usually implementing multiple protocols, operating systems, and applications. host. (1) In a computer network, a computer providing services such as computation, database access, and network control functions. (2) The primary or controlling computer in a multiple computer installation. I instance. An individual application object that belongs to a particular object class. An instance of a class is an actual object displaying the properties of that class. intercommunication. Communication between separate systems by means of Systems Network Architecture (SNA), Transmission Control Protocol/Internet Protocol (TCP/IP), and Network Basic Input/Output System (NetBIOS) networking facilities. interoperability. The ability to interconnect systems from different manufacturers and have them work together to satisfy a business requirement. Some examples of requirements are message interchange between systems and sharing of resources such as data between applications running on different hardware and software platforms. L LU type 6.2 (LU 6.2). Type of logical unit used for CICS intersystem communication (ISC). The LU 6.2 architecture supports CICS host to system-level products and CICS host to device-level products. APPC is the protocol boundary of the LU 6.2 architecture.
LUW. Logical unit of work. An update that durably transforms a resource from one consistent state to another consistent state. A sequence of processing actions (for example, database changes) that must be completed before any of the individual actions can be regarded as committed. When changes are committed (by successful completion of the LUW and recording of the syncpoint on the system log), they do not have to be backed out after a subsequent error within the task or region. The end of an LUW is marked in a transaction by a syncpoint that is issued by either the user program or the CICS server, at the end of task. If there are no user syncpoints, the entire task is an LUW. M macro. An instruction that causes the execution of a predefined sequence of instructions in the source language in which the macro is embedded. The predefined sequence can be modified by parameters in the macro. messaging. A communications model whereby the distributed applications communicate by sending messages to each other. A message is typically a short packet of information that does not necessarily require a reply. Messaging implements asynchronous communications. middleware. Middleware is a set of services that allows distributed applications to interoperate on a LAN or WAN. It shields the developer or end user from the system complexity and enables delivery of service requests or responses transparently across computing resources. O object. A program or a group of data that can behave like a thing in the real world. OLTP. Online transaction processing. A style of computing that supports interactive applications in which requests submitted by terminal users are processed as soon as they are received. Results are returned to the requester in a relatively short period of time. An online transaction processing system supervises the sharing of resources for processing multiple transactions at the same time, minimizes compute time and duration of locks, and separates user think-time from the use of storage and other resources. P partner LU. In SNA, one of an LU pair between which a session is established. portability. The ability to move application software components from one system for use on another system. Perfect portability would permit such movement without modification of the components. process. (1) A unique, finite course of events defined by its purpose or by its effect, achieved under defined conditions. (2) Any operation or combination of operations on data. (3) A function being performed or waiting to be performed. (4) A program in operation, for example, a daemon. protocol. (1) A formal set of conventions governing the format and control of data. (2) A set of procedures or rules for establishing and controlling transmissions from a source device or process to a target device or process. pseudoconversational. A type of CICS application design that appears to the user as a continuous conversation but consists internally of multiple tasks. R recovery. The use of archived copies to reconstruct files, databases, or complete disk images after they are lost or destroyed. recoverable resources. Items whose integrity CICS maintains in the event of a system error. These include individual files and queues. RPC. Remote procedure call. A communication model where requests are made by function calls to distributed procedures elsewhere. The location of the procedures is transparent to the calling application. resource manager. A software program that maintains the state of resources and provides access and control to them through APIs. A resource can be a device as well as a program or object, although normally it is referred to as a device. S server. Any computing resource dedicated to responding to client requests. Servers can be linked to clients through LANs or WANs to perform services, such as printing, database access, fax, and image processing, on behalf of multiple clients at the same time. SQL. Structured query language. SQL started as IBM′s query language for DB2. SQL became so popular with users and vendors outside IBM that ANSI adopted a version of SQL as a U.S. standard in 1986. Glossary 181
Page 1:
Addressing OLTP Solutions with CICS
Page 4 and 5:
Take Note! Before using this inform
Page 6 and 7:
iv CICS for AIX as the Transaction
Page 8 and 9:
9.4 Security Issues on the Internet
Page 10 and 11:
viii CICS for AIX as the Transactio
Page 12 and 13:
x CICS for AIX as the Transaction S
Page 14 and 15:
xii CICS for AIX as the Transaction
Page 16 and 17:
The Team That Wrote This Redbook xi
Page 18 and 19:
xvi CICS for AIX as the Transaction
Page 20 and 21:
2 CICS for AIX as the Transaction S
Page 22 and 23:
1.2 Complex OLTP Business Environme
Page 24 and 25:
Figure 2. OLTP Complex for XYZ Insu
Page 26 and 27:
By using common application program
Page 28 and 29:
1.5 OLTP Market 10 CICS for AIX as
Page 30 and 31:
Figure 5. OLTP Market Segmentation
Page 32 and 33:
14 CICS for AIX as the Transaction
Page 34 and 35:
2.1 IBM Software Servers 2.1.1 Lotu
Page 36 and 37:
2.2.1 CICS Clients V1.1.0 A Transac
Page 38 and 39:
2.2.4 CICS Internet Gateway for AIX
Page 40 and 41:
3.1 Services CICS for AIX is a very
Page 42 and 43:
3.1.2 CICS API 24 CICS for AIX as t
Page 44 and 45:
3.1.3.1 Terminal Users and CICS Reg
Page 46 and 47:
3.2 Implementation 3.2.1 Components
Page 48 and 49:
3.2.2 Processes 3.2.1.3 Application
Page 50 and 51:
3.3.1 DCE RPC 3.3.2 TCP/IP 32 CICS
Page 52 and 53:
Figure 9. Interconnection Using Enc
Page 54 and 55:
connect to a PPC Gateway server mac
Page 56 and 57:
Figure 12. Interconnection Using TC
Page 58 and 59:
3.4.3 Configuration 3.4.4 Managing
Page 60 and 61:
3.4.6 Intersystem Communication CIC
Page 62 and 63:
3.4.8 Data Location 44 CICS for AIX
Page 64 and 65:
3.4.11 Operations plan to cope with
Page 66 and 67:
3.5 Summary 48 CICS for AIX as the
Page 68 and 69:
Figure 13. Application Server Model
Page 70 and 71:
4.2.1 CICS External Call Interface
Page 72 and 73:
By means of mapping files, you can
Page 74 and 75:
4.3 Versions 56 CICS for AIX as the
Page 76 and 77:
4.4 Sample Network Configurations 4
Page 78 and 79:
4.5.1 CICS Client for OS/2 60 CICS
Page 80 and 81:
4.5.2 CICS Client for DOS 62 CICS f
Page 82 and 83:
4.5.5 CICS Client for AIX CICS Clie
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
5.1.1 DCE Threads 5.1.2 Remote Proc
Page 90 and 91:
The GDS is based on the CCITT X.500
Page 92 and 93:
egion or server it is looking for.
Page 94 and 95:
Page 96 and 97:
6.1.2 Encina Toolkit Server Core 6.
Page 98 and 99:
Page 100 and 101:
is also necessary to use native AIX
Page 102 and 103:
Page 104 and 105:
7.1 X/Open XA Interface 7.1.1 X/Ope
Page 106 and 107:
Page 108 and 109:
Communication between the transacti
Page 110 and 111:
Page 112 and 113:
7.2.2 Single-Phase and Two-Phase co
Page 114 and 115:
Page 116 and 117:
Figure 28. Switching Access among D
Page 118 and 119:
Page 120 and 121:
Figure 30. CICS Access to Remote DB
Page 122 and 123:
emote DRDA database. Information ab
Page 124 and 125:
As the COMMAREA has an allowable ma
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
8.2 Workload Management 112 CICS fo
Page 132 and 133:
Page 134 and 135:
8.4.2 System Management Application
Page 136 and 137:
Figure 36. The CICS SM GUI 8.4.6 Di
Page 138 and 139:
Figure 37. CICS SM Component Distri
Page 140 and 141:
Figure 38. Combining Resources 122
Page 142 and 143:
8.5.2 The Reference System 124 CICS
Page 144 and 145:
Page 146 and 147:
8.6 Planning Considerations for CIC
Page 148 and 149: 130 CICS for AIX as the Transaction
Page 152 and 153: 9.1 Some Terminology 9.2 Services 1
Page 154 and 155: Figure 41. CICS Internet Gateway fo
Page 156 and 157: 9.3.3 Data Integrity The Web was or
Page 158 and 159: 9.3.5 High Availability The drawbac
Page 160 and 161: or employee records, eavesdropping
Page 164 and 165: • Type, size, and quantity of rec
Page 166 and 167: 10.3.3 Writing ECI and EPI Applicat
Page 168 and 169: The ANIMATOR debugging tool enables
Page 172 and 173: 10.8 Summary 154 CICS for AIX as th
Page 176 and 177: 11.1 The Big Picture 158 CICS for A
Page 178 and 179: 11.2 User Access 160 CICS for AIX a
Page 180 and 181: Figure 44. Access to Various DB2 Da
Page 184 and 185: takes place over TCP/IP or SNA comm
Page 186 and 187: provide greater protection in the u
Page 194 and 195: How Customers Can Get ITSO Redbooks
Page 200 and 201: A year later ISC gave SQL formal in
Page 204 and 205: designing efficient applications 15
Page 206: IBML ® Printed in U.S.A. SG24-4752
show all

Addressing OLTP Solutions with CICS: The Transaction Server ... - Ibm

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?