Default format: Cross-System Work

On the Cross-System Work report, each line is printed from a single CMF performance class record. Records that are part of the same network unit-of-work are printed sequentially in groups separated by lines containing four dashes (----). The printed information allows you to find the corresponding records in the Performance List report.

The Cross-System Work report is produced using an external SORT facility. An External Work Data Set is required to store the records before they are sorted. This data set is either specified explicitly using EXTERNAL(ddname), or CICS PA assigns one from the External Work File pool.

The records are sorted in the following order:
  1. Network Unit-of-Work NETNAME
  2. Network Unit-of-Work ID
  3. Syncpoint count concatenated with either:
    • Task stop time in descending (reverse) order

      or

    • Task start time in ascending order
  4. APPLID

In the third sort field, the syncpoint count is used to resolve unsynchronized STORE CLOCK (STCK) values between systems. The syncpoint count and stop time (or start time) show the sequence of tasks within the network unit-of-work. In some cases (for example, where user event monitor points (EMPs) are used), the syncpoint count does not reflect the sequence of events within a network unit-of-work. For these instances, all the task records are printed, but not necessarily in the order they happened. You can tell that this situation exists if the stop times are not in descending order (or the start times are not in ascending order).

For more information on correlating the performance class data by network unit-of-work ID, see Correlating performance class data.

The Cross-System Work report shown in Figure 1 was created using the command:
CICSPA CROSS(PRINTS,PRINTM,NOWRITE,OUTPUT(CROS0001))
Figure 1. Cross-System Work report
 V3R2M0                                                  CICS Performance Analyzer
                                                             Cross-System Work
 
CROS0001 Printed at 12:03:45  3/15/2011 Data from 11:10:29  2/04/2010 to 11:33:51  2/04/2010                           Page       8
 
                                        Request           Fcty  Conn                   UOW                 R              Response A
Tran Userid   SC TranType Term  LUName   Type   Program  T/Name Name NETName           Seq APPLID     Task T   Stop Time    Time   B
                                                                                                                                    
STOC BRENNER  U  U      R               AP:     DFH0STOC             GBIBMIYA.IGCS23C   1  IYK2Z1V3    242 T 11:19:41.001    .7984  
RED1 BRENNER  U  U      R               AP:     DFH0RED1             GBIBMIYA.IGCS23C   1  IYK2Z1V3    241 T 11:19:40.337    .1479  
SAL1 BRENNER  TP U        S23C IGCS23C  AP:     DFH0SAL1 T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    239 T 11:19:40.334    .1835  
----                                                                                                                                    
SAL1 BRENNER  TP U        S23C IGCS23C  AP:     DFH0SAL1 T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    251 T 11:19:42.763    .0022  
----                                                                                                                                
SAL1 BRENNER  TP U        S23C IGCS23C  AP:     DFH0SAL1 T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    255 T 11:19:45.463    .0018  
----                                                                                                                                
CBAM BRENNER  TO U        S23C IGCS23C  AP:     DFHECBAM T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    259 T 11:19:55.368   7.0077  
----                                                                                                                                
PAYM BRENNER  TO U        S23C IGCS23C  AP:     DFH0PAY0 T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    289 T 11:20:00.569    .0026  
----                                                                                                                                
PAY1 BRENNER  TP U        S23C IGCS23C  AP:     DFH0PAY1 T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    294 T 11:20:04.202    .1390  
SALE BRENNER  U  U      R               AP:     DFH0SAL2             GBIBMIYA.IGCS23C   1  IYK2Z1V3    295 T 11:20:04.200    .1353  
----                                                                                                                                
3333 BRENNER  TO U        S23C IGCS23C  AP:     ######## T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    300 T 11:20:08.003    .0028  
----                                                                                                                                
PAYM BRENNER  TO U        S23C IGCS23C  AP:     DFH0PAY0 T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    303 T 11:20:15.964    .0022  
----                                                                                                                              
PAY1 BRENNER  TP U        S23C IGCS23C  AP:     DFH0PAY1 T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    305 T 11:20:19.635    .0747
SALE BRENNER  U  U      R               AP:     DFH0SAL2             GBIBMIYA.IGCS23C   1  IYK2Z1V3    306 T 11:20:19.634    .0715
----                                                                                                                              
CSAC BRENNER  TO U        S23C IGCS23C  AP:     DFHACP   T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    313 T 11:20:44.089    .0017
----                                                                                                                              
CBAM BRENNER  TO U        S23C IGCS23C  AP:     DFHECBAM T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    315 T 11:20:50.772   3.7993
----                                                                                                                              
RMNU BRENNER  TO U        S23C IGCS23C  TR:CJB1          T/S23C      GBIBMIYA.IGCS23C   1  IYK2Z1V3    323 T 11:20:54.392    .0317
AMNU CBAKER   TO U        R11  IYK2Z1V3 AP:     DFHSAMNU S/S23C CJB3 GBIBMIYA.IGCS23C   1  IYK2Z1V1    158 T 11:20:54.390    .0228

The following fields are shown on the Cross-System Work report. For more information on these fields, see CMF performance class data fields.

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 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).
NETName
This column is the network unit-of-work ID (field: NETUOWPX, owner: DFHTASK, field ID: 097) from the system where the network unit-of-work ID originated. This name is constant within each network unit-of-work ID.

For more information on the NETUOWPX field, DFHTASK fields.

UOW Seq
The syncpoint sequence number from the network unit-of-work ID (field: NETUOWSX, owner: DFHTASK, field ID: 098) that was assigned at transaction attach time.

For more information on the NETUOWSX field, see DFHTASK fields.

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 was output for a transaction termination (detach).
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.