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 120 Record - Subtype 9

This table shows the record layout for type 120 SMF records
(WebSphere Appl - Network Deployment z/OS, Version 8.0).

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

Purpose: WebSphere Application Server writes record type 120 to collect WebSphere Application Server performance statistics.

Record type 120 has the following subtypes:

  • Subtype 1 - the Server Activity record
  • Subtype 6 - the Server Interval record
  • Subtype 5 - the J2EE Container Activity Record
  • Subtype 6 - the J2EE Container Interval Record
  • Subtype 7 - the WebContainer Activity record
  • Subtype 8 - the WebContainer Interval record
  • Subtype 9 - Network Deployment (z/OS) Request Activity record

Subype 9 - Network Deployment (z/OS) Request Activity Record (Version 8.0)

The purpose of the Request Activity SMF record is to record activity that is running inside the product. This record is produced whenever a server receives a request.

New feature: When you do capacity planning, you need to look at the costs that are involved in running requests and how many requests you process over a set period of time. You can use the SMF 120 Subtype 9 record to monitor which requests are associated with which applications, how many requests you get, and how much resource each request uses. You can also use this record to identify the application involved, and the CPU time that the request consumes. Because a new record is created for each request, you can determine the number of requests that you get over a specific length of time.

After you collect these SMF records for awhile, you should be able to project your future system requirements. For example, you might look at the data that was collected for a specific application, and project what your CPU requirements will be as the number of users accessing that application increases. The data that was collected might also be useful if you are charging a third party to use this application, because the record indicates the resources that were used and who used them.

The default Subtype 9 record contains all of the information that you should need to properly monitor the performance of your Enterprise JavaBeans (EJB), and Web applications. You can specifically request other data, such as the formatted time stamp data, security data, or CPU usage data. However, collecting that data adds to the system overhead that is required to collect the data that populates these sections of the record.

You can activate this record through the administrative console by setting server_SMF_request_activity_enabled=1 (or server_SMF_request_activity_enabled=true).

If you do not want these records to be generated, you can set server_SMF_request_activity_enabled=0 (or server_SMF_request_activity_enabled=false), which turns off the creation of this SMF record type. This is the default value for this property.

Request activity record schema

The record header is the same for every Subtype 9 record that is created by the same controller.

The following triplet sections appears for every record that the controller generates.

  • Platform neutral server information section (one section per record):
    Contains information about each activity that occurred within one server.
  • z/OS server information section (one section per record):
    Contains information about each server servant in the specified server.
  • Platform neutral request information section (one section per record):
    Contains information about each request that was received by one server.
  • z/OS request information section (one section per record):
    Contains information about each request that was received by each server servant in the specified server.
  • z/OS formatted timestamps section (one section per record):
    Contains the date and time information for all of the actions that each server servant in the specified server performed.

These sections are optional.

  • Network data for HTTP, SIP and IIOP transports section (zero or one section per record):
    Contains information about either the HTTP, SIP or IIOP transports that are associated with one server. There is a separate network data section for the HTTP requests, the SIP requests, and the IIOP requests.
  • Classification data section (multiple (0..n) sections per record):
    Contains the classification information for each HTTP, SIP, and IIOP request received by a server. There is a separate classification data section for each piece of classification information.
  • Security data section (multiple (0..n) sections per record):
    Contains the security information for each request received by a server. There is a separate security data section for each identity type. These sections are optional.
  • CPU usage breakdown section (multiple (0..n) sections per record):
    Contains information about each item that was called and the CPU time that the task consumed, minus the time it spent waiting for tasks it initiated to complete. This calculation is different from the way CPU time is calculated in the container records. This section is optional.
  • User data section (multiple (0..n) sections per record):
    Contains information that is added by applications that use the SMF 120 subtype 9 user data APIs.

It's easy to report on SMF 120 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 120 Record -- WebSphere Appl - Network Deployment z/OS, Version 8.0
Offset
(Dec.)
Offset
(Hex)
NameLengthFormatDescription
00SMF120LEN2binary
Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word).
22SMF120SEG2binary
Segment descriptor (see record length field)
44SMF120FLG1binary
Bit meaning when set
0: New SMF record format
1: Subtypes used
2: Reserved
3-6: Version indicators*
7: Reserved
55SMF120RTY1binary
Record type 120(X'78')
66SMF120TME4binary
Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer.
10ASMF120DTE4packed
Date when the record was moved into the SMF buffer, in the form 0 cyydddF.
14ESMF120SID4EBCDIC
System identification (from the SMFPRMxx SID parameter)
1812SMF120SSI4EBCDIC
Subsystem identification from SUBSYS parameter
2216SMF120RST2binary
Record subtype:
1: Server activity
2: Container activity
3: Server interval
4: Container interval.
5: J2EE container activity
6: J2EE container interval
7: WebContainer activity
8: WebContainer interval
9: Request Activity record
Individual header extension for subtype 9
2418SMF1209AA4binary
Subtype version number
281CSMF1209AB4binary
Number of triplets
3220SMF1209AC4binary
Index of this record
3624SMF1209AD4binary
Total number of records
4028SMF1209AE8EBCDIC
Record continuation token
The following triplet appears for the Platform neutral server
information section.
4830SMF1209AF4binary
The offset to the Platform neutral server information section
5234SMF1209AG4binary
The length of the Platform neutral server information section
5638SMF1209AH4binary
The number of Platform neutral server information sections
The following triplet appears for the z/OS® server
information section.
603CSMF1209AI4binary
The offset to the z/OS server information section
6440SMF1209AJ4binary
The length of the z/OS server information section
6844SMF1209AK4binary
The number of z/OS server information sections
The following triplet appears for the Platform neutral request
information section.
7248SMF1209AL4binary
The offset to the Platform neutral request information section
764CSMF1209AM4binary
The length of the Platform neutral request information section
8050SMF1209AN4binary
The number of Platform neutral request information sections
The following triplet appears for the z/OS request
information section.
8454SMF1209AO4binary
The offset to the z/OS request information section
8858SMF1209AP4binary
The length of the z/OS request information section
925CSMF1209AQ4binary
The number of z/OS request information sections
The following triplet appears for the z/OS formatted timestamps
section. This section contains zeros when the formatted timestamps
are not being collected.
9660SMF1209AR4binary
The offset to the z/OS formatted timestamps section
10064SMF1209AS4binary
The length of the z/OS formatted timestamps section
10468SMF1209AT4binary
The number of z/OS formatted timestamps sections
The following triplet contains network information.
Only one version of this section appears for IIOP, HTTP transports,
and SIP transports. This section does not present for MDBs,
or for internal protocols.
1086CSMF1209AU4binary
The offset to the Network data for HTTP, SIP and IIOP transports section
11270SMF1209AV4binary
The length of the Network data for HTTP, SIP and IIOP transports section
11674SMF1209AW4binary
The number of Network data for HTTP, SIP and IIOP transports sections
The following triplet appears for the Classification data section.
12078SMF1209AX4binary
The offset to the Classification data section
1247CSMF1209AY4binary
The length of the Classification data section
12880SMF1209AZ4binary
The number of Classification data sections
The following triplet appears for the Security data section.
13284SMF1209BA4binary
The offset to the Security data section
13688SMF1209BB4binary
The length of the Security data section
1408CSMF1209BC4binary
The number of Security data sections
The following triplet appears 0-30 times for the CPU usage
breakdown sections.
14490SMF1209BD4binary
The offset to the CPU usage breakdown
14894SMF1209BE4binary
The length of the CPU usage breakdown section
15298SMF1209BF4binary
The number of CPU usage breakdown sections
The following triplet appears for the user data section.
1569CSMF1209FB4binary
The offset to the user data section
160A0SMF1209FC4binary
The length of the user data section
164A4SMF1209FD4binary
The number of user data sections
The following triplet appears for the user data section.
168A8SMF1209GB4binary
The offset to the asynchronous data section
172ACSMF1209GC4binary
The length of the asynchronous data section
176B0SMF1209GD4binary
The number of asynchronous data sections
180B4--24binary
Reserved
Subtype 9 - Platform neutral server information section
This section contains information about the server that handled the request.
(Offset from beginning of record: SMF1209AF)
00SMF1209BG4binary
The version of the Server information
44SMF1209BH8EBCDIC
Cell short name
12CSMF1209BI8EBCDIC
Node short name
2014SMF1209BJ8EBCDIC
Cluster short name
281CSMF1209BK8EBCDIC
Server short name
3624SMF1209BL4EBCDIC
Server or controller PID
4028SMF1209BM1binary
Product version level (the w in the format w.x.y.z)
4129SMF1209BN1binary
Product release level (the x in the format w.x.y.z)
422ASMF1209BO1binary
Part of the product modification level (the y in the format w.x.y.z)
432BSMF1209BP1binary
Part of the product modification level (the z in the format w.x.y.z)
442C--32binary
Reserved
z/OS server information section.
This section contains information about the controller and servant where the request was dispatched. One of these sections in included in each record.
(Offset from beginning of record: SMF1209AI)
00SMF1209BQ4binary
The version of the server information
44SMF1209BR8EBCDIC
The name of the system on which the product is running (CVTSNAME)
12CSMF1209BS8EBCDIC
The name of the sysplex on which the product is running
2014SMF1209BT8EBCDIC
The job name for the controller
281CSMF1209BU8EBCDIC
The job ID for the controller
3624SMF1209BV8binary
The STOKEN for the controller
442CSMF1209BW2binary
The ASID for the controller
462E--2binary
Reserved for alignment
4830SMF1209BX20binary
The cluster UUID
6844SMF1209BY20binary
The server UUID
8858SMF1209BZ8EBCDIC
The daemon group name
9660SMF1209CA4binary
The hours portion of the LE GMT offset. The value is obtained from the CEEGMTO API if you are running in 31-bit mode. The field contains all zeros if the CEEGMTO API fails or is unavailable, or if you are running in 64-bit mode. The CEEGMTO API is not supported in 64-bit mode. In these situations, flag SMF1209FJ is turned on to indicate that the zeros in this field are not valid GMT offsets.
10064SMF1209CB4binary
The minutes portion of the LE GMT offset. The value is obtained from the CEEGMTO API if you are running in 31-bit mode. The field contains all zeros if the CEEGMTO API fails or is unavailable, or if you are running in 64-bit mode. The CEEGMTO API is not supported in 64-bit mode. In these situations, flag SMF1209FJ is turned on to indicate that the zeros in this field are not valid GMT offsets.
10468SMF1209CC8binary
The seconds portion of the LE GMT offset. The value is obtained from the CEEGMTO API if you are running in 31-bit mode. The field contains all zeros if the CEEGMTO API fails or is unavailable, or if you are running in 64-bit mode. The CEEGMTO API is not supported in 64-bit mode. In these situations, flag SMF1209FJ is turned on to indicate that the zeros in this field are not valid GMT offsets.
11270SMF1209CD8binary
The system GMT offset. The value is obtained from the CVTLDTO API.
12078SMF1209CE8EBCDIC
The service level
12078SMF1209HV16EBCDIC
The service level (expanded)
13688--20binary
Reserved
Platform neutral request information section.
This section provides request information that is not platform specific.
(Offset from beginning of record: SMF1209AL)
00SMF1209CF4binary
The version of the request information
44SMF1209CG4binary
The PID of the dispatch servant
88SMF1209CH8binary
The ID of the dispatched task. This value is returned from pthread_self.
1610SMF1209CI8binary
The amount of CPU time, in microseconds, that is used by dispatch TCB. This field might contain a negative value if field SMF1209CJ contains a value other than 0.
2418SMF1209CJ4binary
The completion minor code. A value of 0 indicates that the request successfully completed. If a value other than 0 is present, a problem occurred during processing of the request.
281C--4binary
Reserved
3220SMF1209CK4binary
The type of request that was processed:
0 indicates that the request type is not known
1 indicates that the request was an IIOP request
2 indicates that the request was an HTTP request
3 indicates that the request was an HTTPS request
4 indicates that the request was a MDB Plan "A" request. A Plan "A" request is an MDB request from a listener port that is listening in the controller.
5 indicates that the request was a MDB Plan "B" request. A Plan "B" request is an MDB request from a listener port that is listening in the servant.
6 indicates that the request was a MDB Plan "C" request. A Plan "C" request is an MDB request from an activation specification that is listening in the adjunct.
7 indicates that the request was a SIP request
8 indicates that the request was a SIPS request
9 indicates that the request was an MBean request
10 indicates that the request was an OTS request
11 indicates that the request was an internal request
3624--32binary
Reserved
z/OS request information section.
zIIP and zAAP enclaves are not supported on z/OS Version 1.7. Therefore, if you are running the product on z/OS Version 1.7, fields that normally contain zIIP and zAAP enclave information, contain a value of -1.

Avoid trouble: There are several field descriptions within the following table that reference the z/OS WLM IWMEQTME API. You should refer to your z/OS documentation for more specific information about the content of these fields.

(Offset from beginning of record: SMF1209AO)
00SMF1209CL4binary
The version of the request information
44SMF1209CM16S390STCKE
The time that the request was received
2014SMF1209CN16S390STCKE
The time that the request was added to the queue
3624SMF1209CO16S390STCKE
The time that the request was dispatched
5234SMF1209CP16S390STCKE
The time that the dispatch completed
6844SMF1209CQ16S390STCKE
The time that the controller finished processing the request response
8454SMF1209CR8EBCDIC
The job name for the dispatch servant
925CSMF1209CS8EBCDIC
The job ID for the dispatch servant
10064SMF1209CT8binary
The STOKEN for the dispatch servant
1086CSMF1209CU2binary
The ASID for the dispatch servant
1106E--2binary
Reserved for alignment
11270SMF1209CV4binary
The address of the dispatch TCB
11674SMF1209CW16binary
The TTOKEN for the dispatch TCB
13284SMF1209CX8binary
The amount of CPU time that was spent on non-standard CPs, such as the System z Application Assist Processor (zAAP) and z9 Integrated Information Processor (zIIP). This value is obtained from the TIMEUSED API. A value of -1 displays in this field if:
  • A value cannot be obtained from the TIMEUSED service.
  • The level of z/OS on which you are running is not Version 1.9 with APAR OA20758 applied, or Version 1.10 or higher.

This field might also contain a negative value if field SMF1209CJ contains a value other than 0.
1408CSMF1209CY8binary
The enclave token
14894SMF1209CZ32Reserved
180B4SMF1209DA8binary
The enclave CPU time at the end of the dispatch of this request, as reported by the CPUTIME parameter of the IWMEQTME API. The units are in TOD format.
188BCSMF1209DB8binary
The enclave zAAP CPU time at the end of the dispatch of this request, as reported by the ZAAPTIME parameter of the IWMEQTME API. The value is zero if the PTF for z/OS APAR OA22160 is not installed on your system.
196C4SMF1209DC8binary
The amount of CPU time at the end of the dispatch of this request that is spent on a regular CP that could have been run on a zAAP, but the zAAP was not available. This value is obtained from the ZAAPONCPTIME. field in the IWMEQTME macro. The value is zero if the PTF for z/OS APAR OA22160 is not installed on your system.
204CCSMF1209DD8binary
The zIIP enclave that is on the CPU at the end of the dispatch of this request. This value is obtained from the ZIIPONCPTIME. field in the IWMEQTME macro. The value is zero if the PTF for z/OS APAR OA22160 is not installed on your system.
212D4SMF1209DE8binary
The zIIP Quality Time enclave that was on the CPU at the end of the dispatch of this request. This value is obtained from the ZIIPQUALTIME field in the IWMEQTME macro. The value is zero if the PTF for z/OS APAR OA22160 is not installed on your system.
220DCSMF1209DF8binary
The eligible zIIP enclave that is on the CPU at the end of the dispatch of this request. This value is obtained from the ZIIPTIME field in the IWMEQTME macro. The value is zero if the PTF for z/OS APAR OA22160 is not installed on your system.
228E4SMF1209DG4binary
The zAAP normalization factor at the end of the dispatch of this request. This value is obtained from the ZAAPNFACTOR parameter of the IWMEQTME API. The value is zero if the PTF for z/OS APAR OA22160 is not installed on your system.
232E8SMF1209DH8binary
The amount of CPU time that was used by the enclave as reported by the CPUTIME parameter of the IWM4EDEL API
240F0SMF1209DI8binary
The delete zAAP CPU enclave. A value of 0 indicates that the enclave was not deleted or not normalized. This value is obtained from the ZAAPTIME field in the IWM4EDEL macro.
248F8SMF1209DJ4binary
The enclave delete zAAP normalization factor as reported by the ZAAPNFACTOR parameter of the IWM4EDEL API.
252FC--4binary
Reserved
256100SMF1209DK8EBCDIC
The enclave delete zIIP time accumulated by the enclave as reported by the ZIIPTIME parameter of the IWM4EDEL API. A value of 0 indicates that the enclave was not deleted.
264108SMF1209DL8EBCDIC
The enclave delete zIIP Service accumulated by the enclave as reported by the ZIIPSERVICE parameter of the IWM4EDEL API. A value of 0 indicates that the enclave was not deleted or not normalized.
272110SMF1209DM8EBCDIC
The enclave delete zAAP Service accumulated by the enclave as reported by the ZAAPSERVICE parameter of the IWM4EDEL API. A value of 0 indicates that the enclave was not deleted.
280118SMF1209DN8EBCDIC
The enclave delete CPU service accumulated by the enclave as reported by the CPUSERVICE parameter of the IWM4EDEL API. A value of 0 indicates that the enclave was not deleted.
288120SMF1209DO4EBCDIC
The enclave delete Response Time ratio as reported by the RESPTIME_RATIO parameter of the IWM4EDEL API. A value of 0 indicates that the enclave was not deleted.
292124SMF1209DP12Reserved
for alignment
304130SMF1209DQ73binary
The global transaction ID (GTID) value
377179--3binary
Reserved for alignment
38017CSMF1209DR4binary
The dispatch timeout value
384180SMF1209DS8EBCDIC
The transaction class, if one is being used
392188SMF1209DT4binary
Is either blank or contains the following flags:
SMF1209DU (bit 1) - if turned on, an enclave was created by this server for this request
SMF1209DV (bit 2) - if turned on, the timeout value was given to the product by an external source instead of being taken from the configuration for the server
SMF1209DW (bit 3) - if turned on, the transaction class value was given to the product by an external source instead of being taken from the configuration for the server
SMF1209DX (bit 4) - if turned on, this is a one way IIOP request, for which a response is not expected
SMF1209DY (bit 5) - if turned on, the CPU usage section exceeded 30, which is the maximum number of sections that are allowed. Some of your data was lost.
SMF1209DZ (bit 6) - if turned on, the request was queued to a specific servant region because the request had an affinity to that servant, possibly because of HTTP session affinity
SMF1209FJ (bit 7) - if turned on, the GMT offsets failed to be retrieved from the CEEGMTO, API or the CEEGMTO API was not available
SMFBits 8 - 32 are reserved
39618C--32binary
Reserved
4281ACSMF1209FR4binary
The numerical value corresponds to the value of the stalled_thread_dump_action RAS attribute: 0 for none, 1 for javacore, 2 for heapdump, 3 for traceback, 4 for svcdump, and 5 for javatdump.
The field is valid only if the SMF1209CL field is greater than or equal to 2.
4321B0SMF1209FS4binary
The numerical value corresponds to the value of the cputimeused_dump_action RAS attribute: 0 for none, 1 for javacore, 2 for heapdump, 3 for traceback, 4 for svcdump, and 5 for javatdump. The field is valid only if the SMF1209CL field is greater than or equal to 2.
4361B4SMF1209FT4binary
The numerical value corresponds to the value of the dpm_dump_action RAS attribute: 0 for none, 1 for javacore, 2 for heapdump, 3 for traceback, 4 for svcdump, and 5 for javatdump. The field is valid only if the SMF1209CL field is greater than or equal to 2.
4401B8SMF1209FU4binary
The numerical value corresponds to the value of the timeout_recovery RAS attribute: 1 for servant and 2 for session. The field is valid only if the SMF1209CL field is greater than or equal to 2.
4441BCSMF1209FV4binary
The value of the dispatch_timeout classification RAS attribute. The field is valid only if the SMF1209CL field is greater than or equal to 2.
4481C0SMF1209FW4binary
Queue timeout, which is calculated using the dispatch_timeout and queue_timeout_percent classification RAS attributes. The field is valid only if the SMF1209CL field is greater than or equal to 2.
4521C4SMF1209FX4binary
The value of the request_timeout classification RAS attribute. The field is valid only if the SMF1209CL field is greater than or equal to 2.
4561C8SMF1209FY4binary
The value of the cputimeused_limit classification RAS attribute. The field is valid only if the SMF1209CL field is greater than or equal to 2.
4601CCSMF1209FZ4binary
The value of the dpm_interval classification RAS attribute. The field is valid only if the SMF1209CL field is greater than or equal to 2.
4641D0SMF1209GA8EBCDIC
The value of the message_tag classification RAS attribute. The field is valid only if the SMF1209CL field is greater than or equal to 2.
4721D8SMF1209GH4binary
Length of obtained affinity RNAME
4761DCSMF1209GI128EBCDIC
Obtained affinity RNAME
60425CSMF1209GJ4binary
Length of routing affinity RNAME
608260SMF1209GK128EBCDIC
Routing affinity RNAME
z/OS formatted timestamps section
This section contains the date and time information for specific events that occurred during the processing of the request. All of the times that are included in this section are expressed in the format yyyy/mm/dd hh:mm:ss.xxxxxx, where yyyy is the year, mm is the month, dd is the day, hh is the hour, mm is the minutes, ss is the seconds, and xxxxxx is the microseconds.

Including the timestamp section in the Subtype 9 record is optional. Collecting the data to update this section adds system overhead and can make these SMF records larger. Therefore, the collection of this data, by default, is turned off. When the collection of this data is turned off, the Number of records field in the triplets section, that is located at the beginning of the record contains, a zero.

(Offset from beginning of record: SMF1209AR)
00SMF1209EA26EBCDIC
The time that the request was received
261ASMF1209EB26EBCDIC
The time that the request was added to the WLM queue
5234SMF1209EC26EBCDIC
The time that the request was dispatched in the servant
784ESMF1209ED26EBCDIC
The time that the dispatch completed in the servant
10468SMF1209EE26EBCDIC
The time that the controller finished processing the request
13082--2binary
Reserved for alignment
Network data for HTTP, SIP, and IIOP transports section.
This section contains information about the origin of the request that this record describes. It is only present for protocols for which the product can obtain origin information. For example, this section does not exist for Message Driven Beans (MDBs) requests. A record contains only one instance of this section.
(Offset from beginning of record: SMF1209AU)
00SMF1209EF4binary
The version of the network data
44SMF1209EG8binary
The size of the request, in bytes, that was received from the client
12CSMF1209EH8binary
The size of the response, in bytes, that is sent back to the client
2014SMF1209EI4binary
The target port for the request. A value of -1 indicates that local communications was used.
2418SMF1209EJ4binary
The length of the origin string
281CSMF1209EK128EBCDIC
The origin string. Following is an example of an origin string: ip addr=9.57.7.193 port=1344. The bytes that follow the string contain blank spaces.
1569C--32binary
Reserved
Classification data section.
This section contains the classification information for this request. If a transaction class was encountered earlier, this information might have been used to determine that transaction class name.
(Offset from beginning of record: SMF1209AX)
00SMF1209EL4binary
The version of the classification data
44SMF1209EM4binary
The data type. Not all of these data types apply to all requests. For example, only data types 6, 7, or 8 appear in this field for an HTTP request.
1 indicates that it is the name of an application
2 indicates that it is the name of a module
3 indicates that it is the name of a component
4 indicates that it is the name of a class
5 indicates that it is the name of a method
6 indicates that it is a URI
7 indicates that it is the name of the target host
8 indicates that it is the name of the target port
9 indicates that it is a message listener port
10 indicates that it is the name of a selector
88SMF1209EN4binary
The length of the data
12CSMF1209EO128EBCDIC
The data string
Security data section
This section contains the security information for each request. There is a separate security data section for each identity type. Depending on your security configuration, up to three identity types might exist. Therefore, there can be up to three instances of this section in a record, depending on which data is available for the request, for which the report is generated.

Including the security sections in the Subtype 9 record is optional. Collecting the data to update this section adds system overhead and can make these SMF records larger. Therefore, the collection of this data, by default, is turned off. When the collection of this data is turned off, the Number of records field in the triplets section at the top of the record contains a zero.

(Offset from beginning of record: SMF1209BA)
00SMF1209EP4binary
The version of the security data
44SMF1209EQ4binary
The data type:
1 indicates that it is the server identity
2 indicates that it is the received identity
3 indicates that it is the invocation identity
88SMF1209ER4binary
The length of the identity
12CSMF1209ES64EBCDIC
The identity string
CPU usage breakdown section
This section contains information about an item that was called and the CPU time that the task consumed, minus the time that the CPU spent waiting for tasks it initiated to complete. This calculation is different from the way CPU time is calculated in the container records.

There can be up to 30 instances of this section in a record; one for each item that is called. If your application calls more than 30 different items under the dispatch of a single request, only the first 30 items are included. Bit 5 of field SMF1209DT indicates when such a truncation occurs.

Including the CPU usage section in the Subtype 9 record is optional. Collecting the data to update this section adds system overhead and can make these SMF records quite large. Therefore, the collection of this data, by default, is turned off. When the collection of this data is turned off or none were collected during a request, the field for the number of CPU usage break down sections (SMF1209AB) in the triplet at the top of the record contains a zero.

(Offset from beginning of record: SMF1209BA)
00SMF1209ET4binary
The version of the CPU usage data
44SMF1209EU4binary
The data type:
1 indicates that the data comes from the EJB container
2 indicates that the data comes from the Web container
88SMF1209EV8binary
The amount of CPU time, in microseconds, that the item, such as an EJB or a servlet, spent in dispatch
1610SMF1209FI8binary
The elapsed time, in milliseconds, that is spent processing the item, such as an EJB or servlet
2418SMF1209EW4binary
How many times the item, such as an EJB or a servlet, was executed during the dispatch of this request
281CSMF1209EX4binary
The length of string 1
3220SMF1209EY256EBCDIC
String 1. String 1 has one of the following values:
  • AMC, which indicates that an EJB was processed
  • Web App, which indicates that a Servlet was processed
  • 288120SMF1209EZ4binary
    The length of string 2
    292124SMF1209FA256EBCDIC
    String 2 has one of the following values:
    • The method name or signature, if an EJB is accessing the data
    • The name of the servlet if a servlet is accessing the data
    User data section
    You can use the package com.ibm.websphere.smf API to add up to 5 User data sections to the end of this record. Each of these sections must be less than or equal to 2 KB in length. The data that is contained in these sections is not formatted and appears exactly as it is received from your application.
    (Offset from beginning of record: SMF1209BD)
    00SMF1209FE4binary
    The version of the User data section
    44SMF1209FF4binary
    The user data type. Types 65535 and lower are reserved for IBM® use.
    88SMF1209FG4binary
    The length of the User data section
    12CSMF1209FH2048binary
    The data that the application added
    Asynchronous data section [Fix Pack 1 or later]
    This section contains information about requests that the server runs asynchronously.

    An asynchronous request has one instance of this section. This section is not applicable for non-asynchronous requests.

    (Offset from beginning of record: SMF1209FB)
    00SMF1209GM4binary
    The version of the asynchronous data section.
    44SMF1209GL16S390STCKE
    The time that the execution context was created.
    2014SMF1209GN16S390STCKE
    The time that the execution started.
    3624SMF1209GO16S390STCKE
    The time that the execution completed.
    5234SMF1209GP4binary
    The servant process ID.
    5638SMF1209GQ8EBCDIC
    The servant job name.
    6440SMF1209GR8EBCDIC
    The servant job ID.
    7248SMF1209GS8binary
    The servant token.
    8050SMF1209GT2binary
    The servant ASID. 82 52 * 2 The reserved alignment.
    8454SMF1209GU8binary
    The execution context task ID.
    925CSMF1209GV4binary
    The execution context TCB address.
    9660SMF1209GW16binary
    The execution context TCB TToken.
    11270SMF1209GX8binary
    The dispatch task ID.
    12078SMF1209GY4binary
    The dispatch TCB address.
    1247CSMF1209GZ16binary
    The dispatch TCB TToken.
    1408CSMF1209HA8binary
    The execution context enclave token.
    14894SMF1209HB8binary
    The dispatch enclave token.
    1569CSMF1209HC8EBCDIC
    The transaction class used to create the enclave.
    164A4SMF1209HD4binary
    Contains the following flags:
    SMF1209HE in bit 1. A value of 0 indicates that the enclave was joined. A value of 1 indicates that the enclave was created.
    SMF1209HF in bit 2. A value of 1 indicates that the enclave was scheduled with the daemon.
    Reserved, for bits 3 through 32.
    168A8SMF1209HG8binary
    The enclave CPU so far.
    176B0SMF1209HH8binary
    The enclave zAAP CPU so far.
    184B8SMF1209HI8binary
    The enclave zAAP eligible on the CP.
    192C0SMF1209HJ8binary
    The enclave zIIP on the CPU so far.
    200C8SMF1209HK8binary
    The enclave zIIP quality time so far.
    208D0SMF1209HL8binary
    The Enclave zIIP CPU so far.
    216D8SMF1209HM4binary
    The zAAP normalization factor. 220 DC * 4 The reserved alignment.
    224E0SMF1209HN8binary
    The dispatch CPU.
    232E8SMF1209HO8binary
    The dispatch CPU offload to non-standard CPs, for example zAAP or zIIP.
    240ECSMF1209HP4binary
    Length of the work class name.
    244F4SMF1209HQ128EBCDIC
    The work package or class name.
    372174SMF1209HR4binary
    The length of the work manager name.
    376178SMF1209HS128EBCDIC
    The work manager name.
    5041F8SMF1209HT4binary
    The identity length.
    5081FCSMF1209HU64EBCDIC
    The identity.
    57223C--16binary
    Reserved.

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

    Sample Report from SMF 120
    WebSphere Application Java CPU Times


    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 120 WebSphere Application records for Jave 2 Enterprise Edition containers. (See SMF 120-5 record layout.) It then prints a report line for each Java bean method accounting section found. The report shows CPU time information about those Java bean methods. Note that a single SMF 120 record can contain information about multiple beans and multiple methods per bean.

    All of this with just a few 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:  SMF12005
    
    INCLUDEIF: SMF120RTY=120   AND SMF120RST=5
    
    TITLE: 'Z/OS WEBSPHERE APPLICATION SMF 120 DATA'
    TITLE: 'SUBTYPE 5 -- J2EE CONTAINER ACTIVITY'
    
    COL: SMF120RST(3 'SUB/TYP')
         SMF120JA4(5 'TRANS/SERVER/HOST')
         SMF120JA5(6 'TRANS/SERVER/NAME')
         SMF120JA8_EBC(8 'CONTAINER/NAME')
         SMF120CL2('CELL')
         SMF120ND2('NODE')
         SMF120JB1_EBC(10 'BEAN/NAME')
         SMF120JM1_EBC(25 'BEAN/METHOD')
         SMF120JM2(5 'TIMES/INVOK')
         SMF120JM3('AVG/RSP/TIME' TPIC'9.999' )
         SMF120JM4('MAX/RSP/TIME' TPIC'9.999'  )
         SMF120JMQ('AVG/CPU/TIME' TPIC'9.999999' )
         SMF120JMR('MIN/CPU/TIME' TPIC'9.999999')
         SMF120JMS('MAX/CPU/TIME' TPIC'9.999999')
    
    

     

    Produce This SMF Report:

    
                                                Z/OS WEBSPHERE APPLICATION SMF 120 DATA
                                                 SUBTYPE 5 -- J2EE CONTAINER ACTIVITY
    
         TRANS TRANS                                                                         AVG   MAX    AVG      MIN      MAX
     SUB SERVE SERVER CONTAINE                      BEAN              BEAN            TIMES  RSP   RSP    CPU      CPU      CPU
     TYP HOST   NAME    NAME     CELL     NODE      NAME             METHOD           INVOK TIME  TIME    TIME     TIME     TIME
     ___ _____ ______ ________ ________ ________ __________ _________________________ _____ _____ _____ ________ ________ ________
    
       5 AWT4  AXZ4S1 Default  AXZ4     AXZ44    Tonam::Inf invoke:java.lang.String,j     1 0.014 0.014 0.013665 0.013665 0.013665
       5 AWT4  AXZ4S1 Default  AXZ4     AXZ44    Tonam::Inf invoke:java.lang.String,j     1 0.020 0.020 0.006287 0.006287 0.006287
       5 AWT4  AXZ4S1 Default  AXZ4     AXZ44    Tonam::Inf login:java.lang.String,ja     1 0.006 0.006 0.004206 0.004206 0.004206
       5 AWT4  AXZ4S1 Default  AXZ4     AXZ44    Tonam::Inf invoke:java.lang.String,j     1 0.004 0.004 0.003605 0.003605 0.003605
       5 AWT4  AXZ4S1 Default  AXZ4     AXZ44    Tonam::Inf invoke:java.lang.String,j     1 0.007 0.007 0.004831 0.004831 0.004831
       5 AWT4  AXZ4S1 Default  AXZ4     AXZ44    Tonam::Inf invoke:java.lang.String,j     2 0.005 0.010 0.005650 0.001264 0.010036
    
     *** GRAND TOTAL (     6 ITEMS)
    
    

    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