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

More documents

Recommendations

Info

10.3.3 Writing ECI and EPI Application Programs ECI and EPI application programs that run on CICS on Open Systems clients can be written in COBOL, C, or PL/I. Programs that do not make operating-specific calls are portable between CICS on Open Systems clients and other CICS client products. Application programs can use the facilities of both the ECI and the EPI. To use the ECI and EPI, programs must be linked to the appropriate ECI and EPI libraries. Sample programs are supplied with auxiliary files that help with linking the programs. For more information about the ECI and EPI interfaces see CICS Family: Client/Server Programming, SC33-1435-00. 10.4 How CICS Runs Your Transactions The major components of the CICS for AIX run-time system are: • The CICS client processes • The transaction scheduler • A pool of application servers • CICS queue and file manager • A PPC Gateway Server See 3.2.1, “Components” on page 28 for more details. There are two steps when CICS executes your transaction: 1. Requesting a transaction to be run 2. Transaction execution 148 CICS for AIX as the Transaction Server When you enter a CICS transaction identifier through a CICS client, it sends an RPC to the transaction scheduler. The transaction scheduler selects an application server to run the transaction and requests it to do so with an RPC. When you link-edit a CICS program to be run under CICS (for example, using the CICS-provided command, cicstcl, to translate, compile, and link), the object you create is not directly executable by the operating system because it contains some unresolved symbols and expects to be run by a CICS application server. The CICS application server provides a complete environment for running the loadable objects produced by cicstcl. To run your transaction, CICS looks up the name and location of its first CICS program and uses the operating system dynamic loading facility to load that program into the application server. The unresolved symbols in the program are then resolved by symbols provided by the server, and the program begins execution. The resolution of symbols applies irrespective of the language in which the program is written. Programs produced by the C compiler (or by the IBM COBOL or IBM PL/I compilers) are built as standard XCOFF objects and are thus shared automatically among multiple application servers on the same machine.
10.5 CICS Application Programming Interface The CICS API is covered in some level of detail in 3.1.2, “CICS API” on page 24. See that section for details. 10.6 CICS Application Development Tools CICS provides tools to develop and debug transactions. The tools cover a variety of areas from helping to design user screens to helping determine code problems. We discuss each of the tools: 10.6.1 Presentation Interface Development You use the CICS BMS processor to translate BMS source files, which contain the definitions of map sets, to produce a symbolic map and a physical map. The symbolic map is a programming source language data structure (a COBOL, C, or PL/I structure) used by the compiler to resolve source language references to fields in the map. The physical map contains the information necessary to display the map on a physical terminal and instructions for embedding control characters within a data stream. CICS provides the screen design aid (SDA), which is an interactive tool that allows you to easily design and modify BMS maps by using a Motif interface. 10.6.2 Application Program Translation Application programs that include CICS API commands are processed by the command language translator (cicstran) that translates the CICS API commands into statements in the language used. This translator accepts as input a source program written in COBOL or C where CICS API commands are coded and produces as output an equivalent source program where each command is translated into statements in the language of the source program. You can then compile and link-edit your programs using the COBOL or C compilers. Alternatively, you can request that your source program is translated, compiled, and link-edited in one step using the shell script cicstcl. The advantage of this alternative is that CICS uses the correct compilers and sets up the options required by CICS for translation. The IBM PL/I compiler has an integrated CICS processor. Thus it is unnecessary (and indeed not possible) to run a separate CICS translator step for CICS programs written in IBM PL/I. You should therefore only use either cicstcl or the IBM PL/I invoked directly and not attempt to use cicstran. 10.6.3 Application Program Debugging CICS provides a transaction called the Execution Diagnostic Facility (CEDF) that enables you to debug an application program that has been preprocessed with the -e option (on cicstran or cicstcl) without modifying the program. The facility displays the state of the application program at the interception point and allows you to interact with the debugging tool before returning control to the application code. You can use the Lexington Debugger with C, IBM COBOL, and IBM PL/I programs. Chapter 10. Application Design Considerations 149
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:
Page 100 and 101:
is also necessary to use native AIX
Page 102 and 103:
Page 104 and 105:
7.1 X/Open XA Interface 7.1.1 X/Ope
Page 106 and 107:
Page 108 and 109:
Communication between the transacti
Page 110 and 111:
Page 112 and 113:
7.2.2 Single-Phase and Two-Phase co
Page 114 and 115:
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 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 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 198 and 199: design. The process of composing a
Page 200 and 201: A year later ISC gave SQL formal in
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?