IBM OS manual Saving affinity data

Page 32

 

2. There is an affinity table for each of the following command groups that cause

 

transaction-system affinity:

 

v INQUIRE, SET, ENABLE, DISABLE, EXTRACT, COLLECT STATS,

 

PERFORM, DISCARD, CREATE, and RESYNC commands

v CICS BTS BROWSE commands are treated as inquire commands

 

v WAITCICS, WAIT EVENT, and WAIT EXTERNAL commands

 

3. There are two affinity tables that are used as aids to searching some of the

 

other tables.

 

The affinity tables reside in the data space and are saved to the Transaction

 

Affinities Utility ®les when you stop the Detector and, optionally, at predetermined

 

intervals.

 

Saving affinity data

 

The affinity data collected by the Detector is saved to the Transaction Affinities

 

Utility VSAM ®les by the autosave transaction, CAFB. For more information about

 

these ®les, see ªThe affinity data VSAM ®lesº on page 17.

The CAFB transaction saves affinity data automatically when you stop the Detector. You can also specify that the CAFB transaction save affinity data as follows:

vOn a predetermined time/activity basis. That is, data is saved if either more than 300 seconds has passed, or more than 1000 table elements have changed, since the last save.

vWhen you pause the Detector.

Once the CAFB transaction has saved any data collected, it either becomes dormant until next activated (while the Detector is still running or paused), or terminates (if the Detector has been stopped).

Not all the affinity tables in the data space need to be saved, because some are temporary or are used only as an aid to searching. Furthermore, some tables contain temporary elements, used for recording a possible affinity. Such elements are not saved to the ®les. They are either deleted when the Transaction Affinities Utility deduces that there is actually no affinity, or are made permanent when it deduces that there really is affinity (in which case they get saved). Also, when data is saved, only those table elements that have been added or changed since the last save are written to the dataset. Time stamps in each table element indicate whether the element has been written already, and whether it has changed since the last write. This minimizes the number of writes performed.

To improve performance, each affinity table is browsed and saved in its entirety, before the next table is considered.

The affinity table elements are written in such an order that the data on the ®le is always consistent.

Note: If CICS or the Detector abends, the affinity data may be incomplete. Where possible, the Reporter detects this and issues a message to warn about possible incomplete data.

16 CICS Transaction Affinities Utility Guide

Page 31 Page 33
Image 32
Page 31 Page 33
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 books for Cics Transaction Server for OS/390 BibliographyCics 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 GuideTarget region Requesting regionRouting region Transaction affinities Benets of dynamic routingWhat does dynamic routing cost? Inter-transaction affinity Transaction-system affinityAffinity relations GlobalAffinity lifetimes Cics programming techniques for transaction affinitySafe programming techniques Unsafe programming techniquesSuspect 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 leDetector performance Reporter componentBuilder component Report presenting the affinity data in a readable formIntroducing the Transaction Affinities Utility Cics Transaction Affinities Utility Guide Estimating the size of the MVS data space and Vsam les Preparing to use the affinity utility programCreating the 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 options Running the DetectorChanging the state Displaying the Detector control screen CAFF01When you can start collecting affinity data Starting the collection of affinity dataPausing the collection of affinity data When you can pause affinity data collectionWhen you can resume collecting affinity data 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 saves„4… Last update by userid Size of dataspaceTransid prex „2… Detect affinity typesDetector errors Cics Transaction Affinities Utility Guide Running the Reporter Requesting a report from the ReporterCAUAFF1, CAUAFF2, and CAUAFF3 DD statements Caucntl DD statementsTrangrps DD statement Output from the ReporterCmdgrps DD statement Affinity report System„1… Incorrect affinity types „2… Affinity types reported„3… Affinities reports TrangroupRecoverable CommandAffinity LifetimeProducing affinity transaction group denitions TerminalBTS Task Total TransactionsUsing the affinity report Afflifesystem Descaddress CWAUnderstanding the affinities Modifying affinity transaction groupsRemove false affinities Remove affinity relation worseningCompressing affinity data Using the IBM Cross System Product SPI commandsENQUEUEs/DEQUEUEs Shared storageDetailed affinity analysis ENQUEUE/DEQUEUEGetmain Shared SPI commands Cics Transaction Affinities Utility Guide CONTEXT=plexname Running the BuilderDSPSIZE=16number Affgrps DD statement Syntax for input to the BuilderRepgrps DD statement Builder input syntax Combined affinity transaction group denitions Header statementsOutput from the Builder Combining basic affinity transaction groups Relation a Relation B Resultant relation C Group merge report Data sets processed reportEmpty transaction groups 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 Examples Reporter outputScanner output Example 2±VS Cobol Which occurs for the rst Move Move Unrecognized Transids Logon or System when Pconv expectedCobol affinities Cics Transaction Affinities Utility Guide Function code values Appendix D. DiagnosticsDetector table manager diagnostics Table identier values Reason code values Detector Cafb request queue manager diagnostics Date formatter diagnosticsReason code values 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