IBM OS manual Affinity, Lifetime, Queue resource, Recoverable, Terminal Id, Program, Command

Page 61

Note: The Trangroup value for an affinity transaction group may vary from one run to another of the Detector or Reporter.

Affinity

The affinity relation. If appropriate, this also indicates whether the relation was worsened from a less restrictive relation. For more information about worsened relations, see ªWorsening of transaction affinities relationsº on page 14.

Lifetime

The affinity lifetime. If appropriate, this also indicates whether the lifetime was worsened from a less restrictive lifetime. For more information about worsened lifetimes, see ªWorsening of transaction affinities lifetimesº on page 14.

Queue (resource)

The resource causing the affinity. This may be the name of the resource (for example, Queue : LOCA1 (D3D6C3C1F1404040) as shown) or the address

of the resource, depending on the type of affinity.

Note: An unprintable character appears as a period (.).

Recoverable

Whether or not the resource is recoverable. For TS queues, this also indicates whether the queue is in auxiliary or main temporary storage.

Terminal Id

The identi®er of the terminal where the transactions taking part in the affinity were initiated. This information is available only for TS queue affinity, and is meaningful only if the affinity is LUNAME or worsened from LUNAME to GLOBAL. Therefore, the terminal identi®er is included in the report only in these cases.

Tranid The identi®er of each transaction taking part in the affinity. It is possible for an affinity transaction group to contain only one tranid. An example of such a situation is where each part of a pseudoconversation accesses a TS queue, and each part runs under the same tranid.

Program

The name of each program taking part in the affinity.

Offset The offset from the load point of the BALR instruction at the EXEC CICS command causing the affinity. The Reporter outputs a negative offset (X©FFFFxxxx©) if it could not determine an offset; that is, if the offset calculated is not within the program. This may indicate that the program (or perhaps language run-time code) has passed control to another program by using a non-CICS mechanism (for example, a VS COBOL II dynamic call).

Notes:

1.This offset is not the same as the offset given by the Scanner, which is the offset of the command argument 0 declaration from the start of the load module. (See page 71.)

2.If a negative offset (X©FFFFxxxx©) is used, it is not possible to directly locate individual affinity commands within a program. The program must be scanned for every instance of the affinity command, as there may be more than one.

Command

The EXEC CICS command causing the affinity.

Chapter 6. Running the Reporter 45

Page 60 Page 62
Image 61
Page 60 Page 62
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 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 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 dataWhen you can pause affinity data collection Pausing the collection of affinity dataWhen 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 statements Cmdgrps DD statement Output from the Reporter Trangrps 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 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 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