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

More documents

Recommendations

Info

8.6 Planning Considerations for CICS SM 8.6.1 Overall Objectives Before implementing CICS SM in your environment, it is important that you understand what CICS SM has to offer. You must be able to distinguish between the roles of systems management and workload management. You must also be clear about which components of CICS SM are used in which roles. As with the introduction of other software components, it is important to put a lot of thought and effort into the early planning stages. If the role of systems management itself is not new in your installation, the technology that CICS SM uses almost certainly will be. Starting small rather than going for a complete change at once will enable you to become more familiar with the product. The emphasis in the sections that follow is on planning your configuration and ensuring that it meets your requirements. Be clear about what it is that you want to gain from the introduction of CICS SM into your environment. Are you looking to provide systems management or do you want workload management active as well? Consider whether you are prepared to introduce change into your existing environment to achieve your objectives. Introducing systems management into an existing configuration is relatively easily done and does not necessarily require change. Implementing workload management is a somewhat more involved task, and depending on your current configuration, it may well require change in order to obtain the best value from it. 8.6.2 Understand Today′s Configuration 128 CICS for AIX as the Transaction Server If you are going to remodel your existing CICS systems to combine applications into a few multipurpose application-serving regions, most of the work is CICS related. CICS SM is the catalyst for the change. You will most likely have your own procedures for remodeling CICS systems. Below are some issues to address in the planning and execution phases of the remodel. • Which applications do the CICS systems support? Ensure that you have a thorough list of the applications that are running within the CICS systems that are to be remodeled. • Which CICS facilities are required to support those applications? Remember that these multipurpose application-serving regions will be the sum of the different types of regions that existed. Some applications will use facilities or resources that others do not. All should be included. • Are there any special requirements for those applications? An application might have special operational requirements, such as having to be available for less time in the day than other applications. This is not a problem with CICS SM as it can stop some applications while leaving others active. The key thing is to be aware of all of the different requirements. • Where is the data held for each application? Ensure that all applications have access to the data that they require regardless of where it is held. • Are there any application affinities? The most preferable solution to dealing with application affinities is to remove the affinities, but this is not always feasible. Alternative approaches
are to use workload separation or run the applications in their own CICS systems. • Is the enterprise business structure represented? CICS systems and applications exist to serve the enterprise. If the CICS systems have grown apart from the enterprise business structure, perhaps because of changes within the enterprise or takeover and merge activity, now is a good opportunity to make the necessary changes to update the configuration. • How does work arrive to be processed by the CICS systems? You must understand how work arrives to be processed by the CICS systems. Does it arrive from another system or is it from one of the CICS clients? Remember that it is only possible to workload manage AIX CICS clients directly. With the IBM CICS Clients you would have to have the clients attach to a CICS for AIX region, which then manages the routing of work. This is not an ideal solution because of the overhead that going through a CICS for AIX system adds. The solution does allow work to be workload managed to your CICS for AIX systems, however, when it would not otherwise be possible. • Are all processors equal? Know the relative processor speeds of the machines that will have work routed to them. This information must be entered for each system clone that is being workload managed. See 8.5.2, “The Reference System” on page 124 for more details. • What is the current performance? Before introducing CICS SM, collect data that enables you to understand the current performance of your systems. This data should include transaction rates, user response times, and processor utilization. Such data can be invaluable for comparison purposes after the introduction of CICS SM. The response time data is required to specify the estimated execution time on the reference system for both transaction and program models. The data is also helpful for pinpointing any problems that you may initially experience. 8.6.3 New Configuration Considerations If the structure of the configuration is to be changed, the transition is likely to be largely controlled by application migration considerations. To produce a new logical and physical organization showing the components in the system, where work arrives from, where it is processed, and how the routing decisions are made, you will want to look at: • Location of the systems management function Decide where the management focal point will be. We recommend that the GUI, SMappl, and WLMAppl (if workload management is in use) be located on the same dedicated machine. This arrangement keeps all management components physically adjacent and thus reduces the amount of intersystem DSOM traffic and provides plenty of processing capacity for Plex activation. Alternatively, use a system with low CPU utilization to ensure that the SMappl is unlikely to be CPU constrained. No performance measurements have been done to date looking at the CPU cost of the SMappl. The cost to a large extent depends on the size of the configuration, that is, the number of CICS systems and the number of resources within them. The most intense period of CPU activity is during a Plex activation. • Management domains Chapter 8. Using CICS System Manager for AIX 129
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:
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 94 and 95:
Page 96 and 97: 6.1.2 Encina Toolkit Server Core 6.
Page 98 and 99: 80 CICS for AIX as the Transaction
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 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 130 and 131: 8.2 Workload Management 112 CICS fo
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 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 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?