Using the rmname value, the entry in $TUXDIR/udataobj/RM is used to include the associated libraries for the resource manager automatically and to set up the interface between the transaction manager and resource manager properly. Other values can be specified as they are added to the resource manager table. If the -r option is not specified, the default is that the client is not associated with a resource manager.
buildqserver—Used to construct an OTMQ load module which can run as a Tuxedo application server.
Specifies the names of services that can be advertised when the server is booted. Service names (and implicit function names) must be less than or equal to 127 characters in length. An explicit function name (that is, a name specified after a colon) can be up to 128 characters in length. Names longer than these limits are truncated with a warning message. When retrieved by tmadmin or TM_MIB, only the first 15 characters of a name are displayed. All functions that can be associated with a service must be specified with this option. In the most common case, a service is performed by a function that carries the same name; that is, the x service is performed by function x. For example, the following specification builds the associated server with services x, y, and z, each to be processed by a function of the same name: "-s x,y,z".
In other cases, a service (or several services) may be performed by a function of a different name. The following specification builds the associated server with services x, y, and z, each to be processed by the function abc: "-s x,y,z:abc". Spaces are not allowed between commas. Function name is preceded by a colon. In another case, the service name may not be known until run time. Any function that can have a service associated with it must be specified to buildqserver. To specify a function that can have a service name mapped to it, put a colon in front of the function name. For example, the following specification builds the server with a function pqr, which can have a service association. tpadvertise could be used to map a service name to the pqr function. "-s :pqr". A filename can be specified with the -s option by prefacing the filename with the '@' character. Each line of this file is treated as an argument to the -s option. You may put comments in this file. All comments must start with the '#' character. This file can be used to specify all the functions in the server that may have services mapped to them. The -s option may appear several times. Note that services beginning with the '.' character are reserved for system use, and buildqserver will fail if the -s option is used to include such a service in the server.
dmqclconv — Creates an UBB/DUBB/CRQUE/ENV/NameEnv to the current path.
|
Note:
|
dmqclconv can only output one UBB/DUBB/ENV/CRQUE/NameEnv file. If there are several groups deployed on one Oracle Tuxedo domain, the CRQUE file creates all groups.
|
tmqadmin—Queue manager administration program.
When tmqadmin is initially entered, no queue space is opened. To create a queue space, run qspacecreate; to open it, run qopen. The qaborttrans, qclear, qclose, qchangeprio, qchangequeue, qchangetime, qchangeexptime, qcommittrans, qchange, qcreate, qdeletemsg, qinfo, qlist, qprinttrans and qset commands can be executed only when a queue space is open.
If queue_space_name is a cluster queue space, set
qopen queue_space_name.cluster_group_name to specify specific group name, openning the specified queue space group in this cluster. If you just specify
qopen queue_space_name,
qopen will open the primary group of this cluster.
The ipckey that you set is just for the primary group shared memory segment and semaphore.
ipckey for physical groups is automatically calculated. All
ipckey form a tolerance of 1 arithmetic progression, of which the initial term is the
ipckey that you specified for the primary group. For example, if you set group1's
ipckey value is
a, group2's
ipckey value will become
a+1 and group3's
ipckey value will becom
a+2.
Destroys the named queue space. If not provided on the command line, the program will prompt for it. If the specified queue space is open in tmqadmin, it will be closed. By default, an error is returned if processes are attached to the queue space or if requests exist on any queues in the queue space. See the
qdestroy command for destroying queues that contain requests. The
-f option can be specified to "force" deletion of all queues, even if they may have messages or processes are attached to the queue space. This command prompts for confirmation before proceeding unless the
-y option is specified. All non-persistent messages in the specified queue space are lost when this command completes successfully. If you use
qspacedestroy to destroy one cluster, all queue spaces of this cluster will be destroyed.
Destroys the queue space groups that group_name specifies. If not provided on the command line, the program will prompt for it. If the specified queue space is open in
tmqadmin, it will be closed. By default, an error is returned if processes are attached to the queue space or if requests exist on any queues in the queue space. See the
qdestroy command for destroying queues that contain requests. The
-f option can be specified to "force" deletion of all queues, even if they may have messages or processes are attached to the queue space. This command prompts for confirmation before proceeding unless
-y option is specified. All non-persistent messages in the specified queue space group are lost when this command completes successfully.
The out-of-order values are none,
top, and
msgid. Both top and msgid may be specified, separated by a comma. The threshold values are used to allow for automatic execution of a command when a threshold is reached for persistent messages.
If the -d option is not specified, the system does not prompt for information and the default delivery policy is unchanged. When the default delivery policy is modified, the delivery quality of service is not changed for messages already in the queue. 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. If a non-persistent message cannot be enqueued due to an exhausted or fragmented memory area, the enqueuing operation fails, even if there is sufficient persistent storage for the message.
The -n option specifies the threshold values used for automatic execution of a command when a non-persistent storage area threshold is reached. The
nhigh limit specifies when the command
ncmd is executed. The
nlow limit must be reached before the command will be executed again when the nhigh limit is reached. If the -n option is specified, the
nhigh,
nlow, and
ncmd values must all be supplied, or the command fails. The ncmd value may be specified as an empty string. If the
-n option is not specified, the program does not prompt for information.
The memory capacity (amount of non-persistent data in the queue) can be specified as one of the following threshold types: bytes (b), blocks (B), or percentage (number followed by %). The threshold type for the nhigh and
nlow values must be the same. For example, if
nhigh is set to 100%, then
nlow, if specified, must also be specified as a percentage. The threshold type of the
nlow value is optional. If the -n option is not specified, the default threshold values for non-persistent messaging are unchanged. If ncmd contains white space, it must be enclosed in double quotation marks. The m suffix of the
[ . . . [high[low[cmd]]] . . . ] thresholds applies to all messages in a queue, including both persistent and non-persistent messages, and therefore is not available with nhigh and nlow. The
[ . . . [high[low[cmd]]] . . . ] thresholds specified without the
-m suffix apply to persistent (disk-based) messages only.
The -e default_relative_expiration_time option sets an expiration time for all messages enqueued to the queue that do not have an explicitly specified expiration time. The expiration time may be either a relative expiration time or none. When the expiration time is reached and the message has not been dequeued or administratively deleted, the message is removed from the queue, all resources associated with the message are reclaimed by the system, and statistics are updated.
If the -e option is not specified, the default expiration time of the queue is not changed. When the queue expiration time is modified using qchange, the expiration times for messages already in the queues are not modified. If the
-e option is not specified, the program does not prompt for it. The format of a relative
default_relative_expiration_time is +seconds where seconds is the number of seconds from the time that the queue manager successfully completes the operation to the time that the message expires. A value of zero (0) indicates immediate expiration.
The value of default_relative_expiration_time may also be set to the string none. The none string indicates that messages that are enqueued with no explicit expiration time will not expire unless an expiration time is explicitly assigned to them.
The -o "owner" option is used for secondary queues. And defines the primary queue with which this queue is to be associated. The valid value for it is primary queue name.
The valid values for the -a "active" option are "
Y" or "
N". The default value is "N". This is to define if the queue is permanent active. If yes, then the queue always can receive and store message unless the quota is exceeded. If not, the queue cannot receive and store message before it is attached, and will report invalid queue in the sender side. This feature doesn't make impact for
MRQ and unlimited queue (inherited from
/Q).
If the -q option is specified, the nhigh, nlow, and ncmd values must all be supplied, or the command fails. The
ncmd value may be specified as an empty string.
qcreate supports the following options:
The valid values for the -t "type" option are
PQ (primary queue),
SQ (secondary queue) and
MRQ (
MRQ). The default value is "
unlimited queue".
The default value is "N". This is to define if the queue is permanent active. If yes, then the queue always can receive and store message unless the quota is exceeded. If not, the queue cannot receive and store message before it is attached, and will report invalid queue in the sender side. This feature doesn't make impact for
MRQ and unlimited queue (inherited from /Q).
When command line options give a value range (for example, -t, -e, or -p) the value range may not contain white space. The -t option can be used to indicate a time value or a time range. The format of time1 and time2 is: YY[MM[DD[HH[MM[SS]]]]] specifying the year, month, day, hour, minute, and second. Units omitted from the date-time value default to their minimum possible values. For example, "7502" is equivalent to "750201000000." The years 00-37 are treated as 2000-2037, years 70-99 are treated as 1970-1999, and 38-69 are invalid. The -p option can be used to indicate a priority value or a priority range. Priority values are in the range 1 to 100, inclusive.
