Description 1
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).
Original text from OID Repository
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)."
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)."