Manuals / IBM / Computer Equipment / Credit Card Machine

IBM Summary of changes, Changes for the CICS Transaction Server for OS/390 Release 3 edition

Models: OS

1 103

Download 103 pages 52.71 Kb

Page 15

Summary of changes

Summary of changes

The affinity utility program is an integral part of CICS Transaction Server for OS/390 and is for use only with the CICS Transaction Server for OS/390.

To use the utility on CICS for MVS/ESA 4.1 and earlier releases of CICS, install the IBM CICS Transaction Affinities Utility MVS/ESA (program number 5696-582).

Changes for the CICS Transaction Server for OS/390 Release 3 edition

This book is based on the CICS Transaction Server for OS/390, release 2, edition, SC33-1777-01.

Signi®cant changes for this edition are indicated by vertical lines to the left of the changes.

Changes for the CICS Transaction Server for OS/390 Release 2 edition

This book is based on the CICS Transaction Server for OS/390, release 1, edition, SC33-1777-00.

A new section has been added to ªChapter 6. Running the Reporterº on page 41. ªUsing the IBM Cross System Productº on page 50 describes the use of the Transaction Affinities Utility with programs developed using the IBM Cross System Product.

Changes for the CICS Transaction Server for OS/390 Release 1 edition

The chapter entitled ªInstalling the affinity utilityº was renamed to ªPreparing to use the Transaction Affinities Utilityº, and was largely rewritten.

The messages and codes previously published in Appendix C were moved to the CICS Messages and Codes manual. The affinity utility program messages became standard CICS messages. They are pre®xed with the letters ªDFHº, and have a component identi®er of ªAUº.

© Copyright IBM Corp. 1994, 1999

xiii

Image 15

IBM manual Summary of changes, Changes for the CICS Transaction Server for OS/390 Release 3 edition, xiii

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 3. Preparing to use the affinity utility program ContentsChapter 1. Introducing transaction affinities Chapter 2. Introducing the Transaction Affinities UtilityAppendix 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 CICS/ESA TrademarksBookManager CICSWho this book is for How to use this bookPreface What this book is aboutArgument zero Notes on terminologyCICS Transaction Server for OS/390 Planning for Installation BibliographyCICS Transaction Server for OS/390 CICS books for CICS Transaction Server for OS/390CICSPlex SM Administration CICSPlex SM books for CICS Transaction Server for OS/390Other CICS books CICSPlex SM View Commands Reference SummaryChanges for the CICS Transaction Server for OS/390 Release 1 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 2 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 Global Inter-transaction affinityTransaction-system affinity Affinity relationsSystem Affinity lifetimesCICS programming techniques for transaction affinity UseridAvoiding the effects of transaction affinity Safe programming techniquesUnsafe programming techniques Suspect programming techniquesProtecting 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 What is not detected Worsening of transaction affinities relationsWorsening of transaction affinities lifetimes How the affinity data is collected Controlling the DetectorSaving affinity data The control record VSAM le The affinity data VSAM lesv A report presenting the affinity data in a readable form Detector performanceThe Reporter component The Builder componentChapter 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 $SUMMARY Chapter 4. Running the ScannerCreating a summary report v The JOB accounting parameters v The PARM statementv The AFFMOD DD statement Creating a detailed report v The PARM statement$DETAIL v The INPUT DD statement Contents of a detailed reportv The DETAIL DD statement v The STEPLIB DD statementFigure 5 is an example of a detailed report produced by the Scanner ± The total possible affinity commands± The total possible MVS post commands v A summary report of the modules, giving30 CICS Transaction Affinities Utility Guide Chapter 5. Running the Detector v Changing the statev Changing the options Displaying the Detector control screen Starting the collection of affinity data When you can start collecting affinity dataResuming the collection of affinity data Pausing the collection of affinity dataWhen you can pause affinity data collection When you can resume collecting 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 start„2… Detect affinity types „4… Last update by useridv Size of dataspace v Transid prexDetector errors 40 CICS Transaction Affinities Utility Guide v The PARM parameter of the EXEC statement For example Chapter 6. Running the ReporterRequesting a report from the Reporter v The JOB accounting parametersv The SYSPRINT DD statement Output from the Reporterv The CMDGRPS DD statement v The TRANGRPS 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 Trangroup Notes for Figure „1… Incorrect affinity types„2… Affinity types reported „3… Affinities reportsLifetime RecoverableCommand AffinityTotal Transactions Producing affinity transaction group denitionsTerminal BTS TaskUsing the affinity report v Remove affinity relation worsening Understanding the affinitiesModifying affinity transaction groups v Remove false affinitiesv Add WAIT affinities Compressing affinity datav Remove affinity lifetime worsening v Change LUNAME affinity relation to USERIDENQUEUEs/DEQUEUEs Using the IBM Cross System ProductSPI commands Affinity analysis for a CICS region containing CSP 3.3 applicationsENQUEUE/DEQUEUE Detailed affinity analysisGETMAIN SHARED Temporary storage queues52 CICS Transaction Affinities Utility Guide SPI commands 54 CICS Transaction Affinities Utility Guide MATCH=LUNAMEUSERID Chapter 7. Running the Builderv The PARM parameter of the EXEC statement DSPSIZE=16numberv The SYSPRINT DD statement Syntax for input to the Builderv The REPGRPS DD statement v The AFFGRPS DD statementHEADER statement. Otherwise comment lines are thrown away 58 CICS Transaction Affinities Utility Guide HEADER statementsOutput from the Builder Combined affinity transaction group denitionsCombining basic affinity transaction groups Builder produces a report that lists the combinations that occurred Lifetime Data sets processed reportEmpty transaction groups report Group merge reportFigure 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 detected66 CICS Transaction Affinities Utility Guide TS commandsLOAD HOLD/RELEASE RETRIEVE WAIT/STARTLOAD/FREEMAIN ADDRESS CWAGETMAIN SHARED/FREEMAIN CANCEL/DELAY/POST/START WAIT commands SPI commands70 CICS Transaction Affinities Utility Guide Examples Appendix B. Correlating Scanner and Reporter output to sourceReporter output Scanner outputDFHEIV0 Example 2±VS COBOLThe equivalent Assembler-language is To determine the EXEC CICS commandFor the Scanner output The COBOL source after translation was74 CICS Transaction Affinities Utility Guide 001126 MOVELOGON 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 This section Detector CAFB request queue manager diagnosticsDate formatter diagnostics Reason code valuesIndex A continued Page 84 CICS Transaction Affinities Utility Guide Sending your comments to IBM IBMR Program NumberSC33-1777-02 CICS TS for OS/390 ReleaseCICS Transaction Affinities Utility Guide Spine information