Manuals / IBM / Computer Equipment / Credit Card Machine

IBM OS manual Notes on terminology, Argument zero

Models: OS

1 103

Download 103 pages 52.71 Kb

Page 12

usually in step. However, due to the time required to print and distribute hardcopy books, the BookManager version is more likely to have had last-minute changes made to it before publication.

Subsequent updates will probably be available in softcopy before they are available in hardcopy. This means that at any time from the availability of a release, softcopy versions should be regarded as the most up-to-date.

For CICS Transaction Server books, these softcopy updates appear regularly on the Transaction Processing and Data Collection Kit CD-ROM, SK2T-0730-xx. Each reissue of the collection kit is indicated by an updated order number suffix (the -xx part). For example, collection kit SK2T-0730-06 is more up-to-date than SK2T-0730-05. The collection kit is also clearly dated on the cover.

Updates to the softcopy are clearly marked by revision codes (usually a ª#º character) to the left of the changes.

Notes on terminology

CICS In general, this book refers to the Customer Information Control System as ªCICSº, the element in the CICS Transaction Server for OS/390.

MVS ªMVSº is used for the operating system, which is an element of the CICS Transaction Server for OS/390.

Argument zero

When an EXEC CICS command is translated and compiled, it results in an encoded parameter list to be used with a call statement. The ®rst parameter in this list is a constant known as the CICS argument zero. The ®rst two bytes of this constant identify the command; for example, X©0A04© identi®es it as a READQ TS command.

x CICS Transaction Affinities Utility Guide

Image 12

IBM OS manual Notes on terminology, Argument zero

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 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 Requesting region Routing regionTarget region The benets of dynamic routing What does dynamic routing cost?Transaction affinities 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 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 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 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 Chapter 4. Running the Scanner Creating a summary reportv The JOB accounting parameters v The PARM statement $SUMMARYv The AFFMOD DD statement Creating a detailed report v The PARM statement$DETAIL 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 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 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 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 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/DEQUEUEGETMAIN SHARED Temporary storage queues52 CICS Transaction Affinities Utility Guide 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 GuideLOAD/FREEMAIN ADDRESS CWAGETMAIN SHARED/FREEMAIN 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 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 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 IBMR Program NumberSC33-1777-02 Release CICS Transaction Affinities Utility GuideSpine information CICS TS for OS/390