|
SMF Type 120 Record - Subtype 1This 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. Plus, Spectrum SMF Writer can export SMF data as comma delimited files to use on your PC.
|
Offset (Dec.) | Offset (Hex) | Name | Length | Format | Description |
0 | 0 | SMF120LEN | 2 | binary | Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word).
|
2 | 2 | SMF120SEG | 2 | binary | Segment descriptor (see record length field)
|
4 | 4 | SMF120FLG | 1 | binary | Bit meaning when set
0: New SMF record format 1: Subtypes used 2: Reserved 3-6: Version indicators* 7: Reserved |
5 | 5 | SMF120RTY | 1 | binary | Record type 120(X'78')
|
6 | 6 | SMF120TME | 4 | binary | Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer.
|
10 | A | SMF120DTE | 4 | packed | Date when the record was moved into the SMF buffer, in the form 0 cyydddF.
|
14 | E | SMF120SID | 4 | EBCDIC | System identification (from the SMFPRMxx SID parameter)
|
18 | 12 | SMF120SSI | 4 | EBCDIC | Subsystem identification from SUBSYS parameter
|
22 | 16 | SMF120RST | 2 | binary | 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 |
24 | 18 | SMF120TRN | 4 | binary | 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.
Subtypes: 1: Value is equal to the number of sessions +2 2 and 4: Value is equal to the number of classes +2. |
28 | 1C | SMF120PRS | 4 | binary | Offset to product section from RDW.
|
32 | 20 | SMF120PRL | 4 | binary | Length of product section.
|
36 | 24 | SMF120PRN | 4 | binary | Number of product sections.
|
40 | 28 | SMF120SAS | 4 | binary | Offset to server activity section from RDW
|
44 | 2C | SMF120SAL | 4 | binary | Length of server activity section
|
48 | 30 | SMF120SAN | 4 | binary | Number of server activity sections
|
52 | 34 | SMF120CSS | 4 | binary | Offset to communication session section from RDW
|
56 | 38 | SMF120CSL | 4 | binary | Length of communication session section
|
60 | 3C | SMF120CSN | 4 | binary | Number of communication session sections
|
64 | 40 | SMF120JHS | 4 | binary | Offset to JVM heap section from RDW
|
68 | 44 | SMF120JHL | 4 | binary | Length of JVM heap section
|
72 | 48 | SMF120JHN | 4 | binary | Number of jvm heap sections
|
40 | 28 | SMF120SIS | 4 | binary | Offset to server interval section from RDW
|
44 | 2C | SMF120SIL | 4 | binary | Length of server interval section
|
48 | 30 | SMF120SIN | 4 | binary | Number of server interval sections
|
52 | 34 | SMF120SRS | 4 | binary | Offset to server region section from RDW
|
56 | 38 | SMF120SRL | 4 | binary | Length of server region section
|
60 | 3C | SMF120SRN | 4 | binary | Number of server region sections
|
40 | 28 | SMF120JA1 | 4 | binary | Offset to J2EE container activity section from RDW
|
44 | 2C | SMF120JA2 | 4 | binary | Length of J2EE container activity section
|
48 | 30 | SMF120JA3 | 4 | binary | Number of J2EE container activity sections
|
52 | 34 | SMF120JAS | 4 | binary | Offset to bean section from RDW
|
56 | 38 | SMF120JAL | 4 | binary | Length of bean section
|
60 | 3C | SMF120JAN | 4 | binary | Number of bean sections
|
40 | 28 | SMF120JI1 | 4 | binary | Offset to J2EE container interval section from RDW
|
44 | 2C | SMF120JI2 | 4 | binary | Length of J2EE container interval section
|
48 | 30 | SMF120JI3 | 4 | binary | Number of J2EE container interval sections
|
52 | 34 | SMF120JIS | 4 | binary | Offset to bean section from RDW
|
56 | 38 | SMF120JIL | 4 | binary | Length of bean section
|
60 | 3C | SMF120JIN | 4 | binary | Number of bean sections
|
40 | 28 | SMF120WA1 | 4 | binary | Offset to WebContainer activity section from RDW.
|
44 | 2C | SMF120WA2 | 4 | binary | Length of WebContainer activity section.
|
48 | 30 | SMF120WA3 | 4 | binary | Number of WebContainer activity sections.
|
52 | 34 | SMF120WA4 | 4 | binary | Offset to HttpSessionManager activity section from RDW.
|
56 | 38 | SMF120WA5 | 4 | binary | Length of HttpSessionManager activity section.
|
60 | 3C | SMF120WA6 | 4 | binary | Number of HttpSessionManager activity sections.
|
64 | 40 | SMF120WA7 | 4 | binary | Offset to WebApplication section from RDW.
|
68 | 44 | SMF120WA8 | 4 | binary | Length of WebApplication section.
|
72 | 48 | SMF120WA9 | 4 | binary | Number of WebApplication sections.
|
40 | 28 | SMF120WI1 | 4 | binary | Offset to WebContainer interval section from RDW.
|
44 | 2C | SMF120WI2 | 4 | binary | Length of WebContainer interval section.
|
48 | 30 | SMF120WI3 | 4 | binary | Number of WebContainer interval sections.
|
52 | 34 | SMF120WI4 | 4 | binary | Offset to HttpSessionManager interval section from RDW.
|
56 | 38 | SMF120WI5 | 4 | binary | Length of HttpSessionManager interval section.
|
60 | 3C | SMF120WI6 | 4 | binary | Number of HttpSessionManager interval sections.
|
64 | 40 | SMF120WI7 | 4 | binary | Offset to WebApplication section from RDW.
|
68 | 44 | SMF120WI8 | 4 | binary | Length of WebApplication section.
|
72 | 48 | SMF120WI9 | 4 | binary | Number of WebApplication sections.
|
0 | 0 | SMF120MFV | 4 | binary | CB SMF version
|
4 | 4 | SMF120COD | 8 | EBCDIC | Character codeset in which strings in the SMF record are encoded
|
12 | C | SMF120END | 4 | binary | Encode of numbers in the SMF record
|
16 | 10 | SMF120TSF | 4 | binary | Encoding of timestamps:
1: S390STCK 64: The time values are encoded in 64-bit S/390 Store Clock format. |
20 | 14 | SMF120IXR | 4 | binary | Index of this record
|
24 | 18 | SMF120NRC | 4 | binary | Total number of records
|
28 | 1C | SMF120NTR | 4 | binary | Total number of triplets
|
The server activity SMF record is used to record activity that is running inside a WebSphere Application Server for z/OS. This record can be used to perform basic charge-back accounting and to profile your applications to determine, in detail, what is happening inside the WebSphere Application Server transaction server. A single record is created for each activity that is run inside a server or server instance. If the activity runs in multiple servers, then a record is written for each server. | |||||
0 | 0 | SMF120HNM | 64 | EBCDIC | WebSphere Application Server for z/OS transaction server host name
|
64 | 40 | SMF120SNA | 8 | EBCDIC | WebSphere Application Server for z/OS transaction server name
|
72 | 48 | SMF120INA | 8 | EBCDIC | WebSphere Application Server for z/OS transaction server instance name
|
80 | 50 | SMF120SNM | 4 | binary | Total number of server servants that were involved to process this activity. If applicable, up to the first five server servant address space IDs are listed within the next five fields.
|
84 | 54 | SMF120SR1 | 4 | binary | The specific WebSphere Application Server for z/OS transaction server instance server servant where the request ran
|
88 | 58 | SMF120SR2 | 4 | binary | The specific WebSphere Application Server for z/OS transaction server instance server servant where the request ran
|
92 | 5C | SMF120SR3 | 4 | binary | The specific WebSphere Application Server for z/OS transaction server instance server servant where the request ran
|
96 | 60 | SMF120SR4 | 4 | binary | The specific WebSphere Application Server for z/OS transaction server instance server servant where the request ran
|
100 | 64 | SMF120SR5 | 4 | binary | The specific WebSphere Application Server for z/OS transaction server instance server servant where the request ran
|
104 | 68 | SMF120CRE | 8 | EBCDIC | The user credentials under which the activity began. Due to deferred security authentication, the user credentials assigned to the request when it first reaches the server will often be the unauthenticated guest ID, and not the ID of the authenticated user that submitted the request.
|
112 | 70 | SMF120ATY | 4 | binary | Type of activity that this record references:
1: Method request: This record refers to a method request that is not part of a global transaction. 2: Transaction: This record refers to a transaction. |
116 | 74 | SMF120AID | 20 | HEX | Identity of the activity
|
136 | 88 | SMF120WLM | 8 | HEX | WLM enclave token
|
144 | 90 | SMF120AST | 8 | binary | Activity start time
|
152 | 98 | -- | 8 | binary | reserved
|
160 | A0 | SMF120AET | 8 | binary | Activity stop time
|
168 | A8 | -- | 8 | binary | reserved
|
176 | B0 | SMF120NIM | 4 | binary | Number of input methods
|
180 | B4 | SMF120NGT | 4 | binary | Number of global transactions that were started in the server servant
|
184 | B8 | SMF120NLT | 4 | binary | Number of local transactions that were started in the server servant
|
188 | BC | SMF120J2E | 4 | binary | J2EE server
|
192 | C0 | SMF120CEL | 8 | EBCDIC | WebSphere Application Server for z/OS cell name
|
200 | C8 | SMF120NOD | 8 | EBCDIC | WebSphere Application Server for z/OS node name
|
208 | D0 | SMF120WCP | 8 | binary | Total CPU time accumulated by the WLM enclave. TOD clock format (bit 51 = microseconds).
|
There are zero, one, or multiple sections per record. The Communications session section contains information about each communication session. | |||||
0 | 0 | SMF120CSH | 8 | HEX | Communications session handle
|
8 | 8 | SMF120CSA | 64 | EBCDIC | Communications session address
|
72 | 48 | SMF120CSO | 4 | binary | Communications session optimization
1: Local communications session: The session is a local OS/390 optimized communications session. 2: Remote communications session: The session is a remote communications session. 3: Remote encrypted (SSL) 4: Remote within sysplex. 5: HTTP session. 6: HTTP encrypted session. 7. Message-driven bean session |
76 | 4C | SMF120SDR | 4 | binary | Data received; the number of bytes received by the server. 'FFFFFFFF'X indicates the 4-byte field is too small. Use SMF120CDR, an 8-byte field, instead.
|
80 | 50 | SMF120SDT | 4 | binary | Data transferred; the number of bytes transferred from the server back to the client. 'FFFFFFFF'X indicates the 4-byte field is too small. Use SMF120CDT, an 8-byte field, instead.
|
84 | 54 | SMF120CDR | 8 | binary | Data received; the number of bytes received by the server.
|
92 | 5C | SMF120CDT | 8 | binary | Data transferred; the number of bytes transferred from the server back to the client.
|
There are zero, one, or multiple sections per record. The JVM heap section contains information about the heap in each server servant. The information in the JVM heap section comes from the QueryGCStatus() JNI function. | |||||
0 | 0 | SMF120JHA | 4 | binary | Servant address space ID
|
4 | 4 | SMF120JHH | 4 | binary | The heap for which the following data applies.
|
8 | 8 | SMF120JHC | 4 | binary | The total number of allocation failures on this heap or, if querying shared storage, the subpool identifier. A negative value indicates the information is for the shared memory page pool.
|
12 | C | SMF120JHF | 8 | binary | The total number of free bytes in the heap/subpool/page pool.
|
20 | 14 | SMF120JHT | 8 | binary | The total number of bytes in the heap, subpool, or page pool.
|
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!
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')
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)
Home |
Products |
Prices |
Documentation |
30-Day Trials |
Customer Reviews |
Company
| FAQ
| Sample Reports
| SMF Records
Send Your Comments or Questions