IBM OS manual Detector performance, Reporter component, Builder component

Page 34

Detector performance

The Detector is intended to be run against production CICS regions. However, over the period when the Detector is running, the CICS region suffers a performance degradation (dependent on the workload and number of affinities) equivalent to the performance impact of vendor monitor products that use the same user exits. The Detector is intended to be used over limited periods. To further limit the impact of running the Detector during periods of particularly heavy workloads, you can pause or stop the collection of data, or select speci®c commands or transactions to search for.

If your naming convention for TS queues uses a unique counter as part of the name, the Detector performance is likely to be worse than described above. This is because if every TS queue created has a unique name, the Detector creates a very large number of affinity records, which adversely affects performance.

The most likely reason for poor performance is the detection of TS commands. You may prefer to run the Detector twice, once for TS commands and once for all other affinity commands.

The Reporter component

The Reporter is a batch utility that you can use to convert the affinity data collected by the Detector into two output formats:

vA report presenting the affinity data in a readable form

This is intended for use by system programmers and application designers, and indicates the transactions and programs issuing the EXEC CICS commands that cause inter-transaction and transaction-system affinities. This information should help you understand the transactions making up the workload, and should highlight the changes you need to make to remove unwanted affinities.

vA ®le containing a set of basic affinity transaction group de®nitions in a syntax approximating to the batch API of CICSPlex SM

This is intended as input to the Builder, which can merge these basic groups into the combined groups suitable for input to CICSPlex SM.

The input to the Reporter is the three ®les of affinity data from a single CICS region. The output from the Reporter therefore describes the affinities detected in a single CICS region.

Note: The output produced may not contain all the transaction affinities in the CICS region concerned, because some affinities may not have been found by the Detector. You may have to supplement the basic affinity transaction groups with information from the Scanner report, or from your own knowledge of your transactions, before using the ®le as input to the Builder.

The Builder component

The Builder is a batch utility that you can run against a set of ®les containing the basic affinity transaction group de®nitions as created by the Reporter. The Builder produces a ®le containing combined affinity transaction group de®nitions suitable for input to CICSPlex SM.

18 CICS Transaction Affinities Utility Guide

Page 33 Page 35
Image 34
Page 33 Page 35
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 CICSPlex SM books for Cics Transaction Server for OS/390 Other Cics booksSummary of changes Xiv Cics Transaction Affinities Utility Guide Introducing transaction affinities Affinities, see the Cics Application Programming GuideRouting region Requesting regionTarget region What does dynamic routing cost? Benets of dynamic routingTransaction affinities Affinity relations Inter-transaction affinityTransaction-system affinity GlobalAffinity lifetimes Cics programming techniques for transaction affinitySuspect programming techniques Safe programming techniquesUnsafe programming techniques Avoiding the effects of transaction affinityProtecting applications from one another What next? Introducing the Transaction Affinities Utility Important noteAffinity utility program components Commands detected by the Transaction Affinities Utility Scanner component Detector componentWhat is detected Detector componentsWhat is not detected Worsening of transaction affinities relationsControlling the Detector How the affinity data is collectedSaving affinity data Affinity data Vsam les Control record Vsam leBuilder component Detector performanceReporter component Report presenting the affinity data in a readable formIntroducing 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 Dening the Vsam les to Cics #termidsPreparing to use the affinity utility program Cics Transaction Affinities Utility Guide Running the Scanner Creating a summary reportAffmod DD statement Creating a detailed report Cics Transaction Affinities UtilityContents 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 Displaying the Detector control screen CAFF01When you can start collecting affinity data Starting the collection of affinity dataWhen you can resume collecting affinity data Pausing the collection of affinity dataWhen you can pause affinity data collection Resuming the collection of affinity dataWhen you can stop collecting affinity data Stopping the collection of affinity dataChanging the Detector options CAFF02Restore data on start „1… The control options Perform periodic savesTransid prex „4… Last update by useridSize of dataspace „2… Detect affinity typesDetector errors Cics Transaction Affinities Utility Guide CAUAFF1, CAUAFF2, and CAUAFF3 DD statements Running the ReporterRequesting a report from the Reporter Caucntl DD statementsCmdgrps DD statement Output from the ReporterTrangrps DD statement Affinity report System„3… Affinities reports „1… Incorrect affinity types„2… Affinity types reported TrangroupAffinity RecoverableCommand LifetimeBTS Task Producing affinity transaction group denitionsTerminal Total TransactionsUsing the affinity report Afflifesystem Descaddress CWARemove false affinities Understanding the affinitiesModifying affinity transaction groups Remove affinity relation worseningCompressing affinity data ENQUEUEs/DEQUEUEs Using the IBM Cross System ProductSPI commands Shared storageDetailed affinity analysis ENQUEUE/DEQUEUEGetmain 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 Error report Sample group merge reportSample error report Cics Transaction Affinities Utility Guide Appendix A. Details of what is detected ENQ/DEQTS commands Load HOLD/RELEASEAddress CWA CANCEL/DELAY/POST/START SPI commands Wait 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 Reason code values Detector Cafb request queue manager diagnosticsDate formatter diagnostics This sectionIndex 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