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

More documents

Recommendations

Info

emote DRDA database. Information about the attributes must be gathered as part of the planning process for DDCS customization. See the DDCS User′s Guide, S20H-4793, for more details. There are security considerations with this type of connection. In the CICS for AIX region, the security policy should be based on CICS security facilities such as transaction security and resource access security for the reasons we discuss in “Security Implications” on page 100. Security is implemented through the use of authentication and DB2 internal security. Authentication can take place in one or both machines, depending on the configuration of the RDBMSs and the network products. The internal security of the DB2 products then determines what the user can do with regard to DB2 resources. With DDCS for AIX, it is possible to specify where the user name and password are to be validated when a user tries to connect to a particular database. With your own security requirements in mind, you must plan ahead and decide the location of authentication for each database. The authentication type is specified when you catalog the database in the DB2 system database directory at the local machine. The possible authentication types are: • AUTHENTICATION = CLIENT The user name and password are validated locally. The user is expected to be authenticated at the location where he or she first signs on. Passwords do not flow across the network. • AUTHENTICATION = SERVER The user name and password are validated at the DDCS workstation on which DDCS is installed. Passwords flow to the DDCS workstation over the network. • AUTHENTICATION = DCS The user name and password are validated at the mainframe. Authentication takes place at the host for the user accessing a host database. The specified authentication type along with the SECURITY parameter value (either SAME or PROGRAM) defined for the APPC node that represents the DRDA connection determine the flow and where validation takes place. This is a complex area. We recommend reading Distributed Relational Database Cross Platform Connectivity and Application, SG24-4311. 7.4.4 Accessing a DB2 for MVS/ESA Database through CICS/ESA 104 CICS for AIX as the Transaction Server Another way for a CICS for AIX application to access a DB2 for MVS/ESA database is to use the CICS intersystem communication (ISC) facilities as the transport mechanism and then access the DB2 for MVS/ESA database from an application running within the CICS/ESA region. Either CICS DPL or DTP can be used to facilitate the communication between the pair of user application programs involved. For simplicity we assume CICS DPL is used. In the local RISC System/6000 machine, the user application program running in a CICS for AIX region writes the required SQL access information into a COMMAREA and then issues the DPL request (EXEC CICS LINK call). The access information might consist of an SQL select statement along with the associated qualifiers and predicates, for example. The request travels though
the Encina PPC Gateway to arrive in the connected CICS/ESA region. In the CICS/ESA region the partner application program is invoked. The application program retrieves the access information from the COMMAREA and builds the necessary SQL call. The SQL call is then issued through the CICS-DB2 interface to DB2 for MVS/ESA server for processing. The result returned by the DB2 for MVS/ESA server can be filtered and further processed by this partner user transaction program before the final result is passed back to the originator of the DPL request in the CICS for AIX region. The Encina PPC Gateway may or may not be located on a separate RISC System/6000 machine from the machine containing the CICS for AIX region, as required. Both RISC System/6000 machines must belong to the same DCE cell, however. An Encina PPC Gateway is used to facilitate connectivity to the mainframe system over a SNA network while also providing two-phase commit processing. It may be that you already have an existing connection defined to the CICS/ESA region, in which case this simplifies the amount of work to be done, and an existing connection may favor this approach over the use of DDCS, for example, which would have to be set up from scratch. In this configuration the XA interface is not used for communication with DB2, so there is no need to define an XAD entry. Significant programming effort is required, however, to implement this configuration. Figure 33 shows how a CICS for AIX application can access a DB2 for MVS/ESA database through the CICS/ESA region. Figure 33. CICS for AIX Access to Remote DB2 for MVS/ESA Database Using CICS ISC 7.4.4.1 Planning Considerations This configuration is based on the use of the CICS DPL facility. These programs must be developed. There are no special security configuration considerations; normal CICS security facilities apply in this configuration. If resources are being updated in more than one location, that is, one CICS or DB2 system, we strongly recommend that you use two-phase commit support. This support requires the use of an SNA communication product such as SNA Server for AIX. See “Encina PPC Gateway” on page 35 for more details. Chapter 7. Interactions with the DB2 Family of Products 105
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: 66 CICS for AIX as the Transaction
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 120 and 121: Figure 30. CICS Access to Remote DB
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 146 and 147: 8.6 Planning Considerations for CIC
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 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?