Go to Home Page
Questions?
Call 1-800-572-5517
 
  Go to Home Page  
  See all products
  See price schedules
  See manuals, tutorials, articles
  Download a free 30-day trial
  See user testimonials
  About Pacific Systems Group
 
 
SMF Tools
  See SMF Record Layouts
  See Sample SMF Reports
  Learn How to Export SMF Data
  Download Free SMF Reporting Software (30 days)
 
One of the greatest SMF record parsing programming languages I've ever seen. Chief, Large Systems Services Branch, NIH
  Choose Spectrum Writer to add 4GL to your product
  Free 60-Page Book (PDF) - How to Make an SMF Report
Spectrum DCOLLECT Reporter - the 4GL DCOLLECT Report Writer.

Spectrum SMF Writer - the 4GL SMF Report Writer.

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)

SMF Spectrum Writer
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.
 
Try It FREE Now!

SMF Type 110 Record -- CICS Monitoring Record
Offset
(Dec.)
Offset
(Hex)
NameLengthFormatDescription
00SMF110LEN2BINARY
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.
22SMF110SEG2BINARY
Segment descriptor (see record length field).
44SMF110FLG1BINARY
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.
55SMF110RTY1BINARY
Record type 110 (X'6E').
66SMF110TME4BINARY
Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer.
10ASMF110DTE4packed
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.
14ESMF110SID4EBCDIC
System identification (from the SID parameter).
1812SMF110SSI4BINARY
Subsystem ID
2216SMF110STY2BINARY
Record subtype
2418SMF110TRN2BINARY
Number of triplets
261ASMF110RES2BINARY
Reserved
281CSMF110APS4BINARY
Offset to CICS product section
3220SMF110LPS2BINARY
Length of CICS product section
3422SMF110NPS2BINARY
Number of CICS product sections
3624SMF110ASS4BINARY
Offset to CICS data section
4028SMF110LSS2BINARY
Length of CICS data section
422ASMF110NSS2BINARY
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)
00SMF110S1_
MNRVN
2BINARY
RECORD VERSION (CICS)
22SMF110S1_
MNPRN
8EBCDIC
PRODUCT NAME (GENERIC APPLID)
10ASMF110S1_
MNSPN
8EBCDIC
PRODUCT NAME (SPECIFIC APPLID)
1812SMF110S1_
MNMFL
2BINARY
RECORD MAINTENANCE INDICATOR
2014--2BINARY
RESERVED
2216SMF110S1_
MNCL
2BINARY
CLASS OF DATA
1 = DICTIONARY
3 = PERFORMANCE
4 = EXCEPTION
5 = TRANSACTION RESOURCE
2418SMF110S1_
MNDCA
4BINARY
OFFSET TO CICS FIELD CONNECTORS. Applies to performance class records only.
281CSMF110S1_
MNDCL
2BINARY
LENGTH OF EACH CICS FIELD CONNECTOR, Applies to performance class records only.
301ESMF110S1_
MNDCN
2BINARY
NUMBER OF CICS FIELD CONNECTORS, Applies to performance class records only.
3220SMF110S1_
MNDRA
4BINARY
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.
3624SMF110S1_
MNDRL
2BINARY
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.
3826SMF110S1_
MNDRN
2BINARY
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.
4028--18BINARY
RESERVED
583ASMF110S1_
MNCRL
2BINARY
COMPRESSED RECORD LENGTH
603CSMF110S1_
MNTAD
4BINARY
LOCAL TOD CLOCK ADJUSTMENT VALUE
6440SMF110S1_
MNLSO
8BINARY
LEAP SECOND OFFSET TOD FORMAT
7248SMF110S1_
MNDTO
8BINARY
LOCAL TIME/DATE OFFSET
8050--2BINARY
RESERVED
8252SMF110S1_
MNJBN
8EBCDIC
JOBNAME
905ASMF110S1_
MNRSD
4BINARY
JOB DATE
945ESMF110S1_
MSRST
4BINARY
JOB TIME
9862SMF110S1_
MNUIF
8EBCDIC
USER IDENTIFICATION
1066ASMF110S1_
MNPDN
8EBCDIC
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)
00SMF110S1_
CMODNAME
8EBCDIC
The identifier of the group to which the field belongs
88SMF110S1_
CMODTYPE
8EBCDIC
The field type
* S = STOPWATCH (CLOCK)
* A = ACCUMULATOR (COUNT)
* C = BYTE-STRING FIELD
* T = TIMESTAMP (STCK FORMAT)
* P = PACKED-DECIMAL FIELD
99SMF110S1_
CMODIDNT
3EBCDIC
The field identifier
12CSMF110S1_
CMODLENG
2BINARY
The length of the field
14ESMF110S1_
CMODCONN
2BINARY
The connector value assigned to the field
1610SMF110S1_
CMODOFST
2BINARY
The offset of the field
1812SMF110S1_
CMODHEAD
8EBCDIC
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)
00SMF110S1_
CONN
2BINARY
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)
00SMF110S1_
TRAN
4EBCDIC
Transaction identification.
44SMF110S1_
TERM
4EBCDIC
88SMF110S1_
USERID
8EBCDIC
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.
1610SMF110S1_
TTYPE
4EBCDIC
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.
2014SMF110S1_
START
8BINARY
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.
2014SMF110S1_
START
8BINARY
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
281CSMF110S1_
STOP
8BINARY
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.
281CSMF110S1_
STOP
8BINARY
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.
3624SMF110S1_
TRANNUM
4PACKED
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.
4028SMF110S1_
TRANPRI
4BINARY
442CSMF110S1_
TCLSNAME
8EBCDIC
5234SMF110S1_
LUNAME
8EBCDIC
603CSMF110S1_
PGMNAME
8EBCDIC
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.
6844SMF110S1_
NETUOWPX
20EBCDIC
8858SMF110S1_
NETUOWSX
8EBCDIC
9660SMF110S1_
RSYSID
4EBCDIC
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.
10064SMF110S1_
PERRECNT
4BINARY
The total number of performance class records written by the CICS Monitoring Facility (CMF) for this user task.
10468SMF110S1_
RMUOWID
8EBCDIC
11270SMF110S1_
SRVCLSNM
8EBCDIC
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
12078SMF110S1_
RPTCLSNM
8EBCDIC
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.
12880SMF110S1_
FCTYNAME
4EBCDIC
13284SMF110S1_
TRANFLAG
8EBCDIC
1408CSMF110S1_
TERMINFO
4EBCDIC
14490SMF110S1_
TERMCNNM
4EBCDIC
14894SMF110S1_
BRDGTRAN
4EBCDIC
15298SMF110S1_
RRMSURID
16EBCDIC
168A8SMF110S1_
PRCSNAME
36EBCDIC
204CCSMF110S1_
PRCSTYPE
8EBCDIC
212D4SMF110S1_
PRCSID
52EBCDIC
264108SMF110S1_
ACTVTYID
52EBCDIC
31613CSMF110S1_
ACTVTYNM
16EBCDIC
33214CSMF110S1_
CLIPADDR
16EBCDIC
The Client IP address in the form of nnn.nnn.nnn.nnn or Telnet client IP address.
34815CSMF110S1_
TRNGRPID
28EBCDIC
376178SMF110S1_
NETID
8EBCDIC
384180SMF110S1_
RLUNAME
8EBCDIC
392188SMF110S1_
TCPSRVCE
8EBCDIC
The name of the installed TCP/IP service resource definition from which the transaction was initiated.
400190SMF110S1_
PORTNUM
4BINARY
The port number of the installed TCP/IP service resource definition from which the transaction was initiated.
404194SMF110S1_
OTSTID
128EBCDIC
532214SMF110S1_
CBSRVRNM
4BINARY
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).
536218SMF110S1_
TASKFLAG
4EBCDIC
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
54021CSMF110S1_
ABCODEO
4EBCDIC
If the transaction abends, this field contains the 4 character abend code of the original abend.
544220SMF110S1_
ABCODEC
4EBCDIC
If the transaction abends, this field contains the 4 character abend code of the current abend.
548224SMF110S1_
RTYPE
4EBCDIC
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.
552228SMF110S1_
TCMSGIN1
4BINARY
55622CSMF110S1_
TCCHRIN1
4BINARY
560230SMF110S1_
TCMSGOU1
4BINARY
564234SMF110S1_
TCCHROU1
4BINARY
568238SMF110S1_
TCMSGIN2
4BINARY
57223CSMF110S1_
TCCHRIN2
4BINARY
576240SMF110S1_
TCMSGOU2
4BINARY
580244SMF110S1_
TCCHROU2
4BINARY
584248SMF110S1_
TCM62IN2
4BINARY
58824CSMF110S1_
TCC62IN2
4BINARY
592250SMF110S1_
TCM62OU2
4BINARY
596254SMF110S1_
TCC62OU2
4BINARY
600258SMF110S1_
TCALLOCT
4BINARY
60425CSMF110S1_
SCUGETCT1
4BINARY
The number of user-storage GETMAIN requests issued by the user task for storage below the 16MB line, in the UDSA.
608260SMF110S1_
SCUGETCT2
4BINARY
The number of user-storage GETMAIN requests issued by the user task for storage above the 16MB line, in the EUDSA.
612264SMF110S1_
SCCGETCT1
4BINARY
The number of user-storage GETMAIN requests issued by the user task for storage below the 16MB line, in the CDSA.
616268SMF110S1_
SCCGETCT2
4BINARY
The number of user-storage GETMAIN requests issued by the user task for storage above the 16MB line, in the EUDSA.
62026CSMF110S1_
SCUSRHWM1
4BINARY
Maximum amount (high-water mark) of user-storage allocated to the user task below the 16MB line, in the user dynamic storage area (UDSA).
624270SMF110S1_
SCUSRHWM2
4BINARY
Maximum amount (high-water mark) of user-storage allocated to the user task above the 16MB line, in the user dynamic storage area (EUDSA).
628274SMF110S1_
SC24CHWM1
4BINARY
Maximum amount (high-water mark) of user-storage allocated to the user task below the 16MB line, in the CICS® dynamic storage area (CDSA).
632278SMF110S1_
SC31CHWM2
4BINARY
Maximum amount (high-water mark) of user-storage allocated to the user task above the 16MB line, in the CICS dynamic storage area (CDSA).
63627CSMF110S1_
SCUSRSTG1
8BINARY
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.
644284SMF110S1_
SCUSRSTG2
8BINARY
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.
65228CSMF110S1_
SC24COCC1
8BINARY
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.
660294SMF110S1_
SC31COCC2
8BINARY
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.
66829CSMF110S1_
SC24SGCT
4BINARY
The number of storage GETMAIN requests issued by the user task for shared storage below the 16MB line, in the CDSA or SDSA.
6722A0SMF110S1_
SC24GSHR
4BINARY
The number of bytes of shared storage GETMAINed by the user task below the 16MB line, in the CDSA or SDSA.
6762A4SMF110S1_
SC24FSHR
4BINARY
The number of bytes of shared storage FREEMAINed by the user task below the 16MB line, in the CDSA or SDSA.
6802A8SMF110S1_
SC31SGCT
4BINARY
The number of storage GETMAIN requests issued by the user task for shared storage above the 16MB line, in the ECDSA or ESDSA.
6842ACSMF110S1_
SC31GSHR
4BINARY
The number of bytes of shared storage GETMAINed by the user task above the 16MB line, in the ECDSA or ESDSA.
6882B0SMF110S1_
SC31FSHR
4BINARY
The number of bytes of shared storage FREEMAINed by the user task above the 16MB line, in the CDSA or SDSA.
6922B4SMF110S1_
PCSTGHWM
4BINARY
The maximum amount (high-water mark) of program storage in use by the user task both above and below the 16MB line.
6962B8SMF110S1_
PC31AHWM
4BINARY
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.
7002BCSMF110S1_
PC24BHWM
4BINARY
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.
7042C0SMF110S1_
PC31CHWM
4BINARY
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.
7082C4SMF110S1_
PC24CHWM
4BINARY
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.
7122C8SMF110S1_
PC31RHWM
4BINARY
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.
7162CCSMF110S1_
PC24RHWM
4BINARY
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.
7202D0SMF110S1_
PC31SHWM
4BINARY
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.
7242D4SMF110S1_
PC24SHWM
4BINARY
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.
7282D8SMF110S1_
FCGETCT
4BINARY
The number of file control GET requests issued by the user task.
7322DCSMF110S1_
FCPUTCT
4BINARY
The number of file control PUT requests issued by the user task.
7362E0SMF110S1_
FCBRWCT
4BINARY
The number of file control BROWSE requests issued by the user task.
7402E4SMF110S1_
FCADDCT
4BINARY
The number of file control ADD requests issued by the user task.
7442E8SMF110S1_
FCDELCT
4BINARY
The number of file control DELETE requests issued by the user task.
7482ECSMF110S1_
FCTOTCT
4BINARY
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.
7522F0SMF110S1_
FCAMCT
4BINARY
The number of times the user task invoked file access-method interfaces. This number excludes requests for file OPEN and CLOSE.
7562F4SMF110S1_
TDGETCT
4BINARY
The number of transient data GET requests issued by the user task. 042 (Type-A, TDPUTCT, 4 bytes)
7602F8SMF110S1_
TDPUTCT
4BINARY
The number of transient data PUT requests issued by the user task.
7642FCSMF110S1_
TDPURCT
4BINARY
The number of transient data PURGE requests issued by the user task
768300SMF110S1_
TDTOTCT
4BINARY
The total number of transient data requests issued by the user task.
772304SMF110S1_
TSGETCT
4BINARY
The number of temporary storage READQ requests issued by the user task.
776308SMF110S1_
TSPUTACT
4BINARY
The number of temporary storage WRITEQ AUX requests issued by the user task.
78030CSMF110S1_
TSPUTMCT
4BINARY
The number of temporary storage WRITEQ MAIN requests issued by the user task.
784310SMF110S1_
TSTOTCT
4BINARY
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.
788314SMF110S1_
BMSMAPCT
4BINARY
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.
792318SMF110S1_
BMSINCT
4BINARY
The number of BMS RECEIVE MAP requests issued by the user task that did incur a terminal I/O.
79631CSMF110S1_
BMSOUTCT
4BINARY
The number of BMS SEND MAP requests issued by the user task.
800320SMF110S1_
BMSTOTCT
4BINARY
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.
804324SMF110S1_
PCLINKCT
4BINARY
The number of program LINK requests issued by the user task.
808328SMF110S1_
PCXCTLCT
4BINARY
The number of program XCTL requests issued by the user task.
81232CSMF110S1_
PCLOADCT
4BINARY
The number of program LOAD requests issued by the user task.
816330SMF110S1_
PCLURMCT
4BINARY
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
820334SMF110S1_
PCDPLCT
4BINARY
The number of distributed program link (DPL) requests issued by the user task
824338SMF110S1_
PCDLCSDL
4BINARY
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.
82833CSMF110S1_
PCDLCRDL
4BINARY
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.
832340SMF110S1_
PCLNKCCT
4BINARY
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).
836344SMF110S1_
PCXCLCCT
4BINARY
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).
840348SMF110S1_
PCDPLCCT
4BINARY
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).
84434CSMF110S1_
PCRTNCCT
4BINARY
Number of remote pseudoconversational RETURN requests, with the CHANNEL option, issued by the user task.
848350SMF110S1_
PCRTNCDL
4BINARY
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.
852354SMF110S1_
JNLWRTCT
4BINARY
The number of journal write requests issued by the user task.
856358SMF110S1_
LOGWRTCT
4BINARY
The number of CICS logstream write requests issued by the user task.
86035CSMF110S1_
ICPUINCT
4BINARY
The number of Interval Control START requests issued by the user task.
864360SMF110S1_
ICTOTCT
4BINARY
868364SMF110S1_
ICSTACCT
4BINARY
872368SMF110S1_
ICSTACDL
4BINARY
87636CSMF110S1_
ICSTRCCT
4BINARY
880370SMF110S1_
ICSTRCDL
4BINARY
884374SMF110S1_
SPSYNCCT
4BINARY
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
888378SMF110S1_
CFCAPICT
4BINARY
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.
89237CSMF110S1_
SZALLOCT
4BINARY
The number of FEPI conversations allocated by the user task. This number is incremented for each FEPI ALLOCATE POOL or FEPI CONVERSE POOL.
896380SMF110S1_
SZRCVCT
4BINARY
The number of FEPI RECEIVE requests issued by the user task. This number is also incremented for each FEPI CONVERSE request.
900384SMF110S1_
SZSENDCT
4BINARY
The number of FEPI SEND requests issued by the user task. This number is also incremented for each FEPI CONVERSE request.
904388SMF110S1_
SZSTRTCT
4BINARY
The number of FEPI START requests issued by the user task.
90838CSMF110S1_
SZCHROUT
4BINARY
The number of characters sent through FEPI by the user task.
912390SMF110S1_
SZCHRIN
4BINARY
The number of characters received through FEPI by the user task.
916394SMF110S1_
SZALLCTO
4BINARY
The number of times the user task timed out while waiting to allocate a conversation.
920398SMF110S1_
SZRCVTO
4BINARY
The number of times the user task timed out while waiting to receive data.
92439CSMF110S1_
SZTOTCT
4BINARY
The total number of FEPI API and SPI requests issued by the user task.
9283A0SMF110S1_
BARSYNCT
4BINARY
9323A4SMF110S1_
BARASYCT
4BINARY
9363A8SMF110S1_
BALKPACT
4BINARY
9403ACSMF110S1_
BADPROCT
4BINARY
9443B0SMF110S1_
BADACTCT
4BINARY
9483B4SMF110S1_
BARSPACT
4BINARY
9523B8SMF110S1_
BASUPACT
4BINARY
9563BCSMF110S1_
BARMPACT
4BINARY
9603C0SMF110S1_
BADCPACT
4BINARY
9643C4SMF110S1_
BAACQPCT
4BINARY
9683C8SMF110S1_
BATOTPCT
4BINARY
9723CCSMF110S1_
BAPRDCCT
4BINARY
9763D0SMF110S1_
BAACDCCT
4BINARY
9803D4SMF110S1_
BATOTCCT
4BINARY
9843D8SMF110S1_
BARATECT
4BINARY
9883DCSMF110S1_
BADFIECT
4BINARY
9923E0SMF110S1_
BATIAECT
4BINARY
9963E4SMF110S1_
BATOTECT
4BINARY
10003E8SMF110S1_
WBRCVCT
4BINARY
10043ECSMF110S1_
WBCHRIN
4BINARY
10083F0SMF110S1_
WBSENDCT
4BINARY
10123F4SMF110S1_
WBCHROUT
4BINARY
10163F8SMF110S1_
WBTOTCT
4BINARY
10203FCSMF110S1_
WBREPRCT
4BINARY
1024400SMF110S1_
WBREPWCT
4BINARY
1028404SMF110S1_
WBEXTRCT
4BINARY
1032408SMF110S1_
WBBRWCT
4BINARY
103640CSMF110S1_
WBREADCT
4BINARY
1040410SMF110S1_
WBWRITCT
4BINARY
1044414SMF110S1_
DHCRECT
4BINARY
1048418SMF110S1_
DHINSCT
4BINARY
105241CSMF110S1_
DHSETCT
4BINARY
1056420SMF110S1_
DHRETCT
4BINARY
1060424SMF110S1_
DHTOTCT
4BINARY
1064428SMF110S1_
DHTOTDCL
4BINARY
106842CSMF110S1_
SOBYENCT
4BINARY
The number of bytes encrypted by the secure sockets layer (SSL) for the user task.
1072430SMF110S1_
SOBYDECT
4BINARY
The number of bytes decrypted by the secure sockets layer (SSL) for the user task.
1076434SMF110S1_
SOEXTRCT
4BINARY
The number of EXTRACT TCPIP and EXTRACT CERTIFICATE requests issued by the user task.
1080438SMF110S1_
SOCNPSCT
4BINARY
The number of non-persistent outbound socket create requests issued by the user task.
108443CSMF110S1_
SOCPSCT
4BINARY
The number of persistent outbound socket create requests issued by the user task.
1088440SMF110S1_
SONPSHWM
4BINARY
The number of persistent outbound socket create requests issued by the user task.
1092444SMF110S1_
SOPSHWM
4BINARY
The peak number (high-water mark) of persistent outbound sockets owned by the user task.
1096448SMF110S1_
SORCVCT
4BINARY
The number of outbound socket RECEIVE requests issued by the user task.
110044CSMF110S1_
SOCHRIN
4BINARY
The number of characters received by outbound socket RECEIVE requests issued by the user task.
1104450SMF110S1_
SOSENDCT
4BINARY
The number of outbound socket SEND requests issued by the user task.
1108454SMF110S1_
SOCHROUT
4BINARY
The number of characters sent by outbound socket SEND requests issued by the user task.
1112458SMF110S1_
SOTOTCT
4BINARY
The total number of inbound and outbound socket requests issued by the user task.
111645CSMF110S1_
SOMSGIN1
4BINARY
The number of inbound socket RECEIVE requests issued by the user task.
1120460SMF110S1_
SOCHRIN1
4BINARY
The number of characters received by inbound socket RECEIVE requests issued by the user task.
1124464SMF110S1_
SOMSGOU1
4BINARY
The number of inbound socket SEND requests issued by the user task.
1128468SMF110S1_
SOCHROU1
4BINARY
The number of characters sent by inbound socket SEND requests issued by the user task.
113246CSMF110S1_
IMSREQCT
4BINARY
The total number of IMS (DBCTL) requests issued by the user task.
1136470SMF110S1_
DB2REQCT
4BINARY
The total number of DB2 EXEC SQL and Instrumentation Facility Interface (IFI) requests issued by the user task.
1140474SMF110S1_
TCBATTCT
4BINARY
1144478SMF110S1_
DSTCBHWM
4BINARY
114847CSMF110S1_
EJBSACCT
4BINARY
The number of bean activations that have occurred in this request processor.
1152480SMF110S1_
EJBSPACT
4BINARY
The number of bean passivations that have occurred in this request processor.
1156484SMF110S1_
EJBCRECT
4BINARY
The number of bean creation calls that have occurred in this request processor.
1160488SMF110S1_
EJBREMCT
4BINARY
The number of bean removal calls that have occurred in this request processor.
116448CSMF110S1_
EJBMTHCT
4BINARY
The number of bean method calls run in this request processor.
1168490SMF110S1_
EJBTOTCT
4BINARY
The total for this request processor of activation, passivation, creation, removal and method calls (fields 312–316).
1172494SMF110S1_
WBREDOCT
4BINARY
1176498SMF110S1_
WBWRTOCT
4BINARY
118049CSMF110S1_
WBRCVIN1
4BINARY
11844A0SMF110S1_
WBCHRIN1
4BINARY
11884A4SMF110S1_
WBSNDOU1
4BINARY
11924A8SMF110S1_
WBCHROU1
4BINARY
11964ACSMF110S1_
WBPARSCT
4BINARY
12004B0SMF110S1_
WBBRWOCT
4BINARY
12044B4SMF110S1_
WBIWBSCT
4BINARY
12084B8SMF110S1_
WBREPRDL
4BINARY
12124BCSMF110S1_
WBREPWDL
4BINARY
12164C0SMF110S1_
PGTOTCCT
4BINARY
12204C4SMF110S1_
PGBRWCCT
4BINARY
12244C8SMF110S1_
PGGETCCT
4BINARY
12284CCSMF110S1_
PGPUTCCT
4BINARY
12324D0SMF110S1_
PGMOVCCT
4BINARY
12364D4SMF110S1_
PGGETCDL
4BINARY
12404D8SMF110S1_
PGPUTCDL
4BINARY
12444DCSMF110S1_
PGCRECCT
4BINARY
12484E0SMF110S1_
USRDISPT
8BINARY
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.
12564E8SMF110S1_
USRCPUT
8BINARY
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.
12644F0SMF110S1_
SUSPTIME
8BINARY
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.
12724F8SMF110S1_
DISPWTT
8BINARY
1280500SMF110S1_
QRDISPT
8BINARY
1288508SMF110S1_
QRCPUT
8BINARY
1296510SMF110S1_
MSDISPT
8BINARY
1304518SMF110S1_
MSCPUT
8BINARY
1312520SMF110S1_
RODISPT
8BINARY
1320528SMF110S1_
ROCPUT
8BINARY
1328530SMF110S1_
KY8DISPT
8BINARY
1336538SMF110S1_
KY8CPUT
8BINARY
1344540SMF110S1_
KY9DISPT
8BINARY
1352548SMF110S1_
KY9CPUT
8BINARY
1360550SMF110S1_
L8CPUT
8BINARY
1368558SMF110S1_
L9CPUT
8BINARY
1376560SMF110S1_
J8CPUT
8BINARY
1384568SMF110S1_
S8CPUT
8BINARY
1392570SMF110S1_
J9CPUT
8BINARY
1400578SMF110S1_
X8CPUT
8BINARY
1408580SMF110S1_
X9CPUT
8BINARY
1416588SMF110S1_
QRMODDLY
8BINARY
1424590SMF110S1_
MAXOTDLY
8BINARY
1432598SMF110S1_
MAXJTDLY
8BINARY
14405A0SMF110S1_
MAXXTDLY
8BINARY
14485A8SMF110S1_
MAXSTDLY
8BINARY
14565B0SMF110S1_
DSTCBMWT
8BINARY
14645B8SMF110S1_
DSCHMDLY
8BINARY
14725C0SMF110S1_
EXWTTIME
8BINARY
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.
14805C8SMF110S1_
TCIOWTT
8BINARY
14885D0SMF110S1_
FCIOWTT
8BINARY
14965D8SMF110S1_
JCIOWTT
8BINARY
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).
15045E0SMF110S1_
TSIOWTT
8BINARY
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.
15125E8SMF110S1_
IRIOWTT
8BINARY
15205F0SMF110S1_
TDIOWTT
8BINARY
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).
15285F8SMF110S1_
PCLOADTM
8BINARY
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.
1536600SMF110S1_
DSPDELAY
8BINARY
1544608SMF110S1_
TCLDELAY
8BINARY
1552610SMF110S1_
MXTDELAY
8BINARY
1560618SMF110S1_
ENQDELAY
8BINARY
1568620SMF110S1_
GNQDELAY
8BINARY
1576628SMF110S1_
LU61WTT
8BINARY
1584630SMF110S1_
LU62WTT
8BINARY
1592638SMF110S1_
SZWAIT
8BINARY
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).
1600640SMF110S1_
RMITIME
8BINARY
1608648SMF110S1_
RMISUSP
8BINARY
1616650SMF110S1_
SYNCTIME
8BINARY
The elapsed time in which the user task was dispatched or suspended processing syncpoint requests.
1624658SMF110S1_
RLSWAIT
8BINARY
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).
1632660SMF110S1_
RLSCPUT
8BINARY
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.
1640668SMF110S1_
LMDELAY
8BINARY
1648670SMF110S1_
WTEXWAIT
8BINARY
1656678SMF110S1_
WTCEWAIT
8BINARY
1664680SMF110S1_
ICDELAY
8BINARY
1672688SMF110S1_
GVUPWAIT
8BINARY
1680690SMF110S1_
TSSHWAIT
8BINARY
The elapsed time in which the user task waited for an asynchronous shared temporary storage request to a temporary storage data server to complete.
1688698SMF110S1_
CFDTWAIT
8BINARY
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).
16966A0SMF110S1_
SRVSYWTT
8BINARY
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).
17046A8SMF110S1_
RRMSWAIT
8BINARY
17126B0SMF110S1_
RUNTRWTT
8BINARY
17206B8SMF110S1_
SYNCDLY
8BINARY
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).
17286C0SMF110S1_
SOIOWTT
8BINARY
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).
17366C8SMF110S1_
IMSWAIT
8BINARY
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).
17446D0SMF110S1_
DB2RDYQW
8BINARY
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)
17526D8SMF110S1_
DB2CONWT
8BINARY
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.
17606E0SMF110S1_
DB2WAIT
8BINARY
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).
17686E8SMF110S1_
JVMTIME
8BINARY
17766F0SMF110S1_
JVMSUSP
8BINARY
17846F8SMF110S1_
SOOIOWTT
8BINARY
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)
1792700SMF110S1_
RQRWAIT
8BINARY
1800708SMF110S1_
RQPWAIT
8BINARY
1808710SMF110S1_
OTSINDWT
8BINARY
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.
1816718SMF110S1_
JVMITIME
8BINARY
1824720SMF110S1_
JVMRTIME
8BINARY
1832728SMF110S1_
PTPWAIT
8BINARY
1840730SMF110S1_
DSMMSCWT
8BINARY
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)
00SMF110S1_
EXCMNTRN
4EBCDIC
TRANSACTION IDENTIFICATION
44SMF110S1_
EXCMNTER
4BINARY
TERMINAL IDENTIFICATION
88SMF110S1_
EXCMNUSR
8EBCDIC
USER IDENTIFICATION
1610SMF110S1_
EXCMNTST
4EBCDIC
TRANSACTION START TYPE
2014SMF110S1_
EXCMNSTA
8BINARY
EXCEPTION START TIME
281CSMF110S1_
EXCMNSTO
8BINARY
EXCEPTION STOP TIME
3624SMF110S1_
EXCMNTNO
4PACKED
TRANSACTION NUMBER
4028SMF110S1_
EXCMNTPR
4BINARY
TRANSACTION PRIORITY
442C--4EBCDIC
RESERVED
4830SMF110S1_
EXCMNLUN
8EBCDIC
LUNAME
5638--4EBCDIC
RESERVED
603CSMF110S1_
EXCMNEXN
4BINARY
EXCEPTION NUMBER
6440SMF110S1_
EXCMNRTY
8EBCDIC
EXCEPTION RESOURCE TYPE
7248SMF110S1_
EXCMNRID
8EBCDIC
EXCEPTION RESOURCE ID
8050SMF110S1_
EXCMNTYP
2BINARY
EXCEPTION TYPE
* X'0001' = WAIT
* X'0002' = BUFFER WAIT
* X'0003' = STRING WAIT
8252--2EBCDIC
RESERVED
8454SMF110S1_
EXCMNTCN
8EBCDIC
TRANSACTION CLASS NAME
925CSMF110S1_
EXCMNSRV
8EBCDIC
SERVICE CLASS NAME
10064SMF110S1_
EXCMNRPT
8EBCDIC
REPORT CLASS NAME
1086CSMF110S1_
EXCMNNPX
20EBCDIC
NETWORK UNIT-OF-WORK PREFIX
12880SMF110S1_
EXCMNNSX
8BINARY
NETWORK UNIT-OF-WORK SUFFIX
13688SMF110S1_
EXCMNTRF
8BINARY
TRANSACTION FLAGS
14490SMF110S1_
EXCMNFCN
4EBCDIC
TRANSACTION FACILITY NAME
14894SMF110S1_
EXCMNCPN
8EBCDIC
CURRENT PROGRAM NAME
1569CSMF110S1_
EXCMNBTR
4EBCDIC
BRIDGE TRANSACTION ID
160A0SMF110S1_
EXCMNURI
16EBCDIC
RRMS/MVS UNIT OF RECOVERY ID
176B0SMF110S1_
EXCMNRIL
4BINARY
EXCEPTION RESOURCE ID LENGTH
180B4SMF110S1_
EXCMNRIX
256EBCDIC
EXCEPTION RESOURCE ID (EXTENDED)
4361B4SMF110S1_
EXCMNNID
8EBCDIC
NETWORK ID
4441BCSMF110S1_
EXCMNRLU
8EBCDIC
REAL LUNAME
Transaction Resource Data Section
(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)
00SMF110S1_
MNR_
LENGTH
2BINARY
Length of resource data
22SMF110S1_
MNR_
ID
2BINARY
Monitoring domain id (79)
44SMF110S1_
MNR_
DSECT_
VERS
1EBCDIC
DSECT version number (X'02')
55--3EBCDIC
Reserved
88SMF110S1_
MNR_
HDRLEN
2BINARY
Length of header data
10A--2EBCDIC
Reserved
12C--8EBCDIC
Reserved
2014SMF110S1_
MNR_
TRN
2BINARY
Number of record triplets
2216--2EBCDIC
Reserved
2418SMF110S1_
MNR_
ISO
4BINARY
Offset to ID data
281CSMF110S1_
MNR_
ISL
2BINARY
Length of ID entry
301ESMF110S1_
MNR_
ISN
2BINARY
Number of ID entries
3220SMF110S1_
MNR_
FSO
4BINARY
Offset to File data
3624SMF110S1_
MNR_
FSL
2BINARY
Length of File entry
3826SMF110S1_
MNR_
FSN
2BINARY
Number of File entries
4028SMF110S1_
MNR_
TSO
4BINARY
Offset to TSQueue data
442CSMF110S1_
MNR_
TSL
2BINARY
Length of TSQueue entry
462ESMF110S1_
MNR_
TSN
2BINARY
Number of TSQueue entries
Transaction Resource Data - ID Data
(Offset from beginning of record: SMF110S1_MNR_ILO)
00SMF110S1_
MNR_
ID_
TRANID
4EBCDIC
Transaction id
44SMF110S1_
MNR_
ID_
TERMID
4EBCDIC
Terminal id
88SMF110S1_
MNR_
ID_
USERID
8EBCDIC
User id
1610SMF110S1_
MNR_
ID_
STYPE
4EBCDIC
Transaction Start type
2014SMF110S1_
MNR_
ID_
START
8BINARY
Transaction Start time
281CSMF110S1_
MNR_
ID_
STOP
8BINARY
Transaction Stop time
3624SMF110S1_
MNR_
ID_
TASKNO
4BINARY
Transaction Sequence Number
4028SMF110S1_
MNR_
ID_
LUNAME
8EBCDIC
VTAM Luname
4830SMF110S1_
MNR_
ID_
PGMNAME
8EBCDIC
First program name
5638SMF110S1_
MNR_
ID_
UOW_
PX
20EBCDIC
Network Unit-of-Work Prefix
764CSMF110S1_
MNR_
ID_
UOW_
SX
8EBCDIC
Network Unit-of-Work Suffix
8454SMF110S1_
MNR_
ID_
RSYSID
4EBCDIC
Remote sysid routed to
8858SMF110S1_
MNR_
ID_
TRN_
FLAGS
8EBCDIC
Transaction flags
9660SMF110S1_
MNR_
ID_
FCTYNAME
4EBCDIC
Transaction Facility name
10064SMF110S1_
MNR_
ID_
RTYPE
4EBCDIC
Resource Record Type
10468SMF110S1_
MNR_
ID_
TERMINFO
4EBCDIC
Terminal Information
1046CSMF110S1_
MNR_
ID_
NATURE
1BINARY
Nature
* X'00'= Not applic
* X'01' = Terminal
* X'02' = Session
1056DSMF110S1_
MNR_
ID_
SESSTYPE
1BINARY
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
1066ESMF110S1_
MNR_
ID_
ACMETH
1BINARY
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
1076FSMF110S1_
MNR_
ID_
DEVCODE
1BINARY
Device type code. See TYPETERM RDO attribute
10870SMF110S1_
MNR_
ID_
TERMCNNM
4EBCDIC
Terminal Connection name
11274SMF110S1_
MNR_
ID_
RES_
FLAGS
4EBCDIC
Resource flags
11274SMF110S1_
MNR_
ID_
RES_
FLAG1
1BINARY
Resource flag 1
* X'80' = Resource File limit exceeded +
* X'40' = Resource TSQueue limit exceeded
11375--3BINARY
Reserved
11678--8EBCDIC
Reserved
12480--8EBCDIC
Reserved
13288--8EBCDIC
Reserved
Transaction Resource Data - File Data
(Offset from beginning of record: SMF110S1_MNR_FSO)
00SMF110S1_
MNR_
FILE_
NAME
8EBCDIC
File name
88SMF110S1_
MNR_
FILE_
GET
8BINARY
File Get time/count
1610SMF110S1_
MNR_
FILE_
PUT
8BINARY
File Put time/count
2418SMF110S1_
MNR_
FILE_
BRWSE
8BINARY
File Browse time/count
3220SMF110S1_
MNR_
FILE_
ADD
8BINARY
File Add time/count
4028SMF110S1_
MNR_
FILE_
DEL
8BINARY
File Delete time/count
4830SMF110S1_
MNR_
FILE_
TOTAL
8BINARY
File Total time/count
5638SMF110S1_
MNR_
FILE_
AM_
RQ
4BINARY
File Access Method request count
603C--4EBCDIC
Reserved
6440SMF110S1_
MNR_
FILE_
IO_
WT
8BINARY
File I/O wait time
7248SMF110S1_
MNR_
RLS_
FILE_
IO_
WT
8BINARY
RLS File I/O wait time
8050SMF110S1_
MNR_
CFDT_
IO_
WT
8BINARY
CFDT I/O wait time
8858--8EBCDIC
Reserved
Transaction Resource Data - TSQueue Data
(Offset from beginning of record: SMF110S1_MNR_TSO)
00SMF110S1_
MNR_
TSQUEUE_
NAME
16EBCDIC
TSQueue Name
1610SMF110S1_
MNR_
TSQUEUE_
GET
8BINARY
TSQueue Get time/count
2418SMF110S1_
MNR_
TSQUEUE_
PUT_
AUX
8BINARY
TSQueue Put Aux time/count
3220SMF110S1_
MNR_
TSQUEUE_
PUT_
MAIN
8BINARY
TSQueue Put Main time/count
4028SMF110S1_
MNR_
TSQUEUE_
TOTAL
8BINARY
TSQueue Total time/count
4830--4BINARY
Reserved
5234SMF110S1_
MNR_
TSQUEUE_
GET_
ITEML
4BINARY
TSQueue Get Item length
5638SMF110S1_
MNR_
TSQUEUE_
PUT_
AUX_
ITEML
4BINARY
TSQueue Put Aux Item length
603CSMF110S1_
MNR_
TSQUEUE_
PUT_
MAIN_
ITEML
4BINARY
TSQueue Put Main Item length
6440--8EBCDIC
Reserved
7248SMF110S1_
MNR_
TSQUEUE_
IO_
WT
8BINARY
TSQueue I/O wait time
8050SMF110S1_
MNR_
SHR_
TSQUEUE_
IO_
WT
8BINARY
Shared TSQueue I/O wait time
8858--8EBCDIC
Reserved

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

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.

Copyright 2017.
Pacific Systems Group.
All rights reserved.


Spectrum Writer 4GL - the economical alternative to SAS, Easytrieve, DYL-280...

Home | Products | Prices | Documentation | 30-Day Trials | Customer Reviews | Company | FAQ | Sample Reports | SMF Records
Send Your Comments or Questions