MIB Discovery
1856 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 34 (snanauMIB). 3 (appcMIB). 1 (appcObjects). 5 (appcConversation). 2 (appcHistConvTable). 1 (appcHistConvEntry). 5 (appcHistConvTpName)
OID : 1.3.6.1.2.1.34.3.1.5.2.1.5
TXT : iso. org. dod. internet. mgmt. mib-2. snanauMIB. appcMIB. appcObjects. appcConversation. appcHistConvTable. appcHistConvEntry. appcHistConvTpName
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.2.1.34.3.1.5.2.1.5
Module APPC-MIB (ietf)
NomappcHistConvTpName
Accesreadonly
Statuscurrent
DescriptionThe 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).
SyntaxeOctetString (0...64)