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

More documents

Recommendations

Info

3.3.1 DCE RPC 3.3.2 TCP/IP 32 CICS for AIX as the Transaction Server • CICS on Open Systems clients • IBM CICS Clients • IBM mainframe-based CICS systems • Remote LU 6.2 applications To facilitate such communication, CICS for AIX supports several different communication protocols: DCE RPC, TCP/IP, and SNA. Each protocol has different characteristics and properties that make them more suitable for some purposes than for others. Below we briefly describe each protocol and its use by CICS for AIX. DCE RPC enables an application to make an RPC without regard to its location. A DCE RPC can be implemented over TCP/IP, a connection-oriented protocol, or over UDP/IP, a connectionless protocol. DCE RPC over UDP/IP is used in CICS on Open Systems client to CICS on Open Systems region communication. Communication between a CICS on Open Systems application server and an Encina SFS can use DCE RPC over UDP/IP or TCP/IP. DCE RPC does not support synchronization levels for application update coordination. It can be considered more of a function call than a protocol in the way in which SNA is. The use of DCE RPC takes advantage of the flexibility that DCE CDS brings to CICS on Open Systems transaction processing. TCP/IP is a connection-oriented protocol. It includes conventions that allow communication between networks based on different hardware technologies. TCP/IP is widely available on UNIX-based systems as well some other systems, such as OS/2 and Windows NT. It is a simple protocol. For CICS to use TCP/IP for intercommunications, it has to provide much of the support for the data formats used to send intersystem requests as well as the security needed to protect system resources. CICS for AIX offers a choice of two methods for using TCP/IP: CICS family TCP/IP or Encina PPC TCP/IP. One method or the other may be more appropriate for your installation. 3.3.2.1 CICS Family TCP/IP CICS family TCP/IP enables connectivity for a CICS for AIX region to: • CICS on Open Systems systems • CICS on OS/2 regions • CICS on Windows NT regions • IBM CICS Clients Figure 8 on page 33 shows a CICS for AIX region using CICS family TCP/IP to communicate with a CICS for OS/2 and an IBM CICS Client.
Figure 8. Interconnection Using CICS Family TCP/IP Support When a request is first made to communicate between two systems with CICS family TCP/IP, a connection is acquired between the two systems. The connection remains for as long as the two systems are active. The connection can carry many concurrent intersystem requests flowing in either direction. The two communicating systems do not have to be in the same DCE cell. A CICS for AIX region can be configured to accept TCP/IP connections on one or more TCP/IP ports in the local machine. It can also receive requests on one or more token-ring adapters. This is important as the maximum number of concurrent connections through a single port is around 450. The exact number depends on the number of open file descriptors in CICS. CICS family TCP/IP supports function shipping, transaction routing, DPL and asynchronous processing. It does not support distributed transaction processing. CICS family TCP/IP supports synchronization level 0 and level 1 for all flows. 3.3.2.2 Encina PPC TCP/IP Encina PPC TCP/IP supports function shipping, transaction routing, DPL, asynchronous processing, and distributed transaction processing between CICS on Open Systems systems and enables distributed transaction processing with Encina applications. If DCE CDS is in use, both systems must be in the same DCE cell. If the two communicating systems are not in the same DCE cell, consider using CICS family TCP/IP. Figure 9 on page 34 shows the Encina PPC Executive being used to interconnect CICS for AIX regions and an application that is using the Encina PPC Executive. Chapter 3. CICS for AIX 33
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 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 86 and 87: 4.6 Summary 68 CICS for AIX as the
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 96 and 97: 6.1.2 Encina Toolkit Server Core 6.
Page 100 and 101:
is also necessary to use native AIX
Page 102 and 103:
84 CICS for AIX as the Transaction
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:
7.5 Summary 108 CICS for AIX as the
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:
Page 150 and 151:
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 162 and 163:
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 170 and 171:
Page 172 and 173:
10.8 Summary 154 CICS for AIX as th
Page 174 and 175:
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 182 and 183:
Page 184 and 185:
takes place over TCP/IP or SNA comm
Page 186 and 187:
provide greater protection in the u
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
How Customers Can Get ITSO Redbooks
Page 196 and 197:
Page 198 and 199:
design. The process of composing a
Page 200 and 201:
A year later ISC gave SQL formal in
Page 202 and 203:
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

Create successful ePaper yourself

Delete template?

Save as template?