+

Search Tips   |   Advanced Search

(ZOS) SMF Subtype 1: Server activity record

The server activity SMF record is used to record activity running inside a WAS for z/OS . This record can be used to perform basic charge-back accounting and to profile the applications to determine, in detail, what is happening inside the WebSphereApplication 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.

We can activate this record through the administrative console by setting server_SMF_server_activity_enabled=1 (or server_SMF_server_activity_enabled=true). See Use the administrative console to enable properties for specific SMF record typesfor instructions.


Server activity record schema

This section includes Subtype 1: Server activity record.


Server activity section

Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120HNM 64 EBCDIC WebSphereApplication Server for z/OStransaction server host name
64 40 SM120SNA 8 EBCDIC WebSphereApplication Server for z/OStransaction server name
72 48 SM120INA 8 EBCDIC WebSphereApplication Server for z/OStransaction server instance name
80 50 SM120SNM 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 SM120SR1 4 binary The specific WebSphereApplication Server for z/OStransaction server instance server servant where the request ran
88 58 SM120SR2 4 binary The specific WebSphereApplication Server for z/OStransaction server instance server servant where the request ran
92 5C SM120SR3 4 binary The specific WebSphereApplication Server for z/OStransaction server instance server servant where the request ran
96 60 SM120SR4 4 binary The specific WebSphereApplication Server for z/OStransaction server instance server servant where the request ran
100 64 SM120SR5 4 binary The specific WebSphereApplication Server for z/OStransaction server instance server servant where the request ran
104 68 SM120CRE 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 SM120ATY 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 SM120AID 20 HEX Identity of the activity
136 88 SM120WLM 8 HEX WLM enclave token
144 90 SM120AST 16 S390STCK Activity start time
160 A0 SM120AET 16 S390STCK Activity stop time
176 B0 SM120NIM 4 binary Number of input methods
180 B4 SM120NGT 4 binary Number of global transactions that were started in the server servant
184 B8 SM120NLT 4 binary Number of local transactions that were started in the server servant
188 BC SM120J2E 4 binary J2EE server
192 C0 SM120CEL 8 EBCDIC WebSphereApplication Server for z/OScell name
200 C8 SM120NOD 8 EBCDIC WebSphereApplication Server for z/OSnode name
208 D0 SM120WCP 8 binary Total CPU time accumulated by the WLM enclave. TOD clock format (bit 51 = microseconds).


Communications session section

Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120CSH 8 HEX Communications session handle
8 8 SM120CSA 64 EBCDIC Communications session address
72 48 SM120CSO 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 SM120SDR 4 binary Data received; the number of bytes received by the server.

'FFFFFFFF'X indicates the 4-byte field is too small. Use SM120CDR, an 8-byte field, instead.

80 50 SM120SDT 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 SM120CDT, an 8-byte field, instead.

84 54 SM120CDR 8 binary Data received; the number of bytes received by the server.
92 5C SM120CDT 8 binary Data transferred; the number of bytes transferred from the server back to the client.


JVM Heap section

There are zero, one, or multiple sections per record. The JVM heap section contains information about the heap in each server servant.

Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120JHA 4 binary Servant address space ID
4 4 SM120JHH 4 binary The heap for which the following data applies.
8 8 SM120JHC 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 SM120JHF 8 binary The total number of free bytes in the heap/subpool/page pool.
20 14 SM120JHT 8 binary The total number of bytes in the heap, subpool, or page pool.

  • Collecting job-related information with the System Management Facility (SMF)
  • Triplets
  • Header/self-defining section
  • Product section
  • SMF Subtype 3: Server interval record
  • SMF Subtype 5: J2EE container activity record (v2)
  • SMF Subtype 6: J2EE container interval record (v2)
  • SMF Subtype 7: WebContainer activity record (v2)
  • SMF Subtype 8: WebContainer interval record (v2)
  • SMF Subtype 9: Request Activity record
  • SMF Subtype 10: Outbound Request record
  • Application server custom properties for z/OS

    MVS System Management Facilities (SMF)