04.04.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3.4.3 Configuration<br />

3.4.4 Managing the Work<br />

40 <strong>CICS</strong> for AIX as the <strong>Transaction</strong> <strong>Server</strong><br />

− Understand how application data will be accessed from <strong>with</strong>in the<br />

application. This may not be determined by <strong>CICS</strong> but by an RDBMS. It<br />

is still important to understand though<br />

− Understand the amount of logical and physical I/O<br />

− Understand the level of logging involved<br />

• Determine which other software components, such as an RDBMS or a<br />

remote system, are involved. What is the projected load of the new<br />

applications? Can they accommodate the load?<br />

Capacity planning will enable you to see whether the expected work can be<br />

accommodated by the current processing power and I/O capacity or whether<br />

additional machines will be required. If new machines are required, you have to<br />

determine their size. <strong>The</strong>re are extremes of effort in performing capacity<br />

planning. A minimal level of effort would be to look at the application design<br />

and estimate the volume of I/O and the CPU requirements. <strong>The</strong> other extreme<br />

would be to model in quite some level of detail, the clients, the <strong>CICS</strong> for AIX<br />

region, the RDBMS, and possibly the network load.<br />

Consider the other processes that may be competing <strong>with</strong> this <strong>CICS</strong> for AIX<br />

region; for example, is a large amount of batch work processed on the same<br />

machine?<br />

To implement new <strong>CICS</strong> systems, you first have to form an idea of what the<br />

configuration is going to be, that is, you have to know how many regions on how<br />

many processors are required. <strong>The</strong> decision may or may not be straightforward.<br />

It is likely to be influenced by a number of factors:<br />

• <strong>The</strong> likely processing power required. From your application capacity<br />

planning, you can determine whether you will have a single or multisystem<br />

implementation.<br />

• <strong>The</strong> design requirements of the proposed systems. If high availability of the<br />

application is a key requirement, consider implementing multiple regions<br />

capable of running the application and managing the workload. See 8.5.1,<br />

“Maximizing the Benefit” on page 121 for more details of this approach.<br />

• If the new application is incompatible <strong>with</strong> existing applications or has<br />

special operational or security requirements, you will have to implement<br />

another <strong>CICS</strong> region.<br />

• If the aim is to exploit a parallel database, the recommended approach is to<br />

have multiple <strong>CICS</strong> systems capable of accessing the database (see 8.5.1.3,<br />

“Using an SP Processor” on page 123).<br />

In implementing new <strong>CICS</strong> systems, you may find that applications are split over<br />

more than one <strong>CICS</strong> system for reasons of availability or because the processing<br />

capacity required exceeds that available from a single machine. Incoming user<br />

transactions have to be distributed over the available <strong>CICS</strong> systems. <strong>The</strong><br />

distribution of work is an awkward problem that must be resolved. You must<br />

understand how you are going to deal <strong>with</strong> it in your environment.<br />

<strong>The</strong> incoming work must be distributed in such a manner that no one <strong>CICS</strong><br />

system is flooded <strong>with</strong> more work than it can process. One approach might be<br />

to distribute the number of users evenly over the available systems so that<br />

groups of users access particular systems. <strong>The</strong> allocation of work is performed<br />

by controlling the number of users who access the system. Some groups of

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!