appcActiveConvTpName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..64))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The transaction program name which started this conversation.
This name could either be from a FMH5 ATTACH for a remotely
started conversation, otherwise it could the name of the local
TP if available.
When the TP name consists entirely of displayable EBCDIC code
points, it is mapped directly to the equivalent ASCII display
string. However, registered TP names always have a non-
displayable EBCDIC code point (value less than or equal to
xF) as the first character, so they cannot be directly
mapped to an ASCII display string. These TP names are
converted to a display string that is equivalent to a
hexadecimal display of the EBCDIC code points. For example,
the 2-byte TP name xF1 (CNOS) is converted to the 6-byte
ASCII display string F1 (including the two single quotes).
This name is NULL if the conversation is started locally
(i.e., not with a FMH5 ATTACH)."
View at oid-info.com
The transaction program name which started this conversation.
This name could either be from a FMH5 ATTACH for a remotely
started conversation, otherwise it could the name of the local
TP if available.
When the TP name consists entirely of displayable EBCDIC code
points, it is mapped directly to the equivalent ASCII display
string. However, registered TP names always have a non-
displayable EBCDIC code point (value less than or equal to
x'3F') as the first character, so they cannot be directly
mapped to an ASCII display string. These TP names are
converted to a display string that is equivalent to a
hexadecimal display of the EBCDIC code points. For example,
the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte
ASCII display string '06F1' (including the two single quotes).
This name is NULL if the conversation is started locally
(i.e., not with a FMH5 ATTACH).
Parsed from file rfc2051-APPC.mib.txt
Company: None
Module: APPC-MIB
The transaction program name which started this conversation.
This name could either be from a FMH5 ATTACH for a remotely
started conversation, otherwise it could the name of the local
TP if available.
When the TP name consists entirely of displayable EBCDIC code
points, it is mapped directly to the equivalent ASCII display
string. However, registered TP names always have a non-
displayable EBCDIC code point (value less than or equal to
x'3F') as the first character, so they cannot be directly
mapped to an ASCII display string. These TP names are
converted to a display string that is equivalent to a
hexadecimal display of the EBCDIC code points. For example,
the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte
ASCII display string '06F1' (including the two single quotes).
This name is NULL if the conversation is started locally
(i.e., not with a FMH5 ATTACH).
Parsed from file APPC-MIB.mib
Module: APPC-MIB
Automatically extracted from RFC2051
appcActiveConvTpName OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The transaction program name which started this conversation. This name could either be from a FMH5 ATTACH for a remotely started conversation, otherwise it could the name of the local TP if available. When the TP name consists entirely of displayable EBCDIC code points, it is mapped directly to the equivalent ASCII display string. However, registered TP names always have a non- displayable EBCDIC code point (value less than or equal to x'3F') as the first character, so they cannot be directly mapped to an ASCII display string. These TP names are converted to a display string that is equivalent to a hexadecimal display of the EBCDIC code points. For example, the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte ASCII display string '06F1' (including the two single quotes). This name is NULL if the conversation is started locally (i.e., not with a FMH5 ATTACH)." ::= { appcActiveConvEntry 21 }
appcActiveConvTpName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..64)) MAX-ACCESS read-only STATUS current DESCRIPTION "The transaction program name which started this conversation. This name could either be from a FMH5 ATTACH for a remotely started conversation, otherwise it could the name of the local TP if available. When the TP name consists entirely of displayable EBCDIC code points, it is mapped directly to the equivalent ASCII display string. However, registered TP names always have a non- displayable EBCDIC code point (value less than or equal to x'3F') as the first character, so they cannot be directly mapped to an ASCII display string. These TP names are converted to a display string that is equivalent to a hexadecimal display of the EBCDIC code points. For example, the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte ASCII display string '06F1' (including the two single quotes). This name is NULL if the conversation is started locally (i.e., not with a FMH5 ATTACH)." ::= { appcActiveConvEntry 21 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.34.3.1.5.1.1.1 | appcActiveConvLocLuName | 0 | 0 | The SNA name of the local LU for the conversation. This field is from 1 to 17 characters in length, including a period (.) which… |
| 1.3.6.1.2.1.34.3.1.5.1.1.2 | appcActiveConvParLuName | 0 | 0 | The SNA name of the partner LU for the conversation. This field is from 1 to 17 characters in length, including a period (.) whi… |
| 1.3.6.1.2.1.34.3.1.5.1.1.3 | appcActiveConvSessIndex | 0 | 0 | Index of entry in appcActSessTable that is associated with this conversation. If this object has the same value as appcActSessIn… |
| 1.3.6.1.2.1.34.3.1.5.1.1.4 | appcActiveConvId | 0 | 0 | The 4-byte ID of the conversation. |
| 1.3.6.1.2.1.34.3.1.5.1.1.5 | appcActiveConvState | 0 | 0 | Indicates the state of the conversation at the instant when the information was retrieved. The values are: reset The conversation… |
| 1.3.6.1.2.1.34.3.1.5.1.1.6 | appcActiveConvType | 0 | 0 | Indicates the type of conversation. The values are: basic Indicates that this conversation supports basic verbs. mapped Indicates t… |
| 1.3.6.1.2.1.34.3.1.5.1.1.7 | appcActiveConvCorrelator | 0 | 0 | This is an 8-byte identifier that the source LU assigns to the conversation; the source LU is the one that sent the allocation re… |
| 1.3.6.1.2.1.34.3.1.5.1.1.8 | appcActiveConvSyncLvl | 0 | 0 | Indicates the highest sync level support for the conversation. The values are: none Indicates that no sync-level processing can be… |
| 1.3.6.1.2.1.34.3.1.5.1.1.9 | appcActiveConvSource | 0 | 0 | Indicates whether the local or partner LU is the source of the conversation, that is, which LU started the conversation by sendin… |
| 1.3.6.1.2.1.34.3.1.5.1.1.10 | appcActiveConvDuplex | 0 | 0 | Indicates the conversation duplex style in effect for the conversation. half Indicates that information can be transferred… |
| 1.3.6.1.2.1.34.3.1.5.1.1.11 | appcActiveConvUpTime | 0 | 0 | The length of time since the conversation started, measured in hundredths of a second. |
| 1.3.6.1.2.1.34.3.1.5.1.1.12 | appcActiveConvSendBytes | 0 | 0 | Indicates the number of bytes that was sent on the conversation. The count includes all SNA RU bytes sent, including those in th… |
| 1.3.6.1.2.1.34.3.1.5.1.1.13 | appcActiveConvRcvBytes | 0 | 0 | Indicates the number of bytes that was received on the conversation. The count includes all SNA RU bytes sent, including those i… |
| 1.3.6.1.2.1.34.3.1.5.1.1.14 | appcActiveConvUserid | 0 | 0 | The user ID that the initiating program provided in the incoming attach. |
| 1.3.6.1.2.1.34.3.1.5.1.1.15 | appcActiveConvPcidNauName | 0 | 0 | The network-qualified NAU name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either CP n… |
| 1.3.6.1.2.1.34.3.1.5.1.1.16 | appcActiveConvPcid | 0 | 0 | The procedure correlation identifier (PCID) of the session. It is an 8-octet value assigned by the control point providing sessio… |
| 1.3.6.1.2.1.34.3.1.5.1.1.17 | appcActiveConvModeName | 0 | 0 | The Mode Name used for this conversation. This is a 1-8 character name. |
| 1.3.6.1.2.1.34.3.1.5.1.1.18 | appcActiveConvLuwIdName | 0 | 0 | The SNA name of the LU that initiated the logical unit of work that is associated with this active TP. This field is from 1 to 17… |
| 1.3.6.1.2.1.34.3.1.5.1.1.19 | appcActiveConvLuwIdInstance | 0 | 0 | The instance identifier for the logical unit of work. |
| 1.3.6.1.2.1.34.3.1.5.1.1.20 | appcActiveConvLuwIdSequence | 0 | 0 | The sequence identifier for the logical unit of work. |