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

Page 31

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 30 Page 32
Image 31
Page 30 Page 32
Contents IBM Page IBM Third edition March Contents Appendix A. Details of what is detected Reporter output Scanner output Examples Vi Cics Transaction Affinities Utility Guide Vii Trademarks Preface Argument zero Cics Transaction Server for OS/390 BibliographyCics books for Cics Transaction Server for OS/390 Other Cics books CICSPlex SM books for Cics Transaction Server for OS/390Summary of changes Xiv Cics Transaction Affinities Utility Guide Affinities, see the Cics Application Programming Guide Introducing transaction affinitiesRouting region Requesting regionTarget region What does dynamic routing cost? Benets of dynamic routingTransaction affinities Global Inter-transaction affinityTransaction-system affinity Affinity relationsCics programming techniques for transaction affinity Affinity lifetimesAvoiding the effects of transaction affinity Safe programming techniquesUnsafe programming techniques Suspect programming techniquesProtecting applications from one another What next? Important note Introducing the Transaction Affinities UtilityAffinity utility program components Commands detected by the Transaction Affinities Utility Detector component Scanner componentDetector components What is detectedWorsening of transaction affinities relations What is not detectedHow the affinity data is collected Controlling the DetectorSaving affinity data Control record Vsam le Affinity data Vsam lesReport presenting the affinity data in a readable form Detector performanceReporter component Builder componentIntroducing the Transaction Affinities Utility Cics Transaction Affinities Utility Guide Creating the Vsam les Preparing to use the affinity utility programEstimating the size of the MVS data space and Vsam les #termids Dening the Vsam les to CicsPreparing to use the affinity utility program Cics Transaction Affinities Utility Guide Creating a summary report Running the ScannerAffmod DD statement Cics Transaction Affinities Utility Creating a detailed reportContents of a detailed report Is an example of a detailed report produced by the Scanner Cics Transaction Affinities Utility Guide Changing the state Running the DetectorChanging the options CAFF01 Displaying the Detector control screenStarting the collection of affinity data When you can start collecting affinity dataResuming the collection of affinity data Pausing the collection of affinity dataWhen you can pause affinity data collection When you can resume collecting affinity dataStopping the collection of affinity data When you can stop collecting affinity dataCAFF02 Changing the Detector options„1… The control options Perform periodic saves Restore data on start„2… Detect affinity types „4… Last update by useridSize of dataspace Transid prexDetector errors Cics Transaction Affinities Utility Guide Caucntl DD statements Running the ReporterRequesting a report from the Reporter CAUAFF1, CAUAFF2, and CAUAFF3 DD statementsCmdgrps DD statement Output from the ReporterTrangrps DD statement System Affinity reportTrangroup „1… Incorrect affinity types„2… Affinity types reported „3… Affinities reportsLifetime RecoverableCommand AffinityTotal Transactions Producing affinity transaction group denitionsTerminal BTS TaskAfflifesystem Descaddress CWA Using the affinity reportRemove affinity relation worsening Understanding the affinitiesModifying affinity transaction groups Remove false affinitiesCompressing affinity data Shared storage Using the IBM Cross System ProductSPI commands ENQUEUEs/DEQUEUEsENQUEUE/DEQUEUE Detailed affinity analysisGetmain Shared SPI commands Cics Transaction Affinities Utility Guide DSPSIZE=16number Running the BuilderCONTEXT=plexname Repgrps DD statement Syntax for input to the BuilderAffgrps DD statement Builder input syntax Output from the Builder Header statementsCombined affinity transaction group denitions Combining basic affinity transaction groups Relation a Relation B Resultant relation C Empty transaction groups report Data sets processed reportGroup merge report Sample group merge report Error reportSample error report Cics Transaction Affinities Utility Guide ENQ/DEQ Appendix A. Details of what is detectedLoad HOLD/RELEASE TS commandsAddress CWA CANCEL/DELAY/POST/START Wait commands SPI commandsCics Transaction Affinities Utility Guide Scanner output Reporter outputExamples Example 2±VS Cobol Which occurs for the rst Move Move Cobol affinities Logon or System when Pconv expectedUnrecognized Transids Cics Transaction Affinities Utility Guide Detector table manager diagnostics Appendix D. DiagnosticsFunction code values Table identier values Reason code values This section Detector Cafb request queue manager diagnosticsDate formatter diagnostics Reason code valuesIndex Bappl Vsam Cics Transaction Affinities Utility Guide Sending your comments to IBM Ibmr IBM

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