Offsets | Name | Length | Format | Description | |
---|---|---|---|---|---|
0 | 0 | SMF33CID | 8 | binary | The conversation ID. This ID uniquely identifies a particular conversation. |
8 | 8 | SMF33CCO | 8 | binary | The conversation correlator. This field contains zeroes when there is no conversation correlator. |
16 | 10 | SMF33CLO | 4 | binary | Offset to the logical unit of work ID (LUWID) section. |
20 | 14 | SMF33CIO | 1 | binary | Conversation inbound / outbound indicator. Possible
values are:
|
21 | 15 | SMF33CLR | 1 | binary | Conversation partner LU location. Possible values
are:
|
22 | 16 | SMF33CKD | 1 | binary | 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:
|
23 | 17 | SMF33CSL | 1 | Sync level of the conversation. Possible values
are:
|
|
24 | 18 | SMF33CLL | 17 | EBCDIC | Conversation local LU name (not fully qualified). |
41 | 29 | SMF33CPL | 17 | EBCDIC | Conversation partner LU name (fully qualified). |
58 | 3A | SMF33RS2 | 2 | Reserved. | |
60 | 3C | SMF33CSH | 8 | EBCDIC | 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. |
68 | 44 | SMF33CPO | 4 | binary | Offset (from beginning of record) to Partner TP Name Section. |
72 | 48 | SMF33CTO | 4 | binary | Offset (from beginning of record) to Local TP Name Section. |
76 | 4C | SMF33RS1 | 10 | EBCDIC | Reserved. |
86 | 56 | SMF33CPU | 10 | EBCDIC | Partner user ID. |
96 | 60 | SMF33CRT | 8 | binary | Date/Time (in STCK format) allocate request was received for the conversation. The field is zero for outbound requests. |
104 | 68 | SMF33CQT | 8 | binary | Date/Time (in STCK format) conversation was put on allocate queue. The field is zero for outbound requests and for scheduled inbound requests. |
112 | 6C | SMF33CST | 8 | binary | 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. |
120 | 78 | SMF33CET | 8 | binary | Date/time (in STCK format) when the conversation was deallocated. |
128 | 80 | SMF33CMN | 8 | EBCDIC | Mode name of the conversation. |
136 | 88 | SMF33CSN | 4 | binary | Number of Send calls issued during the conversation. |
140 | 88 | SMF33CDS | 8 | long floating point hex | Amount of data (in bytes) sent through the conversation. |
148 | 90 | SMF33CRE | 4 | binary | Number of Receive calls issued during the conversation. |
152 | 98 | SMF33CDR | 8 | long floating point hex | Amount of data (in bytes) received during the conversation. |
160 | A0 | SMF33CVB | 4 | binary | Number of callable service requests issued during the conversation. |
164 | A4 | SMF33CRC | 4 | binary | Return code from the last callable service on this conversation (Possible return codes are documented in the APPC/MVS publications.) |
168 | A8 | SMF33CRS | 4 | binary | Last reason code from a callable service in this conversation (Possible reason codes are documented in the APPC/MVS publications.) |
172 | AC | SMF33CSA | 4 | binary | Conversation state. Possible values are:
|
176 | B0 | SMF33CSS | 8 | binary | Date/Time (in STCK format) when the last APPC/MVS callable service was requested during the conversation. |
184 | B8 | SMF33CSE | 8 | binary | Date/Time (in STCK format) when the last APPC/MVS callable service completed during the conversation. |