#transids

is the number of transaction identi®ers in the CICS region.

#termids

is the number of terminal identi®ers in the CICS region.

Note: The amount of storage needed in the data space for the Builder is about 25% of the storage needed for the Detector.

The algorithm assumes that all affinities are represented, and that all transactions participate in all affinities, and that all transactions run at all terminals (the worst possible scenario). This gives a worst case ®gure.

For example, consider the worst case scenario of a CICS region with 500 different transaction IDs and 1000 terminals, where all transactions issue all affinity commands and all transactions run at all terminals.

For this scenario, the storage requirement for the Detector in the data space is:

Data space : 130 Megabytes

CAUAFF1 : 21 Megabytes

CAUAFF2 : 76 Megabytes

CAUAFF3 : 1 Megabyte

The space required for the data space is different than that required for the ®les because:

veach record has a storage overhead in the data space

vcertain tables are not saved to ®le

vkey length is ®xed per ®le, so short keys must be padded out

Notes:

1.The critical affinity type is temporary storage. The space required for all other affinity types together should be no more than 5MB.

2.The calculations in this section assume that you do not use unique counters when naming temporary storage queues. If you do use unique counters, the

space needed for temporary storage affinity types is much greater. For your calculations with unique counters, replace #transids * #termids by the number of unique queues.

De®ning the VSAM ®les to CICS

The CICS-supplied sample group, DFH$AFFY, contains de®nitions for:

vthree affinity data ®les (CAUAFF1, CAUAFF2 and CAUAFF3)

vthe affinity control ®le, CAUNCNTL

Change some of the attributes of these resource de®nitions to suit your own environment. To do this, use the CEDA transaction (or the DFHCSDUP utility) to:

1.COPY the sample group to a group of your own choosing. For example,

CEDA COPY GROUP(DFH$AFFY) TO(mygroup)

2.EXPAND group mygroup and change the following attributes appropriately: v For each resource de®nition, change the pre®xes of the VSAM ®les, as

de®ned by the CAUJCLCC and CAUJCLCA jobs.

vFor each resource de®nition, ensure that the LSRPOOLID speci®ed for each ®le is capable of handling the keylength de®ned for the ®le. If it isn't, change it so that it is. See Table 2 on page 21 for more information.

22 CICS Transaction Affinities Utility Guide

Page 37 Page 39
Page 38
Image 38
IBM OS manual Dening the Vsam les to Cics, #termids
Page 37 Page 39

OS specifications

IBM OS, or IBM Operating System, refers to a family of operating systems developed by IBM to support its hardware architectures. IBM has produced a range of OS versions tailored for different computing needs, such as mainframes, servers, and personal computers. Among the most notable operating systems in IBM's portfolio are OS/2, z/OS, and AIX, representing a blend of innovation and reliability that has defined IBM's reputation in the computing world.

One of the defining features of IBM OS is its robust multitasking capabilities. Both z/OS, predominantly used in IBM's mainframe environments, and AIX, the Unix-based system for IBM Power Systems, support multiple users and processes simultaneously. This ability allows organizations to run numerous applications in parallel efficiently, maximizing resource utilization and improving productivity.

In terms of security, IBM OS incorporates advanced features aimed at protecting data and maintaining integrity. z/OS offers multifactor authentication, data encryption, and a security model that adheres to the latest regulatory requirements. AIX provides Secure Virtualization, which enhances isolation and security in cloud environments, essential for enterprises handling sensitive information.

Another key characteristic is the adaptability of IBM OS to modern technologies. For instance, z/OS is designed to integrate with cloud computing, open source, and DevOps practices. This adaptability supports organizations in modernizing their infrastructure while retaining the stability associated with IBM solutions. AIX similarly supports containerization and virtualization, which are critical for optimizing resource usage in dynamic computing environments.

IBM's commitment to scalability is evident across its OS offerings. Organizations leveraging z/OS can handle enormous workloads and transactional volumes, making it a preferred choice for industries like finance and telecommunications. AIX also supports scalability, allowing businesses to expand their computing resources as demands grow without significant downtime.

The availability of development tools and environments is another noteworthy aspect of IBM OS. With robust IDEs and programming languages support, developers can create and deploy applications smoothly. This assists businesses in streamlining their development processes and improving time-to-market for innovative solutions.

In summary, IBM OS encompasses a suite of operating systems characterized by multitasking, security, adaptability to modern technologies, scalability, and comprehensive development support. These features have cemented IBM's position as a leader in enterprise solutions, allowing organizations across various industries to thrive in an increasingly digital world.
Top Page Image Contents