(ZOS) Collecting job-related information with the System Management Facility (SMF)
SMF can be enabled to collect and record system and work-related information on the WebSphere for z/OS system. This information can be used to bill users, report system reliability, analyze the configuration, schedule work, identify system resource usage, and perform other performance-related tasks that our organization may require.
We can enable SMF recording for:
- Capacity planning, to determine:
- How many transactions have run?
- What is the average and maximum completion time for methods running on each server?
- How many clients are attached to each server instance? Of these clients, how many are active?
- Application profiling:
- To show an application broken down into its component parts.
- To provide timing information on the application's component parts.
- Error reporting:
- To detect and record soft failures (those generated through an exception or those that are performance-related).
- To use this error information to trigger an event that will cause an action to occur once a threshold has been reached.
Tasks
- Read Enable SMF recording for information on enabling SMF type 120 records.
- Read View the output data set for steps on viewing the data you record.
- Read Disable SMF recording for WAS for steps on disabling SMF data collection.
Example
The SMF Browser available on the WebSphere for z/OS download site is able to display record type 120. To download the SMF Browser go to: https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=zosos390. For further information on the SMF Browser, download the browser package and read the associated documentation.
The following example shows sample output from the SMF Browser. The example features subtype 7 and subtype 8, in that order.
Record#: 14; Type: 120; Size: 820; Date: Fri Nov 23 04:54:17 EST 2001; SystemID: SY1; SubsystemID: WAS; Flag: 94; Subtype: 7 (WEB CONTAINER ACTIVITY); # Triplets: 4; Triplet #: 1; offset: 76; length: 32; count: 1; Triplet #: 2; offset: 108; length: 140; count: 1; Triplet #: 3; offset: 264; length: 556; count: 1; Triplet #: 1; Type: ProductSection; Version: 1; Codeset: Unicode; Endian: 1; TimeStampFormat: 1 (S390STCK64); IndexOfThisRecord: 1; Total # records: 1; Total # triplets: 4; Triplet #: 2; Type: WebContainerActivitySection; HostName : PLEX1; ServerName : BBOASR4; ServerInstanceName: BBOASR4A; WlmEnclaveToken * 00000020 00000242 -------- -------- * ^... * p1047 ActivityID * b6c7a7b7 14e9bc85 000000b0 00000007 * 0926306b -------- -------- -------- *,............ *Cp1047 ActivityStartTime * b6c7a7b7 14e9bc85 40404040 40404040 * ActivityStopTime * b6c7a7b7 53a8a645 40404040 40404040 * Triplet #: 3; Type: HttpSessionManagerActivitySection; # http sessions created: 0; # http sessions invalidated: 0; # http sessions active: 0; Average session life time: 0 [sec*10**-3]; Triplet #: 4; Type: WebApplicationActivitySection; Name: PolicyIVP-localhost_1; # Servlets: 1; Triplet #: 4.1; offset: 272; length: 284; count: 1; Triplet #: 4.1; Type: ServletActivitySection; Name: SimpleFileServlet; ResponseTime: 48 [sec*10**-3]; # errors: 0; Loaded by this request: 0; Loaded since (raw): ea54948e0d; Loaded since: Thu Nov 22 10:02:49 EST 2001; Record#: 72; Type: 120; Size: 1744; Date: Fri Nov 23 05:01:02 EST 2001; SystemID: SY1; SubsystemID: WAS; Flag: 94; Subtype: 8 (WEB CONTAINER INTERVAL); # Triplets: 4; Triplet #: 1; offset: 76; length: 32; count: 1; Triplet #: 2; offset: 108; length: 112; count: 1; Triplet #: 3; offset: 264; length: 1480; count: 1; Triplet #: 1; Type: ProductSection; Version: 1; Codeset: Unicode; Endian: 1; TimeStampFormat: 1 (S390STCK64); IndexOfThisRecord: 1; Total # records: 1; Total # triplets: 4; Triplet #: 2; Type: WebContainerIntervalSection; HostName : PLEX1; ServerName : BBOASR4; ServerInstanceName: BBOASR4A; SampleStartTime * b6c7a6fd 655c0604 40404040 40404040 * SampleStopTime * b6c7a939 9a0e614c 40404040 40404040 * Triplet #: 3; Type: HttpSessionManagerIntervalSection; http sessions #created: 1; #invalidated: 0; http sessions #active: 0; Min #active: 0; Max #active: 0; Average session life time: 0; Average session invalidate time: 0; http sessions #finalized: 0; #tracked: 0; http sessions #min live: 0; #max live: 0; Triplet #: 4; Type: WebApplicationIntervalSection; Name: PolicyIVP-localhost_1; # Servlets loaded: 0; # Servlets: 4; Triplet #: 4.1; offset: 312; length: 292; count: 1; Triplet #: 4.2; offset: 604; length: 292; count: 1; Triplet #: 4.3; offset: 896; length: 292; count: 1; Triplet #: 4.4; offset: 1188; length: 292; count: 1; Triplet #: 4.1; Type: ServletIntervalSection; Name: SimpleFileServlet; # requests: 6; AverageResponseTime: 764 [sec*10**-3]; MinimumResponseTime: 18 [sec*10**-3]; MaximumResponseTime: 4133 [sec*10**-3]; # errors: 0; Loaded since (raw): ea54948e0d; Loaded since: Thu Nov 22 10:02:49 EST 2001; Triplet #: 4.2; Type: ServletIntervalSection; Name: Was40Ivp; # requests: 4; AverageResponseTime: 4664 [sec*10**-3]; MinimumResponseTime: 1584 [sec*10**-3]; MaximumResponseTime: 12572 [sec*10**-3]; # errors: 0; Loaded since (raw): ea58a1509e; Loaded since: Fri Nov 23 04:55:14 EST 2001; Triplet #: 4.3; Type: ServletIntervalSection; Name: /cebit.jsp; # requests: 1; AverageResponseTime: 204 [sec*10**-3]; MinimumResponseTime: 204 [sec*10**-3]; MaximumResponseTime: 204 [sec*10**-3]; # errors: 0; Loaded since (raw): ea58a24a69; Loaded since: Fri Nov 23 04:56:18 EST 2001; Triplet #: 4.4; Type: ServletIntervalSection; Name: JSP 1.1 Processor; # requests: 1; AverageResponseTime: 482 [sec*10**-3]; MinimumResponseTime: 482 [sec*10**-3]; MaximumResponseTime: 482 [sec*10**-3]; # errors: 0; Loaded since (raw): ea54948b66; Loaded since: Thu Nov 22 10:02:48 EST 2001;
Subtopics
- Enable SMF recording
Use this page to enable SMF recording for WAS and select SMF type 120 records for output to the SMF data sets.- Formatting the output data set
Use this page to format the SMF recording output data set into a readable format for printing to the screen or other output device.- View the output data set
Use the SMF Browser to view the output data set from the WAS for z/OS UNIX environment.- Disable SMF recording for WAS
This information describes how to disable SMF recording for WAS for z/OS.- Disable SMF recording for the entire MVS system
Use this page to disable SMF recording for our MVS™ System (z/OS).- Use SMF type 80 - preparing for audit support
SMF type 80 requires some preparation in order to be fully utilized in a WebSphere environment.- SMF settings
Configure SMF records to collect job information to tune application server performance.- SMF record type 120: overview
Information resulting from the SMF data gathering process for WAS for z/OS is held in SMF record type 120.