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

More documents

Recommendations

Info

4.5.2 CICS Client for DOS 62 CICS for AIX as the Transaction Server 4.5.1.3 Autoinstall User Exits The CCIN calls user exit DFHCCINX when it is about to autoinstall the CD entry for the CICS Client for OS/2 system. If your own version of this user exit is in effect, review its logic to ensure that the CD attributes to be altered are compatible with those of the model CD entry. When the first EPI or cicsterm request arrives at the CICS for AIX server the CCIN has run, the CTIN transaction carries out the autoinstall of a workstation definition (WD) resulting in a four-character terminal identifier of the format =xxx, where xxx is a character string chosen by CICS; the first character of = is fixed. If your autoinstall user exit programs do not expect the = character, you may have to review their logic to prevent potential problems. 4.5.1.4 Security The userid and password are the main security mechanisms with the CICS Client for OS/2 system. The CICS Client for OS/2 holds only a single userid and password for each CICS for AIX server that it connects. You specify the userid and password for the particular CICS for AIX server either in the client initialization file (default name CICSCLI.INI) or by using the cicscli command. Also you must ensure that a user definition (UD) entry with matching userid exists in the connecting CICS for AIX region. Otherwise the default userid of the CICS region is used. In the case of cicsterm, you can enforce the initial transaction to be invoked to be CESN, the CICS-supplied sign-on transaction. This would cause the user to authenticate again. 4.5.1.5 3270 Keyboard Mapping The keyboard mapping for 3270 emulator operation is defined in a keyboard mapping file. CICS Client for OS/2 supplies a default file, CICSKEY.INI, in the \CICSCLI\BIN directory. We recommend that you create your own customized mapping file. To identify this keyboard mapping file, you either specify the /k option on the cicsterm command or specify the CICSKEY environment variable in the CONFIG.SYS file. CICS Client for DOS requires an IBM-compatible PC that supports the DOS operating system and has sufficient memory for the required software components. The disk space required for the client code of CICS Client for DOS is about 0.9 MB. Additional disk space is required if you select the samples and documentation installation options. To benefit from NLS support when communicating with a CICS for AIX server, CICS Client for Windows can run under any of the following operating systems: • Microsoft or IBM PC DOS 3.3, DOS 4.0, DOS 5.0, or later • Windows J (Japanese) Version 4.0 or later, Version 5.0/V or later • Windows H (Korean) Version 4.0 or later, Version 5.0/V or later A CICS Client for DOS can also run in the DOS box of OS/2. CICS Client for DOS requires a product providing TCP/IP or APPC support. For example, IBM TCP/IP for DOS Version 2.1.1 or later provides the TCP/IP support. The particular product providing APPC support depends on the actual network
4.5.3 CICS Client for Windows configuration. For more detail see CICS Clients Administration Version 1.1, SC33-1436-01. All of the configuration considerations for CICS Client for OS/2 are applicable to CICS Client for DOS. Please review 4.5.1, “CICS Client for OS/2” on page 60, replacing CICS Client for OS/2 with CICS Client for DOS and substituting AUTOEXEC.BAT for CONFIG.SYS. CICS Client for Windows requires an IBM-compatible PC that supports the Windows operating system and has sufficient memory for the required software components. A minimum of 2 MB of memory is recommended. The disk space required for the client code of CICS Client for Windows is about 0.9 MB. Additional disk space is required if you select the samples and documentation installation options. To benefit from the NLS when communicating with a CICS for AIX server, CICS Client for Windows can run under any of the following operating systems: • Windows Version 3.1 or later 4.5.4 CICS Client for Macintosh • Windows J (Japanese) Version 3.1 or later • Windows H (Korean) Version 3.1 or later • Windows for Workgroups Version 3.1.1 CICS Client for Windows requires a product providing TCP/IP or APPC support. For example, IBM TCP/IP for DOS Version 2.1.1 or later provides the TCP/IP support, and IBM APPC Networking Services for Windows Version 1.0 provides APPC support. All of the configuration considerations for CICS Client for OS/2 are applicable to CICS Client for Windows. Please review 4.5.1, “CICS Client for OS/2” on page 60 section, replacing CICS Client for OS/2 with CICS Client for Windows and substituting AUTOEXEC.BAT for CONFIG.SYS. CICS Client for Macintosh requires any machine containing the Motorola M68020 (or higher) processor, for example, an Apple Classic II, or an Apple LC II. The PowerMac is also supported. For CICS Client for Macintosh, a minimum of 4 MB of memory is recommended. However, if other software components are to run concurrently with the CICS client, the total memory requirement may be greater. CICS Client for Macintosh is compatible with the Virtual Memory mode of System 7 (accessible from the Memory Control Panel), although use of this Macintosh feature may affect performance. The disk space required for the client code of CICS Client for Macintosh is about 1 MB. Additional disk space is required if you select the samples and documentation installation options. NLS support is not available when using CICS Client for Macintosh to connect to a CICS for AIX server as the Macintosh operating system does not support NLS. Chapter 4. Using CICS Clients 63
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 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 130 and 131:
8.2 Workload Management 112 CICS fo
Page 132 and 133:
114 CICS for AIX as the Transaction
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?