APPC-MIB: View SNMP OID List / Download MIB

This is the MIB module for objects used to manage network devices with APPC capabilities.

Indicates the desired state of statistics collection: notActive collection of counters is not active. active collection of counters is active. When this object is set to notActive, all of the entries are removed from the appcSessStatsTable. Enumeration: 'notActive': 1, 'active': 2.

Indicates the desired state of RSCV information collection: notActive collection of route selection control vectors is not active. active collection of route selection control vectors is active. Enumeration: 'notActive': 1, 'active': 2.

Indicates the desired state of tracing: notActive collection of tracing information is not active active collection of tracing information is active Enumeration: 'notActive': 1, 'active': 2.

Specifies the parameter to be used in conjunction with activating tracing. The actual content is implementation dependent.

Indicates the current collection options in effect: notActive collection of counters is not active. active collection of counters is active. Statistical entries are present in the appcSessStatsTable only when the value of this object is 'active'. Enumeration: 'notActive': 1, 'active': 2.

Time since the appcCntrlOperStat object last changed. This time is in hundreds of a second.

Indicates the current collection options in effect: notActive collection of route selection control vectors is not active. active collection of route selection control vectors is active. Enumeration: 'notActive': 1, 'active': 2.

Time since the appcCntrlOperRscv object last changed. This time is in hundreds of a second.

Indicates the current state of tracing: notActive collection of tracing information is not active. active collection of tracing information is active. Enumeration: 'notActive': 1, 'active': 2.

Time since the appcCntrlOperTrace object last changed. This time is in hundreds of a second.

Specifies the parameter used in conjunction with activating tracing. The actual content is implementation dependent.

The time, in hundredths of a second, since the APPC portion of the system was last reinitialized.

Specifies the mode name to be used under the following conditions: When an incoming BIND request contains a mode name not defined at the local node. The parameters defined for this mode are used for the inbound implicit mode capability. When an APPC program issues an [MC_]ALLOCATE, [MC_]SEND_CONVERSATION, or CNOS verb, or when a CPI-C program issues an Allocate (CMALLC) call, specifying a mode name not defined at the local node. The parameters defined for this mode are used for the outbound implicit mode capability. This mode name must match a defined entry in the appcModeAdminTable.

Specifies the name of the local LU that is to serve as the default LU. This is the default LU to which are routed inbound BIND requests that exclude the secondary LU name. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. This local LU name must match a defined entry in the appcLluAdminTable.

Specifies whether or not inbound implicit partner LU support is enabled. The following values are defined: no - Specifies that inbound implicit partner LU support is disabled, which means that an incoming bind that specifies a partner LU that is not defined at the local node will be rejected. yes - Specifies that inbound implicit partner LU support is enabled, which provides the capability to accept an incoming BIND request that contains a partner LU name that is not defined at the local node. Enumeration: 'yes': 2, 'no': 1.

Specifies the maximum size of a logical record to be used for a mapped conversation when sending data to either the inbound or outbound implicit partner LU. This size is the maximum number of bytes in a single logical record, as indicated in the LL field of the record. The default value is 32767. Note that this object does not limit the maximum size that an application program can supply on the Send Data call for a mapped conversation.

The local file specification that is to be searched by the APPC attach manager when no DEFINE_TP verb has been issued for the TP name received on an incoming attach. In this case, the attach manager will attempt to start a program whose file name is the same as the incoming TP name. If found, the program is loaded. If not found, the attach is rejected. The value '*' indicates that the normal search path for executable programs is to be used for locating an undefined transaction program. A null string indicates that there is no default file specification for undefined transaction programs.

Specifies how the program will be started. other - Specifies that the default TP operation is none of the methods specified below. It may be a product-specific method. queuedOperatorStarted - Specifies that one version of the program will be run at a time. If an incoming attach arrives and the program has not been started yet, APPC will issue a message to the operator to start the specified program. Subsequent attaches that arrive while the program is active will be queued. queuedOperatorPreloaded - Specifies that one version of the program will be run at a time. If an incoming attach arrives and the program has not been started yet, the Attach will be rejected. The APPC attach manager determines that a TP has started upon reception of an APPC RECEIVE_ALLOCATE verb, or a CPI-C Accept_Conversation (CMACCP) or Specify_Local_TP_Name (CMSLTP) call. No message is sent to the operator. Subsequent attaches that arrive while the program is active are queued. queuedAmStarted - Specifies that one version of the program will be run at a time and will be started by the APPC attach manager. Subsequent attaches that arrive while the program is active will be queued. nonqueuedAmStarted - Specifies that multiple copies of the program will be run at a time and will be started by the APPC attach manager. Enumeration: 'nonqueuedAmStarted': 5, 'queuedAmStarted': 4, 'other': 1, 'queuedOperatorPreloaded': 3, 'queuedOperatorStarted': 2.

Specifies whether or not conversation security will be used for default TPs. no - Specifies that the incoming attach does not have to contain security information. yes - Specifies that the incoming attach must contain valid authentication information (e.g., user ID and password). Enumeration: 'yes': 2, 'no': 1.

Specifies the name of the local control point. This field is from 0 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. A null string indicates that the value is unknown.

Specifies the total number of active APPC sessions supported by this implementation. Sessions for which both LUs are local are counted twice.

Specifies the total number of active HPR APPC sessions.

Specifies the CNOS command or verb to issue. First set the values of the particular CNOS parameter objects (from the range { appcCnosControl 2 } through { appcCnosControl 8 }) that apply to the CNOS command to be executed, set the three CNOS target objects ({ appcCnosControl 9 } through { appcCnosControl 11 }), then set this object to the command to be executed. Here is the list of parameter objects that must be set for each of the CNOS commands: INIT_SESSION_LIMIT - appcCnosMaxSessLimit appcCnosMinCwinLimit appcCnosMinClosLimit appcCnosTargetLocLuName appcCnosTargetParLuName appcCnosTargetModeName CHANGE_SESSION_LIMIT - appcCnosMaxSessLimit appcCnosMinCwinLimit appcCnosMinClosLimit appcCnosResponsible appcCnosTargetLocLuName appcCnosTargetParLuName appcCnosTargetModeName RESET_SESSION_LIMIT - appcCnosResponsible appcCnosDrainPart appcCnosForce appcCnosTargetLocLuName appcCnosTargetParLuName appcCnosTargetModeName Enumeration: 'changeSesslimit': 2, 'initSesslimit': 1, 'resetSesslimit': 3.

Specifies the maximum value that the local LU is to use, during CNOS processing, for the session limit. The local LU, as a target LU, will negotiate a higher session limit it receives in the CNOS request down to this maximum value. The local LU, as a source LU, will restrict the session limit it sends in a CNOS request to a value less than or equal to this maximum value. If set (i.e., greater than 0), this overrides the maximum session limit defined in the appcModeAdminTable. This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to the INITIALIZE_SESSION_LIMIT and CHANGE_SESSION_LIMIT verbs.

Specifies the default minimum contention winner sessions limit. This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to the INITIALIZE_SESSION_LIMIT and CHANGE_SESSION_LIMIT verbs.

Specifies the default minimum contention loser sessions limit. This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to the INITIALIZE_SESSION_LIMIT and CHANGE_SESSION_LIMIT verbs.

Specifies whether the local LU is draining its conversations for this mode. When a mode session limit is reset (via a CNOS RESET_SESSION_LIMIT request), the local LU could be set to process all queued conversations before deactivating all of the sessions (using the SNA Bracket Initiation Stopped or BIS protocol). This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies only to the RESET_SESSION_LIMIT verb. Enumeration: 'yes': 2, 'no': 1.

Specifies whether the partner LU is draining its conversations for this mode. When a mode session limit is reset (via a CNOS RESET_SESSION_LIMIT request), the partner LU could be set to process all queued conversations before deactivating all of the sessions (using the SNA Bracket Initiation Stop or BIS protocol). This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies only to the RESET_SESSION_LIMIT verb. Enumeration: 'yes': 2, 'no': 1.

Specifies which LU is responsible for selecting and deactivating sessions as a result of a change that decreases the session limit or the maximum number of contention winner sessions for the source or target LU. If no session need to be deactivated, this parameter is ignored. source - specifies that the source (local) LU is responsible. The target (partner) LU cannot negotiate this value. target - specifies that the target (partner) LU is responsible. The target LU can negotiate this value to source. This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to the RESET_SESSION_LIMIT and CHANGE_SESSION_LIMIT verbs. Enumeration: 'source': 1, 'target': 2.

Specifies whether the local LU should force the resetting of the session limit when certain error conditions occur that prevent the successful exchange of CNOS request and reply. This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies only to the RESET_SESSION_LIMIT verb. Enumeration: 'yes': 2, 'no': 1.

The SNA name of the local LU to which the CNOS command is to be applied. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. This object should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to all CNOS verbs.

The SNA name of the partner LU to which the CNOS command is to be applied. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. This object should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to all CNOS verbs.

Specifies the mode name to which the CNOS command is to be applied. This object should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to all CNOS verbs.

APPC Local LU Admin Table.

Information about local APPC LUs.

Specifies the name of the local LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.

This value identifies whether the LU is dependent or independent. Enumeration: 'dependent': 1, 'independent': 2.

The local address for this LU is a byte with a value ranging from 0 to 254. For dependent LUs, this value ranges from 1 to 254; for independent LUs this value is always 0.

The maximum number of sessions supported by this LU.

Indicates whether or not the local LU, as the sender of a BIND request, allows a partner partner LU to delay sending the BIND response if the partner LU cannot process the BIND request immediately. Enumeration: 'yes': 2, 'no': 1.

Specifies whether compression is supported. The local LU uses this value for negotiation during session activation (SNA BIND). prohibited - specifies that no compression is to be used. required - specifies that compression is required. negotiable - specifies that the usage of compression is to be negotiated between the LUs. The level of compression is also negotiated. Enumeration: 'required': 2, 'prohibited': 1, 'negotiable': 3.

Specifies the maximum level of compression supported for inbound data. The local LU uses this value in conjunction with appcLluAdminCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression. Enumeration: 'rle': 2, 'lz9': 3, 'none': 1, 'lz10': 4, 'lz12': 5.

Specifies the maximum level of compression supported for outbound data. The local LU uses this value in conjunction with appcLluAdminCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression. Enumeration: 'rle': 2, 'lz9': 3, 'none': 1, 'lz10': 4, 'lz12': 5.

Specifies whether run-length encoding is to be applied to the data before applying Lempel-Ziv-like compression. The local LU uses this value for negotiation during session activation (SNA BIND). This parameter is only supported if LZ compression is used. Enumeration: 'yes': 2, 'no': 1.

A local alias for the local LU. If not known or not applicable, this object contains a zero-length string.

APPC Local LU Operational Table.

Information about local APPC LUs.

Specifies the name of the local LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.

This value identifies whether the LU is dependent or independent. Enumeration: 'dependent': 1, 'independent': 2.

The local address for this LU is a byte with a value ranging from 0 to 254. For dependent LUs, this value ranges from 1 to 254; for independent LUs this value is always 0.

The maximum number of sessions supported by this LU.

Indicates whether or not the local LU, as the sender of a BIND request, allows a partner LU to delay sending the BIND response if the partner LU cannot process the BIND request immediately. Enumeration: 'yes': 2, 'no': 1.

Specifies whether compression is supported. The local LU uses this value for negotiation during session activation (SNA BIND). prohibited - specifies that no compression is to be used. required - specifies that compression is required. negotiable - specifies that the usage of compression is to be negotiated between the LUs. The level of compression is also negotiated. Enumeration: 'required': 2, 'prohibited': 1, 'negotiable': 3.

Specifies the maximum level of compression supported for inbound data. The local LU uses this value in conjunction with appcLluOperCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression. Enumeration: 'rle': 2, 'lz9': 3, 'none': 1, 'lz10': 4, 'lz12': 5.

Specifies the maximum level of compression supported for outbound data. The local LU uses this value in conjunction with appcLluAdminCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression. Enumeration: 'rle': 2, 'lz9': 3, 'none': 1, 'lz10': 4, 'lz12': 5.

Specifies whether run-length encoding is to be applied to the data before applying Lempel-Ziv-like compression. The local LU uses this value for negotiation during session activation (SNA BIND). This parameter is only supported if LZ compression is used. Enumeration: 'yes': 2, 'no': 1.

A local alias for the local LU. If not known or not applicable, this object contains a zero-length string.

Specifies the total number of active APPC sessions for this LU.

APPC Partner LU administrative Table

Entry of APPC Partner LU Information Table. It is indexed by the local and partner LU Names.

The SNA name of the local LU to which this partner LU definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the partner LU definition applies to all local LUs, and not just to a single local LU.

The SNA name of the partner LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.

A local alias for the partner LU. If not known or not applicable, this object contains a zero-length string.

The maximum number of sessions supported by this partner LU.

Specifies the type of session-level security information that a local LU will accept on BIND requests it receives from the partner LU. required - Specifies that the BIND request must carry session level verification information that will be verified upon receipt. accepted - Specifies that the BIND request may carry session level verification information that will be verified upon receipt. notAllowed - Specifies that the BIND request must not carry session level verification information. Enumeration: 'accepted': 2, 'required': 1, 'notAllowed': 3.

Specifies support for different levels of access security information in ATTACH requests received from this partner LU. Possible values are: none - No access security information will be accepted on allocation requests (ATTACH) from this LU. conversation - Allocation requests will not be accepted that include already verified or persistent verification indicators. Accept conversation-level access security information, which must include both a user Id and password, and may also include a profile. alreadyVerified - Allocation requests will be accepted that include already verified indicators. Persistent verification indicators will not be accepted. persistentVerification - Allocation requests will be accepted that include persistent verification indicators. Already verified indicators will not be accepted. aVandpV - Allocation requests will be accepted that include already verified or persistent verification indicators. Enumeration: 'aVandpV': 5, 'conversation': 2, 'none': 1, 'persistentVerification': 4, 'alreadyVerified': 3.

Specifies the link associated with this partner LU. This value points to the row in the table containing information on the link instance. (e.g., the sdlcLSAdminTable of the SNA DLC MIB module). This object may be NULL if the link is not specified or if a link is not applicable (as for APPN-level nodes).

Defined Parallel Sessions Supported. Indicates whether or not multiple sessions between the partner LU and its associated local LU are permitted. Parallel session support also indicates that Change Number of Sessions (CNOS) will be used to negotiate session limits between the LUs. Enumeration: 'yes': 2, 'no': 1.

Table of active partner/local LU pairs. Two entries are present in the table when both LUs in a pair are local.

Entry representing one partner/local LU pair.

The SNA name of the local LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLluOperName, then the two entries being indexed apply to the same resource (specifically, to the same local LU).

The SNA name of the partner LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.

A local alias for the partner LU. If not known or not applicable, this object contains a zero-length string.

The maximum number of sessions supported by this partner LU.

Specifies the type of security information that a local LU will accept on BIND requests it receives from the partner LU. required - Specifies that the BIND request must carry session level verification information that will be verified upon receipt. accepted - Specifies that the BIND request may carry session level verification information that will be verified upon receipt. notAllowed - Specifies that the BIND request must not carry session level verification information. Enumeration: 'accepted': 2, 'required': 1, 'notAllowed': 3.

Specifies support for different levels of security acceptance information in ATTACH requests received from this partner LU. Possible values are: none - No access security information will be accepted on allocation requests (ATTACH) from this LU. conversation - Allocation requests will not be accepted that include already verified or persistent verification indicators. Accept conversation-level access security information, which must include both a user Id and password, and may also include a profile. alreadyVerified - Allocation requests will be accepted that include already verified indicators. Persistent verification indicators will not be accepted. persistentVerification - Allocation requests will be accepted that include persistent verification indicators. Already verified indicators will not be accepted. aVandpV - Allocation requests will be accepted that include already verified or persistent verification indicators. Enumeration: 'aVandpV': 5, 'conversation': 2, 'none': 1, 'persistentVerification': 4, 'alreadyVerified': 3.

Specifies the link associated with this partner LU. This value points to the row in the table containing information on the link instance. (e.g., the sdlcLSAdminTable of the SNA DLC MIB module). This object may be NULL if the link is not specified or if a link is not applicable (as for APPN-level nodes).

Active Parallel Sessions Supported. Indicates whether or not multiple session between the partner LU and its associated local LU are permitted. Parallel session support also indicates that Change Number of Sessions (CNOS) will be used to negotiate session limits between the LUs. Enumeration: 'yes': 2, 'no': 1.

Active Parallel Sessions Supported - last starting value. This object represents the initial value proposed by the local LU the last time this capability was negotiated, i.e., when the first session was bound between the local LU and its partner. Enumeration: 'yes': 2, 'no': 1.

The value identifies the current operational state of this LU pair: inactive (1) - no active or pending session exists between the LUs. active (2) - an active or pending session exists between the LUs. Enumeration: 'active': 2, 'inactive': 1.

APPC Mode Table

Entry of APPC Mode Information Table.

The SNA name of the local LU to which this mode definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the mode definition applies to all local LUs for the SNA node identified by appcLocalCpName, and not just to a single local LU.

The SNA name of the partner LU to which this mode definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the mode definition applies to all partner LUs for the SNA node identified by appcModeAdminLocLuName, and not just to a single partner LU.

Specifies the mode name. A mode defines the characteristics for a group of sessions. The mode name can be blank (8 space characters).

Specifies the class of service (COS) name associated with this mode. If the implementation does not support COS names, a null string is returned.

Specifies the name of the transaction program (TP) to be invoked when a session using this mode is deactivated or ended. If no such TP is defined, this object is a null string. 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).

Specifies the maximum value that the local LU is to use, during CNOS processing, for the session limit. The local LU, as a target LU, will negotiate a higher session limit it receives in the CNOS request down to this maximum value. The local LU, as a source LU, will restrict the session limit it sends in a CNOS request to a value less than or equal to this maximum value.

Specifies the default minimum contention winner sessions limit. Some implementations internally issue a INITIALIZE_SESSION_LIMIT verb when a Mode is created. This value is the parameter used for the CNOS processing of that verb. This parameter is not used when issuing an explicit INITIALIZE_SESSION_LIMIT verb. The equivalent object in appcCnosCommandTable is used.

Specifies the default minimum contention loser sessions limit. Some implementations internally issue a INITIALIZE_SESSION_LIMIT verb when a Mode is created. This value is the parameter used for the CNOS processing of that verb. This is the same as target minimum contention winner sessions. This parameter is not used when issuing an explicit INITIALIZE_SESSION_LIMIT verb. The equivalent object in appcCnosCommandTable is used.

Specifies the limit on the number of contention winner sessions to be automatically activated when the minimum number of contention winner sessions increases (as a result of CNOS processing). The actual number of sessions activated is the lesser of this value and the new minimum number of contention winner sessions.

Specifies the size of the receive pacing window. This value is used for negotiation during session activations (SNA BIND). The meaning of this value when set to 0 depends on whether adaptive pacing is supported: adaptive pacing No limit on window size fixed pacing No pacing is supported

Specifies the size of the send pacing window. This value is used for negotiation during session activations (SNA BIND). The meaning of this value when set to 0 depends on whether adaptive pacing is supported: adaptive pacing No limit on window size fixed pacing No pacing is supported

Specifies the preferred receive RU (Request Unit) size of normal-flow requests on the sessions. This value must be less than or equal to the value specified in appcModeAdminRecvRuSzUpBnd and greater than or equal to the value specified in appcModeAdminRecvRuSzLoBnd. The local LU specifies this value for the receive maximum RU size in session activation (SNA BIND) requests and responses. It will allow negotiation up to the appcModeAdminRecvRuSzUpBnd value or down to the appcModeAdminRecvRuSzLoBnd value.

Specifies the preferred send RU (Request Unit) size of normal- flow requests on the sessions. This value must be less than or equal to the value specified in appcModeAdminSendRuSzUpBnd and greater than or equal to the value specified in appcModeAdminSendRuSzLoBnd. The local LU specifies this value for the send maximum RU size in session activation (SNA BIND) requests and responses. It will allow negotiation up to the appcModeAdminSendRuSzUpBnd value or down to the appcModeAdminSendRuSzLoBnd value.

Specifies the upper bound for the maximum receive RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND).

Specifies the upper bound for the maximum send RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND).

Specifies the lower bound for the maximum receive RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND).

Specifies the lower bound for the maximum send RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND).

Specifies the responsibility for session reinitiation of a single session with the partner LU (when the session goes down). The local LU uses this parameter to specify the session reinitiation responsibility in session activation (SNA BIND) requests and responses. notApplicable - specifies that this parameter has no meaning since the value of appcLuPairAdminParaSessSup is yes. The field in the SNA BIND is reserved (set to zero). operatorControlled - specifies that neither LU will automatically attempt to reinitiate the session. The operator on either side will manually reactivate the session. A contention race (both side reinitiating at the same time) is won by the LU with the lexicographically greater fully- qualified LU name. primaryOnly - specifies that the primary LU will automatically attempt to reinitiate the session. secondaryOnly - specifies that the secondary LU will automatically attempt to reinitiate the session. primaryOrSecondary - specifies that either the primary or the secondary may automatically attempt to reinitiate the session. A contention race is handled the same way as with operatorControlled. Enumeration: 'notApplicable': 1, 'primaryOnly': 3, 'operatorControlled': 2, 'primaryOrSecondary': 5, 'secondaryOnly': 4.

Specifies whether compression is supported. The local LU uses this value for negotiation during session activation (SNA BIND). prohibited - specifies that no compression is to be used. required - specifies that compression is required. negotiable - specifies that the usage of compression is to be negotiated between the LUs. The level of compression is also negotiated. Enumeration: 'required': 2, 'prohibited': 1, 'negotiable': 3.

Specifies the maximum level of compression supported for inbound data. The local LU uses this value in conjunction with appcModeAdminCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression. Enumeration: 'rle': 2, 'lz9': 3, 'none': 1, 'lz10': 4, 'lz12': 5.

Specifies the maximum level of compression supported for outbound data. The local LU uses this value in conjunction with appcModeAdminCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression. Enumeration: 'rle': 2, 'lz9': 3, 'none': 1, 'lz10': 4, 'lz12': 5.

Specifies whether run-length encoding is to be applied to the data before applying Lempel-Ziv-like compression. The local LU uses this value for negotiation during session activation (SNA BIND). This parameter is only supported if LZ compression is used. Enumeration: 'yes': 2, 'no': 1.

Specifies the sync level support. This value is used for negotiation during session activations (SNA BIND). none - No sync level is supported. noneConfirm - None and Confirm levels supported. noneConfirmSyncPoint - None, Confirm, and Sync Point is supported. Enumeration: 'none': 1, 'noneConfirmSyncPoint': 3, 'noneConfirm': 2.

Specifies whether session-level cryptography is supported. This value is used for negotiation during session activations (SNA BIND). notSupported - Specifies session-level cryptography is not to be used. mandatory - Specifies session-level cryptography must be used. selective - Specifies session-level cryptography is required just on selected requests flowing on the sessions. Enumeration: 'notSupported': 1, 'mandatory': 2, 'selective': 3.

Operational APPC Mode Information. Two entries are present in the table when both LUs in a pair are local.

Entry of APPC mode operational information table. This entry does not augment the appcModeAdminEntry, but reflects an actual operational mode for a given local LU - partner LU pair.

The SNA name of the local LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLluOperName, then the two entries being indexed apply to the same resource (specifically, to the same local LU).

The SNA name of the partner LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLuPairOperParLuName, then the two entries being indexed apply to the same resource (specifically, to the same partner LU).

Specifies the mode name. A mode defines the characteristics for a group of sessions. The mode name can be blank (8 space characters).

Specifies the class of service (COS) name associated with this mode. If the implementation does not support COS names, a zero-length string is returned.

Specifies the name of the transaction program (TP) to be invoked when a session using this mode is deactivated or ended. If the name is NULL, no transaction program is invoked. 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).

Specifies the current session limit of this mode as negotiated through APPC CNOS (Change Number of Sessions) processing. Identifies the total number of sessions that can be established between the local and partner LU using this mode.

Specifies the maximum value that the local LU is to use, during CNOS processing, for the session limit. The local LU, as a target LU, will negotiate a higher session limit it receives in the CNOS request down to this maximum value. The local LU, as a source LU, will restrict the session limit it sends in a CNOS request to a value less than or equal to this maximum value.

Specifies the minimum contention winner sessions limit that was negotiated via CNOS processing.

Specifies the minimum contention loser sessions limit that was negotiated via CNOS processing. This is the same as target minimum contention winner sessions.

Specifies the limit on the number of contention winner sessions to be automatically activated when the minimum number of contention winner sessions increases (as a result of CNOS processing). The actual number of sessions activated is the lesser of this value and the new minimum number of contention winner sessions.

Specifies the size of the receive pacing window. This value is used for negotiation during session activations (SNA BIND). The meaning of this value when set to 0 depends on whether adaptive pacing is supported: adaptive pacing - No limit on window size fixed pacing - No pacing is supported

Specifies the size of the send pacing window. This value is used for negotiation during session activations (SNA BIND). The meaning of this value when set to 0 depends on whether adaptive pacing is supported: adaptive pacing No limit on window size fixed pacing No pacing is supported

Specifies the preferred receive RU (Request Unit) size of normal-flow requests on the sessions. This value must be less than or equal to the value specified in appcModeOperRecvRuSzUpBnd and greater than or equal to the value specified in appcModeOperRecvRuSzLoBnd. The local LU specifies this value for the receive maximum RU size in session activation (SNA BIND) requests and responses. It will allow negotiation up to the appcModeOperRecvRuSzUpBnd value or down to the appcModeOperRecvRuSzLoBnd value.

Specifies the preferred send RU (Request Unit) size of normal- flow requests on the sessions. This value must be less than or equal to the value specified in appcModeOperSendRuSzUpBnd and greater than or equal to the value specified in appcModeOperSendRuSzLoBnd. The local LU specifies this value for the send maximum RU size in session activation (SNA BIND) requests and responses. It will allow negotiation up to the appcModeOperSendRuSzUpBnd value or down to the appcModeOperSendRuSzLoBnd value.

Specifies the upper bound for the maximum receive RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND).

Specifies the upper bound for the maximum send RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND).

Specifies the lower bound for the maximum receive RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND).

Specifies the lower bound for the maximum send RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND).

Specifies the responsibility for session reinitiation of a single session with the partner LU (when the session goes down). The local LU uses this parameter to specify the session reinitiation responsibility in session activation (SNA BIND) requests and responses. notApplicable - specifies that this parameter has no meaning since the value of appcLuPairOperParaSessSup is yes. The field in the SNA BIND is reserved (set to zero). operatorControlled - specifies that neither LU will automatically attempt to reinitiate the session. The operator on either side will manually reactivate the session. A contention race (both side reinitiating at the same time) is won by the LU with the lexicographically greater fully- qualified LU name. primaryOnly - specifies that the primary LU will automatically attempt to reinitiate the session. secondaryOnly - specifies that the secondary LU will automatically attempt to reinitiate the session. primaryOrSecondary - specifies that either the primary or the secondary may automatically attempt to reinitiate the session. A contention race is handled the same way as with operatorControlled. Enumeration: 'notApplicable': 1, 'primaryOnly': 3, 'operatorControlled': 2, 'primaryOrSecondary': 5, 'secondaryOnly': 4.

Specifies whether compression is supported. The local LU uses this value for negotiation during session activation (SNA BIND). prohibited - specifies that no compression is to be used. required - specifies that compression is required. negotiable - specifies that the usage of compression is to be negotiated between the LUs. The level of compression is also negotiated. Enumeration: 'required': 2, 'prohibited': 1, 'negotiable': 3.

Specifies the maximum level of compression supported for inbound data. The local LU uses this value in conjunction with appcModeOperCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression. Enumeration: 'rle': 2, 'lz9': 3, 'none': 1, 'lz10': 4, 'lz12': 5.

Specifies the maximum level of compression supported for outbound data. The local LU uses this value in conjunction with appcModeOperCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression. Enumeration: 'rle': 2, 'lz9': 3, 'none': 1, 'lz10': 4, 'lz12': 5.

Specifies whether run-length encoding is to be applied to the data before applying Lempel-Ziv-like compression. The local LU uses this value for negotiation during session activation (SNA BIND). This parameter is only supported if LZ compression is used. Enumeration: 'yes': 2, 'no': 1.

Specifies the sync level support for sessions involving this LU pair and mode name. none - No sync level is supported. noneConfirm - None and Confirm level supported. noneConfirmSyncPoint - None, Confirm and Sync Point is supported. Enumeration: 'none': 1, 'noneConfirmSyncPoint': 3, 'noneConfirm': 2.

Specifies whether session-level cryptography is supported for sessions involving this LU pair and mode name. notSupported - Specifies session-level cryptography is not being used. mandatory - Specifies session-level cryptography in being used on all requests flowing on the sessions. selective - Specifies session-level cryptography is required just on selected requests flowing on the sessions. Enumeration: 'notSupported': 1, 'mandatory': 2, 'selective': 3.

Specifies the sync level support. This value represents the initial value proposed by the local LU the last time this capability was negotiated, i.e., when the first session was bound between the local LU and its partner. none - No sync level is supported. noneConfirm - None and Confirm level supported. noneConfirmSyncPoint - None, Confirm and Sync Point is supported. Enumeration: 'none': 1, 'noneConfirmSyncPoint': 3, 'noneConfirm': 2.

Specifies whether session-level cryptography is supported. This value represents the initial value proposed by the local LU the last time this capability was negotiated, i.e., when the first session was bound between the local LU and its partner. notSupported - Specifies session-level cryptography is not to be used. mandatory - Specifies session-level cryptography must be used. selective - Specifies session-level cryptography is required just on selected requests flowing on the sessions. Enumeration: 'notSupported': 1, 'mandatory': 2, 'selective': 3.

Specifies whether CNOS negotiation is in process. CNOS negotiation is used to set or change the various session limits for a mode. Enumeration: 'yes': 2, 'no': 1.

Specifies the number of active contention winner sessions.

Specifies the number of active contention loser sessions.

Specifies the number of contention winner sessions that are pending activation.

Specifies the number of contention loser sessions that are pending activation.

Specifies the number of contention winner sessions that are pending termination.

Specifies the number of contention loser sessions that are pending termination.

Specifies whether the local LU is draining its conversations for this mode. When a mode session limit is reset (via a CNOS RESET_SESSION_LIMIT request), the local LU could be set to process all queued conversations before deactivating all of the sessions (using the SNA Bracket Initiation Stopped or BIS protocol). Enumeration: 'yes': 2, 'no': 1.

Specifies whether the partner LU is draining its conversations for this mode. When a mode session limit is reset (via a CNOS RESET_SESSION_LIMIT request), the partner LU could be set to process all queued conversations before deactivating all of the sessions (using the SNA Bracket Initiation Stop or BIS protocol). Enumeration: 'yes': 2, 'no': 1.

APPC Local TP Table

Entry of APPC Local TP Information Table.

The SNA name of the local LU to which this TP definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the TP definition applies to all local LUs, and not just to a single local LU.

The local transaction program name. This name is sent on an ATTACH remote allocation request. 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).

The local file specification of the transaction program. May be a zero-length string if not applicable.

A parameter string passed to the transaction program when it is started. May be a zero-length string if not supported.

Specifies how the program will be started. other - Specifies that the program operation is none of the methods specified. It may be a product-specific method. queuedOperatorStarted - Specifies that one version of the program will be run at a time. If an incoming attach arrives and the program has not been started yet, APPC will issue a message to the operator to start the specified program. Subsequent attaches that arrive while the program is active will be queued. queuedOperatorPreloaded - Specifies that one version of the program will be run at a time. If an incoming attach arrives and the program has not been started yet, the Attach will be rejected. The APPC attach manager determines that a TP has started upon reception of an APPC RECEIVE_ALLOCATE verb, or a CPI-C Accept_Conversation (CMACCP) or Specify_Local_TP_Name (CMSLTP) call. No message is sent to the operator. Subsequent attaches that arrive while the program is active are queued. queuedAmStarted - Specifies that one version of the program will be run at a time and will be started by the APPC attach manager. Subsequent attaches that arrive while the program is active will be queued. nonqueuedAmStarted - Specifies that multiple copies of the program will be run at a time and will be started by the APPC attach manager. Enumeration: 'nonqueuedAmStarted': 5, 'queuedAmStarted': 4, 'other': 1, 'queuedOperatorPreloaded': 3, 'queuedOperatorStarted': 2.

This object specifies the number of seconds incoming attaches will be queued waiting for an APPC program to issue a RECEIVE_ALLOCATE verb or for a CPI-C program to issue an Accept_Conversation (CMACCP) call. This parameter is meaningful only when appcTpAdminTpOperation has one of the following values: queuedOperatorStarted queuedOperatorPreloaded queuedAmStarted A value of zero indicates that there is no timeout.

This object specifies the number of seconds an APPC program's RECEIVE_ALLOCATE verb or a CPI-C program's Accept_Conversation (CMACCP) call will wait for an incoming attach to arrive. A value of zero indicates that there is no timeout.

Indicates the synchronization level or levels that the transaction program supports. The levels are defined as follows: none - allocation requests indicating a synchronization level of none are allowed to start the program. confirm - allocation requests indicating a synchronization level of confirm are allowed to start the program. syncpoint - allocation requests indicating a synchronization level of sync point are allowed to start the program. Enumeration: 'none': 1, 'confirm': 2, 'syncpoint': 4, 'confirmAndSyncpoint': 6, 'all': 7, 'noneAndSyncpoint': 5, 'noneAndConfirm': 3.

The maximum number of concurrent instances of this transaction program that will be supported for a local LU. A value of zero indicates that there is no limit.

Indicates the status of the TP relative to starting execution when the local LU receives an allocation (ATTACH) request naming this program. enabled - the local LU can start the program. tempDisabled - the local LU cannot start the program. The local LU rejects the request with an indication that the TP is not available but retry is possible. permDisabled - the local LU cannot start the program. The local LU rejects the request with an indication that the TP is not available and retry is not possible. Enumeration: 'enabled': 1, 'permDisabled': 3, 'tempDisabled': 2.

Indicates whether this is a long-running transaction program (i.e., one that stays around even after the conversation goes away). Enumeration: 'yes': 2, 'no': 1.

Specifies the conversation type (basic or mapped) that will be used by the TP. This value is verified upon receipt of an incoming attach. The acceptable values are: basic - Indicates that this transaction program supports basic conversations. mapped - Indicates that this transaction program supports mapped conversations. basicOrMapped - Indicates that this transaction program supports both basic and mapped conversations. Enumeration: 'mapped': 2, 'basicOrMapped': 3, 'basic': 1.

Specifies the conversation duplex type (half or full) that will be used by the TP. This value is verified upon receipt of an incoming attach. The acceptable values are: half - Indicates that this transaction program supports half duplex conversations. full - Indicates that this transaction program supports full duplex conversations. halfOrFull - Indicates that this transaction program supports either half or full duplex conversations. Enumeration: 'full': 2, 'halfOrFull': 3, 'half': 1.

Indicates whether conversation-level security information is required on incoming attaches designating this TP name. Conversation-level security verification is always performed on those requests that include security information. yes - Indicates that conversation-level security information is required. ATTACHs designating the transaction program must carry a user_id and either a password or an already verified indicator. no - Indicates that no security information is required. ATTACHs designating the transaction program can omit or include security information. Enumeration: 'yes': 2, 'no': 1.

Specifies whether the number of PIP (Program Initialization Parameters) subfields should be verified against the number expected (appcTpAdminPipSubNum). Enumeration: 'yes': 2, 'no': 1.

Specifies the number of PIP subfields expected by the TP.

Table of active APPC sessions. Two entries are present in the table when both session partners are local.

Entry of APPC Session Information Table. Indexed by LU pair and integer-valued session index.

Specifies the name of the local LU for the session. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLluOperName, then the two entries being indexed apply to the same resource (specifically, to the same local LU).

Specifies the name of the partner LU for the session. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLuPairOperParLuName, then the two entries being indexed apply to the same resource (specifically, to the same partner LU).

This value identifies the index of the session, which is unique for this LU pair. It is recommended that an Agent not reuse the index of a deactivated session for a significant period of time (e.g., one week).

The network-qualified CP name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located. This field is from 3 to 17 characters in length, including a period (.) which separates the NetId from the NAU name. A null string indicates that the value is unknown.

The procedure correlation identifier (PCID) of a session. It is an 8-octet value assigned by the control point providing session services for the primary LU. A null string indicates that the value is unknown.

Indicates which LU is the PLU for this session. For independent LUs, the PLU (primary LU) is the one that initiated the session (sent BIND), while the SLU (secondary LU) is the one that accepted the session initiation (received BIND). The 'local' LU is the one identified by appcLluOperName. The 'partner' LU is the one identified by appcLuPairOperParLuName. Enumeration: 'partnerLuIsPl': 2, 'localLuIsPl': 1.

The mode name used for this session.

The Class of Service (COS) name used for this session. A null string indicates that the value is unknown.

The transmission priority of this session. 1 = unknown priority 2 = low priority 3 = medium priority 4 = high priority 5 = network priority Enumeration: 'high': 4, 'unknown': 1, 'medium': 3, 'low': 2, 'network': 5.

Enhanced security supported. Indicates the level of enhanced security support: 1 = none 2 = level 1 3 = level 2 Enumeration: 'level1': 2, 'none': 1, 'level2': 3.

The type of pacing being used for sending data. Enumeration: 'none': 1, 'fixed': 2, 'adaptive': 3.

The send residual pace count. This represents the number of MUs that can still be sent in the current session window.

The size of the next window which will be used to send data.

The type of pacing being used for receiving data. Enumeration: 'none': 1, 'fixed': 2, 'adaptive': 3.

The receive residual pace count. This represents the number of MUs that can still be received in the current session window.

The size of the next window which will be used to receive data.

The route selection control vector (RSCV CV2B) used for this session. It is present for APPN-level implementations. LEN-level implementations will return a null string. The internal format of this vector is described in SNA Formats. This object contains an uninterpreted copy of the control vector (including the length and key fields).

Specifies whether the session is currently in use (i.e., in bracket with a conversation). Enumeration: 'yes': 2, 'no': 1.

The maximum RU size used on this session for sending RUs.

The maximum RU size used on this session for receiving RUs.

The size of the send pacing window on this session.

The size of the receive pacing window on this session.

The value indicates the current operational state of the session. 'unbound (1)' - session has been unbound; in this state it will be removed from the session table by the Agent. 'pendingBind (2)' - this state has different meanings for dependent and independent LUs; for dependent LU - waiting for BIND from the host, for independent LU - waiting for BIND response. When a session enters this state, the corresponding entry in the session table is created by the Agent. 'bound (3)' - session has been successfully bound. 'pendingUnbind (4)' - session enters this state when an UNBIND is sent and before the rsp(UNBIND) is received. Session deactivation: If a session is in the operational state 'bound (3)' then setting the value of this object to 'unbound (1)' will initiate the session shutdown. If a session is in the operational state 'pendingBind (2)' then setting the value of this object to 'unbound (1)' will initiate the session shutdown. If a session is in the operational state 'pendingUnbind (4)' for an abnormally long period of time (e.g., three minutes) then setting the value of this object to 'unbound (1)' will change the session operational state to 'unbound (1)'. Enumeration: 'pendingUnbind': 4, 'unbound': 1, 'bound': 3, 'pendingBind': 2.

The length of time the session has been active, measured in hundredths of a second.

The local HPR Network Connection Endpoint of the session.

The local RTP connection TCID of the session.

This value identifies the link over which the session passes. This value points to the row in the table containing information on the link instance. (e.g., the sdlcLSAdminTable of the SNA DLC MIB module). This object may be NULL if the link is not specified or if a link is not applicable (as for APPN-level nodes).

This table contains dynamic statistical information relating to active APPC sessions. The entries in this table cannot be created by a Management Station. Two entries are present in the table when both session partners are local. This table is populated only when the value of appcCntrlOperStat is 'active'.

Contains statistics information for an APPC session. Each entry is created by the Agent. Objects in this table have read-only access. Each session from appcActSessTable has one entry in this table.

Specifies the name of the local LU for the session. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLluOperName, then the two entries being indexed apply to the same resource (specifically, to the same local LU).

Specifies the name of the partner LU for the session. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLuPairOperParLuName, then the two entries being indexed apply to the same resource (specifically, to the same partner LU).

This value identifies the index of the session, which is unique for this LU pair. It is recommended that an Agent not reuse the index of a deactivated session for a significant period of time (e.g., one week). If this object has the same value as appcActSessIndex for the same LU pair, then the two entries being indexed apply to the same resource (specifically, to the same session).

The number of function management data (FMD) bytes sent by the local LU.

The number of non-function management data (non-FMD) bytes sent by the local LU.

The number of function management data (FMD) bytes received by the local LU.

The number of non-function management data (non-FMD) bytes received by the local LU.

The number of function management data (FMD) RUs sent by the local LU.

The number of non-function management data (non-FMD) RUs sent by the local LU.

The number of function management data (FMD) RUs received by the local LU.

The number of non-function management data (non-FMD) RUs received by the local LU.

The length of time the counters for this session have been active, measured in hundredths of a second.

Table of historical information about APPC sessions that terminated abnormally. Two entries may be present in the table when both session partners are local. It is an implementation choice how long to retain information about a given session.

Entry of APPC Session History Table. This table is indexed by an integer which is continuously incremented until it eventually wraps.

Table index. The value of the index begins at zero and is incremented up to a maximum value of 2**31-1 (2,147,483,647) before wrapping.

The time at which the session was either terminated or failed to be established.

Indicates the type of event that caused the entry to be made: recvNegBindRsp - Received a negative bind response from the partner LU. sendNegBindRsp - Sent a negative bind response to the partner LU. sessActRejected - Session activation rejected by the partner LU. unbindSent - Unbind sent to the partner LU. unbindReceived - Unbind received from the partner LU. These event types correspond to the five SNA/MS Alerts LU62001 through LU62005, documented in the SNA Management Services Reference. Enumeration: 'unbindSent': 4, 'sendNegBindRsp': 2, 'sessActRejected': 3, 'recvNegBindRsp': 1, 'unbindReceived': 5.

The network-qualified local LU name. This field is from 3 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.

The network-qualified partner LU name. This field is from 3 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.

The mode name of the session.

The type of unbind which terminated the session. This value is consists of one (1) octet; and its meaning is defined in SNA Formats.

The sense data associated with the termination of the session, taken from the negative BIND response or UNBIND request.

The implementation-specific name of the component which detected the problem.

The implementation-specific name of the module which detected the problem.

A table indicating how many APPC sessions terminating in this node are transported by each RTP connection.

Entry of APPC session RTP table.

The local Network Connection Endpoint of the RTP connection.

The local TCID of the RTP connection.

The number of APPC sessions terminating in this node that are using this RTP connection.

Table of information about active APPC Conversations. In this context 'active' means that a conversation is currently associated with a particular session. Two entries are present in the table when both LUs for the session are local.

Entry representing one active APPC Conversation.

The SNA name of the local LU for the conversation. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLluOperName, then the two entries being indexed apply to the same resource (specifically, to the same local LU).

The SNA name of the partner LU for the conversation. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLuPairOperParLuName, then the two entries being indexed apply to the same resource (specifically, to the same partner LU).

Index of entry in appcActSessTable that is associated with this conversation. If this object has the same value as appcActSessIndex for the same LU pair, then the two entries being indexed apply to the same resource (specifically, to the same session).

The 4-byte ID of the conversation.

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. Enumeration: 'reset': 1, 'confirmSend': 5, 'sendReceive': 9, 'deferDeallocate': 13, 'pendingDeallocate': 7, 'sendOnly': 10, 'confirm': 4, 'receive': 3, 'backoutRequired': 17, 'send': 2, 'syncpoint': 14, 'receiveOnly': 11, 'deferReceive': 12, 'syncpointDeallocate': 16, 'pendingPost': 8, 'syncpointSend': 15, 'confirmDealloc': 6.

Indicates the type of conversation. The values are: basic Indicates that this conversation supports basic verbs. mapped Indicates that this conversation supports mapped verbs. Enumeration: 'mapped': 2, 'basic': 1.

This is an 8-byte identifier that the source LU assigns to the conversation; the source LU is the one that sent the allocation request. The conversation correlator is included on the allocation request. The conversation correlator uniquely identifies a conversation, from among all conversations, between the local and partner LUs. It may be used, for example, during problem determination associated with a conversation. A length of 0 indicates that no conversation correlator is defined.

Indicates the highest sync level support for the conversation. The values are: none Indicates that no sync-level processing can be performed on this conversation. The transaction program does not issue verbs or recognize any returned parameters relating to any sync-level function. confirm Indicates that confirmation processing can be performed on this conversation. The transaction program can issue verbs and recognize returned parameters relating to confirmation. syncpt Indicates that syncpt and confirmation processing can be performed on this conversation. The transaction program can issue verbs and recognize returned parameters relating to syncpt and confirmation. Enumeration: 'none': 1, 'syncpt': 3, 'confirm': 2.

Indicates whether the local or partner LU is the source of the conversation, that is, which LU started the conversation by sending the allocation request. localLu The local LU is the source of the conversation, and the partner LU is the target of the conversation. partnerLu The partner LU is the source of the conversation, and the local LU is the target of the conversation. Enumeration: 'partnerL': 2, 'localL': 1.

Indicates the conversation duplex style in effect for the conversation. half Indicates that information can be transferred in both directions, but only in one direction at a time. full Indicates that information can be transferred in both directions at the same time. Enumeration: 'full': 2, 'half': 1.

The length of time since the conversation started, measured in hundredths of a second.

Indicates the number of bytes that was sent on the conversation. The count includes all SNA RU bytes sent, including those in the FMH-5 (Attach), FMH-7 (Error Description), SIGNAL, LUSTAT, and SNA responses; it does not include SNA TH and RH bytes.

Indicates the number of bytes that was received on the conversation. The count includes all SNA RU bytes sent, including those in the FMH-5 (Attach), FMH-7 (Error Description), SIGNAL, LUSTAT, and SNA responses; it does not include SNA TH and RH bytes.

The user ID that the initiating program provided in the incoming attach.

The network-qualified NAU name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located. This field is from 3 to 17 characters in length, including a period (.) which separates the NetId from the NAU name. A null string indicates that the value is unknown.

The procedure correlation identifier (PCID) of the session. It is an 8-octet value assigned by the control point providing session services for the primary LU. A null string indicates that the value is unknown.

The Mode Name used for this conversation. This is a 1-8 character name.

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 characters in length, including a period (.) which separates the NetId from the LU name if the NetId is present.

The instance identifier for the logical unit of work.

The sequence identifier for the logical unit of work.

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).

Table of historical information about APPC Conversations that ended in error. Possible categories of error conditions that could be saved in this table are: - allocation errors, - deallocate abend, - program errors, and - service errors.

Entry representing one APPC Conversation.

Index for entry in Conversation table. This value identifies the unique index of the conversation. It is recommended that an Agent not reuse the index of a deactivated conversation for a significant period of time (e.g. one week).

The time at which the conversation ended.

The name of the local LU for this conversation. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.

The SNA name of the partner LU for the conversation. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.

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).

The network-qualified NAU name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located. This field is from 3 to 17 characters in length, including a period (.) which separates the NetId from the NAU name. A null string indicates that the value is unknown.

The procedure correlation identifier (PCID) of the session. It is an 8-octet value assigned by the control point providing session services for the primary LU. A null string indicates that the value is unknown.

The sense data associated with the action that ended this conversation, e.g., FMH-7 or UNBIND.

The first 32 bytes of the data portion of the Log Data GDS Variable that is associated with the last FMH-7 that occurred on this conversation. If there was no Log Data GDS Variable associated with the FMH-7, this object is null. This object reflects only the data portion of the Log Data GDS Variable (i.e. not the LL or GDS Id).

Indicates which LU ended the conversation. Enumeration: 'partnerL': 2, 'localL': 1.

APPC CPI-C side information table.

Entry of APPC CPI-C side information Table.

The SNA name of the local LU to which this CPI-C side information definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the definition applies to all local LUs, and not just to a single local LU.

Specifies the symbolic destination name used by CPI-C applications to identify this definition.

A local alias for the partner LU. If not known or not applicable, this object contains a zero-length string.

The SNA name of the partner LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.

Specifies the mode name. A mode defines the characteristics for a group of sessions. The mode name can be blank (8 space characters).

Specifies whether the TP name in appcCpicAdminTpName identifies a normal TP or an SNA service TP. In this context, a normal TP is one with a name consisting only of displayable characters, while an SNA service TP has a name containing octets that do not map to displayable characters. Enumeration: 'snaServiceTp': 2, 'normal': 1.

Specifies the name of the partner TP to be used when a CPI-C application initiates a conversation specifying this side information entry. Display convention 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).

The security userid, if any, associated with the side information definition.

Specifies the security information to be used for allocating the conversation. none - No security information. same - Use the security environment currently associated with this TP. pgm - Use the program-supplied user_id and password. pgmStrong - Use the program-supplied user_id and password. The local LU will insure that the password is not exposed in clear-text form on the physical network. distributed - Use the security environment and a distributed security system to generate the authentication information for this request. If distributed security tokens cannot be generated, then fail the conversation. mutual - Authenticate both the user to the destination system and the destination system to the user. Enumeration: 'none': 1, 'pgmStrong': 4, 'pgm': 3, 'distributed': 5, 'mutual': 6, 'same': 2.

APPC CPI-C side information operational table.

Entry of APPC CPI-C side information Table.

The SNA name of the local LU to which this CPI-C side information definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the definition applies to all local LUs, and not just to a single local LU.

Specifies the symbolic destination name used by CPI-C applications to identify this definition.

A local alias for the partner LU. If not known or not applicable, this object contains a zero-length string.

The SNA name of the partner LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.

Specifies the mode name. A mode defines the characteristics for a group of sessions. The mode name can be blank (8 space characters).

Specifies whether the TP name in appcCpicOperTpName identifies a normal TP or an SNA service TP. In this context, a normal TP is one with a name consisting only of displayable characters, while an SNA service TP has a name containing octets that do not map to displayable characters. Enumeration: 'snaServiceTp': 2, 'normal': 1.

Specifies the name of the partner TP to be used when a CPI-C application initiates a conversation specifying this side information entry. Display convention 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).

The security userid, if any, associated with the active side information definition.

Specifies the security information to be used for allocating the conversation. none - No security information. same - Use the security environment currently associated with this TP. pgm - Use the program-supplied user_id and password. pgmStrong - Use the program-supplied user_id and password. The local LU will insure that the password is not exposed in clear-text form on the physical network. distributed - Use the security environment and a distributed security system to generate the authentication information for this request. If distributed security tokens cannot be generated, then fail the conversation. mutual - Authenticate both the user to the destination system and the destination system to the user. Enumeration: 'none': 1, 'pgmStrong': 4, 'pgm': 3, 'distributed': 5, 'mutual': 6, 'same': 2.

The compliance statement for the SNMPv2 entities which implement the APPC MIB.

A collection of objects providing the instrumentation of APPC global information and defaults.

A collection of objects providing the instrumentation of APPC local LU6.2s.

A collection of objects providing the instrumentation of APPC partner LUs.

A collection of objects providing the instrumentation of APPC modes.

A collection of objects providing the instrumentation of APPC Transaction Programs.

A collection of objects providing the instrumentation of APPC LU6.2 sessions.

A collection of objects providing the instrumentation of APPC control.

A collection of objects providing the instrumentation of APPC CNOS processing.

A collection of objects providing the instrumentation of APPC CPI-C side information.

A collection of objects providing the instrumentation of APPC conversations.