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

More documents

Recommendations

Info

4.5.1 CICS Client for OS/2 60 CICS for AIX as the Transaction Server for AIX. If you want to fully exploit the workload balancing capability of the CICS Systems Manager for AIX in association with your CICS for AIX servers, you have to upgrade the bulk of the workstations (if not all) to RISC System/6000 workstations or equivalents so that you can deploy the CICS Client for AIX on them. The end result is that none of your CICS for AIX servers is overloaded, and good consistent response time is achieved. Thus users are happy because they experience more even response times, and availability can be greater if you configured your CICS for AIX regions suitably. This in turn can lead to improved public image of your enterprise and greater efficiency from the staff who work in it. In the sections that follow we cover the requirements for each CICS Clients, stating hardware and software requirements, limitations, and anything that you should be aware for a smooth implementation. All of these considerations are based on the assumption that the CICS server is a CICS for AIX region. CICS Client for OS/2 requires a machine that supports IBM OS/2 Version 2.0 or later. This implies a machine with an Intel 386SX or higher processor. The appropriate network adapter cards and/or gateway cards are required for connection to the enterprise network. These cards enable the connectivity between the client machine and the CICS for AIX server machine. The disk space required for the client code of CICS Client for OS/2 is about 1 MB. Additional disk space is required if you select the samples and documentation installation options. There is also an additional requirement if you select the CICS gateway for Lotus Notes and CICS Internet gateway components of CICS Client for OS/2. To benefit from NLS support when communicating with a CICS for AIX server, CICS Client for OS/2 can run under any of the following operating systems: • IBM OS/2 Version 2.0 or later • IBM OS/2 J (Japanese) Version 2.0 or later • IBM OS/2 H (Korean) Version 2.0 or later • IBM OS/2 P (Simplified Chinese) Version 2.0 or later • IBM OS/2 Version 3.0 (Warp) CICS Client for OS/2 requires a product providing TCP/IP or APPC support. For example, OS/2 Warp Connect provides TCP/IP support and IBM Communications Server provides APPC support. CICS Client for OS/2 provides its own LU 6.2 emulation to connect to a CICS for AIX region over TCP/IP and SNA networks. CICS for AIX supports requests from the CICS Client for OS/2 by means of a listener process. This multithreaded process (called cicsip in the case of TCP/IP, and cicssl in the case of SNA) communicates with the client process on the client machine. The communication between these processes imitates the flows between CICS regions. The client process, therefore, appears to the CICS for AIX server as a limited terminal owning region (TOR). As the data flows are the same as those between CICS systems, the CICS for AIX server requires a communications definition (CD) entry for the CICS Client
for OS/2 system. When the client process is started on the client, flows that start the initialization transaction (CCIN) are sent to the server. This transaction is responsible for performing an autoinstall of the appropriate CD entry for the CICS Client for OS/2 system. After the CCIN has run, all further requests are the ECI, EPI, or cicsterm request, depending on the type of client. 4.5.1.1 TCP/IP Connection The CICS for AIX region must have a listener definition (LD) entry defined as an additional method to listen for incoming requests from the CICS Client for OS/2 across the TCP/IP network. The Protocol attribute in the LD entry should be set to TCP. The cicsip listener process is started at region startup. It listens on a TCP/IP port. The standard default port number is 1435. If you choose to use a nonstandard port, you must add an entry to the /etc/services file. The CD model used by CCIN for autoinstall must have the ConnectionType attribute set to cics_tcp for the CICS family TCP/IP support. The optimum number of connections simultaneously active through a single port is about 200, and the maximum is about 450 connections. Each time a CICS Client for OS/2 connects to the CICS for AIX server, a thread is started in cicsip and a connection is established. If you need more than 450 connections, there are two choices: • Add a new adapter card to the machine This increases the adapter bandwidth. The port address is the same for all of the client systems, but the server Internet address is different. Two LDs are configured—one to listen exclusively on one network adapter and one to listen on the other. The TCPAddress attribute in the LD is used to specify the server Internet address. • Use a second port The Internet address of the CICS for AIX server machine remains the same, but the port address is different. The TCPAddress attribute in the LD is left blank, and port addresses are explicitly defined. If your CICS for AIX server machine manages many TCP/IP connections, it may run out of space in the mbuf pool (an area of memory allocated by TCP/IP when AIX is initialized). You can check the size by noting the value of thewall in the output of the no -a command. The default size of thewall is 2 MB, which supports up to about 800 CICS family TCP/IP connections. If you have to support more than 800 connections, you have to increase the value of thewall accordingly. 4.5.1.2 SNA Connection The CICS for AIX region must have an LD entry defined as an additional method to listen for incoming requests from the CICS Client for OS/2 across the SNA network. The Protocol attribute in the LD entry should be set to SNA. The cicssl listener process is started at region startup. The CD model used by CCIN for autoinstalling the client must have the ConnectionType attribute set to local_sna. The initial planning effort lies in the tailoring of the supported SNA product that provides the underlying SNA services to be used by the CICS for AIX region. IBM SNA Server for AIX Version 3.1 is an example of a supported SNA product. For more detail refer to CICS on Open Systems Intercommunication Guide, SC33-1564-01, and SNA Server for AIX: Planning and Performance Guide, SC31-8220. Chapter 4. Using CICS Clients 61
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 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 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 122 and 123: emote DRDA database. Information ab
Page 124 and 125: As the COMMAREA has an allowable ma
Page 128 and 129:
110 CICS for AIX as the Transaction
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?