SMF Type 120 Record - Subtype 7
This table shows the record layout for type 120 SMF records
It's easy to report on SMF 120 data! (Jump to sample reports)
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.
Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word).
Segment descriptor (see record length field)
Bit meaning when set
0: New SMF record format
1: Subtypes used
3-6: Version indicators*
Record type 120(X'78')
Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer.
Date when the record was moved into the SMF buffer, in the form 0 cyydddF.
System identification (from the SMFPRMxx SID parameter)
Subsystem identification from SUBSYS parameter
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
Number of triplets in this record. A triplet is a set of three SMF fields (offset/length/number values) that defines a section of the record. The offset is the offset from the RDW.
1: Value is equal to the number of sessions +2
2 and 4: Value is equal to the number of classes +2.
Offset to product section from RDW.
Length of product section.
Number of product sections.
Offset to WebContainer activity section from RDW.
Length of WebContainer activity section.
Number of WebContainer activity sections.
Offset to HttpSessionManager activity section from RDW.
Length of HttpSessionManager activity section.
Number of HttpSessionManager activity sections.
Offset to WebApplication section from RDW.
Length of WebApplication section.
Number of WebApplication sections.
CB SMF version
Character codeset in which strings in the SMF record are encoded
Encode of numbers in the SMF record
Encoding of timestamps:
1: S390STCK 64: The time values are encoded in 64-bit S/390 Store Clock format.
Index of this record
Total number of records
Total number of triplets
There is one section per record. The WebContainer activity section contains information about each activity that occurred within one web container.
The WebSphere transaction server host name.
The WebSphere transaction server name.
The WebSphere transaction server instance name.
The WLM enclave token.
The identity of the activity.
The time the activity began in the server.
The time the activity ended.
There is one section per record. The HttpSessionManager section contains information about all (there may be zero or one) http sessions associated to one single activity.
"created Sessions": Number of http sessions that were created.
"invalidatedSessions": Number of http session that were invalidated.
"activeSessions": Number of http sessions that were referenced during this activity.
"sessionLifeTime": lifetime of the session in milliseconds. If "invalidatedSessions" > 0, this is the average lifetime (in milliseconds) of the invalidated http session.
There are multiple (0-n) sections per record. The WebApplication section contains information about all WebApplications involved in this activity.
The name of the WebApplication.
Number of servlet triplets in this web application section.
The following triplet appears 0-n times, once for each servlet section
Offset to servlet section from the beginning of this WebApplication section.
Length of servlet section.
Number of servlet sections.
There are multiple (0-n) sections per WebApplication section. The Servlet activity section contains information about each servlet associated with WebApplications involved in this activity.
The name of the servlet.
"responseTime": Response time in milliseconds.
"numErrors": The number of errors that were encountered during the servlet execution.
0: The servlet did not have to be loaded as a result of this request.
1: The servlet had to be loaded as the result of this request.
"loadedSince": Timestamp from System.currentTimeMillis() when the servlet was loaded, in HEX format.
Sample: The data as it appears in the record has the format: e7ef7c577c
which needs to be converted to a Java long: 996155348860
The Java long digits can be converted to java.util.Date:
Cpu time in microseconds.
The table above is based on the description provided by IBM in its "MVS Systems Management Facilities (SMF)" manual.
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!