Manuals / IBM / Computer Equipment / Credit Card Machine

IBM OS manual Preparing to use the affinity utility program, Creating the VSAM les

Models: OS

1 103

Download 103 pages 52.71 Kb

Page 37

Chapter 3. Preparing to use the affinity utility program

Chapter 3. Preparing to use the affinity utility program

This chapter describes what needs to be done before you can use the affinity utility program.

vªCreating the VSAM ®lesº

vªEstimating the size of the MVS data space and VSAM ®lesº

vªDe®ning the VSAM ®les to CICSº on page 22

vªTailoring your CICS startup jobº on page 23

vªRestarting your CICS regionº on page 23

Creating the VSAM ®les

The Transaction Affinities Utility uses one copy of each of the following VSAM ®les for each CICS region it is run against:

Table 2. Transaction Affinities Utility VSAM ®les and associated jobs

File	Description	Job

CICSAFF.CAUCNTL	A recoverable ®le used to hold control	CAUJCLCC
	information

CICSAFF.CAUAFF1	Non-recoverable ®les used to hold affinity data	CAUJCLCA
CICSAFF.CAUAFF2	with different key sizes (17, 33, and 225
CICSAFF.CAUAFF3	respectively)

To create a set of these ®les forone CICS region, edit and run a copy of the associated jobs in the CICSTS13.CICS.SDFHINST library. Edit and run a copy of the CAUJCLCC and CAUJCLCA jobs for each CICS region against which you are going to use the Transaction Affinities Utility.

Before you run the CAUJCLCC and CAUJCLCA jobs, change the following parameters in the jobs:

vThe JOB accounting parameters.

vThe pre®x of the ®les (&AFFQ), this should contain a CICS region quali®er.

vThe volume id (&DSVOL) of the DASD device where the ®les are to reside.

Estimating the size of the MVS data space and VSAM ®les

An MVS data space is used to hold the affinity data collected by the Detector. The amount of storage required depends on the number of affinities discovered, the number of different transaction identi®ers, and the number of terminals.

To estimate the amount of storage for the data space (and therefore the size of the VSAM affinity ®les) that you are likely to need for the Detector, you can use the following algorithm (with storage values in bytes):

Data space:		(#transids * #termids * 250)	+ 5		000,000
CAUAFF1	:	(#transids * #termids * 40)	+	1	000,.000
CAUAFF2	:	(#transids * #termids * 150)	+	1	000,000
CAUAFF3	:	1 000,000

where:

© Copyright IBM Corp. 1994, 1999

21

Image 37

IBM OS manual Preparing to use the affinity utility program, Creating the VSAM les

Contents

CICS Transaction Server for OS/390 CICS Transaction Affinities Utility GuideRelease Page CICS Transaction Server for OS/390 CICS Transaction Affinities Utility GuideRelease Third edition March Chapter 1. Introducing transaction affinities ContentsChapter 2. Introducing the Transaction Affinities Utility Chapter 3. Preparing to use the affinity utility programAppendix B. Correlating Scanner and Reporter output to source Appendix A. Details of what is detectedContents Appendix C. Useful tips when analyzing Transaction Affinities Utilityvi CICS Transaction Affinities Utility Guide Notices BookManager TrademarksCICS CICS/ESAPreface How to use this bookWhat this book is about Who this book is forArgument zero Notes on terminologyCICS Transaction Server for OS/390 BibliographyCICS books for CICS Transaction Server for OS/390 CICS Transaction Server for OS/390 Planning for InstallationOther CICS books CICSPlex SM books for CICS Transaction Server for OS/390CICSPlex SM View Commands Reference Summary CICSPlex SM AdministrationChanges for the CICS Transaction Server for OS/390 Release 3 edition Summary of changesChanges for the CICS Transaction Server for OS/390 Release 2 edition Changes for the CICS Transaction Server for OS/390 Release 1 editionxiv CICS Transaction Affinities Utility Guide Chapter 1. Introducing transaction affinities Routing region Requesting regionTarget region What does dynamic routing cost? The benets of dynamic routingTransaction affinities Transaction-system affinity Inter-transaction affinityAffinity relations GlobalCICS programming techniques for transaction affinity Affinity lifetimesUserid SystemUnsafe programming techniques Safe programming techniquesSuspect programming techniques Avoiding the effects of transaction affinityProtecting applications from one another 8 CICS Transaction Affinities Utility Guide What next?Important note Chapter 2. Introducing the Transaction Affinities Utility10 CICS Transaction Affinities Utility Guide Figure 2. Affinity utility program componentsCommands detected by the Transaction Affinities Utility The Detector component The Scanner componentWhat is detected Worsening of transaction affinities relations What is not detectedWorsening of transaction affinities lifetimes How the affinity data is collected Controlling the DetectorSaving affinity data The control record VSAM le The affinity data VSAM lesThe Reporter component Detector performanceThe Builder component v A report presenting the affinity data in a readable formChapter 2. Introducing the Transaction Affinities Utility 20 CICS Transaction Affinities Utility Guide Creating the VSAM les Chapter 3. Preparing to use the affinity utility programEstimating the size of the MVS data space and VSAM les Dening the VSAM les to CICS Chapter 3. Preparing to use the affinity utility program 24 CICS Transaction Affinities Utility Guide Creating a summary report Chapter 4. Running the Scannerv The JOB accounting parameters v The PARM statement $SUMMARYv The AFFMOD DD statement v The PARM statement Creating a detailed report$DETAIL v The DETAIL DD statement Contents of a detailed reportv The STEPLIB DD statement v The INPUT DD statement± The total possible MVS post commands ± The total possible affinity commandsv A summary report of the modules, giving Figure 5 is an example of a detailed report produced by the Scanner30 CICS Transaction Affinities Utility Guide v Changing the state Chapter 5. Running the Detectorv Changing the options Displaying the Detector control screen Starting 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 dataChanging the Detector options „1… The control options v Perform periodic saves v Restore data on startv Size of dataspace „4… Last update by useridv Transid prex „2… Detect affinity typesDetector errors 40 CICS Transaction Affinities Utility Guide Requesting a report from the Reporter Chapter 6. Running the Reporterv The JOB accounting parameters v The PARM parameter of the EXEC statement For examplev The CMDGRPS DD statement Output from the Reporterv The TRANGRPS DD statement v The SYSPRINT DD statementFigure 8. A sample report output by the Reporter Part 1 of Affinity reportFigure 8. A sample report output by the Reporter Part 2 of „2… Affinity types reported Notes for Figure „1… Incorrect affinity types„3… Affinities reports TrangroupCommand RecoverableAffinity LifetimeTerminal Producing affinity transaction group denitionsBTS Task Total TransactionsUsing the affinity report Modifying affinity transaction groups Understanding the affinitiesv Remove false affinities v Remove affinity relation worseningv Remove affinity lifetime worsening Compressing affinity datav Change LUNAME affinity relation to USERID v Add WAIT affinitiesSPI commands Using the IBM Cross System ProductAffinity analysis for a CICS region containing CSP 3.3 applications ENQUEUEs/DEQUEUEsENQUEUE/DEQUEUE Detailed affinity analysisTemporary storage queues GETMAIN SHARED52 CICS Transaction Affinities Utility Guide SPI commands 54 CICS Transaction Affinities Utility Guide v The PARM parameter of the EXEC statement Chapter 7. Running the BuilderDSPSIZE=16number MATCH=LUNAMEUSERIDv The REPGRPS DD statement Syntax for input to the Builderv The AFFGRPS DD statement v The SYSPRINT DD statementHEADER statement. Otherwise comment lines are thrown away Output from the Builder HEADER statementsCombined affinity transaction group denitions 58 CICS Transaction Affinities Utility GuideCombining basic affinity transaction groups Builder produces a report that lists the combinations that occurred Empty transaction groups report Data sets processed reportGroup merge report LifetimeFigure 14. Sample group merge report Error reportFigure 15. Sample error report 64 CICS Transaction Affinities Utility Guide ENQ/DEQ Appendix A. Details of what is detectedLOAD HOLD/RELEASE TS commandsRETRIEVE WAIT/START 66 CICS Transaction Affinities Utility GuideADDRESS CWA LOAD/FREEMAINGETMAIN SHARED/FREEMAIN CANCEL/DELAY/POST/START WAIT commands SPI commands70 CICS Transaction Affinities Utility Guide Reporter output Appendix B. Correlating Scanner and Reporter output to sourceScanner output ExamplesDFHEIV0 Example 2±VS COBOLFor the Scanner output To determine the EXEC CICS commandThe COBOL source after translation was The equivalent Assembler-language is74 CICS Transaction Affinities Utility Guide 001126 MOVECOBOL affinities LOGON or SYSTEM when PCONV expectedUnrecognized Transids 76 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 A continued Page 84 CICS Transaction Affinities Utility Guide Sending your comments to IBM Program Number IBMRSC33-1777-02 CICS Transaction Affinities Utility Guide ReleaseSpine information CICS TS for OS/390