Understanding the affinities

The inter-transaction affinities listed in the report highlight those transactions that have affinities with other transactions.

Understanding the affinities present in the CICS region enables you to determine which of the them are most pervasive. If you decide that it is worth changing your application programs, it is generally more cost-effective to remove the most pervasive affinities, because those affinities most restrict dynamic routing. The most pervasive affinities are those with a relation of GLOBAL, or a lifetime of SYSTEM or PERMANENT, and are heavily used.

The transaction-system affinities listed in the report highlight those transactions that use system programming commands. It may not be appropriate to dynamically route such a transaction, because its action may be tied to a particular CICS region (as opposed to a particular set of other transactions).

The affinity report also lists affinities occurring between transactions that were not initiated from a terminal or are not CICS BTS transactions. These background transactions are known as background relations. This information is really for completeness, because such transactions cannot be dynamically routed.

To get complete information on affinities, use as many code paths as possible while running the Detector, because it can ®nd an affinity only if the commands that cause it have been executed. However, the Scanner detects all instances of affinity commands in the corresponding load library. So a comparison of the Reporter and Scanner outputs is very useful when establishing the full picture.

Important note

Both the Reporter and Scanner may identify commands that, on closer examination, do not cause real affinities. Relate the output from the Reporter and the Scanner to your knowledge of your applications, to distinguish between such commands and those causing real affinities that impact CICS dynamic routing.

For more information about interpreting the affinity report, see ªAppendix C. Useful tips when analyzing Transaction Affinities Utility reportsº on page 75.

Modifying affinity transaction groups

Consider making the following modi®cations to the affinity transaction groups before inputting them to the Builder:

vRemove false affinities

False affinities may arise because the sharing of a resource is done on a read-only basis, so it is possible for the resource to be replicated across cloned CICS regions. The prime example of this is a read-only CWA, where the CWA is set up at CICS startup (for example, from a PLTPI program), and only ever read thereafter. (An alternative way of removing this false affinity is to prohibit detection of ADDRESS CWA by the Detector using the CAFF options.)

vRemove affinity relation worsening

An affinity that has a relation of LUNAME, BAPPL,or USERID may be worsened

 

to GLOBAL because the Detector has not seen enough examples of the affinity

48 CICS Transaction Affinities Utility Guide

Page 64
Image 64
IBM OS manual Understanding the affinities, Modifying affinity transaction groups, Remove false affinities

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.