Reference record for OID 1.3.6.1.2.1.34.3.1.5.1.1.5



parent
1.3.6.1.2.1.34.3.1.5.1.1 (appcActiveConvEntry)
node code
5
node name
appcActiveConvState
dot oid
1.3.6.1.2.1.34.3.1.5.1.1.5
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) snanauMIB(34) appcMIB(3) appcObjects(1) appcConversation(5) appcActiveConvTable(1) appcActiveConvEntry(1) appcActiveConvState(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) snanauMIB(34) appcMIB(3) appcObjects(1) appcConversation(5) appcActiveConvTable(1) appcActiveConvEntry(1) appcActiveConvState(5)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) snanauMIB(34) appcMIB(3) appcObjects(1) appcConversation(5) appcActiveConvTable(1) appcActiveConvEntry(1) appcActiveConvState(5)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) snanauMIB(34) appcMIB(3) appcObjects(1) appcConversation(5) appcActiveConvTable(1) appcActiveConvEntry(1) appcActiveConvState(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) snanauMIB(34) appcMIB(3) appcObjects(1) appcConversation(5) appcActiveConvTable(1) appcActiveConvEntry(1) appcActiveConvState(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) snanauMIB(34) appcMIB(3) appcObjects(1) appcConversation(5) appcActiveConvTable(1) appcActiveConvEntry(1) appcActiveConvState(5)}
    • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/snanauMIB/appcMIB/appcObjects/appcConversation/appcActiveConvTable/appcActiveConvEntry/appcActiveConvState
  • /iso/identified-organization/dod/internet/mgmt/mib/snanauMIB/appcMIB/appcObjects/appcConversation/appcActiveConvTable/appcActiveConvEntry/appcActiveConvState
  • /iso/org/dod/internet/mgmt/mib-2/snanauMIB/appcMIB/appcObjects/appcConversation/appcActiveConvTable/appcActiveConvEntry/appcActiveConvState
  • /iso/org/dod/internet/mgmt/mib/snanauMIB/appcMIB/appcObjects/appcConversation/appcActiveConvTable/appcActiveConvEntry/appcActiveConvState
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/snanauMIB/appcMIB/appcObjects/appcConversation/appcActiveConvTable/appcActiveConvEntry/appcActiveConvState
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/snanauMIB/appcMIB/appcObjects/appcConversation/appcActiveConvTable/appcActiveConvEntry/appcActiveConvState
    • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/34/3/1/5/1/1/5

    Description by oid_info

    appcActiveConvState OBJECT-TYPE
    SYNTAX INTEGER {
    reset(1),
    send(2),
    receive(3),
    confirm(4),
    confirmSend(5),
    confirmDealloc(6),
    pendingDeallocate(7),
    pendingPost(8),
    sendReceive(9),
    sendOnly(10),
    receiveOnly(11),
    deferReceive(12),
    deferDeallocate(13),
    syncpoint(14),
    syncpointSend(15),
    syncpointDeallocate(16),
    backoutRequired(17)
    }
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
    "Indicates the state of the conversation at the instant when
    the information was retrieved. The values are:
    reset
    The conversation is reset (i.e., deallocated).
    send
    The conversation can send data. This value also
    is returned if the conversation is in
    Send-Pending state.
    receive
    The conversation can receive data.
    confirm
    The conversation has received a confirm
    indicator. It can issue an [MC_]CONFIRMED or
    [MC_]SEND_ERROR verb to change state. It will
    continue in Receive state if an [MC_]CONFIRMED
    verb is issued.
    confirmSend
    The conversation is in Confirm state and changes
    to Send state when an [MC_]CONFIRMED verb is
    issued.
    confirmDealloc
    The conversation is in Confirm state and becomes
    inactive when an [MC_]CONFIRMED verb is issued.
    pendingDeallocate
    The conversation is in Pending-Deallocate state
    while it waits for (MC_)DEALLOCATE TYPE
    (sync_level) to complete.
    pendingPost
    The conversation is in Pending-Post state while
    it waits for the [MC_]RECEIVE_AND_POST verb to
    complete its receive function.
    sendReceive
    The full-duplex conversation can send or receive
    data.
    sendOnly
    The full-duplex conversation can send data, but
    it does not have permission to receive data,
    because the partner TP has already deallocated
    its side of the conversation.
    receiveOnly
    The full-duplex conversation can receive data,
    but it does not have permission to send data,
    because it has already deallocated its side of
    the conversation.
    deferReceive
    Waiting for a successful SYNCPT verb operation to
    go into the receive state.
    deferDeallocate
    Waiting for a successful SYNCPT verb operation to
    go into the reset state.
    syncpoint
    Need to response to a SYNCPT verb issued. After
    successful operation, the next state will be
    receive.
    syncpointSend
    Need to response to a SYNCPT verb issued. After
    successful operation, the next state will be
    send.
    syncpointDeallocate
    Need to response to a SYNCPT verb issued. After
    successful operation, the next state will be
    reset.
    backoutRequired
    TP must execute a BACKOUT verb to backout the
    transaction."
    View at oid-info.com

    Description by mibdepot

    Indicates the state of the conversation at the instant when
    the information was retrieved. The values are:


    reset
    The conversation is reset (i.e., deallocated).
    send
    The conversation can send data. This value also
    is returned if the conversation is in
    Send-Pending state.
    receive
    The conversation can receive data.
    confirm
    The conversation has received a confirm
    indicator. It can issue an [MC_]CONFIRMED or
    [MC_]SEND_ERROR verb to change state. It will
    continue in Receive state if an [MC_]CONFIRMED
    verb is issued.
    confirmSend
    The conversation is in Confirm state and changes
    to Send state when an [MC_]CONFIRMED verb is
    issued.
    confirmDealloc
    The conversation is in Confirm state and becomes
    inactive when an [MC_]CONFIRMED verb is issued.
    pendingDeallocate
    The conversation is in Pending-Deallocate state
    while it waits for (MC_)DEALLOCATE TYPE
    (sync_level) to complete.
    pendingPost
    The conversation is in Pending-Post state while
    it waits for the [MC_]RECEIVE_AND_POST verb to
    complete its receive function.
    sendReceive
    The full-duplex conversation can send or receive
    data.
    sendOnly
    The full-duplex conversation can send data, but
    it does not have permission to receive data,
    because the partner TP has already deallocated
    its side of the conversation.
    receiveOnly
    The full-duplex conversation can receive data,
    but it does not have permission to send data,
    because it has already deallocated its side of
    the conversation.
    deferReceive
    Waiting for a successful SYNCPT verb operation to
    go into the receive state.
    deferDeallocate
    Waiting for a successful SYNCPT verb operation to
    go into the reset state.
    syncpoint
    Need to response to a SYNCPT verb issued. After
    successful operation, the next state will be
    receive.
    syncpointSend
    Need to response to a SYNCPT verb issued. After
    successful operation, the next state will be
    send.
    syncpointDeallocate
    Need to response to a SYNCPT verb issued. After
    successful operation, the next state will be
    reset.
    backoutRequired
    TP must execute a BACKOUT verb to backout the
    transaction.

    Parsed from file rfc2051-APPC.mib.txt
    Company: None
    Module: APPC-MIB

    Description by circitor

    Indicates the state of the conversation at the instant when
    the information was retrieved. The values are:

    reset
    The conversation is reset (i.e., deallocated).
    send
    The conversation can send data. This value also
    is returned if the conversation is in
    Send-Pending state.
    receive
    The conversation can receive data.
    confirm
    The conversation has received a confirm
    indicator. It can issue an [MC_]CONFIRMED or
    [MC_]SEND_ERROR verb to change state. It will
    continue in Receive state if an [MC_]CONFIRMED
    verb is issued.
    confirmSend
    The conversation is in Confirm state and changes
    to Send state when an [MC_]CONFIRMED verb is
    issued.
    confirmDealloc
    The conversation is in Confirm state and becomes
    inactive when an [MC_]CONFIRMED verb is issued.
    pendingDeallocate
    The conversation is in Pending-Deallocate state
    while it waits for (MC_)DEALLOCATE TYPE
    (sync_level) to complete.
    pendingPost
    The conversation is in Pending-Post state while
    it waits for the [MC_]RECEIVE_AND_POST verb to
    complete its receive function.
    sendReceive
    The full-duplex conversation can send or receive
    data.
    sendOnly
    The full-duplex conversation can send data, but
    it does not have permission to receive data,
    because the partner TP has already deallocated
    its side of the conversation.
    receiveOnly
    The full-duplex conversation can receive data,
    but it does not have permission to send data,
    because it has already deallocated its side of
    the conversation.
    deferReceive
    Waiting for a successful SYNCPT verb operation to
    go into the receive state.
    deferDeallocate
    Waiting for a successful SYNCPT verb operation to
    go into the reset state.

    syncpoint
    Need to response to a SYNCPT verb issued. After
    successful operation, the next state will be
    receive.
    syncpointSend
    Need to response to a SYNCPT verb issued. After
    successful operation, the next state will be
    send.
    syncpointDeallocate
    Need to response to a SYNCPT verb issued. After
    successful operation, the next state will be
    reset.
    backoutRequired
    TP must execute a BACKOUT verb to backout the
    transaction.

    Parsed from file APPC-MIB.mib
    Module: APPC-MIB

    Information by oid_info

    Automatically extracted from RFC2051

    Information by mibdepot

    appcActiveConvState OBJECT-TYPE
    SYNTAX  INTEGER {
                 reset(1),
                 send(2),
                 receive(3),
                 confirm(4),
                 confirmSend(5),
                 confirmDealloc(6),
                 pendingDeallocate(7),
                 pendingPost(8),
                 sendReceive(9),
                 sendOnly(10),
                 receiveOnly(11),
                 deferReceive(12),
                 deferDeallocate(13),
                 syncpoint(14),
                 syncpointSend(15),
                 syncpointDeallocate(16),
                 backoutRequired(17)
               }
    ACCESS  read-only
    STATUS  mandatory
    DESCRIPTION
           "Indicates the state of the conversation at the instant when
          the information was retrieved.  The values are:


              reset
                        The conversation is reset (i.e., deallocated).
              send
                        The conversation can send data.  This value also
                        is returned if the conversation is in
                        Send-Pending state.
              receive
                        The conversation can receive data.
              confirm
                        The conversation has received a confirm
                        indicator.  It can issue an [MC_]CONFIRMED or
                        [MC_]SEND_ERROR verb to change state.  It will
                        continue in Receive state if an [MC_]CONFIRMED
                        verb is issued.
              confirmSend
                        The conversation is in Confirm state and changes
                        to Send state when an [MC_]CONFIRMED verb is
                        issued.
              confirmDealloc
                        The conversation is in Confirm state and becomes
                        inactive when an [MC_]CONFIRMED verb is issued.
              pendingDeallocate
                        The conversation is in Pending-Deallocate state
                        while it waits for (MC_)DEALLOCATE TYPE
                        (sync_level) to complete.
              pendingPost
                        The conversation is in Pending-Post state while
                        it waits for the [MC_]RECEIVE_AND_POST verb to
                        complete its receive function.
              sendReceive
                        The full-duplex conversation can send or receive
                        data.
              sendOnly
                        The full-duplex conversation can send data, but
                        it does not have permission to receive data,
                        because the partner TP has already deallocated
                        its side of the conversation.
              receiveOnly
                        The full-duplex conversation can receive data,
                        but it does not have permission to send data,
                        because it has already deallocated its side of
                        the conversation.
              deferReceive
                        Waiting for a successful SYNCPT verb operation to
                        go into the receive state.
              deferDeallocate
                        Waiting for a successful SYNCPT verb operation to
                        go into the reset state.
              syncpoint
                        Need to response to a SYNCPT verb issued.  After
                        successful operation, the next state will be
                        receive.
              syncpointSend
                        Need to response to a SYNCPT verb issued.  After
                        successful operation, the next state will be
                        send.
              syncpointDeallocate
                        Need to response to a SYNCPT verb issued.  After
                        successful operation, the next state will be
                        reset.
              backoutRequired
                        TP must execute a BACKOUT verb to backout the
                        transaction."
    ::= { appcActiveConvEntry  5 }

    Information by circitor

    appcActiveConvState OBJECT-TYPE
      SYNTAX INTEGER {
                      reset(1),
                      send(2),
                      receive(3),
                      confirm(4),
                      confirmSend(5),
                      confirmDealloc(6),
                      pendingDeallocate(7),
                      pendingPost(8),
                      sendReceive(9),
                      sendOnly(10),
                      receiveOnly(11),
                      deferReceive(12),
                      deferDeallocate(13),
                      syncpoint(14),
                      syncpointSend(15),
                      syncpointDeallocate(16),
                      backoutRequired(17)
                     }

      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Indicates the state of the conversation at the instant when
          the information was retrieved.  The values are:

              reset
                        The conversation is reset (i.e., deallocated).
              send
                        The conversation can send data.  This value also
                        is returned if the conversation is in
                        Send-Pending state.
              receive
                        The conversation can receive data.
              confirm
                        The conversation has received a confirm
                        indicator.  It can issue an [MC_]CONFIRMED or
                        [MC_]SEND_ERROR verb to change state.  It will
                        continue in Receive state if an [MC_]CONFIRMED
                        verb is issued.
              confirmSend
                        The conversation is in Confirm state and changes
                        to Send state when an [MC_]CONFIRMED verb is
                        issued.
              confirmDealloc
                        The conversation is in Confirm state and becomes
                        inactive when an [MC_]CONFIRMED verb is issued.
              pendingDeallocate
                        The conversation is in Pending-Deallocate state
                        while it waits for (MC_)DEALLOCATE TYPE
                        (sync_level) to complete.
              pendingPost
                        The conversation is in Pending-Post state while
                        it waits for the [MC_]RECEIVE_AND_POST verb to
                        complete its receive function.
              sendReceive
                        The full-duplex conversation can send or receive
                        data.
              sendOnly
                        The full-duplex conversation can send data, but
                        it does not have permission to receive data,
                        because the partner TP has already deallocated
                        its side of the conversation.
              receiveOnly
                        The full-duplex conversation can receive data,
                        but it does not have permission to send data,
                        because it has already deallocated its side of
                        the conversation.
              deferReceive
                        Waiting for a successful SYNCPT verb operation to
                        go into the receive state.
              deferDeallocate
                        Waiting for a successful SYNCPT verb operation to
                        go into the reset state.

              syncpoint
                        Need to response to a SYNCPT verb issued.  After
                        successful operation, the next state will be
                        receive.
              syncpointSend
                        Need to response to a SYNCPT verb issued.  After
                        successful operation, the next state will be
                        send.
              syncpointDeallocate
                        Need to response to a SYNCPT verb issued.  After
                        successful operation, the next state will be
                        reset.
              backoutRequired
                        TP must execute a BACKOUT verb to backout the
                        transaction."

      ::= { appcActiveConvEntry 5 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Brothers (20)

    OIDNameSub childrenSub Nodes TotalDescription
    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.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.
    1.3.6.1.2.1.34.3.1.5.1.1.21 appcActiveConvTpName 0 0 The transaction program name which started this conversation.
    This name could either be from a FMH5 ATTACH for a remotely
    started…