The Workload Activity report shown in
Figure 1 was created using the command:
CICSPA WORKLOAD(LIST,OUTPUT(ddname))
Figure 1. Workload
Activity List report V5R1M0 CICS Performance Analyzer
Workload Manager Activity List
WKLD0001 Printed at 12:03:45 10/15/2012 Data from 15:47:53 2/01/2010 to 15:58:53 2/01/2010 Page 1
Request Fcty Conn Service Report R Response A
Tran Userid SC TranType Term LUName Type Program T/Name Name Class Class APPLID Task T P C Stop Time Time B
FINA STEVEP TP <AAK CICPTOR1 AP: FINANCE S/0005 53T1 FINSCLAS FINRCLAS CICPAOR1 44 T EXE Y 15:57:53.92 .5239
FINS STEVEP TP 0005 TCP00005 TR:AOR1 T/0005 FINSCLAS FINRCLAS CICPTOR1 73 T BTE 15:57:53.93 .5612
STOA SHIRLEY TP <AAK CICPTOR1 AP: STOCK S/0006 53T1 STOSCLAS STORCLAS CICPAOR1 46 T EXE Y 15:57:54.01 .8574
STOS SHIRLEY TP 0006 TCP00006 TR:AOR1 T/0006 STOSCLAS STORCLAS CICPTOR1 78 T BTE 15:57:54.02 .9123
ORDQ SYLVIA TO 0011 TCP00011 AP: ORDRINQ T/0011 QUIKSERV QUIKSERV CICPAOR1 79 T BTE 15:57:55.12 .3762
ORDQ JOHNX TO 0012 TCP00012 AP: ORDRINQ T/0012 QUIKSERV QUIKSERV CICPAOR1 82 T BTE 15:50:55.23 .4321
ORDU SYLVIA TO 0011 TCP00011 AP: ORDRUPD T/0011 LONGSERV LONGSERV CICPAOR1 98 T BTE 15:54:56.13 1.4581
ORDU JOHNX TO 0012 TCP00012 AP: ORDRUPD T/0012 LONGSERV LONGSERV CICPAOR1 109 T BTE 15:58:56.17 1.2394
The following fields are shown on the Workload Activity List report.
For more information on these fields, 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 (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 (owner: DFHTASK, field ID: 164).
- 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
- The LUname (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.
- 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 from the RSYSID field
(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.
- 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).
- Service Class
- The MVS™ Workload Manager
(WLM) service class for this transaction. This field is blank if there
are no transaction classification rules defined for CICS subsystems in the active MVS Workload Manager (WLM) service policy or
the transaction was WLM-classified in another CICS region.
For an EXE Y transaction, the
Service Class is derived from the related BTE transaction. For an
EXE N transaction, the Service Class is blank since it cannot be determined
as the transaction was not complete.
- Report Class
- The MVS Workload Manager
(WLM) report class for this transaction. This field is blank if there
are no transaction classification rules defined for CICS subsystems in the active MVS Workload Manager (WLM) service policy or
the transaction was WLM-classified in another CICS region.
For an EXE Y transaction, the
Report Class is derived from the related BTE transaction. For an EXE
N transaction, the Report Class is blank since it cannot be determined
as the transaction was not complete.
- 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
records 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).
- P
- This field describes the MVS Workload
Manager phase as reported by CICS.
It can be either:
- BTE
- The begin-to-end phase takes place in the first region
to begin processing a transaction.
- EXE
- The execution phase takes place in an application owning
region (AOR) and a file owning region (FOR). However, only the execution
phase that takes place in an application owning region (AOR) is
reported to the MVS Workload
Manager.
For a detailed explanation about Workload
Manager state information, see OS/390® MVS Workload Management Services.
- C
- This field indicates the completion status of an execution
phase of the work request as reported by CICS to the MVS Workload
Manager. It can be either:
- blank
- This performance class record is part of the begin-to-end phase of
a transaction.
- Y
- The entire execution phase of the work request, a transaction,
has now completed.
- N
- Only a portion of the execution phase of the work request,
a transaction, has completed.
- Stop Time or Start Time
- Stop or start time (hh:mm:ss.thm) of the transaction (owner: DFHCICS,
field ID: 005 for start, 006 for stop). The transactions within the
same network unit-of-work are generally displayed in either descending
stop time or ascending start 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).
- A B
- Y in this column indicates that the transaction abended.