SMF Type 120 Record - Subtype 6
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 J2EE container interval section from RDW
Length of J2EE container interval section
Number of J2EE container interval sections
Offset to bean section from RDW
Length of bean section
Number of bean 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: S390STCK64: 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
The J2EE container interval section contains information about each activity that occurred within one J2EE container in the specified interval.
There is one section per record.
The WebSphere Application Server for z/OS® transaction server host name.
The WebSphere Application Server for z/OS transaction server name.
The WebSphere Application Server for z/OS transaction server instance name.
The WebSphere Application Server for z/OS container name. Note: This is hardcoded to 'Default' for the 4.0.1 time frame.
The time that the sample began in the server.
The time that the sample ended.
There are multiple sections per record.
AMCName of the bean activated by the container. Note: If the length of the AMCName exceeds 256 DBCS characters (512 bytes), the rightmost 256 characters are recorded.
UUID based AMC name
The bean's type. 2: Stateless session bean. 3: Stateful session bean. 4: BMP entity bean. 5: CMP entity bean. 6. Message-driven bean.
The bean's reentrance policy. 0: Not reentrant within transaction. 1: Reentrant within transaction.
Number of method triplets in this bean section
The following triplet appears 0-n times; once for each bean method section.
Offset to bean method section from the beginning of this bean section
Length of bean method section
Number of bean method sections
There are multiple sections per bean section. The bean method section contains information about all methods of beans involved in this activity.
The name of the method including its signature in its externalized, human-readable form. If the length of the method exceeds 512 DBCS characters (1024 bytes), the leftmost 512 characters are recorded.
The number of times the method was invoked during the activity.
Average response time. The response time is measured in milliseconds (the granularity provided by the JVM - hopefully, it will be equal to 0 in most cases).
Maximum response time. The response time is measured in milliseconds.
The bean method's transaction policy. Values from com.ibm.websphere.csi. TransactionAttribute.java:
List of ejbRoles associated with the method. Separator character: ";" (semicolon). If the length of the concatenated string exceeds 256 characters (512 bytes), only its leftmost 256 characters are recorded.
ejbLoad: # of invocations
ejbLoad: avg execution time
ejbLoad: max execution time
ejbStore: # of invocations
ejbStore: avg execution time
ejbStore: max execution time
ejbActivate: # of invocations
ejbActivate: avg execution time
ejbActivate: max execution time
ejbPassivate: # of invocations
ejbPassivate: avg execution time
ejbPassivate: max execution time
Average cpu time in microseconds.
Minimum cpu time in microseconds.
Maximum 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!