(ZOS) SMF record type 120 (78) - WAS performance statistics

WebSphere Application Server writes record type 120 to collect WAS performance statistics.

For more information about SMF record types, see z/OS MVS™ System Management Facilities (SMF).

All subtypes of the record type 120 have the following format:

• Standard header section
• Individual header extension for subtype x
• Product section
• Subtype-specific sections

Record type 120 has the following subtypes:

• Subtype 1: Server activity record
  • Server activity section (one section per record):

    Contains information about each activity that occurred within one server.

  • Communication session section (zero, one, or multiple sections per record):

    Contains information about each communication session.

  • JVM heap section (zero, one, or multiple sections per record):

    Contains information about the heap in a server region.

• Subtype 3: Server interval record
  • Server interval section (one section per record):

    Contains aggregated information about all activities that occurred within the specified server interval.

  • Server region section (zero, one, or multiple sections per record):

    Contains information about server regions in the specified interval.

• Subtype 5: J2EE container activity record
  • J2EE container activity section (one section per record):

    Contains information about each activity that occurred within one J2EE container.

  • Bean section (multiple (0..n) sections per record):

    Contains information about all beans involved in this activity.

  • Bean method section (multiple (0..n) sections per bean section):

    Contains information about all methods of this bean involved in this activity.

• Subtype 6: J2EE container interval record
  • J2EE container interval section (one section per record):

    Contains aggregated information about all activities that occurred within one J2EE container in the specified interval.

  • Bean section (multiple (0..n) sections per record, see subtype 5):

    Contains information about all beans involved in this activity in the specified interval.

  • Bean method section (multiple (0..n) sections per bean section, see subtype 5):

    Contains information about all methods of this class involved in this activity in the specified interval.

• Subtype 7: WebContainer activity record (v2)
  • WebContainer activity section (one section per record):

    Contains information about each activity that occurred within one WebContainer.

  • HttpSessionManager activity section (one section per record):

    Contains information about all sessions involved in this activity.

  • WebApplication activity section (multiple (0..n) sections per record):

    Contains information about all WebApplications involved in this activity.

    • Servlet activity section (multiple (0..n) sections per WebApplication section):

      Contains information about all Servlets involved in this activity.

• Subtype 8: WebContainer interval record (v2)
  • WebContainer interval section (one section per record):

    Contains information about each activity that occurred within one WebContainer in the specified interval.

  • HttpSessionManager interval section (one section per record):

    Contains information about all sessions involved in this activity in the specified interval.

  • WebApplication interval section (multiple (0..n) sections per record):

    Contains information about all WebApplications involved in this activity in the specified interval.

    • Servlet interval section (multiple (0..n) sections per WebApplication section):

      Contains information about all Servlets involved in this activity in the specified interval.

• Subtype 9: Request Activity record
  • 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

    (zero or one section per record):

    Contains information about each request that was received by one server.

    This section is not applicable for an asynchronous request.

  • z/OS request information section

    (zero or one section per record):

    Contains information about each request that was received by each server servant in the specified server.

    This section is not applicable for an asynchronous request.

  • z/OS formatted timestamps section

    (zero or 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.

    This section is not applicable for an asynchronous request.

  • 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 associated with one server. There is a separate network data section for the HTTP requests, the SIP requests, and the IIOP requests.

    This section is not applicable for an asynchronous request.

  • 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.

    This section is not applicable for an asynchronous request.

  • 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.

    This section is not applicable for an asynchronous request.

  • 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.

    This section is optional for an asynchronous request.

  • 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.

    This section is optional for an asynchronous request.

  • Asynchronous data section (Asynchronous data section (multiple (0..1) sections per record):

    Contains information created by requests that the server runs asynchronously.

    This section is always present for an asynchronous request.

• Subtype 10: Outbound Request record
  • Platform neutral server information section (one section per record):

    Contains information about the server that handled the outbound request.

  • z/OS server information section (one section per record):

    Contains information about the servant that handled the outbound request.

  • Outbound Request information section (one section per record):

    Contains general information about the outbound request.

  • WOLA Outbound Request type specific section (zero or one section per record):

    Contains WOLA specific information about the outbound request.

  • Outbound Request transaction context section (zero or one section per record):

    Contains the transactional information of the outbound request.

  • Outbound Request security context section (zero or one section per record):

    Contains the security information of the outbound request.

  • Outbound Request CICS context section (zero or one section per record):

    Contains the CICS context associated with the WOLA outbound request.

  • OTMA Outbound Request type specific section (zero or one section per record):

    Contains OTMA specific information about the outbound request.

Collecting job-related information with the System Management Facility (SMF)