Detail report

The Transaction Group report shown in Figure 1 was created using the command:
CICSPA TRANGROUP(PRINTS,PRINTM,OUTPUT(TRGP0001))
Figure 1. Transaction Group report (detail)
 V5R3M0                                                  CICS Performance Analyzer
                                                             Transaction Group
 
TRGP0001 Printed at 12:34:56 02/15/2015 Data from 11:10:29  2/04/2010 to 11:33:51  2/04/2010                           Page      41
 
                            Brdg   Client        Request                         Fcty  Conn                 R             Response
Tran Userid   SC Origin     Tran IP Address       Type   Program  Term LUName   T/Name Name APPLID     Task T  Stop Time    Time
 
SALE BRENNER  U  SCHEDULE                        AP:     DFH0SAL2                           IYK2Z1V3    268 T 11:19:52.38    .0399
 
SALE BRENNER  U  SCHEDULE                        AP:     DFH0SAL2                           IYK2Z1V3    279 T 11:19:57.58    .0683
 
REM1 BRENNER  U  SCHEDULE                        AP:     DFH0REM1                           IYK2Z1V3    281 T 11:19:57.60    .0231
 
SALE BRENNER  U  SCHEDULE                        AP:     DFH0SAL2                           IYK2Z1V3    282 T 11:19:57.64    .0405
 
STAT CBAKER   TO BRIDGE     CWBA                 AP:     DFH0STAT CAAE CAAE     B/CAAE      IYK2Z1V3    292 T 11:20:12.04  10.5089
CWBA CBAKER   U  WEB             9.20.30.232     AP:     DFHWBTTA                           IYK2Z1V3    291 T 11:20:01.65    .1188
CWXN CBAKER   U  SOCKET          9.20.30.232     AP:     DFHWBXN                            IYK2Z1V3    290 T 11:20:01.54    .0169
 
SALE BRENNER  U  SCHEDULE                        AP:     DFH0SAL2                           IYK2Z1V3    293 T 11:20:02.81    .0568
 
SALE BRENNER  U  SCHEDULE                        AP:     DFH0SAL2                           IYK2Z1V3    296 T 11:20:04.33    .1340
 
SALE BRENNER  U  SCHEDULE                        AP:     DFH0SAL2                           IYK2Z1V3    297 T 11:20:04.33    .1326
 
CWBA CBAKER   U  WEB             9.20.30.232     AP:     DFHWBTTA                           IYK2Z1V3    299 T 11:20:07.37   1.0015
CWXN CBAKER   U  SOCKET          9.20.30.232     AP:     DFHWBXN                            IYK2Z1V3    298 T 11:20:06.38    .3103
 
CWBA CBAKER   U  WEB             9.20.30.232     AP:     DFHWBTTA                           IYK2Z1V3    302 T 11:20:12.04    .0423
CWXN CBAKER   U  SOCKET          9.20.30.232     AP:     DFHWBXN                            IYK2Z1V3    301 T 11:20:12.01    .2331
 
CZUX CBAKER   QD TDQUEUE                         AP:     DFH0VZUX               D/CSZX      IYK2Z1V3    304 T 11:20:19.36    .0078
 
SALE BRENNER  U  SCHEDULE                        AP:     DFH0SAL2                           IYK2Z1V3    307 T 11:20:20.34    .7041
 
SALE BRENNER  U  SCHEDULE                        AP:     DFH0SAL2                           IYK2Z1V3    308 T 11:20:20.43    .7920
 
CWXN CBAKER   U  SOCKET          9.20.30.232     AP:     DFHWBXN                            IYK2Z1V3    331 T 11:34:12.76  782.697
CEMT CBAKER   TO BRIDGE     CWBA                 AP:     DFHEMTP  CAAG CAAG     B/CAAG      IYK2Z1V3    354 T 11:21:55.38  13.3797
CWBA CBAKER   U  WEB             9.20.30.232     AP:     DFHWBTTA                           IYK2Z1V3    353 T 11:21:42.10    .0986
CWBA CBAKER   U  WEB             9.20.30.232     AP:                                        IYK2Z1V3    332 T 11:21:10.12    .0529
 
CWXN CBAKER   U  SOCKET          9.20.30.232     AP:     DFHWBXN                            IYK2Z1V3    333 T 11:25:52.65  282.577
CWBA CBAKER   U  WEB             9.20.30.232     AP:     DFHWBTTA                           IYK2Z1V3    351 T 11:21:32.85    .0378
CWBA CBAKER   U  WEB             9.20.30.232     AP:                                        IYK2Z1V3    334 T 11:21:10.12    .0485
 
CZUX CBAKER   QD TDQUEUE                         AP:     DFH0VZUX               D/CSZX      IYK2Z1V3    340 T 11:21:19.48    .0240

This section gives a brief description of the performance class data fields shown in the Transaction Group report. For more information, see the CICS Performance Guide.

Tran
The Transaction ID (field: TRAN, owner: DFHTASK, field ID: 001) identifies the name of the transaction that this performance class record represents. Applications that are using Distributed Program Link (DPL) requests should use the TRANSID('xxxx') parameter on the EXEC CICS® LINK PROGRAM('xxxxxxxx') command to enable better transaction/application analysis from the monitoring performance class data. If the TRANSID('xxxx') parameter is not specified, all the performance class records on the target system for a Distributed Program Link (DPL) mirror transaction will have the same transaction ID. For example, 'CSMI' for a Distributed Program Link (DPL) request from another connected CICS system.
Userid
The User identifier of the transaction (owner: DFHCICS, field ID: 089).
SC
Type of transaction start or start code (field: TTYPE, owner: DFHTASK, field ID: 004).
Origin
This field is an interpretation of the transaction origin type from byte 4 of the transaction flags field (field: TRANFLAG, owner: DFHTASK, field ID: 164) and can be used as an indicator of the source of the transaction. This field can have one of the following values:
Origin Type Description
NONE None
TERM Terminal
TDQ Transient data queue
START Start
TSTART Terminal start
SCHED CICS Business Transaction Services (BTS) scheduler
XM RUN Transaction manager domain (XM)-run transaction
BRIDGE 3270 bridge
SOCKET Socket domain
WEB CICS Web support (CWS)
IIOP Internet Inter-ORB Protocol (IIOP)
RRS Resource Recovery Services (RRS)
LU6.1 LU 6.1 session
LU6.2 LU 6.2 (APPC) session
MRO MRO session
ECI External Call Interface (ECI) session
IIRR IIOP domain request receiver
RZINTR Request stream (RZ) instore transport
IPIC IP interconnectivity session
EVENT Event
JVMSERVER JVMSERVER

The Origin Type is an interpretation of the primary transaction client type with which the transaction was attached using the CICS Transaction Manager.

Brdg Tran
This field contains the name of the bridge listener transaction for those transactions that are attached by the CICS 3270 Bridge interface.
Client IP Address
The client IP address (owner: DFHSOCK, field ID: 244, in CICS TS V3.2 and earlier; or 318, truncated to size, from CICS TS V4.1).
Request Type
This field describes the type of request that the performance record represents:
Description
AP:
An application program request. The Program field will identify the initial application program name invoked for the transaction.
Note: Function shipped Distributed Program Link (DPL) requests are interpreted as application requests. In this case the AP: is followed by the ---- (as for other function shipping requests) to indicate the types of requests issued by the application program.
FS:----
A function shipping request. The ---- indicate the types of function shipping request:
F
File Control
 I
Interval Control
  D
Transient Data
   S
Temporary Storage
TR:xxxx
A transaction routing request from a terminal-owning region. The 'xxxx' is the transaction routing sysid (field: RSYSID, owner: DFHCICS, field ID: 130) and identifies the connection name (sysid) of the remote system to which the transaction was routed.
Program
The Initial Program Name (field: PGMNAME, owner: DFHPROG, field ID: 071) identifies the initial application program invoked for the transaction. Depending on the type of transaction, this field contains either the application program name as defined in the transaction definition, the program name returned by a user written dynamic routing program, the application program name passed on a function shipped Dynamic Program Link (DPL) request, the initial application program name of an ONC RPC Alias Transaction, or the initial application program name of a WEB Alias Transaction. A program name of ######## indicates that the transaction was invoked using the definition of the transaction ID specified by the DTRTRAN system initialization parameter.
Term
The Terminal ID (field: TERM, owner: DFHTERM, field ID: 002) is either the terminal ID or the session ID. This field is blank if the transaction was not associated with a terminal or session facility.
LUName
This field (field: LUNAME, owner: DFHTERM, field ID: 111) is either the VTAM® netname of the terminal ID (if the Access Method for the terminal is VTAM) or the VTAM APPLID of the connection for the session ID. For an EXCI connection, this field is blank. The transaction's terminal or session type can be identified from the NATURE field (byte 0) within the terminal information field (field: TERMINFO, owner: DFHTERM, field ID: 165). This field is blank if the transaction was not associated with a terminal or session facility.
Fcty T
This field is an interpretation of byte 0 of the transaction flags field (owner: DFHTASK, field ID: 164) and describes the transaction's facility type:
Type
Description
blank
None
T
Terminal or Session
S
Surrogate
D
Transient Data queue
B
Bridge Terminal
Fcty Name
The transaction's facility name (owner: DFHTASK, field ID: 163).
Conn Name
The terminal session connection name (owner: DFHTERM, field ID: 169). If the terminal facility associated with this transaction is a session, then this field is the name of the owning connection (sysid).
APPLID
The APPLID of the CICS system upon which the CMF performance record was created. This field indicates the CICS system that performed the work recorded in the record.
Task
The transaction identification number (owner: DFHTASK, field ID: 031). This is printed for all records to help identify the corresponding record on a Performance List report.
R T
The performance class record type (field: RTYPE, owner: DFHCICS, field ID: 112):
C
Record output for a terminal converse.
D
Record output by a user event monitoring point (EMP) DELIVER request.
F
Record output for a long running transaction.
S
Record output for a syncpoint request.
T
Record output for a transaction termination (detach).
Stop Time
Stop time of the transaction (owner: DFHCICS, field ID: 006). The transactions within the same network unit-of-work are generally displayed in ascending stop time sequence. This might not always be true, however, due to syncpointing within the transaction, and to the difficulties involved in synchronizing the STORE CLOCK (STCK) values between different CPUs.
Response Time
The transaction response time. This field is calculated by subtracting the transaction start time (owner: DFHCICS, field ID: 005) from the transaction stop time (owner: DFHCICS, field ID: 006).
Note: If the transaction response time is followed by an asterisk (*) then the transaction has allocated a session to another CICS system for either transaction routing, function shipping, or distributed transaction processing. This information is determined from the terminal session allocation request count field (owner: DFHTERM, field ID: 069). See the Transaction Group report in Figure 1 for examples of transactions that illustrate this session allocation indicator.