The tuxTAppQctrl group enables controlled access to all Application Queue related MIB groups.
If the value is local(1), only the local host where Oracle SNMP Agent is running is considered; alternatively, all LMIDs known to the application are considered if the value is
all(2).
This object applies only to tuxTAppQmsgTbl. The lowest priority within which to search for occurrences of
tuxTAppQmsgTbl instances. This object value is valid only for PRIO-based queues. By default, the minimum value of priority is considered. To revert to the default setting, set this object to
0.
This object applies only to tuxTAppQmsgTbl. The highest priority within which to search for occurrences of
tuxTAppQmsgTbl instances. This object value is valid only for PRIO-based queues. By default, the maximum value of priority is considered. To revert to the default setting, set this object to
0.
This object applies only to tuxTAppQmsgTbl. The end time within which to search for occurrences of
tuxTAppQmsgTbl instances. The range is inclusive. This object value is valid only for TIME-based queues. The default value is the maximum number possible on that machine. To use the default setting, set this object to “*”.
This object applies only to tuxTAppQmsgTbl. The start time within which to search for occurrences of
tuxTAppQmsgTbl instances. The range is inclusive. This object value is valid only for TIME-based queues. By default, the minimum time value is considered to be
0. To use the default setting, set this object to “*”.
This object applies only to tuxTAppQmsgTbl. The expire end time within which to search for occurrences of
tuxTAppQmsgTbl instances. The range is inclusive. This object value is valid only for TIME-based queues. The default value is the maximum number possible on that machine. To use the default setting, set this object to “*”.
This object applies only to tuxTAppQmsgTbl. The Expire start time within which to search for occurrences of
tuxTAppQmsgTbl instances. The range is inclusive. This object value is valid only for TIME-based queues. By default, the minimum time value is considered to be
0. To use the default setting, set this object to “*”.
The tuxTAppQTbl group contains objects that represent application queues. One or more application queues can exist in a single application queue space. Objects in this table are only accessible through a Tuxedo SNMP agent installed on the local machine.
A GET operation retrieves information about the selected application queues. The following list describes the meaning of the
tuxTAppQstate object returned in response to a
GET request. States not listed are not returned.
A SET operation changes characteristics of the selected application queue or creates a new queue. The following list describes the meaning of the
tuxTAppQstate object returned by a
SET request. States not listed cannot be set.
DisplayString (
SIZE(
0..127)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
For example, if tuxTAppQcmdLw is 50m and
tuxTAppQcmdHw is 100m, then the command specified in
tuxTAppQcmd is executed when 100 messages are on the queue, and it is not executed again until the queue is drained below 50 messages and is filled again to 100 messages.
The format is +seconds, where
seconds is the number of seconds allowed to lapse between the time that the queue manager successfully completes the operation and the time that the message is to expire. If
seconds is set to zero (0), the message expires immediately.
The value of this object may also be set to the string “none.” The
none string indicates that messages enqueued to the queue with no explicit expiration time do not expire. You can change the expiration time for messages already in a queue with the
tuxTAppQmsgExpireTime object of the
tuxTAppQmsgTbl group.
This object specifies the default delivery policy for the queue when no delivery mode is specified for a message enqueued to the queue. When the value is “persist,” messages enqueued to the queue without an explicitly specified delivery mode are delivered using the persistent (disk-based) delivery method. When the value is non-persist, messages enqueued to the queue without an explicitly specified delivery method are delivered using the non-persistent (in memory) delivery method. When a queue’s default delivery policy is modified, the delivery quality of service of messages that are in the queue before the modification are not changed. If the queue being modified is the reply queue named for any messages currently in the queue space, the reply quality of service is not changed for those messages as a result of changing the default delivery policy of the queue.
For non-persistent delivery, if the memory area is exhausted or fragmented so that a message cannot be enqueued, the enqueuing operation fails, even if there is sufficient persistent storage for the message. Similarly, if the persistent storage area is exhausted or fragmented so that a message cannot be enqueued, the enqueuing operation fails, even if there is sufficient non-persistent storage for the message. If the tuxTQspaceMemNonPersist object of the
tuxTQspaceTbl group is zero (0) for a queue space, no space is reserved for non -persistent messages. In such a case, any attempt to enqueue a non-persistent message fails. This type of failure results, for example, when no delivery quality of service has been specified for a message and the
tuxTAppQDefDeliveryPolicy object for the target queue has been set to “non-persist.”
DisplayString (
SIZE(
1..127)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
The messages threshold type specified through the tuxTAppQCmdHw and
tuxTAppQcmdLw objects (when followed by an m) applies to all messages in a queue, including both persistent and non-persistent messages, and therefore is not available as a threshold type for
tuxTAppQCmdNonPersistHw and
tuxTAppQCmdNonPersistLw.
The messages threshold type specified through the tuxTAppQCmdHw and
tuxTAppQcmdLw objects (when followed by an m) applies to all messages in a queue, including both persistent and non-persistent messages, and therefore is not available as a threshold type for
tuxTAppQCmdNonPersistHw and
tuxTAppQCmdNonPersistLw.
The tuxTAppQmsgTbl group contains objects that represent messages stored in application queues. A message is not created by an administrator; instead, it comes into existence as a result of a call to
tpenqueue(3). A message can be destroyed either by a call to
tpdequeue(3) or by an administrator. In addition, certain objects of a message can be modified by an administrator. For example, an administrator can move a message from one queue to another queue within the same queue space or change its priority.
A GET operation retrieves information about the selected messages. The following list describes the meaning of the
tuxTAppQmsgState object returned in response to a
GET request. States not listed are not returned.
A SET operation changes characteristics of the selected message. The following list describes the meaning of the
tuxTAppQmsgState object returned by a
SET request. States not listed cannot be set.
The tuxTQspaceTbl group contains objects that represent application queue spaces. Objects in this table are only accessible through a Tuxedo SNMP agent installed on the local machine.
To create a new row in this table, a SET request should be issued with an index (
tuxTQspaceGrpNo) of 40000, which is a reserved value for row creation in the table. The
SET request also needs to specify values for at least
tuxTQspaceQmConfig,
tuxTQspaceName,
tuxTQspaceLmid,
tuxTQspaceIpckey,
tuxTQspaceMaxMsg,
tuxTQspaceMaxPages,
tuxTQspaceMaxProc,
tuxTQspaceMaxQueues, and
tuxTQspaceMaxTrans. The newly created instance (row) is not visible until it is attached to some server group.
A GET operation retrieves information about the selected application queue space. The following list describes the meaning of the
tuxTQspaceState object returned in response to a
GET request. States not listed are not returned.
A SET operation changes the selected application queue space or creates a new one. The following list describes the meaning of the
tuxTQspaceState object returned by a
SET request. States not listed cannot be set.
The [bB]suffix is optional and, if not specified, the default is blocks. Note that the number of bytes requested can be rounded up to the next internal data size. When read, the value is always the actual amount of memory allocated in bytes (
b).
If the variable for a queue space is zero (0), no queue space is reserved. for non-persistent messages. In this case, any attempt to enqueue a non-persistent message fails. This type of failure results, for example, when no delivery quality of service has been specified for a message and the tuxTAppQDefDeliverPolicy object of the
tuxTAppTbl group for the target queue has been set to
NONPERSIST. For non-persistent delivery, if the memory area is exhausted or fragmented so that a message cannot be enqueued, the enqueuing operation fails, even if there is sufficient persistent storage for the message. Similarly, if the persistent storage area is exhausted or fragmented so that a message cannot be enqueued, the enqueuing operation fails, even if there is sufficient non-persistent storage for the message.
This object specifies the size of the memory area to reserve in shared memory to accommodate peak load situations where some or all of the allocated shared memory resources are exhausted. The memory size is specified in bytes. Additional objects are allocated from this additional memory on a first-come, first-served basis. When an object created in the additional memory is closed or destroyed, the memory is released for subsequent overflow situations. This additional memory space can yield more objects than the configured number, but there is no guarantee that additional memory is available for any particular object at any given point in time. Currently, only actions, handles, cursors, owners, temporary queues, timers, and filters use the overflow.
The tuxTQtransTbl group contains objects that represent run-time characteristics of transactions associated with application queue spaces. Objects in this table are only accessible through a Tuxedo SNMP agent installed on the local machine.
Transaction identifier as returned by tx_info(3) and mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.
An integer index for tuxTQtransTbl. This should not be interpreted by the user. It is used only for uniquely identifying a particular row in this table by the combination of Indx1 through Indx5.
An integer index for tuxTQtransTbl. This should not be interpreted by the user. It is used only for uniquely identifying a particular row in this table by the combination of Indx1 through Indx5.
An integer index for tuxTQtransTbl. This should not be interpreted by the user. It is used only for uniquely identifying a particular row in this table by the combination of Indx1 through Indx5.
An integer index for tuxTQtransTbl. This should not be interpreted by the user. It is used only for uniquely identifying a particular row in this table by the combination of Indx1 through Indx5.
An integer index for tuxTQtransTbl. This should not be interpreted by the user. It is used only for uniquely identifying a particular row in this table by the combination of Indx1 through Indx5.
A GET operation retrieves run-time information about the selected transactions. The following list describes the meaning of the
tuxTQtransState object returned in response to a
GET request. States not listed are not returned.
A SET operation updates the state of the selected transactions. The following list describes the meaning of the
tuxTQtransState object returned by a
SET request. States not listed cannot be set.