Manuals / IBM / Computer Equipment / Credit Card Machine

IBM OS Data sets processed report, Empty transaction groups report, Group merge report, Lifetime

Models: OS

1 103

Download 103 pages 52.71 Kb

Page 77

Table 11. Resultant affinity lifetimes (GLOBAL relation)

Lifetime X	Lifetime Y	Resultant lifetime Z

PERMANENT	Any lifetime	PERMANENT

Any other lifetime combination		SYSTEM

Data sets processed report

This report gives the names of all the input data sets (speci®ed on the REPGRPS

DDstatement) that were read. This is produced even if errors occur in the input data sets.

Note: Only data sets that contain a HEADER statement appear in the report.

CICS TRANSACTION AFFINITIES UTILITY			1995/11/28	Page	1
BUILDER REPGRPS DATASETS PROCESSED REPORT
Dataset Name	CICS	Detector Last	Detector Last
	APPLID	Save Date	Save Time
--------------------------------------------	--------	--------------	--------------
CICSPDN1.TRANGRPS.MERGE1	CICSPDN1	95/11/25	09:05:09
CICSPDN1.TRANGRPS.MERGE2	CICSPDN1	95/11/26	15:22:34
CICSPDN1.TRANGRPS.ONE	CICSPDN1	95/11/27	12:00:51

Figure 12. Sample data sets processed report

Empty transaction groups report

This report gives all basic transaction groups (trangroups) that were de®ned, but contained no transactions. It is produced only if the input data sets have no errors. An empty trangroup probably indicates that you have made a mistake. (The Reporter cannot produce empty trangroups, so you must have created the input by hand, and probably omitted some corresponding CREATE DTRINGRP statements.)

CICS TRANSACTION AFFINITIES UTILITY						1995/11/28	Page	2
BUILDER EMPTY TRANGROUP DEFINITIONS
CICSPDN1.TRANGRPS.EMPTY1
G1	(GLOBAL SYSTEM )	G2	(GLOBAL PERMANENT)		G3	(GLOBAL SYSTEM		)
CICSPDN1.TRANGRPS.EMPTY2
L2	(LUNAME PERMANENT)	L3	(LUNAME LOGON	)	L4	(LUNAME PCONV		)

Figure 13. Example empty trangroups report

Group merge report

For each combined group, this report gives the constituent transactions and basic groups that went to comprise it. (This is a kind of audit trail.) It is produced only if there are no errors in the input data sets. It is very useful when establishing which basic group has caused the severe worsening of an affinity lifetime. For example, in Figure 14 on page 62, four groups were merged: three were LUNAME and PCONV, and one was LUNAME and SYSTEM. The latter caused the lifetime worsening.

Chapter 7. Running the Builder 61

Image 77

IBM OS manual Data sets processed report, Empty transaction groups report, Group merge report, Lifetime Y

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 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 Target region Requesting regionRouting region Transaction affinities The benets of dynamic routingWhat does dynamic routing cost? 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 lifetimes What is not detectedWorsening of transaction affinities relations 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 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 Creating a summary report Chapter 4. Running the Scannerv The JOB accounting parameters v The PARM statement $SUMMARYv The AFFMOD DD statement $DETAIL Creating a detailed reportv The PARM statement 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 options Chapter 5. Running the Detectorv Changing the state 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 2 of Affinity reportFigure 8. A sample report output by the Reporter Part 1 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 analysis52 CICS Transaction Affinities Utility Guide GETMAIN SHAREDTemporary storage queues 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 GuideGETMAIN SHARED/FREEMAIN LOAD/FREEMAINADDRESS CWA 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 MOVEUnrecognized 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 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 SC33-1777-02 IBMRProgram Number CICS Transaction Affinities Utility Guide ReleaseSpine information CICS TS for OS/390