The Task identification section provides the following fields.
For more information on these fields, see Task identification fields.
If the task number and the APPLID of a task match
its originating transaction, then this section contains only a single
line. However, if the APPLID or the task number, or both, do not match
the originating transaction, then this section contains a second line
describing the originating transaction. If a field is not available
for the originating transaction, then the second line contains a dash
(-) for that field.
- Tran
- The Transaction ID identifies the name of the transaction that
this transaction resource class record represents. See the performance
class data field TRAN (owner: DFHTASK, field ID: 001).
- Userid
- The User identifier of the transaction. See the performance class
data field USERID (owner: DFHCICS, field ID: 089).
- SC
- Type of transaction start or start code. See the performance class
data field SC (owner: DFHTASK, field ID: 004).
- TranType
- This column describes the transaction type:
S System transaction
U User transaction
M Mirror transaction
D DPL Mirror transaction
O ONC RPC Alias transaction
W WEB Alias transaction
B Bridge transaction
- Reserved
R CICS BTS Run (ACQPROCESS or activity) transaction synchronous
The
transaction type is represented as an interpretation of byte 1 of
the transaction flags field. See the performance class data field
TRANFLAG (owner: DFHTASK, field ID: 164).
- Term
- The Terminal ID 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. See the performance class data field TERM (owner:
DFHTERM, field ID: 002).
- LUName
- The LUname 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. This field is blank if the transaction was not associated with
a terminal or session facility. See the performance class data field
LUNAME (owner: DFHTERM, field ID: 111).
- Request Type
- This field describes the type of request that the transaction
resource 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 and identifies the connection name (SYSID)
of the remote system to which the transaction was routed. See the
performance class data field RSYSID (owner: DFHCICS, field ID: 130).
- Program
- The initial program name (field: PGMNAME, owner: DFHPROG, field
ID: 071). This 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.
- FCTY T
- This field is an interpretation of byte 0 of the transaction flags
field (field: TRANFLAG, owner: DFHTASK, field ID: 164). It 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 (field: TERMCNNM, 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).
- NETName
- This column is the network
unit-of-work ID from the system where the network unit-of-work ID
originated. This name is constant within each network unit-of-work
ID. See the performance class data field NETUOWPX (owner: DFHTASK,
field ID: 097), DFHTASK fields.
- APPLID
- The APPLID of the CICS® system
upon which the CMF transaction resource record was created. This field
indicates the CICS system that
performed the work recorded in the record.
- Task
- The transaction identification number (field: TRANNUM, owner:
DFHTASK, field ID: 031). This is printed for all records to help identify
the corresponding records on a Performance List report.
- UOW Seq
- This column is the syncpoint sequence number from the network
unit-of-work ID that was assigned at transaction attach time. See
the performance class data NETUOWSX (owner: DFHTASK, field ID: 098), DFHTASK fields.
- 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 was output for a transaction termination (detach).
For transaction resource class data, this field
is always T.
- Stop / OStart Time
- The first line in this section contains the Stop time (hh:mm:ss.thm)
of the transaction (field: STOP, owner: DFHCICS, field ID: 006).
If
the section contains two lines, then the second line contains the
Start time of the originating transaction.
- Response Time
- The first line in this section contains the transaction response
time. This field is calculated by subtracting the transaction Start
Time (field: START, owner: DFHCICS, field ID: 005) from the transaction
Stop Time (field: STOP, owner: DFHCICS, field ID: 006).
If the section
contains two lines, then the second line shows the elapsed time between
the Start time of the originating transaction and the Stop time of
the transaction shown on the first line. This is not the response
time of the originating transaction: the Stop time of the originating
transaction is not available in this report.