Manuals / IBM / Computer Equipment / Credit Card Machine

IBM OS manual Creating a detailed report, v The PARM statement, $Detail

Models: OS

1 103

Download 103 pages 52.71 Kb

Page 43

CICS TRANSACTION AFFINITIES UTILITY							1995/11/24	Page	1
LOAD MODULE SCANNER		- SUMMARY LISTING OF CICSTEST.LOAD
Module	Module	Module	Affinity	MVS POSTs		Comment
Name	Length	Language	Statements
--------	--------	---------	----------	---------		------------------------	--------------------
ACSA1	00000198	ASSEMBLER	3	0	Possible affinity commands.
AFFYIC	00000308		0	0
AFFYTS	00000628		0	0
COBACSA	000008B8	COBOL II	4	0	Possible affinity commands.
CRMRPROG	000001A0		0	0
DFHSRT1$		CICS TABLE	0	0
DFHTCTSH		CICS TABLE	0	0
DFHTSTEC		CICS TABLE	0	0
PLIACSA	000003C8	PL/I	3	0	Possible affinity commands.
PLTCCC	00000D48	C/370	2	0	Possible affinity commands.
PLTCOB	000009D8	COBOL II	2	0	Possible affinity commands.
PLTPLI	00000570	PL/I	1	0	Possible affinity commands.
SCRATCH	000006D0		0	0
TRANOUT	000008B8		0	1	Possible MVS POSTs.
CICS TRANSACTION AFFINITIES UTILITY							1995/11/24	Page	2
LOAD MODULE SCANNER		- SUMMARY LISTING OF CICSTEST.LOAD
	LOAD	LIBRARY STATISTICS

==========================================================

Total modules	in library	=	14
Total modules	scanned	=	11
Total CICS modules/tables (not scanned)		=	3
Total modules	in error (not scanned)	=	0
Total modules	containing possible MVS POSTs	=	1
Total modules	containing possible Affinity commands =		6
Total ASSEMBLER modules		=	1
Total C/370	modules	=	1
Total COBOL	modules	=	0
Total COBOL	II modules	=	2
Total PL/I modules		=	2

Figure 4. Example of a summary report produced by the Scanner

Creating a detailed report

You can request a detailed report from the Scanner by editing and running the job

CAUJCLLD.

Change the following statements as appropriate:

vThe PARM statement

PARM=©$DETAIL[,ALL]©

$DETAIL

Speci®es that a detailed scan and report is required. The extent of the scan is de®ned by either the ALL parameter or the DETAIL DD statement.

ALL

Speci®es that all modules in the load library are to be scanned for possible affinity-causing EXEC CICS commands and MVS POST commands.

If ALL is omitted, only those modules listed in the ®le speci®ed on the DETAIL DD statement are to be scanned. This ®le would normally be from the AFFMOD DD output of an Scanner summary report run, which you can edit before creating a detailed report.

Chapter 4. Running the Scanner 27

Image 43

IBM OS manual Creating a detailed report, v The PARM statement, $Detail

Contents

CICS Transaction Server for OS/390 CICS Transaction Affinities Utility GuideRelease Page CICS Transaction Server for OS/390 CICS Transaction Affinities Utility GuideRelease 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 Routing region Requesting regionTarget region What does dynamic routing cost? The benets of dynamic routingTransaction 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 Worsening of transaction affinities relations What is not detectedWorsening 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 Creating the VSAM les Chapter 3. Preparing to use the affinity utility programEstimating 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 v The PARM statement Creating a detailed report$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 v Changing the state Chapter 5. Running the Detectorv 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 statementFigure 8. A sample report output by the Reporter Part 1 of Affinity reportFigure 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 analysisTemporary storage queues GETMAIN SHARED52 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/STARTADDRESS CWA LOAD/FREEMAINGETMAIN 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 MOVECOBOL affinities LOGON or SYSTEM when PCONV expectedUnrecognized Transids 76 CICS Transaction Affinities Utility Guide Detector table manager diagnostics Appendix D. 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 Program Number IBMRSC33-1777-02 CICS TS for OS/390 ReleaseCICS Transaction Affinities Utility Guide Spine information