|
SMF Type 120 Record - Subtype 10This 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 9: Request Activity record 10: Outbound Request record 11: Liberty server log information about HTTP requests |
24 | 18 | SMF120AAA | 4 | binary | Subtype version number
|
28 | 1C | SMF120AAB | 4 | binary | Number of triplets
|
32 | 20 | SMF120AAC | 4 | binary | Index of this record
|
36 | 24 | SMF120AAD | 4 | binary | Total number of records
|
40 | 28 | SMF120AAE | 8 | EBCDIC | Record continuation token
|
48 | 30 | SMF120AAF | 4 | binary | The offset to the Platform neutral server information section
|
52 | 34 | SMF120AAG | 4 | binary | The length of the Platform neutral server information section
|
56 | 38 | SMF120AAH | 4 | binary | The number of Platform neutral server information sections
|
60 | 3C | SMF120AAI | 4 | binary | The offset to the z/OSserver information section
|
64 | 40 | SMF120AAJ | 4 | binary | The length of the z/OSserver information section
|
68 | 44 | SMF120AAK | 4 | binary | The number of z/OSserver information sections
|
72 | 48 | SMF120AAL | 4 | binary | The offset to the Outbound request information section
|
76 | 4C | SMF120AAM | 4 | binary | The length of the Outbound request information section
|
80 | 50 | SMF120AAN | 4 | binary | The number of Outbound request information sections
|
84 | 54 | SMF120AAR | 4 | binary | The offset to the WOLA outbound request type specific information section
|
88 | 58 | SMF120AAS | 4 | binary | The length of the WOLA outbound request type specific information section
|
92 | 5C | SMF120AAT | 4 | binary | The number of WOLA outbound request type specific information sections
|
96 | 60 | SMF120AAU | 4 | Binary | The offset to the outbound request transaction context section
|
100 | 64 | SMF120AAV | 4 | binary | The length of the outbound request transaction context section
|
104 | 68 | SMF120AAW | 4 | binary | The number of outbound request transaction context sections
|
108 | 6C | SMF120AAX | 4 | binary | The offset to the outbound request security context section.
|
112 | 70 | SMF120AAY | 4 | binary | The length of the outbound request security context section.
|
116 | 74 | SMF120AAZ | 4 | binary | The number of outbound request security context sections
|
120 | 78 | SMF120AA1 | 4 | binary | The offset to the outbound request CICS context section
|
124 | 7C | SMF120AA2 | 4 | binary | The length of the outbound request CICS context section
|
128 | 80 | SMF120AA3 | 4 | binary | The number of outbound request CICS context sections
|
132 | 84 | SMF120AA4 | 4 | binary | The offset to the OTMA outbound request type specific section
|
136 | 88 | SMF120AA5 | 4 | binary | The length of the OTMA outbound request type specific section
|
140 | 8C | SMF120AA6 | 4 | binary | The number of OTMA outbound request type specific sections
|
144 | 90 | -- | 60 | binary | Reserved
|
This section contains information about the server that handled the request. | |||||
0 | 0 | SMF120ABG | 4 | binary | The version of the Server information
|
4 | 4 | SMF120ABH | 8 | EBCDIC | Cell short name
|
12 | C | SMF120ABI | 8 | EBCDIC | Node short name
|
20 | 14 | SMF120ABJ | 8 | EBCDIC | Cluster short name
|
28 | 1C | SMF120ABK | 8 | EBCDIC | Server short name
|
36 | 24 | SMF120ABL | 4 | EBCDIC | Server or controller PID
|
40 | 28 | SMF120ABM | 1 | binary | Product version level (the w in the format w.x.y.z)
|
41 | 29 | SMF120ABN | 1 | binary | Product release level (the x in the format w.x.y.z)
|
42 | 2A | SMF120ABO | 1 | binary | Part of the product modification level (the y in the format w.x.y.z)
|
43 | 2B | SMF120ABP | 1 | binary | Part of the product modification level (the z in the format w.x.y.z)
|
44 | 2C | -- | 32 | binary | Reserved
|
This section contains information about the controller and servant where the request was dispatched. One of these sections in included in each record. | |||||
0 | 0 | SMF120ABQ | 4 | binary | The version of the server information
|
4 | 4 | SMF120ABR | 8 | EBCDIC | The name of the system on which the product is running (CVTSNAME)
|
12 | C | SMF120ABS | 8 | EBCDIC | The name of the sysplex on which the product is running
|
20 | 14 | SMF120ABT | 8 | EBCDIC | The job name for the controller
|
28 | 1C | SMF120ABU | 8 | EBCDIC | The job ID for the controller
|
36 | 24 | SMF120ABV | 8 | binary | The STOKEN for the controller
|
44 | 2C | SMF120ABW | 2 | binary | The ASID for the controller
|
46 | 2E | -- | 2 | binary | Reserved for alignment
|
48 | 30 | SMF120ABX | 20 | binary | The cluster UUID
|
68 | 44 | SMF120ABY | 20 | binary | The server UUID
|
88 | 58 | SMF120ABZ | 8 | EBCDIC | The daemon group name
|
96 | 60 | SMF120ACA | 4 | binary | 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 SMF120AFJ is turned on to indicate that the zeros in this field are not valid GMT offsets.
|
100 | 64 | SMF120ACB | 4 | binary | 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 SMF120AFJ is turned on to indicate that the zeros in this field are not valid GMT offsets.
|
104 | 68 | SMF120ACC | 8 | binary | 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 SMF120AFJ is turned on to indicate that the zeros in this field are not valid GMT offsets.
|
112 | 70 | SMF120ACD | 8 | binary | The system GMT offset. The value is obtained from the CVTLDTO API.
|
120 | 78 | SMF120ACE | 8 | EBCDIC | The service level
|
120 | 78 | SMF120AHV | 16 | EBCDIC | The service level (expanded)
|
136 | 88 | -- | 20 | binary | Reserved
|
This section contains information about the outbound request. One of these sections is included in each record. | |||||
0 | 0 | SMF120ACF | 4 | binary | The version of the request information
|
4 | 4 | SMF120ACG | 4 | binary | The PID of the dispatch servant
|
8 | 8 | SMF120ACH | 8 | binary | The ID of the dispatched task. This value is returned from pthread_self.
|
16 | 10 | SMF120ACK | 4 | binary | The type of request that was processed:
0 indicates that the request type is not known 1 indicates that the request was an WOLA request 2 indicates that the request was an OTMA request |
20 | 14 | -- | 4 | binary | Reserved
|
24 | 18 | SMF120ACR | 8 | EBCDIC | The job name for the dispatch servant
|
32 | 20 | SMF120ACS | 8 | EBCDIC | The job ID for the dispatch servant
|
40 | 28 | SMF120ACT | 8 | binary | The STOKEN for the dispatch servant
|
48 | 30 | SMF120ACU | 2 | binary | The ASID for the dispatch servant
|
50 | 32 | -- | 2 | binary | Reserved for alignment
|
52 | 34 | SMF120ACV | 4 | binary | The address of the dispatch TCB
|
56 | 38 | SMF120ACW | 16 | binary | The TTOKEN for the dispatch TCB
|
72 | 48 | SMF120ACY | 8 | binary | The enclave token
|
80 | 50 | SMF120AD1 | 8 | binary | The number of bytes sent
|
88 | 58 | SMF120AD2 | 8 | binary | The number of response bytes
|
96 | 60 | SMF120AD3 | 16 | S390STCKE | The time the request went outbound
|
112 | 70 | SMF120AD4 | 16 | S390STCKE | The time the outbound request returned
|
128 | 80 | -- | 32 | binary | Reserved
|
This section contains specific information about the WOLA outbound request. There are zero to one of these sections included in each record. | |||||
0 | 0 | SMF120AD5 | 4 | binary | The version of the WOLA outbound request type specific section
|
4 | 4 | SMF120AD6 | 12 | EBCDIC | The register name the outbound request is going to
|
16 | 10 | SMF120AD7 | 256 | EBCDIC | The service name the outbound request is going to
|
272 | 110 | SMF120AD8 | 256 | binary | The outbound request correlator context. This correlator context also ends up in the CICS SMF 110 records.
|
528 | 210 | SMF120AD9 | 24 | Reserved | |
This section contains transaction information about the WOLA outbound request. There are zero to one of these sections included in each record. | |||||
0 | 0 | SMF120ADA | 4 | binary | The version of the outbound request transaction context section
|
4 | 4 | SMF120ADB | 140 | binary | The transactional XID
|
144 | 90 | SMF120ADC | 24 | reserved | |
This section contains security information about the WOLA outbound request. There are zero to one of these sections included in each record. | |||||
0 | 0 | SMF120ADD | 4 | binary | The version of the outbound request security context section
|
4 | 4 | SMF120ADE | 8 | EBCDIC | The security context
|
12 | C | SMF120ADF | 28 | -- | Reserved
|
This section contains the CICS context associated with the WOLA outbound request. There are zero to one of these sections included in each record. | |||||
0 | 0 | SMF120ADG | 4 | binary | The version of the outbound request CICScontext section
|
4 | 4 | SMF120ADH | 80 | binary | The CICScontext
|
84 | 54 | SMF120ADI | 28 | -- | Reserved
|
This section contains the OTMA context associated with the WOLA outbound request. There are zero to one of these sections included in each record. | |||||
0 | 0 | SMF120ADJ | 4 | binary | The version of the OTMA outbound request type specific section
|
4 | 4 | SMF120ADK | 12 | EBCDIC | The OTMA register name of the outbound request
|
16 | 10 | SMF120ADL | 256 | EBCDIC | The OTMA service name of the outbound request
|
272 | 110 | SMF120ADM | 8 | EBCDIC | The OTMA IMStransaction name of the outbound request
|
280 | 118 | SMF120ADN | 8 | EBCDIC | The OTMA IMSgroup id of the outbound request
|
288 | 120 | SMF120ADO | 16 | EBCDIC | The OTMA IMSserver name of the outbound request
|
304 | 130 | SMF120ADP | 24 | Reserved |
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