








	*SMF Tools*

SMF Type 110 Record - Subtype 1

This table shows the record layout for type 110 SMF records
(CICS Monitoring Record).

List of other SMF record layouts available.
List of sample SMF reports.

Purpose: CICS/ESA writes record type 110 to record transaction data collected at event monitoring points.

CICS writes several types of SMF 110 record. Each type, or subtype as it is known, can be identified using the record subtype field in the SMF header. The subtype values are as follows:

X'0000' - CICS journaling
X'0001' - CICS monitoring
X'0002' - CICS statistics
X'0003' - Shared temporary storage queue server
X'0004' - Coupling facility data table server statistics
X'0005' - Named counter sequence number server statistics.

CICS Monitoring Records

CICS monitoring collects data about the performance of all user- and CICS-supplied transactions during online processing for later offline analysis. Monitoring data is useful both for performance tuning and for charging your users for the resources they use.

Three types, or “classes”, of monitoring data can be collected. These are performance class data, exception class data, and SYSEVENT data.

Performance class data is detailed transaction-level information, such as the processor and elapsed time for a transaction, or the time spent waiting for I/O. At least one performance record is written for each transaction that is being monitored. CICS performance class monitoring data is collected at system-defined event-monitoring points (EMPs) in the CICS code. You cannot relocate these monitoring points, but you can create additional ones, at which user-defined performance data can be gathered.

Exception class data is information about exceptional conditions suffered by a transaction, such as queuing for file strings, or waiting for temporary storage. This data highlights possible problems in system operation. There is one exception record for each exception condition. Exception records are produced after the exceptional condition encountered by a transaction has been resolved.

SYSEVENT class data is a special kind of transaction timing information. For more information about SYSEVENT data, see the CICS Performance Guide.

The three components of a CICS monitoring record are an SMF header, an SMF product section, and a CICS data section.

The SMF header describes the system creating the output.

The SMF product section identifies the subsystem to which the monitoring data relates, which, in the case of CICS monitoring (and also of CICS statistics), is the CICS region.

The CICS data section can be made up of a dictionary data section, a performance data section, or an exception data section. You can identify which of these you are dealing with by looking at the value of field SMFMNCL in the SMF product section.

It's easy to report on SMF 110 data! (Jump to sample reports)

We have a low-cost 4GL report writer especially for SMF files. It's called Spectrum SMF Writer.

Spectrum SMF Writer handles the difficult SMF record parsing for you automatically. You just specify which fields you want to see.

Spectrum SMF Writer also converts the arcane date and time fields and reformats them into an attractive report.

Plus, Spectrum SMF Writer can export SMF data as comma delimited files to use on your PC.

SMF Type 110 Record -- CICS Monitoring Record
Offset (Dec.)	Offset (Hex)	Name	Length	Format	Description
0	0	SMF110LEN	2	BINARY	Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word). See “Standard SMF Record Header” on page 13-1 for a detailed description.
2	2	SMF110SEG	2	BINARY	Segment descriptor (see record length field).
4	4	SMF110FLG	1	BINARY	System indicator: Bit Meaning When Set 0-2 Reserved 3-6 Version indicators* 7 Reserved.*See “Standard SMF Record Header” on page 13-1 for a detailed description.
5	5	SMF110RTY	1	BINARY	Record type 110 (X'6E').
6	6	SMF110TME	4	BINARY	Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer.
10	A	SMF110DTE	4	packed	Date when the record was moved into the SMF buffer, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
14	E	SMF110SID	4	EBCDIC	System identification (from the SID parameter).
18	12	SMF110SSI	4	BINARY	Subsystem ID
22	16	SMF110STY	2	BINARY	Record subtype
24	18	SMF110TRN	2	BINARY	Number of triplets
26	1A	SMF110RES	2	BINARY	Reserved
28	1C	SMF110APS	4	BINARY	Offset to CICS product section
32	20	SMF110LPS	2	BINARY	Length of CICS product section
34	22	SMF110NPS	2	BINARY	Number of CICS product sections
36	24	SMF110ASS	4	BINARY	Offset to CICS data section
40	28	SMF110LSS	2	BINARY	Length of CICS data section
42	2A	SMF110NSS	2	BINARY	Number of CICS data sections
SMF Product Section The SMF product section identifies the subsystem to which the monitoring data relates, which, in the case of CICS monitoring (and also of CICS statistics), is the CICS region.(Offset from beginning of record: SMF110APS)
0	0	SMF110S1_ MNRVN	2	BINARY	RECORD VERSION (CICS)
2	2	SMF110S1_ MNPRN	8	EBCDIC	PRODUCT NAME (GENERIC APPLID)
10	A	SMF110S1_ MNSPN	8	EBCDIC	PRODUCT NAME (SPECIFIC APPLID)
18	12	SMF110S1_ MNMFL	2	BINARY	RECORD MAINTENANCE INDICATOR
20	14	--	2	BINARY	RESERVED
22	16	SMF110S1_ MNCL	2	BINARY	CLASS OF DATA 1 = DICTIONARY 3 = PERFORMANCE 4 = EXCEPTION 5 = TRANSACTION RESOURCE
24	18	SMF110S1_ MNDCA	4	BINARY	OFFSET TO CICS FIELD CONNECTORS. Applies to performance class records only.
28	1C	SMF110S1_ MNDCL	2	BINARY	LENGTH OF EACH CICS FIELD CONNECTOR, Applies to performance class records only.
30	1E	SMF110S1_ MNDCN	2	BINARY	NUMBER OF CICS FIELD CONNECTORS, Applies to performance class records only.
32	20	SMF110S1_ MNDRA	4	BINARY	OFFSET TO FIRST CICS DATA RECORD. For dictionary class records, offset to the first dictionary entry. For performance and exception class records, offset to the first performance or exception class record. For transaction resource monitoring records, offset to the first transaction resource monitoring record.
36	24	SMF110S1_ MNDRL	2	BINARY	LENGTH OF EACH CICS DATA RECORD. For dictionary class records length of a single dictionary entry. For performance and exception class records, length of each performance or exception class record. For transaction resource monitoring records, this value is always zero because the transaction resource records in the data section are variable length. The length of each record is in the halfword field MNR_LENGTH at the start of each record.
38	26	SMF110S1_ MNDRN	2	BINARY	NUMBER OF CICS DATA RECORDS. For dictionary class records, number of dictionary entries within the CICS data section. For performance class records, Number of performance class records in the data section. For exception class records, this is always one. For transaction class records, number of transaction resource monitoring records in the data section.
40	28	--	18	BINARY	RESERVED
58	3A	SMF110S1_ MNCRL	2	BINARY	COMPRESSED RECORD LENGTH
60	3C	SMF110S1_ MNTAD	4	BINARY	LOCAL TOD CLOCK ADJUSTMENT VALUE
64	40	SMF110S1_ MNLSO	8	BINARY	LEAP SECOND OFFSET TOD FORMAT
72	48	SMF110S1_ MNDTO	8	BINARY	LOCAL TIME/DATE OFFSET
80	50	--	2	BINARY	RESERVED
82	52	SMF110S1_ MNJBN	8	EBCDIC	JOBNAME
90	5A	SMF110S1_ MNRSD	4	BINARY	JOB DATE
94	5E	SMF110S1_ MSRST	4	BINARY	JOB TIME
98	62	SMF110S1_ MNUIF	8	EBCDIC	USER IDENTIFICATION
106	6A	SMF110S1_ MNPDN	8	EBCDIC	OPERATING SYSTEM PRODUCT LEVEL
Dictionary Data Section (Present when subtype=1 and SMF110S1_MNCL=1) Dictionary data sections describe all the fields in the performance data records that are gathered during this CICS run. They describe all the system-provided data fields (whether you have excluded any or not), plus any user-provided data fields, which CICS takes at initialization time from the MCT entries you have coded. This means that the descriptions of the system-provided data fields never change, though the user data fields can be changed each time CICS is initialized. The contents of the dictionary data sections cannot be changed while CICS is running. Dictionary data sections contain a variable number of 26-byte dictionary entries. Each dictionary entry provides the following information about a single performance record data field: Whenever the monitoring of performance class data is switched on, whether at CICS initialization or while CICS is running, a dictionary data section is written. So, if the monitoring of performance class data is switched on and off three times during a single CICS run, there are three separate, but identical, dictionary data sections for that run. The dictionary data section is passed to SMF, together with any performance data sections, when the first buffer of performance data sections for a performance class data monitoring session is output to SMF. Any offline utility should use the most recent dictionary record encountered when processing CICS monitoring records. (Offset from beginning of record: SMF110S1_MNDRA)
0	0	SMF110S1_ CMODNAME	8	EBCDIC	The identifier of the group to which the field belongs
8	8	SMF110S1_ CMODTYPE	8	EBCDIC	The field type * S = STOPWATCH (CLOCK) * A = ACCUMULATOR (COUNT) * C = BYTE-STRING FIELD * T = TIMESTAMP (STCK FORMAT) * P = PACKED-DECIMAL FIELD
9	9	SMF110S1_ CMODIDNT	3	EBCDIC	The field identifier
12	C	SMF110S1_ CMODLENG	2	BINARY	The length of the field
14	E	SMF110S1_ CMODCONN	2	BINARY	The connector value assigned to the field
16	10	SMF110S1_ CMODOFST	2	BINARY	The offset of the field
18	12	SMF110S1_ CMODHEAD	8	EBCDIC	The informal name of the field.
Performance Data Section - Connectors (Present when subtype=1 and SMF110S1_MNCL=3) Relationship of the Dictionary Record to the Performance Records Following the performance records’ SMF product section, and before the performance records themselves, is a string of field connectors. The purpose of the field connectors is to tell you which fields are going to occur in the performance records produced by this CICS run. Each field connector corresponds to one field in each of the succeeding performance records. The first field connector corresponds to the first field, the second to the second field, and so on. Each field connector also corresponds to a single dictionary entry in the associated dictionary record: the connector value is equal to the value of CMODCONN in the corresponding dictionary entry. In this way, each performance record field is connected to the dictionary entry that describes it. A useful technique for calculating the offset of a particular dictionary entry is to take the connector, subtract one, and multiply the result by the length of a single dictionary entry. Thus, the string of field connectors is the key to the dictionary. And without the dictionary, reporting and analysis programs cannot interpret the performance data. How the String of Field Connectors is Constructed When CICS is initialized, a unique connector value is assigned to every dictionary entry. CICS then examines the MCT entries for this run to see if you have excluded any system-defined performance data. If you have, the offset values for their corresponding dictionary entries are set to X'FFFF'. CICS then constructs a sequence of field connectors that excludes those with offsets of X'FFFF'. In this way, the connectors tell you which system- and user-data fields are going to occur in your performance records for this run. If you have not excluded any system-defined performance data, there is one field connector for every dictionary entry. Please note the following: Field connectors link the fields in a performance record with their dictionary entries. They are unique values that are assigned at initialization time. They may, therefore, change from one run of CICS to the next. (Offset from beginning of record: SMF110S1_MNDCA)
0	0	SMF110S1_ CONN	2	BINARY	Value to connect dictionary entries with fields in performance records.
Performance Data Section - Records (Present when subtype=1 and SMF110S1_MNCL=3) Each performance data section is made up of a string of field connectors, followed by one or more performance data records. All of the performance records produced by a single CICS run have the same format, and each record is, by default, 1848 bytes long. However, the length of the performance records changes if you add user data at user EMPs, or if you exclude any system-defined data from the monitoring process. All of the system- defined data fields in the performance records are described in the CICS Performance Guide. The successive performance records can be regarded as rows in a table, with each column corresponding to one type of field within the records. Each field connector then describes the contents of one column. This view of the data is helpful when designing tabular reports, which are often arranged in this way. Please note the following: Field identifiers allow you to exclude specific system-defined performance data from being collected during a CICS run. They are unique within a group name and record type, and they do not change between CICS runs. There is more information about field identifiers in the CICS Resource Definition Guide. Field offsets in the performance record allow you to build a table for fast selection of required fields in your monitoring data processing programs. (Offset from beginning of record: SMF110S1_MNDRA)
0	0	SMF110S1_ TRAN	4	EBCDIC	Transaction identification.
4	4	SMF110S1_ TERM	4	EBCDIC
8	8	SMF110S1_ USERID	8	EBCDIC	User identification at task attach. This can also be a remote user identifier for a task created as the result of receiving an ATTACH request across an MRO or APPC link with attach-time security enabled.
16	10	SMF110S1_ TTYPE	4	EBCDIC	Type of transaction start (Start Code or Start Type): TO - The transaction was started (attached) by input of the transaction ID from the terminal user. S - Attached by automatic transaction initiation (ATI) without data. The transaction was started (attached) by an application program using the EXEC CICS® START TRANSID('xxxx') ... API command. CICS internal transactions such as CATR, CEJR, CESN, CQRY, CRPM, CRSQ, CSFU, CSGM, CXRE, and CWBG are just some examples of CICS transactions that use this start type. SD - Attached by automatic transaction initiation (ATI) with data. The transaction was started (attached) by an application program using the EXEC CICS START TRANSID('xxxx') FROM(xxxx) ... API command. CICS internal transactions such as CLS1 is an example of a transaction that uses this start type. QD - The transaction was started (attached) because the trigger level of an intrapartition transient data queue was reached. If the transaction is not associated with a terminal facility, the Transaction Facility Name (field: FCTYNAME, owner: DFHTASK, field ID: 163) provides the name of the transient data queue ID. U - the transaction was started (attached) by a CICS internal function generally as a result of some user request. CICS internal transactions such as CATA, CATD, CEJR, CESC, CEX2, CFOR, CFQR, CFQS, CFTL, CGRP, CIEP, CIOF, CIOR, CIRP, CITS, CJTR, CLQ1, CLQ2, CLS2, COTR, COVR, CPLT, CPMI, CRSY, CSFR, CSHQ, CSNC, CSNE, CSOL, CSSY, CSTE, CSZI, CWBA, and CWXN are just some examples of the CICS transactions that use this start type. In addition to CICS internal functions, transaction's that are being run under the control of the CICS Execution Diagnostic Facility transaction, CEDF, are also started (attached) with this start type. TP - Attached from terminal (TCTTE) transaction ID. The preset transaction was started (attached) by input from the terminal user or by the previous transaction using the EXEC CICS RETURN TRANSID('xxxx') IMMEDIATE ... API command. The transaction ID can be preset either from the terminal definition, from using the CRTE routing transaction, or by the previous transaction's application program using the EXEC CICS RETURN TRANSID('xxxx') ... API command with or without the IMMEDIATE option specified. Some examples of CICS transactions which use this start type are: CESN (except when used as the initial good morning transaction), CRTE (when invoked on the routed system), and CSSF when invoked as part of a 'CRTE CANCEL' (the initial CRTE transaction which establishes the routing session uses the start type 'TO'). SZ - Attached by the Front End Programming Interface (FEPI). The transaction was started (attached) as the receive program by the Front End Programming Interface as a result of inbound data. In addition to inbound data arriving, the receive program is also started (attached) if the time limit set by a FEPI START command expires, the session is lost, or anything that causes a FEPI RECEIVE command to complete. See the CICS Front End Programming Interface User's Guide for more information on FEPI started tasks.
20	14	SMF110S1_ START	8	BINARY	The start time (in GMT) of the measurement period. This is either: * The time at which the task was attached, or * The time at which data recording was most recently restarted in support of a user event monitoring point (EMP) DELIVER option or the monitoring options MNCONVerse, MNSYNCpoint, or MNFREQuency Note: The transaction response time (or measurement period) can be calculated by subtracting the START time from the STOP time.
20	14	SMF110S1_ START	8	BINARY	The start date (in GMT) of the measurement period. This is either: * The time at which the task was attached, or * The time at which data recording was most recently restarted in support of a user event monitoring point (EMP) DELIVER option or the
28	1C	SMF110S1_ STOP	8	BINARY	The finish time (in GMT) of the measurement period. This is either: * the time at which the task was detached, or * the time at which data recording was most recently completed for the transaction in support of a user event monitoring point (EMP) DELIVER option or the monitoring options MNCONVerse, MNSYNCpoint, or MNFREQuency. Note: The transaction response time (or measurement period) can be calculated by subtracting the START time from the STOP time.
28	1C	SMF110S1_ STOP	8	BINARY	The finish date (in GMT) of the measurement period. This is either: * the time at which the task was detached, or * the time at which data recording was most recently completed for the transaction in support of a user event monitoring point (EMP) DELIVER option or the monitoring options MNCONVerse, MNSYNCpoint, or MNFREQuency. Note: The transaction response time (or measurement period) can be calculated by subtracting the START time from the STOP time.
36	24	SMF110S1_ TRANNUM	4	PACKED	The transaction identification number. Note: The transaction number field is normally a 4-byte packed decimal number. However, some CICS system tasks are identified by special characters in this field as follows: III - for system initialization tasks TCP - for the terminal control task These special identifiers are placed in bytes 2 through 4. Byte 1 is blank (X'40') before the terminal control TCP identifier, and a null value (X'00') before the others.
40	28	SMF110S1_ TRANPRI	4	BINARY
44	2C	SMF110S1_ TCLSNAME	8	EBCDIC
52	34	SMF110S1_ LUNAME	8	EBCDIC
60	3C	SMF110S1_ PGMNAME	8	EBCDIC	The name of the initial application program invoked at transaction attach. Note these points about remote transactions: * If the CICS® definition of the remote transaction does not specify a program name, this field contains blanks. * If the CICS definition of the remote transaction specifies a program name, this field contains the name of the specified program. (This program is not necessarily the program that is run on the remote system.) For a dynamically routed transaction, if the dynamic transaction routing program routes the transaction locally and specifies an alternative program name, this field contains the name of the alternative program. For a dynamic program link (DPL) mirror transaction, this field contains the initial program name specified in the dynamic program LINK request. DPL mirror transactions can be identified using byte 1 of the transaction flags, TRANFLAG (164), field. For Web service applications, this field contains the target application program name. For a Web alias transaction, this field contains the initial application program name called by the alias transaction. Web alias transactions can be identified using byte 1 of the transaction flags, TRANFLAG (164), field. For an ONC RPC transaction, this field contains the initial application program name called by the alias transaction. ONC RPC transactions can be identified using byte 1 of the transaction flags, TRANFLAG (164), field. For an ECI over TCP/IP transaction, this field contains the name of the application program specified in the External Call Interface (ECI) request from the client application. Byte 4 of the transaction flags field, TRANFLAG (owner: DFHTASK, field ID: 164) can also be used to provide additional detail on the transaction's origin. See DFHTASK fields for more details on the transaction origin type.
68	44	SMF110S1_ NETUOWPX	20	EBCDIC
88	58	SMF110S1_ NETUOWSX	8	EBCDIC
96	60	SMF110S1_ RSYSID	4	EBCDIC	The Transaction Routing Sysid RSYSID field IDentifies the connection name (sysid) of the remote system to which the transaction was routed. If the transaction was not routed this field is null and the initial program name (field: PGMNAME, owner: DFHPROG, field ID: 071) will identify the initial application program name invoked for the transaction. See Table 1 for more details. This field also identifies the connection name (sysid) of the remote system to which the transaction was routed when using the CRTE routing transaction. However, this field is null for those CRTE transactions which establish or cancel the transaction routing session.
100	64	SMF110S1_ PERRECNT	4	BINARY	The total number of performance class records written by the CICS Monitoring Facility (CMF) for this user task.
104	68	SMF110S1_ RMUOWID	8	EBCDIC
112	70	SMF110S1_ SRVCLSNM	8	EBCDIC	The MVS™ Workload Manager (WLM) service class for this transaction. This field is null 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. The transaction flags field, TRANFLAG (owner: DFHTASK, field ID: 164) can be used to determine if this transaction was WLM-classified in another region
120	78	SMF110S1_ RPTCLSNM	8	EBCDIC	The MVS Workload Manager (WLM) report class for this transaction. This field is null 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. The transaction flags field, TRANFLAG (owner: DFHTASK, field ID: 164) can be used to determine if this transaction was WLM-classified in another region.
128	80	SMF110S1_ FCTYNAME	4	EBCDIC
132	84	SMF110S1_ TRANFLAG	8	EBCDIC
140	8C	SMF110S1_ TERMINFO	4	EBCDIC
144	90	SMF110S1_ TERMCNNM	4	EBCDIC
148	94	SMF110S1_ BRDGTRAN	4	EBCDIC
152	98	SMF110S1_ RRMSURID	16	EBCDIC
168	A8	SMF110S1_ PRCSNAME	36	EBCDIC
204	CC	SMF110S1_ PRCSTYPE	8	EBCDIC
212	D4	SMF110S1_ PRCSID	52	EBCDIC
264	108	SMF110S1_ ACTVTYID	52	EBCDIC
316	13C	SMF110S1_ ACTVTYNM	16	EBCDIC
332	14C	SMF110S1_ CLIPADDR	16	EBCDIC	The Client IP address in the form of nnn.nnn.nnn.nnn or Telnet client IP address.
348	15C	SMF110S1_ TRNGRPID	28	EBCDIC
376	178	SMF110S1_ NETID	8	EBCDIC
384	180	SMF110S1_ RLUNAME	8	EBCDIC
392	188	SMF110S1_ TCPSRVCE	8	EBCDIC	The name of the installed TCP/IP service resource definition from which the transaction was initiated.
400	190	SMF110S1_ PORTNUM	4	BINARY	The port number of the installed TCP/IP service resource definition from which the transaction was initiated.
404	194	SMF110S1_ OTSTID	128	EBCDIC
532	214	SMF110S1_ CBSRVRNM	4	BINARY	The CorbaServer for which this request processor instance is handling requests. Request processor transactions can be identified using byte 4 of the transaction flags field, TRANFLAG (owner: DFHTASK, field ID: 164).
536	218	SMF110S1_ TASKFLAG	4	EBCDIC	Task error flags, a string of 32 bits used for signaling unusual conditions occurring during the user task: Bit 0 - Reserved. Bit 1 - The CICS Monitoring Facility (CMF) detected an attempt to start a user clock that was already running, or to stop one that was not running. Bits 2-31 - Reserved
540	21C	SMF110S1_ ABCODEO	4	EBCDIC	If the transaction abends, this field contains the 4 character abend code of the original abend.
544	220	SMF110S1_ ABCODEC	4	EBCDIC	If the transaction abends, this field contains the 4 character abend code of the current abend.
548	224	SMF110S1_ RTYPE	4	EBCDIC	The performance record type (low-order byte-3). This field indicates the reason why a performance record has been output for the user task. It can be one of the following values: C - Record output for a terminal converse D - Record output for a user EMP DELIVER request F - Record output for a long-running transaction S - Record output for a syncpoint T - Record output for a task termination.
552	228	SMF110S1_ TCMSGIN1	4	BINARY
556	22C	SMF110S1_ TCCHRIN1	4	BINARY
560	230	SMF110S1_ TCMSGOU1	4	BINARY
564	234	SMF110S1_ TCCHROU1	4	BINARY
568	238	SMF110S1_ TCMSGIN2	4	BINARY
572	23C	SMF110S1_ TCCHRIN2	4	BINARY
576	240	SMF110S1_ TCMSGOU2	4	BINARY
580	244	SMF110S1_ TCCHROU2	4	BINARY
584	248	SMF110S1_ TCM62IN2	4	BINARY
588	24C	SMF110S1_ TCC62IN2	4	BINARY
592	250	SMF110S1_ TCM62OU2	4	BINARY
596	254	SMF110S1_ TCC62OU2	4	BINARY
600	258	SMF110S1_ TCALLOCT	4	BINARY
604	25C	SMF110S1_ SCUGETCT1	4	BINARY	The number of user-storage GETMAIN requests issued by the user task for storage below the 16MB line, in the UDSA.
608	260	SMF110S1_ SCUGETCT2	4	BINARY	The number of user-storage GETMAIN requests issued by the user task for storage above the 16MB line, in the EUDSA.
612	264	SMF110S1_ SCCGETCT1	4	BINARY	The number of user-storage GETMAIN requests issued by the user task for storage below the 16MB line, in the CDSA.
616	268	SMF110S1_ SCCGETCT2	4	BINARY	The number of user-storage GETMAIN requests issued by the user task for storage above the 16MB line, in the EUDSA.
620	26C	SMF110S1_ SCUSRHWM1	4	BINARY	Maximum amount (high-water mark) of user-storage allocated to the user task below the 16MB line, in the user dynamic storage area (UDSA).
624	270	SMF110S1_ SCUSRHWM2	4	BINARY	Maximum amount (high-water mark) of user-storage allocated to the user task above the 16MB line, in the user dynamic storage area (EUDSA).
628	274	SMF110S1_ SC24CHWM1	4	BINARY	Maximum amount (high-water mark) of user-storage allocated to the user task below the 16MB line, in the CICS® dynamic storage area (CDSA).
632	278	SMF110S1_ SC31CHWM2	4	BINARY	Maximum amount (high-water mark) of user-storage allocated to the user task above the 16MB line, in the CICS dynamic storage area (CDSA).
636	27C	SMF110S1_ SCUSRSTG1	8	BINARY	The storage occupancy of the user task below the 16MB line, in the UDSA. This is a measure of the area under the curve of the storage in use against elapsed time.
644	284	SMF110S1_ SCUSRSTG2	8	BINARY	The storage occupancy of the user task above the 16MB line, in the EUDSA. This is a measure of the area under the curve of the storage in use against elapsed time.
652	28C	SMF110S1_ SC24COCC1	8	BINARY	The storage occupancy of the user task below the 16MB line, in the CDSA. This is a measure of the area under the curve of the storage in use against elapsed time.
660	294	SMF110S1_ SC31COCC2	8	BINARY	The storage occupancy of the user task above the 16MB line, in the ECDSA. This is a measure of the area under the curve of the storage in use against elapsed time.
668	29C	SMF110S1_ SC24SGCT	4	BINARY	The number of storage GETMAIN requests issued by the user task for shared storage below the 16MB line, in the CDSA or SDSA.
672	2A0	SMF110S1_ SC24GSHR	4	BINARY	The number of bytes of shared storage GETMAINed by the user task below the 16MB line, in the CDSA or SDSA.
676	2A4	SMF110S1_ SC24FSHR	4	BINARY	The number of bytes of shared storage FREEMAINed by the user task below the 16MB line, in the CDSA or SDSA.
680	2A8	SMF110S1_ SC31SGCT	4	BINARY	The number of storage GETMAIN requests issued by the user task for shared storage above the 16MB line, in the ECDSA or ESDSA.
684	2AC	SMF110S1_ SC31GSHR	4	BINARY	The number of bytes of shared storage GETMAINed by the user task above the 16MB line, in the ECDSA or ESDSA.
688	2B0	SMF110S1_ SC31FSHR	4	BINARY	The number of bytes of shared storage FREEMAINed by the user task above the 16MB line, in the CDSA or SDSA.
692	2B4	SMF110S1_ PCSTGHWM	4	BINARY	The maximum amount (high-water mark) of program storage in use by the user task both above and below the 16MB line.
696	2B8	SMF110S1_ PC31AHWM	4	BINARY	The maximum amount (high-water mark) of program storage in use by the user task above the 16MB line. This field is a subset of PCSTGHWM (field ID: 087) that resides above the 16MB line.
700	2BC	SMF110S1_ PC24BHWM	4	BINARY	The maximum amount (high-water mark) of program storage in use by the user task below the 16MB line. This field is a subset of PCSTGHWM (field ID: 087) that resides below the 16MB line.
704	2C0	SMF110S1_ PC31CHWM	4	BINARY	The maximum amount (high-water mark) of program storage in use by the user task above the 16MB line, in the extended CICS® dynamic storage area (ECDSA). This field is a subset of PC31AHWM (field ID: 139) that resides in the ECDSA.
708	2C4	SMF110S1_ PC24CHWM	4	BINARY	The maximum amount (high-water mark) of program storage in use by the user task below the 16MB line, in the CICS dynamic storage area (CDSA). This field is a subset of PC24BHWM (field ID: 108) that resides in the CDSA.
712	2C8	SMF110S1_ PC31RHWM	4	BINARY	The maximum amount (high-water mark) of program storage in use by the user task above the 16MB line, in the extended read-only dynamic storage area (ERDSA). This field is a subset of PC31AHWM (field ID: 139) that resides above the 16MB line.
716	2CC	SMF110S1_ PC24RHWM	4	BINARY	The maximum amount (high-water mark) of program storage in use by the user task below the 16MB line, in the read-only dynamic storage area (RDSA). This field is a subset of PC24BHWM (field ID: 108) that resides in the RDSA.
720	2D0	SMF110S1_ PC31SHWM	4	BINARY	The maximum amount (high-water mark) of program storage in use by the user task above the 16MB line, in the extended shared dynamic storage area (ESDSA). This field is a subset of PC31AHWM (field ID: 139) that resides in the ESDSA.
724	2D4	SMF110S1_ PC24SHWM	4	BINARY	The maximum amount (high-water mark) of program storage in use by the user task below the 16MB line, in the shared dynamic storage area (SDSA). This field is a subset of PC24BHWM (field ID: 108) that resides in the SDSA.
728	2D8	SMF110S1_ FCGETCT	4	BINARY	The number of file control GET requests issued by the user task.
732	2DC	SMF110S1_ FCPUTCT	4	BINARY	The number of file control PUT requests issued by the user task.
736	2E0	SMF110S1_ FCBRWCT	4	BINARY	The number of file control BROWSE requests issued by the user task.
740	2E4	SMF110S1_ FCADDCT	4	BINARY	The number of file control ADD requests issued by the user task.
744	2E8	SMF110S1_ FCDELCT	4	BINARY	The number of file control DELETE requests issued by the user task.
748	2EC	SMF110S1_ FCTOTCT	4	BINARY	The total number of file control requests issued by the user task. This number excludes any request for OPEN, CLOSE, ENABLE or DISABLE of a file. Note: The number of STARTBR, ENDBR, RESETBR and UNLOCK file control requests can be calculated by subtracting the file request counts FCGETCT, FCPUTCT, FCBRWCT, FCADDCT and FCDELCT from the total file control request count, FCTOTCT.
752	2F0	SMF110S1_ FCAMCT	4	BINARY	The number of times the user task invoked file access-method interfaces. This number excludes requests for file OPEN and CLOSE.
756	2F4	SMF110S1_ TDGETCT	4	BINARY	The number of transient data GET requests issued by the user task. 042 (Type-A, TDPUTCT, 4 bytes)
760	2F8	SMF110S1_ TDPUTCT	4	BINARY	The number of transient data PUT requests issued by the user task.
764	2FC	SMF110S1_ TDPURCT	4	BINARY	The number of transient data PURGE requests issued by the user task
768	300	SMF110S1_ TDTOTCT	4	BINARY	The total number of transient data requests issued by the user task.
772	304	SMF110S1_ TSGETCT	4	BINARY	The number of temporary storage READQ requests issued by the user task.
776	308	SMF110S1_ TSPUTACT	4	BINARY	The number of temporary storage WRITEQ AUX requests issued by the user task.
780	30C	SMF110S1_ TSPUTMCT	4	BINARY	The number of temporary storage WRITEQ MAIN requests issued by the user task.
784	310	SMF110S1_ TSTOTCT	4	BINARY	The total number of temporary storage DELETEQ, READQ, WRITEQ AUX and WRITEQ MAIN requests issued by the user task. Note: The number of temporary storage DELETEQ requests can be calculated by subtracting the temporary storage request counts TSGETCT, TSPUTACT, and TSPUTMCT from the total temporary storage request count, TSTOTCT.
788	314	SMF110S1_ BMSMAPCT	4	BINARY	The number of BMS RECEIVE MAP requests issued by the user task. This field corresponds to the number of RECEIVE MAP requests that did not incur a terminal I/O and the number of RECEIVE MAP FROM requests.
792	318	SMF110S1_ BMSINCT	4	BINARY	The number of BMS RECEIVE MAP requests issued by the user task that did incur a terminal I/O.
796	31C	SMF110S1_ BMSOUTCT	4	BINARY	The number of BMS SEND MAP requests issued by the user task.
800	320	SMF110S1_ BMSTOTCT	4	BINARY	The total number of BMS requests issued by the user task. This field is the sum of the BMS RECEIVE MAP, RECEIVE MAP FROM and SEND MAP requests as well as the number of BMS SEND TEXT and SEND CONTROL requests issued by the user task.
804	324	SMF110S1_ PCLINKCT	4	BINARY	The number of program LINK requests issued by the user task.
808	328	SMF110S1_ PCXCTLCT	4	BINARY	The number of program XCTL requests issued by the user task.
812	32C	SMF110S1_ PCLOADCT	4	BINARY	The number of program LOAD requests issued by the user task.
816	330	SMF110S1_ PCLURMCT	4	BINARY	The number of program LINK URM (user-replaceable module) requests issued by the user task. A user-replaceable module is a CICS-supplied program that is always invoked at a particular point in CICS processing as if it were part of the CICS code. You can modify the supplied program by including your own logic, or you can replace it with a version that you write yourself. The CICS-supplied user-replaceable modules are: * bridge exit program - DFH0CBRE, DFH0CBAE, DFHWBLT, or user specified * CICS JVM interface program - DFHJVMAT * distributed dynamic routing program - DFHDSRP (or user specified) * document template exit program - user specified on the DOCTEMPLATE resource definition * dynamic routing program - DFHDYP (or user specified) * Internet Inter-ORB Protocol (IIOP) inbound request security exit program - DFHXOPUS * Java hot-pooling pre-call program - DFHJHPAT * node error program - DFHNEP * program autoinstall program - DFHPGAxX (or user specified) * program error program - DFHPEP * terminal autoinstall programs - DFHZATDX/DFHZATDY * terminal error program - DFHTEP * transaction restart program - DFHRTY * CICS-DBCTL interface status program - DFHDBUEX * CICS-DB2 dynamic plan exit program - DSNCUEXT * Enterprise JavaBeans (EJB) Distinguished Name program - DFHEJDNx * Enterprise JavaBeans (EJB) event program - DFHEJEP
820	334	SMF110S1_ PCDPLCT	4	BINARY	The number of distributed program link (DPL) requests issued by the user task
824	338	SMF110S1_ PCDLCSDL	4	BINARY	The total length, in bytes, of the data in the containers of all the distributed program link (DPL) requests, with the CHANNEL option, issued by the user task. This total includes the length of any headers to the data.
828	33C	SMF110S1_ PCDLCRDL	4	BINARY	The total length, in bytes, of the data in the containers of all the distributed program link (DPL) RETURN requests, with the CHANNEL option, issued by the user task. This total includes the length of any headers to the data.
832	340	SMF110S1_ PCLNKCCT	4	BINARY	Number of local program LINK requests, with the CHANNEL option, issued by the user task. Note: This field is a subset of the program LINK requests field, PCLINKCT (055).
836	344	SMF110S1_ PCXCLCCT	4	BINARY	Number of program XCTL requests, with the CHANNEL option, issued by the user task. Note: This field is a subset of the program XCTL requests field, PCXCTLCT (056).
840	348	SMF110S1_ PCDPLCCT	4	BINARY	Number of program distributed program link (DPL) requests, with the CHANNEL option, issued by the user task. Note: This field is a subset of the distributed program link requests field, PCDPLCT (073).
844	34C	SMF110S1_ PCRTNCCT	4	BINARY	Number of remote pseudoconversational RETURN requests, with the CHANNEL option, issued by the user task.
848	350	SMF110S1_ PCRTNCDL	4	BINARY	The total length, in bytes, of the data in the containers of all the remote pseudoconversational RETURN CHANNEL commands issued by the user task. This total includes the length of any headers to the data.
852	354	SMF110S1_ JNLWRTCT	4	BINARY	The number of journal write requests issued by the user task.
856	358	SMF110S1_ LOGWRTCT	4	BINARY	The number of CICS logstream write requests issued by the user task.
860	35C	SMF110S1_ ICPUINCT	4	BINARY	The number of Interval Control START requests issued by the user task.
864	360	SMF110S1_ ICTOTCT	4	BINARY
868	364	SMF110S1_ ICSTACCT	4	BINARY
872	368	SMF110S1_ ICSTACDL	4	BINARY
876	36C	SMF110S1_ ICSTRCCT	4	BINARY
880	370	SMF110S1_ ICSTRCDL	4	BINARY
884	374	SMF110S1_ SPSYNCCT	4	BINARY	The total number of syncpoint requests issued by the user task. This also includes: * The SYNCPOINT implicitly issued as part of the task-detach processing * The SYNCPOINT issued at PSB termination for any DBCTL activity
888	378	SMF110S1_ CFCAPICT	4	BINARY	The total number of CICS® OO foundation class requests and Java API for CICS (JCICS) class requests issued by the user task. CICS does not distinguish between the OO foundation class and JCICS class requests.
892	37C	SMF110S1_ SZALLOCT	4	BINARY	The number of FEPI conversations allocated by the user task. This number is incremented for each FEPI ALLOCATE POOL or FEPI CONVERSE POOL.
896	380	SMF110S1_ SZRCVCT	4	BINARY	The number of FEPI RECEIVE requests issued by the user task. This number is also incremented for each FEPI CONVERSE request.
900	384	SMF110S1_ SZSENDCT	4	BINARY	The number of FEPI SEND requests issued by the user task. This number is also incremented for each FEPI CONVERSE request.
904	388	SMF110S1_ SZSTRTCT	4	BINARY	The number of FEPI START requests issued by the user task.
908	38C	SMF110S1_ SZCHROUT	4	BINARY	The number of characters sent through FEPI by the user task.
912	390	SMF110S1_ SZCHRIN	4	BINARY	The number of characters received through FEPI by the user task.
916	394	SMF110S1_ SZALLCTO	4	BINARY	The number of times the user task timed out while waiting to allocate a conversation.
920	398	SMF110S1_ SZRCVTO	4	BINARY	The number of times the user task timed out while waiting to receive data.
924	39C	SMF110S1_ SZTOTCT	4	BINARY	The total number of FEPI API and SPI requests issued by the user task.
928	3A0	SMF110S1_ BARSYNCT	4	BINARY
932	3A4	SMF110S1_ BARASYCT	4	BINARY
936	3A8	SMF110S1_ BALKPACT	4	BINARY
940	3AC	SMF110S1_ BADPROCT	4	BINARY
944	3B0	SMF110S1_ BADACTCT	4	BINARY
948	3B4	SMF110S1_ BARSPACT	4	BINARY
952	3B8	SMF110S1_ BASUPACT	4	BINARY
956	3BC	SMF110S1_ BARMPACT	4	BINARY
960	3C0	SMF110S1_ BADCPACT	4	BINARY
964	3C4	SMF110S1_ BAACQPCT	4	BINARY
968	3C8	SMF110S1_ BATOTPCT	4	BINARY
972	3CC	SMF110S1_ BAPRDCCT	4	BINARY
976	3D0	SMF110S1_ BAACDCCT	4	BINARY
980	3D4	SMF110S1_ BATOTCCT	4	BINARY
984	3D8	SMF110S1_ BARATECT	4	BINARY
988	3DC	SMF110S1_ BADFIECT	4	BINARY
992	3E0	SMF110S1_ BATIAECT	4	BINARY
996	3E4	SMF110S1_ BATOTECT	4	BINARY
1000	3E8	SMF110S1_ WBRCVCT	4	BINARY
1004	3EC	SMF110S1_ WBCHRIN	4	BINARY
1008	3F0	SMF110S1_ WBSENDCT	4	BINARY
1012	3F4	SMF110S1_ WBCHROUT	4	BINARY
1016	3F8	SMF110S1_ WBTOTCT	4	BINARY
1020	3FC	SMF110S1_ WBREPRCT	4	BINARY
1024	400	SMF110S1_ WBREPWCT	4	BINARY
1028	404	SMF110S1_ WBEXTRCT	4	BINARY
1032	408	SMF110S1_ WBBRWCT	4	BINARY
1036	40C	SMF110S1_ WBREADCT	4	BINARY
1040	410	SMF110S1_ WBWRITCT	4	BINARY
1044	414	SMF110S1_ DHCRECT	4	BINARY
1048	418	SMF110S1_ DHINSCT	4	BINARY
1052	41C	SMF110S1_ DHSETCT	4	BINARY
1056	420	SMF110S1_ DHRETCT	4	BINARY
1060	424	SMF110S1_ DHTOTCT	4	BINARY
1064	428	SMF110S1_ DHTOTDCL	4	BINARY
1068	42C	SMF110S1_ SOBYENCT	4	BINARY	The number of bytes encrypted by the secure sockets layer (SSL) for the user task.
1072	430	SMF110S1_ SOBYDECT	4	BINARY	The number of bytes decrypted by the secure sockets layer (SSL) for the user task.
1076	434	SMF110S1_ SOEXTRCT	4	BINARY	The number of EXTRACT TCPIP and EXTRACT CERTIFICATE requests issued by the user task.
1080	438	SMF110S1_ SOCNPSCT	4	BINARY	The number of non-persistent outbound socket create requests issued by the user task.
1084	43C	SMF110S1_ SOCPSCT	4	BINARY	The number of persistent outbound socket create requests issued by the user task.
1088	440	SMF110S1_ SONPSHWM	4	BINARY	The number of persistent outbound socket create requests issued by the user task.
1092	444	SMF110S1_ SOPSHWM	4	BINARY	The peak number (high-water mark) of persistent outbound sockets owned by the user task.
1096	448	SMF110S1_ SORCVCT	4	BINARY	The number of outbound socket RECEIVE requests issued by the user task.
1100	44C	SMF110S1_ SOCHRIN	4	BINARY	The number of characters received by outbound socket RECEIVE requests issued by the user task.
1104	450	SMF110S1_ SOSENDCT	4	BINARY	The number of outbound socket SEND requests issued by the user task.
1108	454	SMF110S1_ SOCHROUT	4	BINARY	The number of characters sent by outbound socket SEND requests issued by the user task.
1112	458	SMF110S1_ SOTOTCT	4	BINARY	The total number of inbound and outbound socket requests issued by the user task.
1116	45C	SMF110S1_ SOMSGIN1	4	BINARY	The number of inbound socket RECEIVE requests issued by the user task.
1120	460	SMF110S1_ SOCHRIN1	4	BINARY	The number of characters received by inbound socket RECEIVE requests issued by the user task.
1124	464	SMF110S1_ SOMSGOU1	4	BINARY	The number of inbound socket SEND requests issued by the user task.
1128	468	SMF110S1_ SOCHROU1	4	BINARY	The number of characters sent by inbound socket SEND requests issued by the user task.
1132	46C	SMF110S1_ IMSREQCT	4	BINARY	The total number of IMS (DBCTL) requests issued by the user task.
1136	470	SMF110S1_ DB2REQCT	4	BINARY	The total number of DB2 EXEC SQL and Instrumentation Facility Interface (IFI) requests issued by the user task.
1140	474	SMF110S1_ TCBATTCT	4	BINARY
1144	478	SMF110S1_ DSTCBHWM	4	BINARY
1148	47C	SMF110S1_ EJBSACCT	4	BINARY	The number of bean activations that have occurred in this request processor.
1152	480	SMF110S1_ EJBSPACT	4	BINARY	The number of bean passivations that have occurred in this request processor.
1156	484	SMF110S1_ EJBCRECT	4	BINARY	The number of bean creation calls that have occurred in this request processor.
1160	488	SMF110S1_ EJBREMCT	4	BINARY	The number of bean removal calls that have occurred in this request processor.
1164	48C	SMF110S1_ EJBMTHCT	4	BINARY	The number of bean method calls run in this request processor.
1168	490	SMF110S1_ EJBTOTCT	4	BINARY	The total for this request processor of activation, passivation, creation, removal and method calls (fields 312–316).
1172	494	SMF110S1_ WBREDOCT	4	BINARY
1176	498	SMF110S1_ WBWRTOCT	4	BINARY
1180	49C	SMF110S1_ WBRCVIN1	4	BINARY
1184	4A0	SMF110S1_ WBCHRIN1	4	BINARY
1188	4A4	SMF110S1_ WBSNDOU1	4	BINARY
1192	4A8	SMF110S1_ WBCHROU1	4	BINARY
1196	4AC	SMF110S1_ WBPARSCT	4	BINARY
1200	4B0	SMF110S1_ WBBRWOCT	4	BINARY
1204	4B4	SMF110S1_ WBIWBSCT	4	BINARY
1208	4B8	SMF110S1_ WBREPRDL	4	BINARY
1212	4BC	SMF110S1_ WBREPWDL	4	BINARY
1216	4C0	SMF110S1_ PGTOTCCT	4	BINARY
1220	4C4	SMF110S1_ PGBRWCCT	4	BINARY
1224	4C8	SMF110S1_ PGGETCCT	4	BINARY
1228	4CC	SMF110S1_ PGPUTCCT	4	BINARY
1232	4D0	SMF110S1_ PGMOVCCT	4	BINARY
1236	4D4	SMF110S1_ PGGETCDL	4	BINARY
1240	4D8	SMF110S1_ PGPUTCDL	4	BINARY
1244	4DC	SMF110S1_ PGCRECCT	4	BINARY
1248	4E0	SMF110S1_ USRDISPT	8	BINARY	Total elapsed time during which the user task was dispatched on each CICS TCB under which the task ran. The TCB modes managed by the CICS dispatcher are: QR, RO, CO, FO, SZ, RP, SL, SP, SO, EP, J8, J9, L8, L9, S8, TP, T8, X8, X9, JM, and D2. Be aware that, for each CICS release, new TCB modes might be added to this list, or obsolete TCB modes might be removed.
1256	4E8	SMF110S1_ USRCPUT	8	BINARY	Processor time for which the user task was dispatched on each CICS TCB under which the task ran. The TCB modes managed by the CICS dispatcher are: QR, RO, CO, FO, SZ, RP, SL, SP, SO, EP, J8, J9, L8, L9, S8, TP, T8, X8, X9, JM, and D2. Be aware that, for each CICS release, new TCB modes might be added to this list, or obsolete TCB modes might be removed.
1264	4F0	SMF110S1_ SUSPTIME	8	BINARY	The total elapsed suspend (wait) time for which the user task was suspended by the CICS dispatcher domain. This includes: * The task suspend (wait) time. * The elapsed time that the transaction waited for its first dispatch. This also includes any delay incurred because of the limits set for this transaction's transaction class (if any) or by the system parameter MXT being reached by this transaction. * The elapsed time waiting for redispatch after a suspended task has been resumed.
1272	4F8	SMF110S1_ DISPWTT	8	BINARY
1280	500	SMF110S1_ QRDISPT	8	BINARY
1288	508	SMF110S1_ QRCPUT	8	BINARY
1296	510	SMF110S1_ MSDISPT	8	BINARY
1304	518	SMF110S1_ MSCPUT	8	BINARY
1312	520	SMF110S1_ RODISPT	8	BINARY
1320	528	SMF110S1_ ROCPUT	8	BINARY
1328	530	SMF110S1_ KY8DISPT	8	BINARY
1336	538	SMF110S1_ KY8CPUT	8	BINARY
1344	540	SMF110S1_ KY9DISPT	8	BINARY
1352	548	SMF110S1_ KY9CPUT	8	BINARY
1360	550	SMF110S1_ L8CPUT	8	BINARY
1368	558	SMF110S1_ L9CPUT	8	BINARY
1376	560	SMF110S1_ J8CPUT	8	BINARY
1384	568	SMF110S1_ S8CPUT	8	BINARY
1392	570	SMF110S1_ J9CPUT	8	BINARY
1400	578	SMF110S1_ X8CPUT	8	BINARY
1408	580	SMF110S1_ X9CPUT	8	BINARY
1416	588	SMF110S1_ QRMODDLY	8	BINARY
1424	590	SMF110S1_ MAXOTDLY	8	BINARY
1432	598	SMF110S1_ MAXJTDLY	8	BINARY
1440	5A0	SMF110S1_ MAXXTDLY	8	BINARY
1448	5A8	SMF110S1_ MAXSTDLY	8	BINARY
1456	5B0	SMF110S1_ DSTCBMWT	8	BINARY
1464	5B8	SMF110S1_ DSCHMDLY	8	BINARY
1472	5C0	SMF110S1_ EXWTTIME	8	BINARY	Accumulated data for exception conditions. The timer component of the clock contains the total elapsed time for which the user waited on exception conditions. The period count equals the number of exception conditions that have occurred for this task. Note: This field is updated when any of the exception conditions are encountered by the user task even when the exception class is inactive.
1480	5C8	SMF110S1_ TCIOWTT	8	BINARY
1488	5D0	SMF110S1_ FCIOWTT	8	BINARY
1496	5D8	SMF110S1_ JCIOWTT	8	BINARY	The elapsed time in which the user task waited for journal (logstream) I/O. Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014).
1504	5E0	SMF110S1_ TSIOWTT	8	BINARY	The elapsed time in which the user task waited for VSAM I/O to the auxiliary temporary storage data set, DFHTEMP. Note: This field is a component of the task suspend time.
1512	5E8	SMF110S1_ IRIOWTT	8	BINARY
1520	5F0	SMF110S1_ TDIOWTT	8	BINARY	The elapsed time in which the user task waited for VSAM I/O to the intrapartition transient data set, DFHINTRA. Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014).
1528	5F8	SMF110S1_ PCLOADTM	8	BINARY	The total elapsed time in which the user task waited for program fetches from the DFHRPL program library. Only fetches for programs with installed program definitions or autoinstalled as a result of application program requests are included in this figure. Installed programs residing in the LPA are not included because they do not incur a physical fetch from a program library.
1536	600	SMF110S1_ DSPDELAY	8	BINARY
1544	608	SMF110S1_ TCLDELAY	8	BINARY
1552	610	SMF110S1_ MXTDELAY	8	BINARY
1560	618	SMF110S1_ ENQDELAY	8	BINARY
1568	620	SMF110S1_ GNQDELAY	8	BINARY
1576	628	SMF110S1_ LU61WTT	8	BINARY
1584	630	SMF110S1_ LU62WTT	8	BINARY
1592	638	SMF110S1_ SZWAIT	8	BINARY	The elapsed time in which the user task waited for FEPI services. Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014).
1600	640	SMF110S1_ RMITIME	8	BINARY
1608	648	SMF110S1_ RMISUSP	8	BINARY
1616	650	SMF110S1_ SYNCTIME	8	BINARY	The elapsed time in which the user task was dispatched or suspended processing syncpoint requests.
1624	658	SMF110S1_ RLSWAIT	8	BINARY	The elapsed time in which the user task waited for RLS file I/O. Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014).
1632	660	SMF110S1_ RLSCPUT	8	BINARY	The RLS File Request CPU (SRB) time field (RLSCPUT) is the SRB CPU time this transaction spent processing RLS file requests. This field should be added to the transaction CPU time field (USRCPUT) when considering the measurement of the total CPU time consumed by a transaction. However, this field cannot be considered a subset of any other single CMF field (including RLSWAIT). This is because the RLS file requests run asynchronously under an MVS™ SRB which can be running in parallel with the requesting transaction. It is also possible for the SRB to complete its processing before the requesting transaction waits for the RLS file request to complete. Note: This clock field could contain a CPU time of zero with a count of greater than zero. This is because the CMF timing granularity is measured in 16 microsecond units and the RLS file requests might complete in less than that time unit.
1640	668	SMF110S1_ LMDELAY	8	BINARY
1648	670	SMF110S1_ WTEXWAIT	8	BINARY
1656	678	SMF110S1_ WTCEWAIT	8	BINARY
1664	680	SMF110S1_ ICDELAY	8	BINARY
1672	688	SMF110S1_ GVUPWAIT	8	BINARY
1680	690	SMF110S1_ TSSHWAIT	8	BINARY	The elapsed time in which the user task waited for an asynchronous shared temporary storage request to a temporary storage data server to complete.
1688	698	SMF110S1_ CFDTWAIT	8	BINARY	The elapsed time in which the user task waited for a data table access request to the coupling facility data table server to complete. Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014).
1696	6A0	SMF110S1_ SRVSYWTT	8	BINARY	The elapsed time in which the user task waited for completion of syncpoint or resynchronization processing using the coupling facility data table server to complete. Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014).
1704	6A8	SMF110S1_ RRMSWAIT	8	BINARY
1712	6B0	SMF110S1_ RUNTRWTT	8	BINARY
1720	6B8	SMF110S1_ SYNCDLY	8	BINARY	The elapsed time in which the user task waited for a syncpoint request to be issued by it's parent transaction. The user task was executing as a result of the parent transaction issuing a CICS® Business Transaction Services (BTS) Run ACQPROCESS or Run Activity requests to run a process or activity synchronously. Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014).
1728	6C0	SMF110S1_ SOIOWTT	8	BINARY	The elapsed time in which the user task waited for inbound socket I/O. The outbound socket I/O wait time is measured in field ID: 299. Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014).
1736	6C8	SMF110S1_ IMSWAIT	8	BINARY	The total elapsed time in which the user task waited for IMS (DBCTL) to service the IMS requests issued by the user task. Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014 and is also a component of the RMI suspend time field, RMISUSP (owner: DFHTASK, field ID: 171).
1744	6D0	SMF110S1_ DB2RDYQW	8	BINARY	The elapsed time in which the user task waited for a DB2 thread to become available. For more general information on DB2 accounting and monitoring, see the CICS DB2 Guide. For more information, see RMI elapsed and suspend time and Transaction timing fields. Note: This field is a component of the task suspend time field, SUSPTIME (group name: DFHTASK, field ID: 014 and is also a component of the RMI suspend time field, RMISUSP (owner: DFHTASK, field ID: 171)
1752	6D8	SMF110S1_ DB2CONWT	8	BINARY	The value of this field depends on the version of DB2 to which CICS® is connected: * When CICS is connected to DB2 Version 5 or earlier, and is therefore not exploiting the CICS open transaction environment (OTE), this field is the elapsed time in which the user task waited for a CICS subtask (TCB) to become available. * When CICS is connected to DB2 Version 6 or later, and so is using the CICS open transaction environment (OTE), this field is the elapsed time in which the user task waited for a DB2 connection to become available for use with the user tasks open TCB.
1760	6E0	SMF110S1_ DB2WAIT	8	BINARY	The value of this field depends on the version of DB2 to which CICS is connected: * When CICS is connected to DB2 Version 5 or earlier, and is therefore not exploiting the CICS open transaction environment (OTE), this field is the elapsed time in which the user task waited for DB2 to service the DB2 EXEC SQL and Instrumentation Facility Interface (IFI) requests issued by the user task. * When CICS is connected to DB2 Version 6 or later, and so is using the CICS open transaction environment (OTE), this field does not apply and is zero. This is because the CICS-DB2 attachment facility uses open TCBs as the thread TCBs rather than using specially created subtask TCBs and as a result any waits in DB2 that occur on a CICS L8 mode TCB will not be visible to the CICS dispatcher domain. Note: This field is a component of the task suspend time field, SUSPTIME (group name: DFHTASK, field ID: 014 and is also a component of the RMI suspend time field, RMISUSP (owner: DFHTASK, field ID: 171).
1768	6E8	SMF110S1_ JVMTIME	8	BINARY
1776	6F0	SMF110S1_ JVMSUSP	8	BINARY
1784	6F8	SMF110S1_ SOOIOWTT	8	BINARY	The elapsed time in which the user task waited for outbound socket I/O. The inbound socket I/O wait time is measured in field ID: 241. Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014)
1792	700	SMF110S1_ RQRWAIT	8	BINARY
1800	708	SMF110S1_ RQPWAIT	8	BINARY
1808	710	SMF110S1_ OTSINDWT	8	BINARY	The elapsed time in which the user task was dispatched or suspended indoubt whilst processing a syncpoint for an Object Transaction Service (OTS) Syncpoint request.
1816	718	SMF110S1_ JVMITIME	8	BINARY
1824	720	SMF110S1_ JVMRTIME	8	BINARY
1832	728	SMF110S1_ PTPWAIT	8	BINARY
1840	730	SMF110S1_ DSMMSCWT	8	BINARY
Exception Data Section (Present when subtype=1 and SMF110S1_MNCL=4) The exception data section contains a single exception record representing one exception condition. For further information about exception class data, see the CICS Performance Guide, which lists all the system-defined data that can be produced by CICS monitoring.(Offset from beginning of record: SMF110S1_MNDRA)
0	0	SMF110S1_ EXCMNTRN	4	EBCDIC	TRANSACTION IDENTIFICATION
4	4	SMF110S1_ EXCMNTER	4	BINARY	TERMINAL IDENTIFICATION
8	8	SMF110S1_ EXCMNUSR	8	EBCDIC	USER IDENTIFICATION
16	10	SMF110S1_ EXCMNTST	4	EBCDIC	TRANSACTION START TYPE
20	14	SMF110S1_ EXCMNSTA	8	BINARY	EXCEPTION START TIME
28	1C	SMF110S1_ EXCMNSTO	8	BINARY	EXCEPTION STOP TIME
36	24	SMF110S1_ EXCMNTNO	4	PACKED	TRANSACTION NUMBER
40	28	SMF110S1_ EXCMNTPR	4	BINARY	TRANSACTION PRIORITY
44	2C	--	4	EBCDIC	RESERVED
48	30	SMF110S1_ EXCMNLUN	8	EBCDIC	LUNAME
56	38	--	4	EBCDIC	RESERVED
60	3C	SMF110S1_ EXCMNEXN	4	BINARY	EXCEPTION NUMBER
64	40	SMF110S1_ EXCMNRTY	8	EBCDIC	EXCEPTION RESOURCE TYPE
72	48	SMF110S1_ EXCMNRID	8	EBCDIC	EXCEPTION RESOURCE ID
80	50	SMF110S1_ EXCMNTYP	2	BINARY	EXCEPTION TYPE * X'0001' = WAIT * X'0002' = BUFFER WAIT * X'0003' = STRING WAIT
82	52	--	2	EBCDIC	RESERVED
84	54	SMF110S1_ EXCMNTCN	8	EBCDIC	TRANSACTION CLASS NAME
92	5C	SMF110S1_ EXCMNSRV	8	EBCDIC	SERVICE CLASS NAME
100	64	SMF110S1_ EXCMNRPT	8	EBCDIC	REPORT CLASS NAME
108	6C	SMF110S1_ EXCMNNPX	20	EBCDIC	NETWORK UNIT-OF-WORK PREFIX
128	80	SMF110S1_ EXCMNNSX	8	BINARY	NETWORK UNIT-OF-WORK SUFFIX
136	88	SMF110S1_ EXCMNTRF	8	BINARY	TRANSACTION FLAGS
144	90	SMF110S1_ EXCMNFCN	4	EBCDIC	TRANSACTION FACILITY NAME
148	94	SMF110S1_ EXCMNCPN	8	EBCDIC	CURRENT PROGRAM NAME
156	9C	SMF110S1_ EXCMNBTR	4	EBCDIC	BRIDGE TRANSACTION ID
160	A0	SMF110S1_ EXCMNURI	16	EBCDIC	RRMS/MVS UNIT OF RECOVERY ID
176	B0	SMF110S1_ EXCMNRIL	4	BINARY	EXCEPTION RESOURCE ID LENGTH
180	B4	SMF110S1_ EXCMNRIX	256	EBCDIC	EXCEPTION RESOURCE ID (EXTENDED)
436	1B4	SMF110S1_ EXCMNNID	8	EBCDIC	NETWORK ID
444	1BC	SMF110S1_ EXCMNRLU	8	EBCDIC	REAL LUNAME
Transaction Resource Data Section TS 5.3 (Present when subtype=1 and SMF110S1_MNCL=5) Each transaction resource data section is made up of one or more transaction resource data records. All the transaction resource data records produced by a single CICS run have the same format, with a resource record header followed by a resource data section for each resource being monitored. Thus, the length of each record is dependent on the number of resources being monitored. For example, each file resource adds 96 bytes, which means that if you specify FILE=10 in the DFHMCT TYPE=INITIAL macro, the file resource data section can have up to 960 bytes of file resource data. Each temporary storage queue also adds 96 bytes to a record. The FILE operand in the MCT sets a limit to the number of files that resource data can be collected for any one transaction. The TSQUEUE operand in the MCT sets a limit to the number of temporary storage queues that resource data can be collected for any one transaction. All the system-defined data fields in the transaction resource monitoring records are described in the CICS Performance Guide.(Offset from beginning of record: SMF110S1_MNDRA)
0	0	SMF110S1_ MNR_ LENGTH	2	BINARY	Length of resource data
2	2	SMF110S1_ MNR_ ID	2	BINARY	Monitoring domain id (79)
4	4	SMF110S1_ MNR_ DSECT_ VERS	1	EBCDIC	DSECT version number (X'02')
5	5	--	3	EBCDIC	Reserved
8	8	SMF110S1_ MNR_ HDRLEN	2	BINARY	Length of header data
10	A	--	2	EBCDIC	Reserved
12	C	--	8	EBCDIC	Reserved
20	14	SMF110S1_ MNR_ TRN	2	BINARY	Number of record triplets
22	16	--	2	EBCDIC	Reserved
24	18	SMF110S1_ MNR_ ISO	4	BINARY	Offset to ID data
28	1C	SMF110S1_ MNR_ ISL	2	BINARY	Length of ID entry
30	1E	SMF110S1_ MNR_ ISN	2	BINARY	Number of ID entries
32	20	SMF110S1_ MNR_ FSO	4	BINARY	Offset to File data
36	24	SMF110S1_ MNR_ FSL	2	BINARY	Length of File entry
38	26	SMF110S1_ MNR_ FSN	2	BINARY	Number of File entries
40	28	SMF110S1_ MNR_ TSO	4	BINARY	Offset to TSQueue data
44	2C	SMF110S1_ MNR_ TSL	2	BINARY	Length of TSQueue entry
46	2E	SMF110S1_ MNR_ TSN	2	BINARY	Number of TSQueue entries
48	30	SMF110S1_ MNR_ DPO	4	BINARY	Offset to Distributed Program data
52	34	SMF110S1_ MNR_ DPL	2	BINARY	Length of Distributed Program entry
54	36	SMF110S1_ MNR_ DPN	2	BINARY	Number of Distributed Program entries
Transaction Resource Data - ID Data(Offset from beginning of record: SMF110S1_MNR_ILO)
0	0	SMF110S1_ MNR_ ID_ TRANID	4	EBCDIC	Transaction id
4	4	SMF110S1_ MNR_ ID_ TERMID	4	EBCDIC	Terminal id
8	8	SMF110S1_ MNR_ ID_ USERID	8	EBCDIC	User id
16	10	SMF110S1_ MNR_ ID_ STYPE	4	EBCDIC	Transaction Start type
20	14	SMF110S1_ MNR_ ID_ START	8	BINARY	Transaction Start time
28	1C	SMF110S1_ MNR_ ID_ STOP	8	BINARY	Transaction Stop time
36	24	SMF110S1_ MNR_ ID_ TASKNO	4	BINARY	Transaction Sequence Number
40	28	SMF110S1_ MNR_ ID_ LUNAME	8	EBCDIC	VTAM Luname
48	30	SMF110S1_ MNR_ ID_ PGMNAME	8	EBCDIC	First program name
56	38	SMF110S1_ MNR_ ID_ UOW_ PX	20	EBCDIC	Network Unit-of-Work Prefix
76	4C	SMF110S1_ MNR_ ID_ UOW_ SX	8	EBCDIC	Network Unit-of-Work Suffix
84	54	SMF110S1_ MNR_ ID_ RSYSID	4	EBCDIC	Remote sysid routed to
88	58	SMF110S1_ MNR_ ID_ TRN_ FLAGS	8	EBCDIC	Transaction flags
96	60	SMF110S1_ MNR_ ID_ FCTYNAME	4	EBCDIC	Transaction Facility name
100	64	SMF110S1_ MNR_ ID_ RTYPE	4	EBCDIC	Resource Record Type
104	68	SMF110S1_ MNR_ ID_ TERMINFO	4	EBCDIC	Terminal Information
104	6C	SMF110S1_ MNR_ ID_ NATURE	1	BINARY	Nature * X'00'= Not applic * X'01' = Terminal * X'02' = Session
105	6D	SMF110S1_ MNR_ ID_ SESSTYPE	1	BINARY	Session Type * X'00' = Not applic * X'01' = IRC * X'02' = IRC XM * X'03' = IRC XCF * X'04' = LU61 * X'05' = LU62 SINGLE * X'06' = LU62 PARALLEL
106	6E	SMF110S1_ MNR_ ID_ ACMETH	1	BINARY	Access method * EQU X'00' = Not applic * EQU X'01' = VTAM * EQU X'02' = BTAM (No longer supported) * EQU X'03' = BSAM * EQU X'04' = TCAM (TCAM local terminals no longer supported) * EQU X'05' = TCAMSNA * EQU X'06' = BGAM * EQU X'07' = CONSOLE
107	6F	SMF110S1_ MNR_ ID_ DEVCODE	1	BINARY	Device type code. See TYPETERM RDO attribute
108	70	SMF110S1_ MNR_ ID_ TERMCNNM	4	EBCDIC	Terminal Connection name
112	74	SMF110S1_ MNR_ ID_ RES_ FLAGS	4	EBCDIC	Resource flags
112	74	SMF110S1_ MNR_ ID_ RES_ FLAG1	1	BINARY	Resource flag 1 * X'80' = Resource File limit exceeded * X'40' = Resource TSQueue limit exceeded * X'20' = Distributed program link requests limit exceeded
113	75	--	3	BINARY	Reserved
116	78	SMF110S1_ MNR_ ID_ ISIPICNM	8	EBCDIC	Name of the IPIC (IPCONN) entry of the TCP/IP service that attached the user task.
124	80	SMF110S1_ MNR_ ID_ CLIPADDR	40	EBCDIC	IP address of the originating client or Telnet client.
164	A4	SMF110S1_ MNR_ ID_ ORIGIN_ NETWKID	8	EBCDIC	network identifier from which this work request (transaction) originated.
172	AC	SMF110S1_ MNR_ ID_ ORIGIN_ APPLID	8	EBCDIC	applid of the CICS region where this work request (transaction) originated; for example, the region in which the CWXN task ran
180	B4	SMF110S1_ MNR_ ID_ ATT_ TIME	8	BINARY	time when the originating task, for example, the CWXN task, was started
188	BC	SMF110S1_ MNR_ ID_ ORIGIN_ TRANNUM	4	Packed	The number of the originating task; for example, the CWXN task.
192	C0	SMF110S1_ MNR_ ID_ ORIGIN_ TRANID	4	EBCDIC	transaction ID (TRANSID) of the originating task; for example, the CWXN task.
196	C4	SMF110S1_ MNR_ ID_ ORIGIN_ USERID	8	EBCDIC	The originating Userid-2 or Userid-1, for example, from CWBA, depending on the originating task.
204	CC	SMF110S1_ MNR_ ID_ USER_ CORR	64	EBCDIC	The originating user correlator.
268	10C	SMF110S1_ MNR_ ID_ ORIGIN_ TCPIPSERV	8	EBCDIC	name of the originating TCPIPSERVICE
276	114	SMF110S1_ MNR_ ID_ ORIGIN_ PORTNUM	4	Binary	The port number used by the originating TCPIPSERVICE.
280	118	SMF110S1_ MNR_ ID_ ORIGIN_ CLIPADDR	40	EBCDIC	IP address of the originating client or Telnet client.
320	140	SMF110S1_ MNR_ ID_ ORIGIN_ CLIPPORT	4	Binary	The TCP/IP port number of the originating client or Telnet client.
324	144	SMF110S1_ MNR_ ID_ ORIGIN_ TRANFLAG	8	EBCDIC	The originating transaction flags. This 64-bit string is used for signaling transaction definition and status information.
332	14C	SMF110S1_ MNR_ ID_ ORIGIN_ FCTYNAME	8	EBCDIC	The facility name of the originating transaction. If the originating transaction is not associated with a facility, this field is null.
340	154	SMF110S1_ MNR_ PHD_ NTWKID	8	EBCDIC	The network identifier of the CICS system of an immediately previous task in another CICS region with which this task is associated.
348	15C	SMF110S1_ MNR_ PHD_ APPLID	8	EBCDIC	The APPLID from previous hop data. This is the APPLID of the CICS system of a previous task in another CICS system with which this task is associated.
356	164	SMF110S1_ MNR_ PHD_ ATTACH_ TIME	8	BINARY	The start time of the immediately previous task in another CICS system with which this task is associated.
364	16C	SMF110S1_ MNR_ PHD_ TRANNUM	4	Packed	The task number of the immediately previous task in another CICS system with which this task is associated.
368	170	SMF110S1_ MNR_ PHD_ TRANID	4	EBCDIC	The transaction ID (TRANSID) of the immediately previous task in another CICS system with which this task is associated.
372	174	SMF110S1_ MNR_ PHD_ COUNT	4	Binary	The number of times there has been a request from one CICS system to another CICS region to initiate a task with which this task is associated.
376	178	SMF110S1_ MNR_ ID_ TRNGRPID	28	EBCDIC	The transaction group ID of the originating task.
Transaction Resource Data - File Data(Offset from beginning of record: SMF110S1_MNR_FSO)
0	0	SMF110S1_ MNR_ FILE_ NAME	8	EBCDIC	File name
8	8	SMF110S1_ MNR_ FILE_ GET_ SECS_ RAW	4	BINARY	File Get time/count
13	D	SMF110S1_ MNR_ FILE_ GET_ CNT	3	BINARY	File Get time/count
16	10	SMF110S1_ MNR_ FILE_ PUT_ SECS_ RAW	4	BINARY	File Put time/count
21	15	SMF110S1_ MNR_ FILE_ PUT_ CNT	3	BINARY	File Put time/count
24	18	SMF110S1_ MNR_ FILE_ BRWSE_ SECS_ RAW	4	BINARY	File Browse time/count
29	1D	SMF110S1_ MNR_ FILE_ BRWSE_ CNT	3	BINARY	File Browse time/count
32	20	SMF110S1_ MNR_ FILE_ ADD_ SECS_ RAW	4	BINARY	File Add time/count
37	25	SMF110S1_ MNR_ FILE_ ADD_ CNT	3	BINARY	File Add time/count
40	28	SMF110S1_ MNR_ FILE_ DEL_ SECS_ RAW	4	BINARY	File Delete time/count
45	2D	SMF110S1_ MNR_ FILE_ DEL_ CNT	3	BINARY	File Delete time/count
48	30	SMF110S1_ MNR_ FILE_ TOTAL_ SECS_ RAW	4	BINARY	File Total time/count
53	35	SMF110S1_ MNR_ FILE_ TOTAL_ CNT	3	BINARY	File Total time/count
56	38	SMF110S1_ MNR_ FILE_ AM_ RQ	4	BINARY	File Access Method request count
60	3C	--	4	EBCDIC	Reserved
64	40	SMF110S1_ MNR_ FILE_ IO_ WT_ SECS_ RAW	4	BINARY	File I/O wait time/count
69	45	SMF110S1_ MNR_ FILE_ IO_ WT_ CNT	3	BINARY	File I/O wait time/count
72	48	SMF110S1_ MNR_ RLS_ FILE_ IO_ WT_ SECS_ RAW	4	BINARY	RLS File I/O wait time/count
77	4D	SMF110S1_ MNR_ RLS_ FILE_ IO_ WT_ CNT	3	BINARY	RLS File I/O wait time/count
80	50	SMF110S1_ MNR_ CFDT_ FILE_ IO_ WT_ SECS_ RAW	4	BINARY	CFDT File I/O wait time/count
85	55	SMF110S1_ MNR_ CFDT_ FILE_ IO_ WT_ CNT	3	BINARY	CFDT File I/O wait time/count
88	58	--	8	EBCDIC	Reserved
Transaction Resource Data - TSQueue Data(Offset from beginning of record: SMF110S1_MNR_TSO)
0	0	SMF110S1_ MNR_ TSQUEUE_ NAME	16	EBCDIC	TSQueue Name 16
10	50	SMF110S1_ MNR_ TSQUEUE_ GET_ SECS_ RAW	4	BINARY	TSQueue Get time/count
21	15	SMF110S1_ MNR_ TSQUEUE_ GET_ CNT	3	BINARY	TSQueue Get time/count 24
18	50	SMF110S1_ MNR_ TSQUEUE_ PUT_ AUX_ SECS_ RAW	4	BINARY	TSQueue Put Aux time/count
29	1D	SMF110S1_ MNR_ TSQUEUE_ PUT_ AUX_ CNT	3	BINARY	TSQueue Put Aux time/count 32
20	50	SMF110S1_ MNR_ TSQUEUE_ PUT_ MAIN_ SECS_ RAW	4	BINARY	TSQueue Put Main time/count
37	25	SMF110S1_ MNR_ TSQUEUE_ PUT_ MAIN_ CNT	3	BINARY	TSQueue Put Main time/count 40
28	50	SMF110S1_ MNR_ TSQUEUE_ TOTAL_ SECS_ RAW	4	BINARY	TSQueue Total time/count
45	2D	SMF110S1_ MNR_ TSQUEUE_ TOTAL_ CNT	3	BINARY	TSQueue Total time/count
48	30	--	4	BINARY	Reserved
52	34	SMF110S1_ MNR_ TSQUEUE_ GET_ ITEML	4	BINARY	TSQueue Get Item length
56	38	SMF110S1_ MNR_ TSQUEUE_ PUT_ AUX_ ITEML	4	BINARY	TSQueue Put Aux Item length
60	3C	SMF110S1_ MNR_ TSQUEUE_ PUT_ MAIN_ ITEML	4	BINARY	TSQueue Put Main Item length
64	40	--	8	EBCDIC	Reserved 72
48	50	SMF110S1_ MNR_ TSQUEUE_ IO_ WT_ SECS_ RAW	4	BINARY	TSQueue I/O wait time/count
77	4D	SMF110S1_ MNR_ TSQUEUE_ IO_ WT_ CNT	3	BINARY	TSQueue I/O wait time/count 80
50	50	SMF110S1_ MNR_ SHR_ TSQUEUE_ IO_ WT_ SECS_ RAW	4	BINARY	Shared TSQueue I/O wait time/count
85	55	SMF110S1_ MNR_ SHR_ TSQUEUE_ IO_ WT_ CNT	3	BINARY	Shared TSQueue I/O wait time/count
88	58	SMF110S1_ MNR_ TSQUEUE_ GET_ SHR_ SECS_ RAW	4	BINARY	The elapsed time that the user task waited for completion of GET requests to shared temporary storage, issued by the user task for this temporary storage queue. The count part of this field (the low-order 24 bits) contains the number of GET requests to shared temporary storage issued against the temporary storage queue.
93	5D	SMF110S1_ MNR_ TSQUEUE_ GET_ SHR_ CNT	3	BINARY	Count portion of above field
96	60	SMF110S1_ MNR_ TSQUEUE_ PUT_ SHR_ SECS_ RAW	4	BINARY	The elapsed time that the user task waited for completion of PUT requests to shared temporary storage, issued by the user task for this temporary storage queue. The count part of this field (the low-order 24 bits) contains the number of PUT requests to shared temporary storage issued against the temporary storage queue.
101	65	SMF110S1_ MNR_ TSQUEUE_ PUT_ SHR_ CNT	3	BINARY	Count portion of above field
104	SMF110S1_ MNR_ SQUEUE_ GET_ SHR_ ITEML	4	Binary	The total length of all items obtained from this shared temporary storage queue.
108	SMF110S1_ MNR_ TSQUEUE_ PUT_ SHR_ ITEML	4	Binary	The total length of all items written to this shared temporary storage queue.
Transaction Resource Data - Dispatched Program Links (Offset from beginning of record: SMF110S1_MNR_DPO)
0	0	SMF110S1_ MNR_ DPL_ PROGRAM_ NAME	8	EBCDIC	The name of the program to which the following data fields refer.
8	8	SMF110S1_ MNR_ DPL_ SYSID	4	EBCDIC	The name of the remote system to which this program was routed for the distributed program link.
12	C	SMF110S1_ MNR_ DPL_ LINK_ REQS	4	Binary	The number of distributed program link requests issued by the user task for this program and sysid combination.

The table above is based on the description provided by IBM in its "MVS Systems Management Facilities (SMF)" manual.

Spectrum SMF Writer - the 4GL SMF Report Writer.

Sample CICS Performance Report from SMF 110 Subtype 1 Records

The sample SMF report below was created with Spectrum SMF Writer, the low-cost 4GL SMF report writer.

It reads as input the SMF file and selects just the type 110 subtype 1 (CICS Monitoring) records, with data class 3 (performance). (See SMF 110 Subtype 1 record layout.)

We normalize those 110 records in order to process each performance segment present on each record. We print some identifying information from each segment. (Most users would also add a column for one or more of the performance measures present on the record.)

We sorted the records by transaction, printing two blank lines at the breaks.

All of this with just a few lines of code!
Why not install a Spectrum SMF Writer trial right now and start making your own SMF reports!

These Spectrum SMF Writer Statements:


INPUT:  SMF110S1
        NORMWHEN(SMF110RTY=110 & SMF110STY=1 & SMF110S1_MNCL=3)
        NORMALIZE(SMF110S1_PERF_SECTION, SMF110S1_MNDRN)

INCLUDEIF: SMF110RTY = 110  AND SMF110STY = 1
 
COLUMNS:
     SMF110DTE('SMF DATE')
     SMF110TME('SMF TIME' TP'99:99:99')
     SMF110RTY(3 'REC|TYP')
     SMF110STY(3 'SUB|TYP')
     SMF110S1_MNCL(4 'CLASS|OF|DATA')
     SMF110S1_TRAN('TRAN')
     SMF110S1_USERID
     SMF110S1_START('START|TIME' TP'99:99:99')
     SMF110S1_STOP
     SMF110S1_PGMNAME
     SMF110S1_SRVCLSNM(8 'SERVICE|CLASS')

TITLE: 'SMF 110 SUBTYPE 1 CICS MONITORING DATA'
TITLE: 'PERFORMANCE RECORDS FOR:' SMF110DTE
TITLE: 'SORTED BY CICS TRANSACTION'

SORT: SMF110S1_TRAN(2 NOTOTALS)

Produce This SMF Report:


                         SMF 110 SUBTYPE 1 CICS MONITORING DATA
                            PERFORMANCE RECORDS FOR: 08/24/10
                               SORTED BY CICS TRANSACTION

                           CLAS
                   REC SUB  OF       SMF110S1  START      SMF110S1     SMF110S1 SERVICE
 SMF DATE SMF TIME TYP TYP DATA TRAN  USERID    TIME        STOP       PGMNAME   CLASS
 ________ ________ ___ ___ ____ ____ ________ ________ _______________ ________ ________

 08/24/10 11:47:28 110   1    3 CRSQ W24AA01  10:47:04 10:47:03.618166 DFHCRQ   CICSCPSM
 08/24/10 11:48:17 110   1    3 CRSQ W24AA01  10:47:03 10:47:03.448452 DFHCRQ   CICSCPSM
 08/24/10 11:58:28 110   1    3 CRSQ W24AA01  10:58:13 10:58:12.701763 DFHCRQ   CICSCPSM
 08/24/10 11:59:41 110   1    3 CRSQ W24AA01  10:59:40 10:59:39.733808 DFHCRQ   CICSCPSM
 
 08/24/10 11:31:37 110   1    3 CSKP W24AA01  10:30:56 10:30:56.408895 DFHRMXN3 CICSMISC
 08/24/10 11:33:46 110   1    3 CSKP W24AA01  10:31:57 10:31:56.772842 DFHRMXN3 CICSMISC
 08/24/10 11:38:48 110   1    3 CSKP W24AA01  10:38:38 10:38:38.174839 DFHRMXN3 CICSMISC
 08/24/10 11:48:51 110   1    3 CSKP W24AA01  10:48:44 10:48:43.822947 DFHRMXN3 CICSMISC
 08/24/10 11:59:33 110   1    3 CSKP W24AA01  10:57:38 10:57:37.741627 DFHRMXN3 CICSMISC
 
 08/24/10 11:42:06 110   1    3 CWBG W24AA01  10:40:01 10:40:00.609872 DFHWBGB  CICSCPSM
 08/24/10 11:45:43 110   1    3 CWBG W24AA01  10:43:27 10:43:27.329171 DFHWBGB  CICSCPSM
 08/24/10 11:47:28 110   1    3 CWBG W24AA01  10:47:05 10:47:04.996727 DFHWBGB  CICSCPSM
 08/24/10 11:48:17 110   1    3 CWBG W24AA01  10:47:05 10:47:05.001450 DFHWBGB  CICSCPSM
 08/24/10 11:55:21 110   1    3 CWBG W24AA01  10:54:59 10:54:58.978051 DFHWBGB  CICSCPSM
 08/24/10 11:56:21 110   1    3 CWBG W24AA01  10:55:06 10:55:06.317385 DFHWBGB  CICSCPSM
 08/24/10 11:56:47 110   1    3 CWBG W24AA01  10:55:40 10:55:40.387347 DFHWBGB  CICSCPSM
 08/24/10 11:57:49 110   1    3 CWBG W24AA01  10:57:23 10:57:22.894420 DFHWBGB  CICSCPSM
 08/24/10 11:58:28 110   1    3 CWBG W24AA01  10:58:13 10:58:13.488356 DFHWBGB  CICSCPSM
 08/24/10 11:59:41 110   1    3 CWBG W24AA01  10:59:41 10:59:40.782089 DFHWBGB  CICSCPSM
 08/24/10 11:59:47 110   1    3 CWBG W24AA01  10:57:18 10:57:18.433078 DFHWBGB  CICSCPSM
 
 08/24/10 12:00:18 110   1    3 SBQE W24AA01  11:00:18 11:00:17.834936 SMM0100B CICSCPSM
 08/24/10 12:00:18 110   1    3 SBQE W24AA01  11:00:18 11:00:17.944291 SMM0100B CICSCPSM
 08/24/10 12:00:21 110   1    3 SBQE W24AA01  11:00:18 11:00:17.880463 SMM0100B CICSCPSM
 08/24/10 12:00:21 110   1    3 SBQE W24AA01  11:00:18 11:00:17.881020 SMM0100B CICSCPSM
 08/24/10 12:00:34 110   1    3 SBQE W24AA01  11:00:34 11:00:34.204671 SMM0100B CICSCPSM
 08/24/10 12:00:52 110   1    3 SBQE W24AA01  11:00:13 11:00:12.836766 SMM0100B CICSCPSM
 08/24/10 12:00:52 110   1    3 SBQE W24AA01  11:00:13 11:00:12.837173 SMM0100B CICSCPSM
 08/24/10 12:00:58 110   1    3 SBQE W24AA01  11:00:26 11:00:26.386854 SMM0100B CICSCPSM
 08/24/10 12:00:58 110   1    3 SBQE W24AA01  11:00:26 11:00:26.431278 SMM0100B CICSCPSM

 ...

See other sample SMF reports.