The MIB module for retrieving Cisco Transaction Connection configuration and status. Cisco Transaction Connection routes transactions between IBM CICS (Customer Information Control System) hosts and clients using the ISC (Inter-System Communication) protocol.
The state of the Transaction Connection license.
unconfigured : A license key has not been provided.
notValidatedYet : A license key has been provided, but it cannot be validated until a server is created. When the first server is created, the license key is validated, changing the license state to one of the following.
badKey : The content of ctcLicenseKey is not a
valid license key.
licenseOK : The license has been validated.
expired : The expiration date of the license
has passed.
ctcLicenseKey
1.3.6.1.4.1.9.9.144.1.1.2
OCTET STRING SIZE (16)
A Transaction Connection license key. The field must be exactly 32 hexadecimal characters in length.
ctcLicenseMaxConn
1.3.6.1.4.1.9.9.144.1.1.3
Unsigned32
The maximum number of connections allowed by the license. This field contains zero if the license is for an unlimited number of connections or if the ctcLicenseState is not licenseOK.
ctcLicenseCurrConn
1.3.6.1.4.1.9.9.144.1.1.4
Unsigned32
Current number of connections in use. Normally, the value of this field should be less then or equal to the value in ctcLicenseMaxConn if it is not zero. However, when a license key is changed to decrease the maximum number ofconnections,
the value of this field may temporarily exceed the limit.
When this occurs, existing connections will not be deleted automatically to meet the new, smaller limit. New connections will be denied until the existing connections voluntarily disconnect.
ctcLicenseExpiration
1.3.6.1.4.1.9.9.144.1.1.5
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The expiration date of the Transaction Connection license. This object contains a valid expiration date only if the license is not permanent.
Table details
ctcDestinationTable
1.3.6.1.4.1.9.9.144.1.2
Index: ctcDestinationName
A table containing Cisco Transaction Connection destination configurations.
ctcDestinationName
1.3.6.1.4.1.9.9.144.1.2.1.1
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..16) · OCTET STRING · hint 255t
The destination name.
ctcDestinationRemoteLUName
1.3.6.1.4.1.9.9.144.1.2.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..17) · OCTET STRING · hint 255t
The Remote LU (Logical Unit) name of the destination target.
ctcDestinationModeName
1.3.6.1.4.1.9.9.144.1.2.1.3
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..10) · OCTET STRING · hint 255t
The mode name of the destination target. In SNA, a mode name is the name used by the initiator of a session to designate the characteristics desired for that session, such as traffic pacing values, message length limits, and the class of service within the transport network.
ctcDestinationNumHits
1.3.6.1.4.1.9.9.144.1.2.1.4
Unsigned32
The number of hits the destination target has received. A hit is registered each time a route is looked up. This means that every time a connection is established, one destination target of the route has its hit count incremented.
ctcRouteTable
1.3.6.1.4.1.9.9.144.1.3
Index: ifIndex
A table containing Cisco Transaction Connection route configurations.
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
ctcRouteOwningServer
1.3.6.1.4.1.9.9.144.1.3.1.1
Unsigned32
The ctcServerIndex of the server that owns this route.
ctcRouteTransactionID
1.3.6.1.4.1.9.9.144.1.3.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..16) · OCTET STRING · hint 255t
The transaction ID that this route handles.
ctcRouteDestinationName
1.3.6.1.4.1.9.9.144.1.3.1.3
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..16) · OCTET STRING · hint 255t
The name of this route's destination.
ctcServerTable
1.3.6.1.4.1.9.9.144.1.4
Index: ctcServerIndex
A table containing Transaction Connection servers.
ctcServerIndex
1.3.6.1.4.1.9.9.144.1.4.1.1
Unsigned32
The index of this server in the server list.
ctcServerName
1.3.6.1.4.1.9.9.144.1.4.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..16) · OCTET STRING · hint 255t
The name of the server.
ctcServerListening
1.3.6.1.4.1.9.9.144.1.4.1.3
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object reflects whether or not the server is listening for connections. A return value of 'true' means the server is actively listening.
ctcServerIPAddr
1.3.6.1.4.1.9.9.144.1.4.1.4
IpAddress SIZE (4)
This object reflects the IP address for which the server is listening for connections. If it is set to 0.0.0.0, then the server is listening on all IP addresses.
ctcServerPort
1.3.6.1.4.1.9.9.144.1.4.1.5
Unsigned32 (1..65535)
The port on which the server is listening for connections.
ctcServerDestinationName
1.3.6.1.4.1.9.9.144.1.4.1.6
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..16) · OCTET STRING · hint 255t
This object reflects the name of this server's default destination.
ctcServerClientTimeout
1.3.6.1.4.1.9.9.144.1.4.1.7
Unsigned32 (0..1440) · minutes
This object reflects the period of time that a client end connection can remain idle before being dropped by a server. The maximum time is 24 hours. If set to 0, the server will never drop the connection due to a timeout event.
ctcServerHostTimeout
1.3.6.1.4.1.9.9.144.1.4.1.8
Unsigned32 (0..1440) · minutes
This object reflects the period of time that a host end connection can remain idle before being dropped by a server. The maximum time is 24 hours. If set to 0, the server will never drop the connection due to a timeout event.
ctcServerWindowSize
1.3.6.1.4.1.9.9.144.1.4.1.9
Unsigned32 · bytes
TCP window size for each connection of the Transaction Connection server.
ctcServerConnectionCount
1.3.6.1.4.1.9.9.144.1.4.1.10
Unsigned32
The number of connections on this server at this moment.
ctcServerProgNameUpperCase
1.3.6.1.4.1.9.9.144.1.4.1.11
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object reflects whether or not the server will convert CICS program names to upper case. A return value of 'true' means the server will convert such names to upper case.
ctcConnectionTable
1.3.6.1.4.1.9.9.144.1.5
Index: ifIndex
A table containing connection information. Each row reflects a client connection that is active at this moment.
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
ctcConnectionId
1.3.6.1.4.1.9.9.144.1.5.1.1
OCTET STRING SIZE (4)
The ID of the connection object.
ctcConnectionServer
1.3.6.1.4.1.9.9.144.1.5.1.2
Unsigned32
The ctcServerIndex of the server that owns this connection.
The state of a connection object.
reset : the connection is ready to process data
closing : the connection is in the process of closing
halt : the connection has halted due to an error
condition
receiving : the connection is receive normal data
ctcConnectionSessionCount
1.3.6.1.4.1.9.9.144.1.5.1.4
Unsigned32
The number of sessions currently in use for the connection.
ctcConnectionClientIPAddr
1.3.6.1.4.1.9.9.144.1.5.1.5
IpAddress SIZE (4)
IP address of client machine using this connection.
ctcConnectionClientPort
1.3.6.1.4.1.9.9.144.1.5.1.6
Unsigned32 (1..65535)
Port number used on client machine for this connection.
ctcConnectionTotalConversations
1.3.6.1.4.1.9.9.144.1.5.1.7
Unsigned32
The number of conversations that have been processed by the connection.
ctcConnectionConnectTime
1.3.6.1.4.1.9.9.144.1.5.1.8
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The moment when the connection was established.
ctcConnectionIdleTime
1.3.6.1.4.1.9.9.144.1.5.1.9
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
Amount of time the connection has gone without activity.
ctcConnectionTotalBytesRecvd
1.3.6.1.4.1.9.9.144.1.5.1.10
Unsigned32
The total number of bytes received from client.
ctcTransactionTable
1.3.6.1.4.1.9.9.144.1.6
Index: ifIndex
A table containing transaction information. Each row reflects a host transaction that is active at this moment.
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
ctcTransactionSessionId
1.3.6.1.4.1.9.9.144.1.6.1.1
OCTET STRING SIZE (4)
The ID of the transaction session object.
ctcTransactionServer
1.3.6.1.4.1.9.9.144.1.6.1.2
Unsigned32
The ctcServerIndex of the server that owns this transaction.
ctcTransactionConnectionId
1.3.6.1.4.1.9.9.144.1.6.1.3
OCTET STRING SIZE (4)
The ID of the transaction session object's connection.
The state of a connection object.
reset : the transaction is ready to process data
opening : the transaction is opening a connection
sending : the transaction is sending data
receiving : the transaction is receiving data
exception : the transaction has encountered an error
exceptionresponse : the transaction is awaiting an error response
closing : the transaction is in the process of
closing
ctcTransactionTPName
1.3.6.1.4.1.9.9.144.1.6.1.5
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t
The transaction program name of the transaction. This is sometimes referred to as the TRANID in CICS.
ctcTransactionUserId
1.3.6.1.4.1.9.9.144.1.6.1.6
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..16) · OCTET STRING · hint 255t
The user ID that was used to initiate the transaction.