








	*SMF Tools*

SMF Type 120 Record - Subtype 9

This table shows the record layout for type 120 SMF records
(WebSphere Appl - Network Deployment z/OS, Version 9.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

Subtype 9 - Network Deployment (z/OS) Request Activity Record (Version 9.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)

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.

SMF Type 120 Record -- WebSphere Appl - Network Deployment z/OS, Version 9.0
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
Individual header extension for subtype 9
24	18	SMF1209AA	4	binary	Subtype version number
28	1C	SMF1209AB	4	binary	Number of triplets
32	20	SMF1209AC	4	binary	Index of this record
36	24	SMF1209AD	4	binary	Total number of records
40	28	SMF1209AE	8	EBCDIC	Record continuation token
The following triplet appears for the Platform neutral server information section.
48	30	SMF1209AF	4	binary	The offset to the Platform neutral server information section
52	34	SMF1209AG	4	binary	The length of the Platform neutral server information section
56	38	SMF1209AH	4	binary	The number of Platform neutral server information sections
The following triplet appears for the z/OS® server information section.
60	3C	SMF1209AI	4	binary	The offset to the z/OS server information section
64	40	SMF1209AJ	4	binary	The length of the z/OS server information section
68	44	SMF1209AK	4	binary	The number of z/OS server information sections
The following triplet appears for the Platform neutral request information section.
72	48	SMF1209AL	4	binary	The offset to the Platform neutral request information section
76	4C	SMF1209AM	4	binary	The length of the Platform neutral request information section
80	50	SMF1209AN	4	binary	The number of Platform neutral request information sections
The following triplet appears for the z/OS request information section.
84	54	SMF1209AO	4	binary	The offset to the z/OS request information section
88	58	SMF1209AP	4	binary	The length of the z/OS request information section
92	5C	SMF1209AQ	4	binary	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.
96	60	SMF1209AR	4	binary	The offset to the z/OS formatted timestamps section
100	64	SMF1209AS	4	binary	The length of the z/OS formatted timestamps section
104	68	SMF1209AT	4	binary	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.
108	6C	SMF1209AU	4	binary	The offset to the Network data for HTTP, SIP and IIOP transports section
112	70	SMF1209AV	4	binary	The length of the Network data for HTTP, SIP and IIOP transports section
116	74	SMF1209AW	4	binary	The number of Network data for HTTP, SIP and IIOP transports sections
The following triplet appears for the Classification data section.
120	78	SMF1209AX	4	binary	The offset to the Classification data section
124	7C	SMF1209AY	4	binary	The length of the Classification data section
128	80	SMF1209AZ	4	binary	The number of Classification data sections
The following triplet appears for the Security data section.
132	84	SMF1209BA	4	binary	The offset to the Security data section
136	88	SMF1209BB	4	binary	The length of the Security data section
140	8C	SMF1209BC	4	binary	The number of Security data sections
The following triplet appears 0-30 times for the CPU usage breakdown sections.
144	90	SMF1209BD	4	binary	The offset to the CPU usage breakdown
148	94	SMF1209BE	4	binary	The length of the CPU usage breakdown section
152	98	SMF1209BF	4	binary	The number of CPU usage breakdown sections
The following triplet appears for the user data section.
156	9C	SMF1209FB	4	binary	The offset to the user data section
160	A0	SMF1209FC	4	binary	The length of the user data section
164	A4	SMF1209FD	4	binary	The number of user data sections
The following triplet appears for the user data section.
168	A8	SMF1209GB	4	binary	The offset to the asynchronous data section
172	AC	SMF1209GC	4	binary	The length of the asynchronous data section
176	B0	SMF1209GD	4	binary	The number of asynchronous data sections
180	B4	--	24	binary	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)
0	0	SMF1209BG	4	binary	The version of the Server information
4	4	SMF1209BH	8	EBCDIC	Cell short name
12	C	SMF1209BI	8	EBCDIC	Node short name
20	14	SMF1209BJ	8	EBCDIC	Cluster short name
28	1C	SMF1209BK	8	EBCDIC	Server short name
36	24	SMF1209BL	4	EBCDIC	Server or controller PID
40	28	SMF1209BM	1	binary	Product version level (the w in the format w.x.y.z)
41	29	SMF1209BN	1	binary	Product release level (the x in the format w.x.y.z)
42	2A	SMF1209BO	1	binary	Part of the product modification level (the y in the format w.x.y.z)
43	2B	SMF1209BP	1	binary	Part of the product modification level (the z in the format w.x.y.z)
44	2C	--	32	binary	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)
0	0	SMF1209BQ	4	binary	The version of the server information
4	4	SMF1209BR	8	EBCDIC	The name of the system on which the product is running (CVTSNAME)
12	C	SMF1209BS	8	EBCDIC	The name of the sysplex on which the product is running
20	14	SMF1209BT	8	EBCDIC	The job name for the controller
28	1C	SMF1209BU	8	EBCDIC	The job ID for the controller
36	24	SMF1209BV	8	binary	The STOKEN for the controller
44	2C	SMF1209BW	2	binary	The ASID for the controller
46	2E	--	2	binary	Reserved for alignment
48	30	SMF1209BX	20	binary	The cluster UUID
68	44	SMF1209BY	20	binary	The server UUID
88	58	SMF1209BZ	8	EBCDIC	The daemon group name
96	60	SMF1209CA	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 SMF1209FJ is turned on to indicate that the zeros in this field are not valid GMT offsets.
100	64	SMF1209CB	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 SMF1209FJ is turned on to indicate that the zeros in this field are not valid GMT offsets.
104	68	SMF1209CC	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 SMF1209FJ is turned on to indicate that the zeros in this field are not valid GMT offsets.
112	70	SMF1209CD	8	binary	The system GMT offset. The value is obtained from the CVTLDTO API.
120	78	SMF1209CE	8	EBCDIC	The service level
120	78	SMF1209HV	16	EBCDIC	The service level (expanded)
136	88	--	20	binary	Reserved
Platform neutral request information section. This section provides request information that is not platform specific.(Offset from beginning of record: SMF1209AL)
0	0	SMF1209CF	4	binary	The version of the request information
4	4	SMF1209CG	4	binary	The PID of the dispatch servant
8	8	SMF1209CH	8	binary	The ID of the dispatched task. This value is returned from pthread_self.
16	10	SMF1209CI	8	binary	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.
24	18	SMF1209CJ	4	binary	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.
28	1C	--	4	binary	Reserved
32	20	SMF1209CK	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 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
36	24	--	32	binary	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)
0	0	SMF1209CL	4	binary	The version of the request information
4	4	SMF1209CM	16	S390STCKE	The time that the request was received
20	14	SMF1209CN	16	S390STCKE	The time that the request was added to the queue
36	24	SMF1209CO	16	S390STCKE	The time that the request was dispatched
52	34	SMF1209CP	16	S390STCKE	The time that the dispatch completed
68	44	SMF1209CQ	16	S390STCKE	The time that the controller finished processing the request response
84	54	SMF1209CR	8	EBCDIC	The job name for the dispatch servant
92	5C	SMF1209CS	8	EBCDIC	The job ID for the dispatch servant
100	64	SMF1209CT	8	binary	The STOKEN for the dispatch servant
108	6C	SMF1209CU	2	binary	The ASID for the dispatch servant
110	6E	--	2	binary	Reserved for alignment
112	70	SMF1209CV	4	binary	The address of the dispatch TCB
116	74	SMF1209CW	16	binary	The TTOKEN for the dispatch TCB
132	84	SMF1209CX	8	binary	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.
140	8C	SMF1209CY	8	binary	The enclave token
148	94	SMF1209CZ	32	Reserved
180	B4	SMF1209DA	8	binary	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.
188	BC	SMF1209DB	8	binary	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.
196	C4	SMF1209DC	8	binary	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.
204	CC	SMF1209DD	8	binary	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.
212	D4	SMF1209DE	8	binary	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.
220	DC	SMF1209DF	8	binary	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.
228	E4	SMF1209DG	4	binary	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.
232	E8	SMF1209DH	8	binary	The amount of CPU time that was used by the enclave as reported by the CPUTIME parameter of the IWM4EDEL API
240	F0	SMF1209DI	8	binary	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.
248	F8	SMF1209DJ	4	binary	The enclave delete zAAP normalization factor as reported by the ZAAPNFACTOR parameter of the IWM4EDEL API.
252	FC	--	4	binary	Reserved
256	100	SMF1209DK	8	EBCDIC	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.
264	108	SMF1209DL	8	EBCDIC	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.
272	110	SMF1209DM	8	EBCDIC	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.
280	118	SMF1209DN	8	EBCDIC	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.
288	120	SMF1209DO	4	EBCDIC	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.
292	124	SMF1209DP	12	Reserved	for alignment
304	130	SMF1209DQ	73	binary	The global transaction ID (GTID) value
377	179	--	3	binary	Reserved for alignment
380	17C	SMF1209DR	4	binary	The dispatch timeout value
384	180	SMF1209DS	8	EBCDIC	The transaction class, if one is being used
392	188	SMF1209DT	4	binary	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
396	18C	--	32	binary	Reserved
428	1AC	SMF1209FR	4	binary	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.
432	1B0	SMF1209FS	4	binary	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.
436	1B4	SMF1209FT	4	binary	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.
440	1B8	SMF1209FU	4	binary	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.
444	1BC	SMF1209FV	4	binary	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.
448	1C0	SMF1209FW	4	binary	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.
452	1C4	SMF1209FX	4	binary	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.
456	1C8	SMF1209FY	4	binary	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.
460	1CC	SMF1209FZ	4	binary	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.
464	1D0	SMF1209GA	8	EBCDIC	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.
472	1D8	SMF1209GH	4	binary	Length of obtained affinity RNAME
476	1DC	SMF1209GI	128	EBCDIC	Obtained affinity RNAME
604	25C	SMF1209GJ	4	binary	Length of routing affinity RNAME
608	260	SMF1209GK	128	EBCDIC	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)
0	0	SMF1209EA	26	EBCDIC	The time that the request was received
26	1A	SMF1209EB	26	EBCDIC	The time that the request was added to the WLM queue
52	34	SMF1209EC	26	EBCDIC	The time that the request was dispatched in the servant
78	4E	SMF1209ED	26	EBCDIC	The time that the dispatch completed in the servant
104	68	SMF1209EE	26	EBCDIC	The time that the controller finished processing the request
130	82	--	2	binary	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)
0	0	SMF1209EF	4	binary	The version of the network data
4	4	SMF1209EG	8	binary	The size of the request, in bytes, that was received from the client
12	C	SMF1209EH	8	binary	The size of the response, in bytes, that is sent back to the client
20	14	SMF1209EI	4	binary	The target port for the request. A value of -1 indicates that local communications was used.
24	18	SMF1209EJ	4	binary	The length of the origin string
28	1C	SMF1209EK	128	EBCDIC	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.
156	9C	--	32	binary	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)
0	0	SMF1209EL	4	binary	The version of the classification data
4	4	SMF1209EM	4	binary	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
8	8	SMF1209EN	4	binary	The length of the data
12	C	SMF1209EO	128	EBCDIC	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)
0	0	SMF1209EP	4	binary	The version of the security data
4	4	SMF1209EQ	4	binary	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
8	8	SMF1209ER	4	binary	The length of the identity
12	C	SMF1209ES	64	EBCDIC	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)
0	0	SMF1209ET	4	binary	The version of the CPU usage data
4	4	SMF1209EU	4	binary	The data type: 1 indicates that the data comes from the EJB container 2 indicates that the data comes from the Web container
8	8	SMF1209EV	8	binary	The amount of CPU time, in microseconds, that the item, such as an EJB or a servlet, spent in dispatch
16	10	SMF1209FI	8	binary	The elapsed time, in milliseconds, that is spent processing the item, such as an EJB or servlet
24	18	SMF1209EW	4	binary	How many times the item, such as an EJB or a servlet, was executed during the dispatch of this request
28	1C	SMF1209EX	4	binary	The length of string 1
32	20	SMF1209EY	256	EBCDIC	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
288	120	SMF1209EZ	4	binary	The length of string 2
292	124	SMF1209FA	256	EBCDIC	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)
0	0	SMF1209FE	4	binary	The version of the User data section
4	4	SMF1209FF	4	binary	The user data type. Types 65535 and lower are reserved for IBM® use.
8	8	SMF1209FG	4	binary	The length of the User data section
12	C	SMF1209FH	2048	binary	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)
0	0	SMF1209GM	4	binary	The version of the asynchronous data section.
4	4	SMF1209GL	16	S390STCKE	The time that the execution context was created.
20	14	SMF1209GN	16	S390STCKE	The time that the execution started.
36	24	SMF1209GO	16	S390STCKE	The time that the execution completed.
52	34	SMF1209GP	4	binary	The servant process ID.
56	38	SMF1209GQ	8	EBCDIC	The servant job name.
64	40	SMF1209GR	8	EBCDIC	The servant job ID.
72	48	SMF1209GS	8	binary	The servant token.
80	50	SMF1209GT	2	binary	The servant ASID. 82 52 * 2 The reserved alignment.
84	54	SMF1209GU	8	binary	The execution context task ID.
92	5C	SMF1209GV	4	binary	The execution context TCB address.
96	60	SMF1209GW	16	binary	The execution context TCB TToken.
112	70	SMF1209GX	8	binary	The dispatch task ID.
120	78	SMF1209GY	4	binary	The dispatch TCB address.
124	7C	SMF1209GZ	16	binary	The dispatch TCB TToken.
140	8C	SMF1209HA	8	binary	The execution context enclave token.
148	94	SMF1209HB	8	binary	The dispatch enclave token.
156	9C	SMF1209HC	8	EBCDIC	The transaction class used to create the enclave.
164	A4	SMF1209HD	4	binary	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.
168	A8	SMF1209HG	8	binary	The enclave CPU so far.
176	B0	SMF1209HH	8	binary	The enclave zAAP CPU so far.
184	B8	SMF1209HI	8	binary	The enclave zAAP eligible on the CP.
192	C0	SMF1209HJ	8	binary	The enclave zIIP on the CPU so far.
200	C8	SMF1209HK	8	binary	The enclave zIIP quality time so far.
208	D0	SMF1209HL	8	binary	The Enclave zIIP CPU so far.
216	D8	SMF1209HM	4	binary	The zAAP normalization factor. 220 DC * 4 The reserved alignment.
224	E0	SMF1209HN	8	binary	The dispatch CPU.
232	E8	SMF1209HO	8	binary	The dispatch CPU offload to non-standard CPs, for example zAAP or zIIP.
240	EC	SMF1209HP	4	binary	Length of the work class name.
244	F4	SMF1209HQ	128	EBCDIC	The work package or class name.
372	174	SMF1209HR	4	binary	The length of the work manager name.
376	178	SMF1209HS	128	EBCDIC	The work manager name.
504	1F8	SMF1209HT	4	binary	The identity length.
508	1FC	SMF1209HU	64	EBCDIC	The identity.
572	23C	--	16	binary	Reserved.

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

Spectrum SMF Writer - the 4GL SMF Report Writer.

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.