Tips for collecting CMP data
UIE can process CMP data for all supported versions of CICS Transaction Server for z/OS, which are listed in the BMC AMI Capacity Management
documentation.
For CMP version 3.2 and later, the CMP data can be in compressed or uncompressed format.
The following list includes tips to help you when collecting CMP data:
CMP data contains the following subtypes:
- 0—CICS journaling
- 1—CICS monitoring
- Exception class records (110/1E)
- Dictionary class records (110/1D)
- Performance class records (110/1P)
- 2—CICS statistics
- 3—Shared temporary storage queue server
- 4—Coupling facility data table server statistics
- 5—Named counter sequence number server statistics
UIE processes the subtype 1 dictionary and performance class records, and the subtype 2 statistics records.
- Set the MNCONV parameter in your CICS system initialization parameters (DFHSIT macro) to YES to cause each interchange of a conversational transaction to be reported as a separate transaction.
- Set the MNFREQ parameter in your CICS system initialization parameters (DFHSIT macro). The MNFREQ parameter specifies an interval for which CICS automatically produces a performance class record for long-running transactions. The value is specified as a one- to six-digit number in the format hhmmss. We recommend that you set the value to equal the duration of the UIE interval, which, by default, would be 006000 (60 minutes).
The following table shows the fields that UIE collects from CMP data. If you choose to exclude any of these fields from your CMP data records, some parameters in the XML model might be unavailable or incomplete.
IBM field numbers | Field name | Field descriptions |
---|---|---|
001 (required) | TRAN 1 | Transaction name |
002 (required) | TERM | Terminal ID |
004 (required) | TTYPE | Transaction type |
005 (required) | START | Transaction start time |
006 (required) | STOP | Transaction stop time |
007 | USRDISPT | Dispatch time |
008 | USRCPUT | Application CPU time |
009 | TCIOWTT | Terminal control I/O wait tim |
010 | JCIOWTT | Journal control I/O wait time |
011 | TSIOWTT | Temporary storage I/O wait time |
014 | SUSPTIME | Suspend time |
031 | TRANNUM | Transaction identification number |
063 | FCIOWTT | File control I/O wait time |
070 | FCAMCT | File control access method count |
071 | PROGRAM | Program name, which is required for grouping transactions and defining applications by PROGRAM |
082 | TRNGRPID | Transaction group ID |
089 | USERID | CICS user logon ID, which is required for grouping transactions and defining applications by USERID |
093 | FCTOTCT | File control request count |
097 | NETNAME | Network name that is used for MRO processing |
098 | UOWID | Unit-of-work ID that is used for MRO processing |
100 2 | IRIOWTT | Inter-region I/O wait time |
101 | TDIOWTT | Transient data I/O wait time |
102 | DISPWTT | Dispatch wait time |
095 | SCUSRSTG | Storage occupancy below the 16 MB line in the user dynamic storage area (UDSA) |
107 | SCUSRSTG | Storage occupancy above the 16 MB line in the extended user dynamic storage area (EUDSA) |
109 | TRANPRI | Transaction priority |
111 | LUNAME | IBM VTAM logical unit (LU) name |
112 | RTYPE | Performance record type |
113 | ABCODEO | Original abend code |
114 | ABCODEC | Current abend code |
118 | SC24COCC | Storage occupancy of the user task below the 16 MB line, in the CDSA |
121 | SC31COCC | Storage occupancy of the user task above the 16 MB line, in the ECDSA |
123 2 | GNQDELAY | Global enqueue wait time |
124 | BRDGTRAN | Bridge listener transaction identifier |
125 2 | DSPDELAY | Wait for first dispatch |
128 2 | LMDELAY | Lock manager wait time |
129 2 | ENQDELAY | Local enqueue wait time |
130 | RSYSID | Remote system ID |
132 | RMUOWID | Resource manager unit of work (unit of recovery) ID |
133 2 | LU61WTT | LU 6.1 connection I/O wait time |
134 2 | LU62WTT | LU 6.2 connection I/O wait time |
156 2 | SZWAIT | FEPI service wait time |
163 | FCTYNAME | Transaction facility name |
164 | TRANFLAG | Transaction flags |
166 | TCLSNAME | Transaction class name |
167 | SRVCLSNM | IBM MVS Workload Manager service class name |
168 | RPTCLSNM | MVS Workload Manager report class name |
169 | TERMCNNM | Terminal session connection name |
171 2 | RMISUSP | Resource Manager Interface (RMI) suspend time |
174 2 | RLSWAIT | Record level sharing (RLS) Wait time |
175 | RLSCPUT | RLS file request CPU time |
176 2 | CFDTWAIT | Coupling Facility wait time |
177 2 | SRVSYWTT | Coupling Facility data tables syncpoint processing wait time |
178 2 | TSSHWAIT | Shared temporary storage wait time |
181 2 | WTEXWAIT | EXEC CICS WAIT EXTERNAL ECBLIST command wait time |
182 2 | WTCEWAIT | EXEC CICS WAITCICS ECBLIST command wait time |
183 2 | ICDELAY | Interval control wait time |
184 | GVUPWAIT | Wait time when user task gives up control to another task |
190 | RRMSURID | RRMS/MVS unit-of-recovery ID |
191 2 | RRMSWAIT | Resource recovery services wait time |
194 | OTSTID | Object transaction service transaction ID |
195 2 | RUNTRWTT | CICS Business Transaction Service (BTS) run process request wait time |
196 2 | SYNCDLY | Syncpoint request wait time |
197 | NETID | Network name received from VTAM |
198 | RLUNAME | Real network name received from VTAM |
200 | PRCSNAME | BTS process name |
201 | PRCSTYPE | BTS process type |
202 | PRCSID | BTS root activity identifier |
203 | ACTVTYID | BTS activity identifier |
204 | ACTVTYNM | BTS activity name |
241 2 | SOIOWTT | Inbound socket I/O wait time |
244 | CLIPADDR | Client IP address |
245 | TCPSRVCE | TCP/IP service name |
250 2 | MXTOTDLY | Wait time for an open TCB when the MAXOPENTCBS limit had been reached |
253 2 | JVMTIME | JVM elapsed time |
254 2 | JVMSUSP | JVM suspend time |
305 | ISIPICNM | IPIC connection name for the TCP/IP service that attached the user task |
311 | CBSRVRNM | CorbaServer name |
359 | ONETWKID | Network identifier from which this work request originated |
360 | OAPPLID | Applid of the CICS region in which this work request originated |
363 | OTRAN | Transaction ID of the originating task |
364 | OUSERID | Originating Userid-2 or Userid-1 |
365 | OUSERCOR | Originating user correlator |
366 | OTCPSVCE | Name of the originating TCPIPSERVICE |
371 | OFCTYNME | Facility name of the originating transaction |
372 | OCLIPADR | IP address of the originating client or Telnet client |
380 | WBURIMNM | URIMAP resource definition name that was mapped to the URI of the inbound request |
381 | WBPIPLNM | PIPELINE resource definition name that was used to provide information about the message handlers that act on the service request processed by this task |
382 | WBATMSNM | ATOMSERVICE resource definition name that was used to process this task |
383 | WBSVCENM | WEBSERVICE resource definition name that was used to process this task |
384 | WBSVOPNM | First 64 bytes of the Web service operation name |
385 | WBPROGNM | Program name from the URIMAP resource definition that was used to provide the application-generated response to the HTTP request |
001 1 | USERFLD | User field Optionally used for collecting and identifying a transaction. Required for grouping transactions and defining applications by USERFLD. |
- Although the field ID for USERFLD is the same as that for TRAN, the CICS Monitor Program is able to distinguish between the two.
- These fields are processed by UIE but currently the output is not sent to the Visualizer file.
For more information, see The system initialization parameter descriptions and summary in the IBM CICS Transaction Server online documentation.
Related topic