SMF Subtype 10: Outbound Request record

The purpose of the Outbound Request SMF record is to record requests that go outbound. This record is produced whenever an optimized local adapter request goes outbound.

You can use the SMF Subtype 10 record to monitor how many outbound requests are occurring, where they are going and how long it takes.

You can activate this record through the administrative console by setting server_SMF_outbound_enabled=1 (or server_SMF_outbound_enabled=true).

If you do not want these records to be generated, you can set server_SMF_outbound_enabled=0 (or server_SMF_outbound_enabled=false), which turns off the creation of this SMF record type. This is the default value for this property.

Outbound Request record schema

The record header is the same for every Subtype 10 record that is created by the same server.

The Outbound Request record is divided into the following sections.

Platform neutral server information section

Table 1. Platform neutral server information section. This section contains information about the server that handled the request.
Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120ABG 4 binary The version of the server information
4 4 SM120ABH 8 EBCDIC Cell short name
12 C SM120ABI 8 EBCDIC Node short name
20 14 SM120ABJ 8 EBCDIC Cluster short name
28 1C SM120AAK 8 EBCDIC Server short name
36 24 SM120ABL 4 EBCDIC Server or controller PID
40 28 SM120ABM 1 binary Product version level (the w in the format w.x.y.z)
41 29 SM120ABN 1 binary Product release level (the x in the format w.x.y.z)
42 2A SM120ABO 1 binary Part of the product modification level (the y in the format w.x.y.z)
43 2B SM120ABP 1 binary Part of the product modification level (the z in the format w.x.y.z)
44 2C * 32   Reserved

z/OS server information section

Table 2. 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 (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120ABQ 4 binary The version of the server information
4 4 SM120ABR 8 EBCDIC The name of the system on which the product is running (CVTSNAME)
12 C SM120ABS 8 EBCDIC The name of the sysplex on which the product is running
20 14 SM120ABT 8 EBCDIC The job name for the controller
28 1C SM120ABU 8 EBCDIC The job ID for the controller
36 24 SM120ABV 8 binary The STOKEN for the controller
44 2C SM120ABW 2 binary Controller ASID
46 2E SM120AGE 2 binary Contains the following flags:
  • .Bit 1 is reserved
  • SMF120AGG (bit 2) CEEGMTO failed/unavailable if turned on, the GMT offsets failed to be retrieved from the CEEGMTO API or the CEEGMTO API was not available.
  • Bits 3-16 are reserved
48 30 SM120ABX 20 binary The cluster UUID
68 44 SM120ABY 20 binary The server UUID
88 58 SM120ABZ 8 EBCDIC The daemon group name
96 60 SM120ACA 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 SM120AGG is turned on to indicate that the zeros in this field are not valid GMT offsets.
100 64 SM120ACB 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 SM120AGG is turned on to indicate that the zeros in this field are not valid GMT offsets.
104 68 SM120ACC 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 SM120AGG is turned on to indicate that the zeros in this field are not valid GMT offsets.
112 70 SM120ACD 8 binary The system GMT offset. The value is obtained from the CVTLDTO API.
120 78 SM120AHV 16 EBCDIC The service level (expanded)
136 88 * 20 Reserved  

Outbound Request information section

Table 3. Outbound Request information section. This section contains information about the outbound request. One of these sections is included in each record.
Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120ACF 4 binary The version of the outbound request information
4 4 SM120ACG 4 binary The PID of the dispatch servant
8 8 SM120ACH 8 binary The ID of the dispatched task. This value is returned from pthread_self.
16 10 SM120ACK 4 binary Outbound request type
o
unknown
1
WOLA
2
OTMA
20 14 * 4   Reserved
24 18 SM120ACR 8 EBCDIC The job name for the dispatch servant
32 20 SM120ACS 8 EBCDIC The job ID for the dispatch servant
40 28 SM120ACT 8 binary The STOKEN for the dispatch servant
48 30 SM120ACU 2 binary The ASID for the dispatch servant
50 32 * 2   Reserved for alignment
52 34 SM120ACV 4 binary The address of the dispatch TCB
56 38 SM120ACW 16 binary The TTOKEN for the dispatch TCB
72 48 SM120ACY 8 binary The enclave token
80 50 SM120AD1 8 binary The number of bytes sent
88 58 SM120AD2 8 binary The number of response bytes
96 60 SM120AD3 16 S390STCKE The time the request went outbound
112 70 SM120AD4 16 S390STCKE The time the outbound request returned
128 80 * 32   Reserved

WOLA Outbound Request type specific section

Table 4. WOLA Outbound Request type specific section. This section contains specific information about the WOLA outbound request. There are zero to one of these sections included in each record.
Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120AD5 4 binary The version of the WOLA outbound request type specific section
4 4 SM120AD6 12 EBCDIC The register name the outbound request is going to
16 10 SM120AD7 256 EBCDIC The service name the outbound request is going to
272 110 SM120AD8 256 binary The outbound request correlator context. This correlator context also ends up in the CICS SMF 110 records.
528 210 SM120AD9 24   Reserved

Outbound Request transaction context section

Table 5. Outbound Request transaction context section. This section contains transaction information about the WOLA outbound request. There are zero to one of these sections included in each record.
Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120ADA 4 binary The version of the outbound request transaction context section
4 4 SM120ADB 140 binary The transactional XID
144 90 SM120ADC 24   Reserved

Outbound Request security context section

Table 6. Outbound Request security context section. This section contains security information about the WOLA outbound request. There are zero to one of these sections included in each record.
Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120ADD 4 binary The version of the outbound request security context section
4 4 SM120ADE 8 EBCDIC The security context
12 C SM120ADF 28   Reserved

Outbound Request CICS context section

Table 7. Outbound Request CICS context section. This section contains the CICS context associated with the WOLA outbound request. There are zero to one of these sections included in each record.
Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120ADG 4 binary The version of the outbound request CICS context section
4 4 SM120ADH 80 binary The CICS context
84 54 SM120ADI 28   Reserved

OTMA Outbound Request type specific section

Table 8. OTMA Outbound Request type specific section
Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120ADJ 4 binary The version of the OTMA outbound request type specific section
4 4 SM120ADK 12 EBCDIC The OTMA register name of the outbound request
16 10 SM120ADL 256 EBCDIC The OTMA service name of the outbound request
272 110 SM120ADM 8 EBCDIC The OTMA IMS transaction name of the outbound request
280 118 SM120ADN 8 EBCDIC The OTMA IMS group id of the outbound request
288 120 SM120ADO 16 EBCDIC The OTMA IMS server name of the outbound request
304 130 SM120ADP 24   Reserved



Related concepts
Messaging flow for ASF message-driven beans with WebSphere MQ as the messaging provider
Messaging flow for JCA message-driven beans with service integration as the messaging provider
Messaging flow for JCA message-driven beans with WebSphere MQ as the messaging provider
Related tasks
Collecting job-related information with the System Management Facility (SMF)
Related reference
Triplets
Header/self-defining section
SMF Subtype 1: Server activity record
SMF Subtype 3: Server interval record
SMF Subtype 5: J2EE container activity record (Version 2)
SMF Subtype 6: J2EE container interval record (Version 2)
SMF Subtype 7: WebContainer activity record (Version 2)
SMF Subtype 8: WebContainer interval record (Version 2)
SMF Subtype 9: Request Activity record
Record environment and mapping
Related information
MVS System Management Facilities (SMF)
Reference topic Reference topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 3:08:41 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=rtrb_SMFsubtype10
File name: rtrb_SMFsubtype10.html