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

More documents

Recommendations

Info

3.5 Summary 48 CICS for AIX as the Transaction Server CICS for AIX provides an excellent basis for reliable, secure, industrial strength OLTP in an open distributed systems environment. CICS for AIX has the advantage of being a member of a family. Thus it can communicate with other members of the CICS family to access data that they may hold or have access to. CICS for AIX provides support for clients on multiple operating systems; thus it can be the OLTP server where users operate from a variety of hardware and operating systems. CICS for AIX provides a wide and varied API that is available in multiple programming languages. It has access to multiple types of data. It provides multiple forms of intersystem communication. It allows connectivity to non-CICS applications if a suitable protocol is used. The key characteristic of CICS for AIX is flexibility. CICS for AIX recognizes that the world is complex. Its aim is to simplify, so that application development can see the required transactional services as a set of services to be called. Thus application developers can concentrate on their core objective, producing business applications to best serve the enterprise.
Chapter 4. Using CICS Clients 4.1 Application Server Model Users require an interface to interact with a CICS for AIX region. The longer-established members of the CICS family, those running on mainframe computers, were designed with a terminal network that largely consists of 3270-type displays and printers. Tens of thousands of CICS applications have been written using the 3270 data stream for terminal input and output. The existing investment in these CICS applications must be preserved and protected. CICS for AIX and CICS Clients address this requirement and enable such CICS applications to run successfully without any changes. The CICS Clients are designed with modern requirements in mind, such as the ability to add a GUI to a CICS Client or the ability to access a CICS for AIX region from a non-CICS application. CICS Clients support multiple functions, and multiple versions of CICS Clients are available. By multiple functions we mean that the CICS client produced for one operating system can provide a number of different interfaces, giving you greater flexibility in the type of user interface that you decide to implement. By multiple versions we mean that CICS Clients are available to run on multiple, different hardware types and operating systems. This increased choice protects the investment in the hardware and software that your users use. The design of CICS Clients is such that the client accesses the business application that runs in the server machine. Typically the client will run on a different computer from the server so that processor usage is offloaded from the server machine. CICS Clients enable users to access CICS for AIX systems to run their business applications. Through CICS Clients you can interact with the CICS for AIX system as a terminal (3270-emulated terminal) user. CICS Clients also provide additional functions that enable you to write your own user interface while still providing client access to a CICS for AIX region. These functions are the ECI and the EPI. The availability of the ECI and EPI greatly extends the choice when deciding on a user interface. If none of the standard CICS-provided interfaces is suitable, you can create your own and combine it with the ECI or EPI to provide the CICS client component. The design of CICS Clients is based on the application server model, a processing model used in an open distributed multivendor OLTP environment. The purpose of the model is to separate the presentation logic from the business logic to enable the client to run on a separate processor from the business application and so offload processor usage from the server machine. Figure 13 on page 50 illustrates the components in the application server model. In this model the screen handling is run on the end-user workstation, or client computer. The business application is run in an application enabling environment on a server computer located on the LAN. The application is accessed through a thin layer of client code in the client computer. © Copyright IBM Corp. 1996 49
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 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 108 and 109: Communication between the transacti
Page 112 and 113: 7.2.2 Single-Phase and Two-Phase co
Page 116 and 117:
Figure 28. Switching Access among D
Page 118 and 119:
100 CICS for AIX as the Transaction
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?