![]() |
![]() |
![]() |
![]() |
![]() |
For information about using the Create New Object window, see Creating Administrative Class Objects.The Configuration Tool contains some fields that are read-only. The information provided by these display-only fields is described briefly. For general information about using the Configuration Tool to configure administrative resources, see Configuring Administrative Objects.The name of the application queue space associated with the application queue. Filling in this field is half of what you must do to identify such a queue space; you must also enter a value in the App Queue Space Device (TA_QMCONFIG).The pathname for an application queue configuration device, which must be on the current machine when you are using a deactivated configuration. Filling in this field is half of what you must do to identify a queue space associated with the application queue; you must also enter a value in the App Queue Space Name (TA_APPQSPACENAME).The value in this field must be specified as a key field except when the application is unconfigured (i.e., the TUXCONFIG environment variable is not set).
•
•
• All operations (whether GET or SET) on application queues silently open the associated queue space (i.e., they implicitly set the state of the queue space to OPEN if it is not already OPEN or ACTIVE). This may be a time-consuming operation if the queue space is large.Select one of the combinations listed below. The commas indicate a secondary (or lower) processing order within the primary processing order. For example, PRIO, LIFO means that the queue is processed in priority order, but if two items in the queue share the same priority, they are then processed in last in first out order.FIFO — first in first outPRIO, LIFO — Priority (then last in first out)PRIO, FIFO — Priority (then first in first out)TIME, LIFO — Execution Time (then last in first out)PRIO, TIME, LIFO — Priority (then Execution Time (then last in first out)PRIO, TIME, LIFO — Priority (then Execution Time (then first in last out)TIME, PRIO, LIFO — Execution Time (then Priority (then last in first out)
•
•
• The maximum number of retries for a failed queue message. When this number of retries is exhausted, the message is placed on the error queue of the queue’s application queue space, as defined by Error Queue Name (TA_ERRORQNAME). If there is not error queue, the message is dropped.B or b — the high-water marks are expressed in disk blocks.M or m — the high-water marks are expressed in messages.% — the high-water marks are expressed as a percentage of queue capacity.B or b — the low-water marks are expressed in disk blocks.M or m — the low-water marks are expressed in messages.% — the low-watermarks are expressed as a percentage of queue capacity.For information about using the Create New Object window, see Creating Administrative Class Objects.For general information about using the Configuration Tool to configure administrative resources, see Configuring Administrative Objects.You must specify that this field is a key field except when the application is unconfigured (that is, when the TUXCONFIG environment variable is not set).
•
•
• All operations on application queue classes silently open the associated queue space (i.e., implicitly set the state of the queue space to OPEN if it is not already OPEN or ACTIVE). This may be a time-consuming operation if the queue space is large.Select Yes to force the application queue space to initialize immediately, or No to delay the initialization.Yes or NoFor general information about using the Configuration Tool to configure administrative resources, see Configuring Administrative Objects.
Note: All operations on application queue messages (both GET and SET) silently open the associated queue space (i.e., implicitly set the state of the queue space to OPEN if it is not already OPEN or ACTIVE). This may be a time-consuming operation if the queue space is large.Note: <a name="12276"></a>The priority of the message. The value in this field is valid only for PRIO-based queues. A value of -1 is returned by a GET operation if the queue is not PRIO-based.This field displays the correlation identifier for this message provided by the application in the tpenqueue(3) request. The empty string indicates that a correlation identifier is not present.The time when the message will be processed. This field is valid only for TIME-based queues. (If the queue is not TIME-based, an empty string is returned by a GET operation.)+secondsSpecifies that the message will be processed seconds in the future. The value 0 (zero) specifies that the message should be processed immediately.This is equivalent to 950601000000. The years 00 through 37 are treated as 2000 through 20037, 70 through 99 are treated as 1970 through 1999, and 38 through 69 are invalid.This field displays the state of the application queue transaction. An application queue transaction may be in any of the following states: ACTIVE, ABORTONLY, ABORTED, COMCALLED, READY, DECIDED, or SUSPENDED.All operations on application queue transactions (both GET and SET) silently open the associated queue space (i.e., implicitly set the state of the queue space to OPEN if it is not already OPEN or ACTIVE). This may be a time-consuming operation if the queue space is large.This field displays 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.