IBM OS manual TS commands, Load HOLD/RELEASE

Page 82

	TS commands
	v The affinity here is between all transactions that use the same TS queue. It
	applies to both MAIN and AUXILIARY TS. The match is made on the name of
	the TS queue.
	v The affinity relation can be GLOBAL, BAPPL, LUNAME, or USERID.
	v Lifetime can be PCONV, LOGON, SIGNON, ACTIVITY, PROCESS,SYSTEM, and
	PERMANENT. A MAIN queue cannot be recovered, regardless of de®nition, so
	cannot cause PERMANENT.
	v No data is collected if a TS queue is de®ned as remote or if a remote SYSID is
	speci®ed on the TS command. In such cases, the request is satis®ed by a
	remote CICS region or by a temporary storage pool in the coupling facility.
	v Commands in error are treated in the same way as commands that give a
	NORMAL response, so data is collected.
	v If a TS queue is created and deleted within the same task, no data is collected.
	Scanner differences: Scanner detects all instances of TS commands.

LOAD HOLD/RELEASE

	v The affinity here is between all transactions that LOAD HOLD and RELEASE the
	same program (or, more probably, table). The match is made on the program
	name.
	v The LOAD and RELEASE protocol applies only to programs that are de®ned with
	RELOAD(NO). If the Detector can not establish the RELOAD attribute for some
	reason, RELOAD(NO) is assumed.
	v Once a LOAD HOLD has occurred for a program, any subsequent LOAD (with or
	without HOLD) or RELEASE is part of the affinity.
	v The affinity relation is GLOBAL or BAPPL.
	v Lifetime is always SYSTEM.
	v Commands in error are treated in the same way as commands that give a
	NORMAL response, so data is collected.
	v LOAD with no HOLD for programs de®ned as RESIDENT is not treated as an
	affinity because relying on residency for sharing is inherently unsafe, the program
	can be replaced by SET PROG() NEWCOPY.
	v The incorrect use of RELEASE for a program de®ned with RELOAD(YES) is not
	detected.
	Scanner differences: Scanner detects all instances of LOAD, not just LOAD HOLD,
	and all instances of RELEASE.

RETRIEVE WAIT/START

vThe affinity here is between all the transactions that issue START commands for a particular transaction at a terminal, where that transaction issues RETRIEVE WAIT. The transaction that issues the RETRIEVE WAIT is also part of the affinity. The match is made on the transid.

vThe affinity relation can be GLOBAL or USERID.

vLifetime can be SYSTEM or PERMANENT. PERMANENT is assumed if PROTECT is speci®ed on any START.

66 CICS Transaction Affinities Utility Guide

Image 82

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 report Sample 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