SMF Type 33 Record

Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word). See “Standard SMF Record Header” on page 13-1 for a detailed description.

Segment descriptor (see record length field).

System indicator Bit Meaning When Set 0 Subsystem name follows system identification 1 Subtypes used 2 Reserved 3-6 Version indicators* 7 Reserved.*See “Standard SMF Record Header” on page 13-1 for a detailed description.

Record type 33 (X'21').

Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer.

Date when the record was moved into the SMF buffer, in the form 0cyydddF.

System identification (from the SID parameter).

Subsystem identifier.

Record subtype.

Length of Self-defining Section.

Offset to Product section.

Length of Product section.

Number of Product Sections in this record.

Offset to TP Identification Section.

Length of TP Identification Section.

Number of TP Identification Sections in this record.

Offset to TP Usage Section.

Length of TP Usage Section.

Number of TP Usage Sections in this record.

Offset to Address Space ID Section.

Length of Address Space ID Section.

Number of Address Space ID Sections in this record.

Offset to Conversation ID Section.

Length of Conversation ID Section.

Number of Conversation ID Sections in this record.

Offset to User Data Field Section.

Length of User Data Field Section.

Number of User Data Field Sections in this record.

Record Subtype
1 — APPC/MVS transaction record.
2 — APPC/MVS conversation record.

Record version number — 01.

Product name — ASCH for APPC/MVS-scheduled TPs. APPC for APPC/MVS Conversion Records. If you use your own scheduler, you will not have access to IBM's APPC/MVS accounting support.

MVS operating system name.

System name (from the SYSNAME parameter in the IEASYSxx parmlib member).

Sysplex name (from the SYSPLEX parameter in the COUPLExx parmlib member).

Job or session name.

Time since midnight, in hundredths of a second, reader recognized this job.

Date when the reader recognized this job, in the form 0cyydddF.

Step name (taken from the name on the EXEC card).

Offset to TP name section.

TP Class — a general grouping of TPs with related scheduling properties (like the MVS Job Class — CPU Time limit, shift execution requirements, etc).

APPC/MVS TP schedule type Value Schedule Type
0 Standard

TP profile name.

Length of TP name in SMFTPN1 field.

TP name

RACF user ID (of the requesting user).

RACF group ID (of the requesting user).

Type of user
Value User
0 Standard
1 Multi-trans shell.

Offset to Accounting Section.

Length of Accounting Section.

Number of Accounting Sections in this record.

Count of uses of this TP (by this user).

Offset to TP Usage Detail Section.

Length of TP Usage Detail Section.

Number of TP Usage Detail Sections.

First accounting sub-field length (this field is set to zero for no accounting data).

Accounting sub-fields.

Offset to TP Usage Scheduler Section.

Length of TP Usage Scheduler Section.

Number of TP Usage Scheduler Sections.

Total number of conversations for this request.

Total number of conversations allocated by this request.

Total number of sends issued by this request.

Total number of bytes sent by this request.

Total number of receives issued by this request.

Total number of bytes received by this request.

Task control block (TCB) time for this request, in hundredths of a second.

Service request block (SRB) time for this request, in hundredths of a second.

Execute channel programs (EXCP) for this request. Valid up to X'FFFFFFFE', zero and invalid when SMFEXF is set.

Total accumulated device connect time for the address during the life of the transaction. The field reported (in 128 micro-second units) of I/O activity in the address space by some chargeback schemes. See SMF30TCN in the ‘I/O Activity’ section of SMF type 30 record.

Detail section flags
Bit Meaning when set
SMFEXF 0 Count in SMF32EXP is not valid.

Reserved

EXCPs for this request. This is the 8-byte equivalent of SMFEXP. This field remains valid after SMFEXP is invalid.

Local logical unit (LU) name for the TP.

Partner logical unit (LU) name for this user's use of this TP (format = node.LUname).

Reserved.

Time since midnight, in hundredths of a second, request recognized by functional manager header (FMH) 5.

Date request recognized by functional manager header (FMH) 5, in the form 0cyydddF.

Time since midnight, in hundredths of a second, that the request was placed on scheduler work queue.

Date that the request was placed on scheduler work queue, in the form 0cyydddF.

Time since midnight, in hundredths of a second, that the request started execution.

Date that the request started execution, in the form 0cyydddF.

Time since midnight, in hundredths of a second, that the request ended execution.

Date that the request ended execution, in the form 0cyydddF.

The conversation ID. This ID uniquely identifies a particular conversation.

The conversation correlator. This field contains zeroes when there is no conversation correlator.

Offset to the logical unit of work ID (LUWID) section.

Conversation inbound / outbound indicator. Possible values are:
0 When conversation is outbound
1 When conversation is inbound.

Conversation partner LU location. Possible values are:
0 When partner LU is local
1 When partner LU is remote.

Conversation kind. For inbound conversations, this field indicates whether this conversation was processed by an APPC/MVS transaction scheduler or an APPC/MVS server. Possible values are:
0 Transaction scheduler
1 APPC/MVS server For outbound conversations, this field is always set to zero.

Sync level of the conversation. Possible values are:
0 None - Specifies that the programs will not perform confirmation processing on this conversation. The programs will not call any services and will not recognize any returned parameters relating to confirmation.
1 Confirm - Specifies that the programs can perform confirmation processing on this conversation. The programs can call services and will recognize returned parameters relating to confirmation.
2 Syncpt - Specifies that the programs can perform sync point processing on this conversation. The programs can call services and will recognize returned parameters relating to sync point processing.

Conversation local LU name (not fully qualified).

Conversation partner LU name (fully qualified).

Reserved.

Conversation scheduler name (for example, ‘ASCH’). When there is no scheduler for this conversation (because an APPC/MVS server is processing the conversation), this field contains blanks.

Offset (from beginning of record) to Partner TP Name Section.

Offset (from beginning of record) to Local TP Name Section.

Reserved.

Partner user ID.

Date/Time (in STCK format) allocate request was received for the conversation. The field is zero for outbound requests.

Date/Time (in STCK format) conversation was put on allocate queue. The field is zero for outbound requests and for scheduled inbound requests.

Inbound Requests: Date/Time (in STCK format) when the conversation was associated with a new address space for processing. If an APPC/MVS server processed this conversation, this field shows the time when the server received the conversation through the Receive_Allocate service. Outbound Requests: Date/Time (in STCK format) when the local program called the Allocate service.

Date/time (in STCK format) when the conversation was deallocated.

Mode name of the conversation.

Number of Send calls issued during the conversation.

Amount of data (in bytes) sent through the conversation.

Number of Receive calls issued during the conversation.

Amount of data (in bytes) received during the conversation.

Number of callable service requests issued during the conversation.

Return code from the last callable service on this conversation (Possible return codes are documented in the APPC/MVS publications.)

Last reason code from a callable service in this conversation (Possible reason codes are documented in the APPC/MVS publications.)

Conversation state. Possible values are:
1 Reset
2 Initialize
3 Send
4 Receive
5 Send pending
6 Confirm
7 Confirm send
8 Confirm deallocate

Date/Time (in STCK format) when the last APPC/MVS callable service was requested during the conversation.

Date/Time (in STCK format) when the last APPC/MVS callable service completed during the conversation.

Length of the local TP name field (SMFTPN2).

binary Local transaction program name. If this conversation is inbound, this field contains the name of the program that was attached on this LU in response to an Allocate call. If this conversation is outbound, this field contains the name of the program that initiated the conversation (that is, issued the Allocate call).

Length of logical unit of work ID (SMFLUW).

Logical unit of work ID (LUW_ID).

Length of data in user data field (SMFUDF).

User data field. This is user-defined data that one of the partner programs wrote to this record, through the Set_Conversation_Accounting_Information service. binary User data field. This is user-defined data that one of the partner programs wrote to this record, through the Set_Conversation_Accounting_Information service.