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

More documents

Recommendations

Info

connect to a PPC Gateway server machine, which in turn connects to an SNA network. Figure 11. Interconnection Using Encina PPC Gateway Support 36 CICS for AIX as the Transaction Server The Encina PPC Gateway uses a product such as SNA Server for AIX to connect to the remote SNA system. SNA Server for AIX has to be installed on the same machine as the Encina PPC Gateway. A CICS for AIX region can use more than one Encina PPC Gateway. The Encina PPC Gateways must be on the same system. Reasons for using more than one Encina PPC Gateway might be: • To allow the network links from a large number of remote systems to be spread across more than one gateway machine and hence across multiple SNA products • To introduce some level of redundancy so that a backup is available if one Encina PPC Gateway fails • To spread the processing load over more than one Encina PPC Gateway
An Encina PPC Gateway can be used by more than one CICS for AIX region if the CICS for AIX regions do not make too many SNA intercommunication requests. Be careful, however; the Encina PPC Gateway is implemented on a single process within the operating system and could become swamped with work. Problem determination is more difficult if more than one CICS for AIX region uses an Encina PPC Gateway. 3.3.3.2 Mixing TCP/IP and SNA Using the products available, you can mix the methods used to connect your CICS systems to meet complex interconnection requirements. For example, a CICS for AIX region could use the Encina PPC Executive to communicate with another CICS for AIX region, while also communicating over SNA using both local SNA support and an Encina PPC Gateway server. Figure 12 on page 38 shows a CICS for AIX region communicating with another CICS for AIX region using TCP/IP. Encina TCP/IP is used because both regions are in the same DCE cell. The CICS for AIX region is also communicating across an SNA network to a CICS for OS/2 system, some APPC workstations, and a CICS for MVS/ESA system. The communications between the CICS for OS/2 system and the workstations use local SNA support. Local SNA was chosen because CICS for OS/2 and the APPC workstations do not support synchronization level 2. The communications with CICS for MVS/ESA use a PPC Gateway because synchronization level 2 is required. The PPC Gateway server is running on the same machine as the CICS region and is using the same SNA product. Chapter 3. CICS for AIX 37
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 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 104 and 105:
7.1 X/Open XA Interface 7.1.1 X/Ope
Page 106 and 107:
88 CICS for AIX as the Transaction
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

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

Delete template?

Save as template?