IBM Transaction Server OS User Manual Page 62
- Page / 103
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
Usage The number of times that this particular EXEC CICS command (with the
transaction, program, and offset values reported) taking part in the affinity,
up to a limit of 5000.
Note: The usage count is an indication of the relative importance of the
affinity, and is not a completely accurate usage count. For
performance reasons, when the usage count is incremented by the
Detector, the “save to file” flag is not necessarily set to indicate that
the record needs to be saved to the data file. The save flag is set as
follows:
0 <= usage count < 10, save flag set every increment
10 <= usage count < 100, save flag set every 10 increments
100 <= usage count < 5000, save flag set every 100 increments
5000 <= usage count, neither increment nor save flag set
If the usage count is ’1+’, it means that at least one example of the affinity
was seen but that the total number of occurrences of that affinity is
unknown.
Terminal
Whether this particular EXEC CICS command (with the transaction,
program, and offset values reported) was ever issued by a transaction
initiated from a terminal; that is, started as a result of terminal input or for
an EXEC CICS RETURN TRANSID command. (This does not include
ATI-started transactions.)
The word Mix in this column is used to indicate that a particular EXEC
CICS command was issued by a transaction initiated from a terminal and
also issued by the transaction when it was initiated with no associated
terminal.
BTS Task
Whether it is a CICS BTS task or not.
Total Transactions
The total number of different transactions in the affinity transaction group.
Total Programs
The total number of different programs in the affinity transaction group.
Producing affinity transaction group definitions
The Reporter produces affinity transaction group definitions suitable for input to the
Builder (but not to CICSPlex SM). Each definition consists of a unique transaction
group name, a relation, a lifetime, and a set of tranids.
Not everything that appears in the report appears as an affinity transaction group. In
particular, transaction-system affinities do not appear, because they are not of
interest to a dynamic routing program; nor do transactions that were not initiated
from a terminal (for the same reason).
Figure 9 on page 47 shows a sample set of definitions to match the report in
Figure 8 on page 43.
Notes:
1. The transaction group name is not a valid CICSPlex SM transaction group
name, because the latter must be eight characters; it is used only as a
cross-reference to the report.
46 CICS Transaction Affinities Utility Guide
|
|
|
|
|
|
- Release 3 1
- Contents 5
- Contents v 7
- Trademarks 10
- What this book is about 11
- Who this book is for 11
- How to use this book 11
- Notes on terminology 12
- Bibliography 13
- Other CICS books 14
- Summary of changes 15
- CICSPlex SM 17
- Managing Workloads 17
- Intercommunication Guide 18
- Transaction affinities 19
- Inter-transaction affinity 20
- Transaction-system affinity 20
- Affinity relations 20
- Affinity lifetimes 21
- Safe programming techniques 22
- Unsafe programming techniques 22
- The Scanner component 28
- The Detector component 28
- What is detected 29
- What is not detected 30
- Controlling the Detector 31
- Saving affinity data 32
- The affinity data VSAM files 33
- The control record VSAM file 33
- Detector performance 34
- The Reporter component 34
- The Builder component 34
- Creating the VSAM files 37
- Defining the VSAM files to CICS 38
- Restarting your CICS region 39
- Creating a summary report 41
- Creating a detailed report 43
- Contents of a detailed report 44
- CICS Customization Guide 49
- 3270 terminal CAFF PAUSE 50
- Changing the Detector options 52
- Detector errors 55
- Output from the Reporter 58
- Affinity report 59
- Using the affinity report 63
- Understanding the affinities 64
- Compressing affinity data 65
- ENQUEUE/DEQUEUE 67
- GETMAIN SHARED 68
- Temporary storage queues 68
- SPI commands 69
- //BUILD EXEC PGM=CAUBLD 71
- HEADER statements 74
- Output from the Builder 74
- Data sets processed report 77
- Group merge report 77
- Error report 78
- TS commands 82
- LOAD HOLD/RELEASE 82
- RETRIEVE WAIT/START 82
- ADDRESS CWA 83
- GETMAIN SHARED/FREEMAIN 83
- LOAD/FREEMAIN 83
- CANCEL/DELAY/POST/START 84
- WAIT commands 85
- Example 1–Assembler-language 87
- Example 2–VS COBOL II 88
- = X'7A6' 89
- = X'B8' 89
- 001126 MOVE 90
- Utility reports 91
- Appendix D. Diagnostics 93
- Table identifier values 94
- Reason code values 95
- (continued) 98
- Index 83 99
- Sending your comments to IBM 101
- SC33-1777-02 102
- Spine information: 103
Related products and manuals for Software IBM Transaction Server OS
Software IBM SC34-5764-01 User Manual
(481 pages)
(481 pages)
Software IBM TIVOLI SC32-0129-00 User Manual
(82 pages)
(82 pages)
Software IBM G325-2585-02 User Manual
(90 pages)
(90 pages)
Software IBM SG24-6526-00 User Manual
(184 pages)
(184 pages)
Software IBM SC33-1686-02 User Manual
(317 pages)
(317 pages)
Software IBM 5697-VM3 User Manual
(6 pages)
(6 pages)
Software IBM DS6000 User Manual
(406 pages)
(406 pages)
Software IBM CDI5UG1107 User Manual
(178 pages)
(178 pages)
Software IBM GC28-1982-02 User Manual
(216 pages)
(216 pages)
Software IBM 12.1(22)EA6 User Manual
(550 pages)
(550 pages)
Cub Cadet 770-10538 31AH4Q3G100 Handbücher
Bedienungsanleitungen und Benutzerhandbücher für Autos Cub Cadet 770-10538 31AH4Q3G100.
Wir stellen 1 PDF-Handbücher Cub Cadet 770-10538 31AH4Q3G100 zum kostenlosen herunterladen nach Dokumenttypen zur Verfügung Bedienungsanleitung
Comments to this Manuals