Manuals / IBM / Computer Equipment / Credit Card Machine

IBM OS manual v The AFFMOD DD statement

Models: OS

1 103

Download 103 pages 52.71 Kb

Page 42

vThe AFFMOD DD statement

Specify the name of the sequential data set where the list of modules with potential transaction affinities is to be sent. You can edit the data set to alter the list of modules to be scanned before running the Scanner to produce a detailed report.

vThe DETAIL DD statement (dummy) You do not need this for a summary run.

Each summary report contains:

vA separate line giving the following information about each module in the library:

±Name

±Size

±Language (if determined)

±Number of possible affinity-causing EXEC CICS commands

±Number of possible MVS POST commands

If a module seems to contain affinity-causing EXEC CICS commands, it is ¯agged with the message ªPossible affinity commandsº. If a module seems to contain MVS POST commands, it is ¯agged with the message ªPossible MVS POSTsº.

Note: The language is determined only if at least one affinity-causing EXEC CICS command is detected, and is derived from the EXEC argument zero

4of the ®rst such command. Therefore, if a load module is created from several source languages, only one language is indicated.

v The total count of:

±Modules in the library

±Modules scanned

±CICS modules and tables (not scanned)

±Modules in error (not scanned)

±Modules that possibly contain MVS POST commands

±Modules that possibly contain affinity-causing EXEC CICS commands

±Assembler modules

±C/370 modules5

±OS/VS COBOL modules

±VS COBOL II modules5

±PL/I modules5

Figure 4 on page 27 is an example of a summary report produced by the Scanner.

4.For an explanation of argument zero, see ªNotes on terminologyº on page x .

5.This includes programs compiled by a Language Environment®/370-enabled compiler.

26 CICS Transaction Affinities Utility Guide

Image 42

IBM OS manual v The AFFMOD DD statement

Contents

CICS Transaction Affinities Utility Guide CICS Transaction Server for OS/390Release Page CICS Transaction Affinities Utility Guide CICS Transaction Server for OS/390Release Third edition March Chapter 2. Introducing the Transaction Affinities Utility ContentsChapter 1. Introducing transaction affinities Chapter 3. Preparing to use the affinity utility programAppendix A. Details of what is detected Appendix B. Correlating Scanner and Reporter output to sourceAppendix C. Useful tips when analyzing Transaction Affinities Utility Contentsvi CICS Transaction Affinities Utility Guide Notices CICS TrademarksBookManager CICS/ESAWhat this book is about How to use this bookPreface Who this book is forNotes on terminology Argument zeroCICS books for CICS Transaction Server for OS/390 BibliographyCICS Transaction Server for OS/390 CICS Transaction Server for OS/390 Planning for InstallationCICSPlex SM View Commands Reference Summary CICSPlex SM books for CICS Transaction Server for OS/390Other CICS books CICSPlex SM AdministrationChanges for the CICS Transaction Server for OS/390 Release 2 edition Summary of changesChanges for the CICS Transaction Server for OS/390 Release 3 edition Changes for the CICS Transaction Server for OS/390 Release 1 editionxiv CICS Transaction Affinities Utility Guide Chapter 1. Introducing transaction affinities Requesting region Routing regionTarget region The benets of dynamic routing What does dynamic routing cost?Transaction affinities Affinity relations Inter-transaction affinityTransaction-system affinity GlobalUserid Affinity lifetimesCICS programming techniques for transaction affinity SystemSuspect programming techniques Safe programming techniquesUnsafe programming techniques Avoiding the effects of transaction affinityProtecting applications from one another What next? 8 CICS Transaction Affinities Utility GuideChapter 2. Introducing the Transaction Affinities Utility Important noteFigure 2. Affinity utility program components 10 CICS Transaction Affinities Utility GuideCommands detected by the Transaction Affinities Utility The Scanner component The Detector componentWhat is detected What is not detected Worsening of transaction affinities relationsWorsening of transaction affinities lifetimes Controlling the Detector How the affinity data is collectedSaving affinity data The affinity data VSAM les The control record VSAM leThe Builder component Detector performanceThe Reporter component v A report presenting the affinity data in a readable formChapter 2. Introducing the Transaction Affinities Utility 20 CICS Transaction Affinities Utility Guide Chapter 3. Preparing to use the affinity utility program Creating the VSAM lesEstimating 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 v The JOB accounting parameters v The PARM statement Chapter 4. Running the ScannerCreating a summary report $SUMMARYv The AFFMOD DD statement Creating a detailed report v The PARM statement$DETAIL v The STEPLIB DD statement Contents of a detailed reportv The DETAIL DD statement v The INPUT DD statementv A summary report of the modules, giving ± The total possible affinity commands± The total possible MVS post commands Figure 5 is an example of a detailed report produced by the Scanner30 CICS Transaction Affinities Utility Guide Chapter 5. Running the Detector v Changing the statev Changing the options Displaying the Detector control screen When 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 v Restore data on start „1… The control options v Perform periodic savesv Transid prex „4… Last update by useridv Size of dataspace „2… Detect affinity typesDetector errors 40 CICS Transaction Affinities Utility Guide v The JOB accounting parameters Chapter 6. Running the ReporterRequesting a report from the Reporter v The PARM parameter of the EXEC statement For examplev The TRANGRPS DD statement Output from the Reporterv The CMDGRPS DD statement v The SYSPRINT DD statementAffinity report Figure 8. A sample report output by the Reporter Part 1 ofFigure 8. A sample report output by the Reporter Part 2 of „3… Affinities reports Notes for Figure „1… Incorrect affinity types„2… Affinity types reported TrangroupAffinity RecoverableCommand LifetimeBTS Task Producing affinity transaction group denitionsTerminal Total TransactionsUsing the affinity report v Remove false affinities Understanding the affinitiesModifying affinity transaction groups v Remove affinity relation worseningv Change LUNAME affinity relation to USERID Compressing affinity datav Remove affinity lifetime worsening v Add WAIT affinitiesAffinity analysis for a CICS region containing CSP 3.3 applications Using the IBM Cross System ProductSPI commands ENQUEUEs/DEQUEUEsDetailed affinity analysis ENQUEUE/DEQUEUEGETMAIN SHARED Temporary storage queues52 CICS Transaction Affinities Utility Guide SPI commands 54 CICS Transaction Affinities Utility Guide DSPSIZE=16number Chapter 7. Running the Builderv The PARM parameter of the EXEC statement MATCH=LUNAMEUSERIDv The AFFGRPS DD statement Syntax for input to the Builderv The REPGRPS DD statement v The SYSPRINT DD statementHEADER statement. Otherwise comment lines are thrown away Combined affinity transaction group denitions HEADER statementsOutput from the Builder 58 CICS Transaction Affinities Utility GuideCombining basic affinity transaction groups Builder produces a report that lists the combinations that occurred Group merge report Data sets processed reportEmpty transaction groups report LifetimeError report Figure 14. Sample group merge reportFigure 15. Sample error report 64 CICS Transaction Affinities Utility Guide Appendix A. Details of what is detected ENQ/DEQRETRIEVE WAIT/START TS commandsLOAD HOLD/RELEASE 66 CICS Transaction Affinities Utility GuideLOAD/FREEMAIN ADDRESS CWAGETMAIN SHARED/FREEMAIN CANCEL/DELAY/POST/START SPI commands WAIT commands70 CICS Transaction Affinities Utility Guide Scanner output Appendix B. Correlating Scanner and Reporter output to sourceReporter output ExamplesExample 2±VS COBOL DFHEIV0The COBOL source after translation was To determine the EXEC CICS commandFor the Scanner output The equivalent Assembler-language is001126 MOVE 74 CICS Transaction Affinities Utility GuideLOGON or SYSTEM when PCONV expected COBOL affinitiesUnrecognized Transids 76 CICS Transaction Affinities Utility Guide Appendix D. Diagnostics Detector table manager diagnosticsFunction code values Table identier values Reason code values Reason code values Detector CAFB request queue manager diagnosticsDate formatter diagnostics This sectionIndex A continued Page 84 CICS Transaction Affinities Utility Guide Sending your comments to IBM IBMR Program NumberSC33-1777-02 Spine information ReleaseCICS Transaction Affinities Utility Guide CICS TS for OS/390