IBM OS Header statements, Output from the Builder, Combined affinity transaction group denitions

Page 74

HEADER statements

The HEADER statement is speci®c to the Builder, and is not a CICSPlex SM statement. It is produced by the Reporter, and is needed by the Builder to create unique transaction group names.

The Reporter generates temporary transaction group names (for example, CW.00000001 and TS.00000001) while it is running, and stores these names in the output data set for that run. However, the Builder can take several Reporter data sets as input, and may therefore get the same transaction group name from different input data sets (describing different affinity transaction groups).

To ensure that the transaction group names are unique, the input transaction group names are quali®ed by the input data set name. To do this, when the Builder reads a HEADER statement (the ®rst line of an input data set), it obtains the data set name from MVS. The HEADER statement is vital because without it the Builder cannot detect the change from one input data set to another.

If you omit a HEADER statement, the Builder may generate error messages or add transactions to the wrong group, and give incorrect line numbers in the error report and an incomplete report of data sets processed.

Output from the Builder

The Builder outputs a ®le containing a set of de®nitions for combined affinity transaction groups, and a report listing the combinations that occurred.

Combined affinity transaction group de®nitions

Before each de®nition of a combined group in the output ®le, the Builder adds a commented-out REMOVE command for that group. If you already have combined groups of the same name, check that it is appropriate to delete them before uncommenting the REMOVE command.

The name of each combined affinity transaction group is derived from the alphanumerically ®rst transaction identi®er in the combined group. For example, if ABCD was ®rst, the transaction group name would be ABCDGRP.

Note: For CICSPlex SM, the name of each combined affinity transaction group must be unique.

For example, Figure 11 on page 59 shows the set of combined de®nitions that correspond to the basic de®nitions in Figure 9 on page 47, assuming that a MATCH ®lter of LUNAME, a STATE of ACTIVE, and a CONTEXT of CICPLEX1 was speci®ed on the PARM statement.

58 CICS Transaction Affinities Utility Guide

Page 73 Page 75
Image 74
Page 73 Page 75
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? 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 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 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 statementsTrangrps DD statement Output from the ReporterCmdgrps 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 CONTEXT=plexname Running the Builder DSPSIZE=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 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
Top Page Image Contents