v Command is a non-terminal-related START or a DPL

v ENQ or DEQ commands that specify a resource name for which an appropriate

ENQMODEL de®nition is enabled, and that ENQMODEL has a nonÐblank

ENQSCOPE

 

The Detector does not detect CICS macro-level commands, MVS POST calls, or

 

the hand posting of ECBs.

 

If you continue a pseudoconversation by setting a transid in the TIOA (rather than

 

by using RETURN TRANSID), the Detector cannot detect PCONV lifetimes. In this

 

case, the shortest lifetime detected is LOGON or SIGNON because it interprets

 

every transaction end as a pseudoconversation end.

 

Ideally the Transaction Affinities Utility should ignore commands issued by

 

task-related user exits and global user exits because they are not part of

 

applications. However, it cannot distinguish such commands from others, and does

 

detect them. If your user exits use commands that can cause transaction affinities,

 

the commands are detected, perhaps making any affinity problem seem worse than

 

it actually is.

 

If an exit program at XICEREQ or XTSEREQ modi®es the EXEC CICS command,

 

that modi®cation is not visible to the Detector. (It detects the original, unmodi®ed

 

command.) However, if an XICEREQ, XICEREQC, XEIIN, XTSEREQ, or

 

XTSEREQC exit program (or an XEIOUT exit program invoked earlier) modi®es

 

EIBRESP, the Detector sees the modi®ed value.

 

Controlling the Detector

 

You can monitor and control the Detector through the CAFF transaction, which

 

enables you to start, pause, continue, and stop the collection of affinity data into the

 

tables in the data space. Using the CAFF transaction, you can also specify for

 

which affinity commands, and for which transactions, data is to be collected.

 

The options that you specify to control the Detector for a CICS region are preserved

 

in a recoverable VSAM control ®le. For more information about this ®le, see ªThe

 

control record VSAM ®leº on page 17.

 

How the affinity data is collected

The Detector uses a number of affinity tables in the data space to hold collected affinity data. The affinity tables are in three categories:

1.There is an affinity table, or set of tables, for each of the following command groups that cause inter-transaction affinity:

v ENQ and DEQ commands

vREADQ TS, WRITEQ TS, and DELETEQ TS commands

vLOAD HOLD and RELEASE commands

vRETRIEVE WAIT and START commands

vADDRESS CWA commands

vGETMAIN SHARED and FREEMAIN commands

vLOAD and FREEMAIN commands

vCANCEL, DELAY, POST, and START commands

The tables for a particular group have a structure appropriate to that group.

Chapter 2. Introducing the Transaction Affinities Utility 15

Page 31
Image 31
IBM OS manual Controlling the Detector, How the affinity data is collected

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.