IBM OS manual „1… The control options Perform periodic saves, Restore data on start

Page 53

The Detector options screen, CAFF02, shows the options available to you. You can change an option only when the Detector has stopped, unless one of the notes that follow says otherwise.

Notes:

„1… The control options:

vPerform periodic saves

Whether or not you want the affinity data collected to be saved to the affinity data VSAM ®les if either:

±More than 300 seconds has passed, or more than 1000 table elements have changed, since the last save

±You paused the Detector

(The autosave transaction, CAFB, writes the affinity data to the affinity data VSAM ®les automatically when you stop the Detector.)

Note: This option can be changed while the Detector is stopped, paused, or running.

vRestore data on start

Whether or not you want the affinity data to be restored from the affinity data VSAM ®les when the Detector is started. This enables affinity data to be added to the data collected from previous runs of the Detector. If you are gathering data use this:

±For one set of transaction identi®ers at a time

±For one set of commands at a time

±If the Detector is being run at varying times

It is also of particular value if the Detector terminates unexpectedly, because you do not have to start collecting affinity data all over again; you can start from the last time data was saved.

Notes:

1.The data restored is only for those affinity types that you have chosen to be detected (by specifying Y for the affinity type on the CAFF02 screen).

Data is kept on ®le for all commands, but only the data for the commands that you have selected to be detected may change, and therefore is restored.

2.You can change this option while the Detector is stopped, paused, or running. v Multiple signon with the same userid

Whether or not your conventions allow for more than one user to be signed on to CICS with the same userid at the same time. If so, set the multiple signon with same userid to Y; otherwise, the Detector may incorrectly deduce some affinity lifetimes and create erroneous affinity transaction groups (also known as affinity groups). This includes conventions where more than one user is simultaneously not signed on; that is, they all take the default userid CICSUSER.

Also, if you are running the Detector in an AOR, the userids examined depend on whether the userid is propagated from the TOR, or derived from the SESSION and CONNECTION resource de®nitions. In the last case, you should set the multiple signon option to Y if your conventions allow the same AOR userids to be signed on to CICS at the same time.

It is very important that this option is set correctly. If you are about to start a new run of the Detector, and intend restoring data from the affinity data VSAM ®les,

Chapter 5. Running the Detector 37

Page 52 Page 54
Image 53
Page 52 Page 54
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 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 affinitiesTarget region Requesting regionRouting region Transaction affinities Benets of dynamic routingWhat does dynamic routing cost? Transaction-system affinity Inter-transaction affinityAffinity relations GlobalCics programming techniques for transaction affinity Affinity lifetimesUnsafe programming techniques Safe programming techniquesSuspect programming techniques Avoiding the effects of transaction affinityProtecting 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 lesReporter component Detector performanceBuilder 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 #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 options Running the DetectorChanging the state CAFF01 Displaying the Detector control screenStarting the collection of affinity data When you can start collecting affinity data When you can pause affinity data collection Pausing the collection of affinity data When you can resume collecting affinity data Resuming the collection of 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 startSize of dataspace „4… Last update by useridTransid prex „2… Detect affinity typesDetector errors Cics Transaction Affinities Utility Guide Requesting a report from the Reporter Running the ReporterCAUAFF1, CAUAFF2, and CAUAFF3 DD statements Caucntl DD statementsTrangrps DD statement Output from the ReporterCmdgrps DD statement System Affinity report„2… Affinity types reported „1… Incorrect affinity types„3… Affinities reports TrangroupCommand RecoverableAffinity LifetimeTerminal Producing affinity transaction group denitionsBTS Task Total TransactionsAfflifesystem Descaddress CWA Using the affinity reportModifying affinity transaction groups Understanding the affinitiesRemove false affinities Remove affinity relation worseningCompressing affinity data SPI commands Using the IBM Cross System ProductENQUEUEs/DEQUEUEs Shared storageENQUEUE/DEQUEUE Detailed affinity analysisGetmain 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 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 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 Date formatter diagnostics Detector Cafb request queue manager diagnosticsReason code values This sectionIndex Bappl Vsam Cics Transaction Affinities Utility Guide Sending your comments to IBM Ibmr IBM
Top Page Image Contents