Go to Home Page
Questions?
Call 1-800-572-5517
 
  Go to Home Page  
  See all products
  See price schedules
  See manuals, tutorials, articles
  Download a free 30-day trial
  See user testimonials
  About Pacific Systems Group
 
 
SMF Tools
  See SMF Record Layouts
  See Sample SMF Reports
  Learn How to Export SMF Data
  Download Free SMF Reporting Software (30 days)
 
One of the greatest SMF record parsing programming languages I've ever seen. Chief, Large Systems Services Branch, NIH
  Choose Spectrum Writer to add 4GL to your product
  Free 60-Page Book (PDF) - How to Make an SMF Report
Spectrum DCOLLECT Reporter - the 4GL DCOLLECT Report Writer.

Spectrum SMF Writer - the 4GL SMF Report Writer.

SMF Type 33 Record

This table shows the record layout for type 33 SMF records
(APPC/MVS TP Accounting).

List of other SMF record layouts available.
List of sample SMF reports.

Purpose: When APPC/MVS inbound conversations create work scheduled by the APPC/MVS transaction scheduler, SMF writes a type 33 subtype 1 record. When an APPC/MVS inbound or outbound conversation is deallocated, SMF writes a type 33 subtype 2 record.

The subtype is indicated in the SMF33TYP field.

It's easy to report on SMF 33 data!

SMF Spectrum Writer
We have a low-cost 4GL report writer especially for SMF files. It's called Spectrum SMF Writer.

Spectrum SMF Writer handles the difficult SMF record parsing for you automatically. You just specify which fields you want to see.

Spectrum SMF Writer also converts the arcane date and time fields and reformats them into an attractive report.

Plus, Spectrum SMF Writer can export SMF data as comma delimited files to use on your PC.
 
Try It FREE Now!

SMF Type 33 Record -- APPC/MVS TP Accounting
Offset
(Dec.)
Offset
(Hex)
NameLengthFormatDescription
00SMF33LEN2binary
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.
22SMF33SEG2binary
Segment descriptor (see record length field).
44SMF33FLG1binary
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.
55SMF33RTY1binary
Record type 33 (X'21').
66SMF33TME4binary
Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer.
10ASMF33DTE4packed
Date when the record was moved into the SMF buffer, in the form 0cyydddF.
14ESMF33SID4EBCDIC
System identification (from the SID parameter).
1812SMF33WID4EBCDIC
Subsystem identifier.
2216SMF33STP2binary
Record subtype.
2418SMF33SDL4binary
Length of Self-defining Section.
281CSMF33POF4binary
Offset to Product section.
3220SMF33PLN2binary
Length of Product section.
3422SMF33PON2binary
Number of Product Sections in this record.
3624SMF33IOF4binary
Offset to TP Identification Section.
4028SMF33ILN2binary
Length of TP Identification Section.
422ASMF33ION2binary
Number of TP Identification Sections in this record.
442CSMF33UOF4binary
Offset to TP Usage Section.
4830SMF33ULN2binary
Length of TP Usage Section.
5032SMF33UON2binary
Number of TP Usage Sections in this record.
5234SMF33SOF4binary
Offset to Address Space ID Section.
5638SMF33SLN2binary
Length of Address Space ID Section.
583ASMF33SON2binary
Number of Address Space ID Sections in this record.
603CSMF33COF4binary
Offset to Conversation ID Section.
6440SMF33CLN2binary
Length of Conversation ID Section.
6642SMF33CON2binary
Number of Conversation ID Sections in this record.
6844SMF33FOF4binary
Offset to User Data Field Section.
7248SMF33FLN2binary
Length of User Data Field Section.
748ASMF33FON2binary
Number of User Data Field Sections in this record.
Product Section
This section contains the product that generated the record.
(Offset from beginning of record: SMF33POF)
00SMF33TYP2binary
Record Subtype
1 — APPC/MVS transaction record.
2 — APPC/MVS conversation record.
22SMF33RVN2EBCDIC
Record version number — 01.
44SMF33PNM8EBCDIC
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.
12CSMF33OSL8EBCDIC
MVS operating system name.
2014SMF33SYN8EBCDIC
System name (from the SYSNAME parameter in the IEASYSxx parmlib member).
281CSMF33SYP8EBCDIC
Sysplex name (from the SYSPLEX parameter in the COUPLExx parmlib member).
Address space ID section
(Offset from beginning of record: SMF33SOF)
00SMF33JID8EBCDIC
Job or session name.
88SMF33RST4binary
Time since midnight, in hundredths of a second, reader recognized this job.
12CSMF33RSD4binary
Date when the reader recognized this job, in the form 0cyydddF.
1610SMF33STN8EBCDIC
Step name (taken from the name on the EXEC card).
TP Identification Section
Present only for Subtype 1
(Offset from beginning of record: SMF33IOF)
00SMF33TPO4binary
Offset to TP name section.
44SMF33TPC8EBCDIC
TP Class — a general grouping of TPs with related scheduling properties (like the MVS Job Class — CPU Time limit, shift execution requirements, etc).
12CSMF33TSC4binary
APPC/MVS TP schedule type Value Schedule Type
0 Standard
1610SMF33TPF8EBCDIC
TP profile name.
TP Program Name Section
Present only for Subtype 1
(Offset from beginning of record: SMF33TPO)
00SMF33TPL12binary
Length of TP name in SMFTPN1 field.
22SMF33TPN1255EBCDIC
TP name
TP Usage Section
This section identifies the user requesting the TP being reported on. This section contains the general user identification information.
Present only for Subtype 1
(Offset from beginning of record: SMF33UOF)
00SMF33UID8EBCDIC
RACF user ID (of the requesting user).
88SMF33GRP8EBCDIC
RACF group ID (of the requesting user).
1610SMF33UST4binary
Type of user
Value User
0 Standard
1 Multi-trans shell.
2014SMF33AOF4binary
Offset to Accounting Section.
2418SMF33ALN2binary
Length of Accounting Section.
261ASMF33AON2binary
Number of Accounting Sections in this record.
281CSMF33UCT4binary
Count of uses of this TP (by this user).
3220SMF33TDO4binary
Offset to TP Usage Detail Section.
3624SMF33TDL2binary
Length of TP Usage Detail Section.
3826SMF33TDN2binary
Number of TP Usage Detail Sections.
TP Usage Accounting Section
This section identifies the variable length accounting information for the user requesting the TP being reported on.
Present only for Subtype 1
(Offset from beginning of record: SMF33AOF)
00SMF33ACL1binary
First accounting sub-field length (this field is set to zero for no accounting data).
11SMF33ACT175EBCDIC
Accounting sub-fields.
TP Usage Detail Section
This section identifies detailed information about the specific execution of TP that is being reported on:
Present only for Subtype 1
(Offset from beginning of record: SMF33TDO)
00SMF33TSO4binary
Offset to TP Usage Scheduler Section.
44SMF33TSL2binary
Length of TP Usage Scheduler Section.
66SMF33TSN2binary
Number of TP Usage Scheduler Sections.
88SMF33CN4binary
Total number of conversations for this request.
12CSMF33CNA4binary
Total number of conversations allocated by this request.
1610SMF33SEN4binary
Total number of sends issued by this request.
2014SMF33DAS8long
Total number of bytes sent by this request.
281CSMF33REC4binary
Total number of receives issued by this request.
3220SMF33DAR8long
Total number of bytes received by this request.
4028SMF33TCB4binary
Task control block (TCB) time for this request, in hundredths of a second.
442CSMF33SRB4binary
Service request block (SRB) time for this request, in hundredths of a second.
4830SMF33EXP4binary
Execute channel programs (EXCP) for this request. Valid up to X'FFFFFFFE', zero and invalid when SMFEXF is set.
5234SMF33DCT4binary
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.
5638SMF33DSF1binary
Detail section flags
Bit Meaning when set
SMFEXF 0 Count in SMF32EXP is not valid.
5739--7binary
Reserved
6440SMF33EXF8binary
EXCPs for this request. This is the 8-byte equivalent of SMFEXP. This field remains valid after SMFEXP is invalid.
TP Usage Scheduler Section
This section identifies scheduler data about the specific execution of TP that is being reported on. This section does not appear for as multi-trans shell.
Present only for Subtype 1
(Offset from beginning of record: SMF33TSO)
00SMF33LLU17EBCDIC
Local logical unit (LU) name for the TP.
1711SMF33PLU17EBCDIC
Partner logical unit (LU) name for this user's use of this TP (format = node.LUname).
3422SMF33RV22--
Reserved.
3624SMF33FMT4binary
Time since midnight, in hundredths of a second, request recognized by functional manager header (FMH) 5.
4028SMF33FMD4packed
Date request recognized by functional manager header (FMH) 5, in the form 0cyydddF.
442CSMF33TQT4binary
Time since midnight, in hundredths of a second, that the request was placed on scheduler work queue.
4830SMF33TQD4packed
Date that the request was placed on scheduler work queue, in the form 0cyydddF.
5234SMF33TST4binary
Time since midnight, in hundredths of a second, that the request started execution.
5638SMF33TSD4packed
Date that the request started execution, in the form 0cyydddF.
603CSMF33TET4binary
Time since midnight, in hundredths of a second, that the request ended execution.
6440SMF33TED4packed
Date that the request ended execution, in the form 0cyydddF.
Conversation ID section
Present only for Subtype 2
(Offset from beginning of record: SMF33COF)
00SMF33CID8binary
The conversation ID. This ID uniquely identifies a particular conversation.
88SMF33CCO8binary
The conversation correlator. This field contains zeroes when there is no conversation correlator.
1610SMF33CLO4binary
Offset to the logical unit of work ID (LUWID) section.
2014SMF33CIO1binary
Conversation inbound / outbound indicator. Possible values are:
0 When conversation is outbound
1 When conversation is inbound.
2115SMF33CLR1binary
Conversation partner LU location. Possible values are:
0 When partner LU is local
1 When partner LU is remote.
2216SMF33CKD1binary
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.
2317SMF33CSL1binary
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.
2418SMF33CLL17EBCDIC
Conversation local LU name (not fully qualified).
4129SMF33CPL17EBCDIC
Conversation partner LU name (fully qualified).
583ASMF33RS22--
Reserved.
603CSMF33CSH8EBCDIC
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.
6844SMF33CPO4binary
Offset (from beginning of record) to Partner TP Name Section.
7248SMF33CTO4binary
Offset (from beginning of record) to Local TP Name Section.
764CSMF33RS110EBCDIC
Reserved.
8656SMF33CPU10EBCDIC
Partner user ID.
9660SMF33CRT8binary
Date/Time (in STCK format) allocate request was received for the conversation. The field is zero for outbound requests.
10468SMF33CQT8binary
Date/Time (in STCK format) conversation was put on allocate queue. The field is zero for outbound requests and for scheduled inbound requests.
1126CSMF33CST8binary
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.
12078SMF33CET8binary
Date/time (in STCK format) when the conversation was deallocated.
12880SMF33CMN8EBCDIC
Mode name of the conversation.
13688SMF33CSN4binary
Number of Send calls issued during the conversation.
14088SMF33CDS8long
Amount of data (in bytes) sent through the conversation.
14890SMF33CRE4binary
Number of Receive calls issued during the conversation.
15298SMF33CDR8long
Amount of data (in bytes) received during the conversation.
160A0SMF33CVB4binary
Number of callable service requests issued during the conversation.
164A4SMF33CRC4binary
Return code from the last callable service on this conversation (Possible return codes are documented in the APPC/MVS publications.)
168A8SMF33CRS4binary
Last reason code from a callable service in this conversation (Possible reason codes are documented in the APPC/MVS publications.)
172ACSMF33CSA4binary
Conversation state. Possible values are:
1 Reset
2 Initialize
3 Send
4 Receive
5 Send pending
6 Confirm
7 Confirm send
8 Confirm deallocate
176B0SMF33CSS8binary
Date/Time (in STCK format) when the last APPC/MVS callable service was requested during the conversation.
184B8SMF33CSE8binary
Date/Time (in STCK format) when the last APPC/MVS callable service completed during the conversation.
Partner TP Program Name Section
Present only for Subtype 2
(Offset from beginning of record: SMF33CPO)
00SMF33TPL22binary
Length of the local TP name field (SMFTPN2).
22SMF33TPN264EBCDIC
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).
Local TP Program Name Section
Present only for Subtype 2
(Offset from beginning of record: SMF33CTO)
00SMF33LUL2binary
Length of logical unit of work ID (SMFLUW).
22SMF33LUW26EBCDIC
Logical unit of work ID (LUW_ID).
Logical Unit of Work ID (LUWID) Section
Present only for Subtype 2
(Offset from beginning of record: SMF33CLO)
00SMF33UDL2binary
Length of data in user data field (SMFUDF).
22SMF33UDF255ebcdic
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.

The table above is based on the description provided by IBM in its "MVS Systems Management Facilities (SMF)" manual.

Copyright 2017.
Pacific Systems Group.
All rights reserved.


Spectrum Writer 4GL - the economical alternative to SAS, Easytrieve, DYL-280...

Home | Products | Prices | Documentation | 30-Day Trials | Customer Reviews | Company | FAQ | Sample Reports | SMF Records
Send Your Comments or Questions