Manuals / IBM / Computer Equipment / Credit Card Machine

IBM OS manual Contents of a detailed report, v The DETAIL DD statement, v The STEPLIB DD statement

Models: OS

1 103

Download 103 pages 52.71 Kb

Page 44

vThe STEPLIB DD statement

Specify the name of the Transaction Affinities Utility load library in which you have installed the Scanner program, CAULMS.

vThe INPUT DD statement

Specify the name of the load library to be scanned.

vThe SYSPRINT DD statement

Specify the destination for the detailed report.

vThe AFFMOD DD dummy statement You do not need this for a detailed run.

vThe DETAIL DD statement

Specify the name of the data set containing the list of modules to be scanned. This list may be created initially as the output from a summary run of the Scanner. If you specify ALL on the PARM statement, change the DETAIL DD statement to specify //DETAIL DD DUMMY.

Contents of a detailed report

Each detailed report contains a section for each module, with:

vA header line giving the name, size, and entry point of the module

vA line for each possible affinity-causing command found, giving:

±The offset of the command argument zero declaration from the start of the load module.

Note: This offset is not the same as the offset given by the Reporter; the offset given by the Reporter is for the command itself. (See page 45 and page 71.)

±The contents of the command argument zero declaration (in hexadecimal).

±The EDF DEBUG line number, if present. This can provide a useful clue for identifying false affinities. If a section of a load module was translated with the DEBUG option, EDF DEBUG line numbers are given. For such a module, if no DEBUG line number is given, this may indicate that what was found was not an argument zero.

±What the command appears to be (for example, WRITEQ TS).

±Whether the affinity is inter-transaction (Trans), or transaction-system (System).

vA line for each possible MVS POST command found, giving:

±The offset of the MVS POST command from the start of the load module

±The MVS POST instruction

±The 12 bytes of storage immediately before, and the 10 bytes after, the MVS POST command

±Whether the MVS POST is SVC or otherwise

28 CICS Transaction Affinities Utility Guide

Image 44

IBM OS Contents of a detailed report, v The DETAIL DD statement, v The STEPLIB DD statement, v The INPUT DD statement

Contents

Release CICS Transaction Affinities Utility GuideCICS Transaction Server for OS/390 Page Release CICS Transaction Affinities Utility GuideCICS Transaction Server for OS/390 Third edition March Contents Chapter 1. Introducing transaction affinitiesChapter 2. Introducing the Transaction Affinities Utility 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 Trademarks BookManagerCICS CICS/ESAHow to use this book PrefaceWhat this book is about Who this book is forNotes on terminology Argument zeroBibliography CICS Transaction Server for OS/390CICS books for CICS Transaction Server for OS/390 CICS Transaction Server for OS/390 Planning for InstallationCICSPlex SM books for CICS Transaction Server for OS/390 Other CICS booksCICSPlex SM View Commands Reference Summary CICSPlex SM AdministrationSummary of changes Changes for the CICS Transaction Server for OS/390 Release 3 editionChanges 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 Target region Requesting regionRouting region Transaction affinities The benets of dynamic routingWhat does dynamic routing cost? Inter-transaction affinity Transaction-system affinityAffinity relations GlobalAffinity lifetimes CICS programming techniques for transaction affinityUserid SystemSafe programming techniques Unsafe programming techniquesSuspect 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 Worsening of transaction affinities lifetimes What is not detectedWorsening of transaction affinities relations Controlling the Detector How the affinity data is collectedSaving affinity data The affinity data VSAM les The control record VSAM leDetector performance The Reporter componentThe 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 Estimating the size of the MVS data space and VSAM les Chapter 3. Preparing to use the affinity utility programCreating the VSAM les Dening the VSAM les to CICS Chapter 3. Preparing to use the affinity utility program 24 CICS Transaction Affinities Utility Guide Chapter 4. Running the Scanner Creating a summary reportv The JOB accounting parameters v The PARM statement $SUMMARYv The AFFMOD DD statement $DETAIL Creating a detailed reportv The PARM statement Contents of a detailed report v The DETAIL DD statementv The STEPLIB DD statement v The INPUT DD statement± The total possible affinity commands ± The total possible MVS post 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 options Chapter 5. Running the Detectorv Changing the state Displaying the Detector control screen When you can start collecting affinity data Starting the collection of affinity dataPausing the collection of affinity data When you can pause affinity data collectionWhen you can resume collecting affinity data 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 saves„4… Last update by userid v Size of dataspacev Transid prex „2… Detect affinity typesDetector errors 40 CICS Transaction Affinities Utility Guide Chapter 6. Running the Reporter Requesting a report from the Reporterv The JOB accounting parameters v The PARM parameter of the EXEC statement For exampleOutput from the Reporter v The CMDGRPS DD statementv The TRANGRPS DD statement v The SYSPRINT DD statementFigure 8. A sample report output by the Reporter Part 2 of Affinity reportFigure 8. A sample report output by the Reporter Part 1 of Notes for Figure „1… Incorrect affinity types „2… Affinity types reported„3… Affinities reports TrangroupRecoverable CommandAffinity LifetimeProducing affinity transaction group denitions TerminalBTS Task Total TransactionsUsing the affinity report Understanding the affinities Modifying affinity transaction groupsv Remove false affinities v Remove affinity relation worseningCompressing affinity data v Remove affinity lifetime worseningv Change LUNAME affinity relation to USERID v Add WAIT affinitiesUsing the IBM Cross System Product SPI commandsAffinity analysis for a CICS region containing CSP 3.3 applications ENQUEUEs/DEQUEUEsDetailed affinity analysis ENQUEUE/DEQUEUE52 CICS Transaction Affinities Utility Guide GETMAIN SHAREDTemporary storage queues SPI commands 54 CICS Transaction Affinities Utility Guide Chapter 7. Running the Builder v The PARM parameter of the EXEC statementDSPSIZE=16number MATCH=LUNAMEUSERIDSyntax for input to the Builder v The REPGRPS DD statementv The AFFGRPS DD statement v The SYSPRINT DD statementHEADER statement. Otherwise comment lines are thrown away HEADER statements Output from the BuilderCombined affinity transaction group denitions 58 CICS Transaction Affinities Utility GuideCombining basic affinity transaction groups Builder produces a report that lists the combinations that occurred Data sets processed report Empty transaction groups reportGroup merge 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/DEQTS commands LOAD HOLD/RELEASERETRIEVE WAIT/START 66 CICS Transaction Affinities Utility GuideGETMAIN SHARED/FREEMAIN LOAD/FREEMAINADDRESS CWA CANCEL/DELAY/POST/START SPI commands WAIT commands70 CICS Transaction Affinities Utility Guide Appendix B. Correlating Scanner and Reporter output to source Reporter outputScanner output ExamplesExample 2±VS COBOL DFHEIV0To determine the EXEC CICS command For the Scanner outputThe COBOL source after translation was The equivalent Assembler-language is001126 MOVE 74 CICS Transaction Affinities Utility GuideUnrecognized Transids LOGON or SYSTEM when PCONV expectedCOBOL affinities 76 CICS Transaction Affinities Utility Guide Function code values Appendix D. DiagnosticsDetector table manager diagnostics Table identier values Reason code values Detector CAFB request queue manager diagnostics Date formatter diagnosticsReason code values This sectionIndex A continued Page 84 CICS Transaction Affinities Utility Guide Sending your comments to IBM SC33-1777-02 IBMRProgram Number Release CICS Transaction Affinities Utility GuideSpine information CICS TS for OS/390