OpenTP1 Version 7 System Definition
Message queue service definition
Format
set format
[set que_xidnum=concurrent-transaction-count] [set que_io_maxrecsize=maximum-record-length-for-overwriting-delay] |
command format
{{quegrp -g queue-group-ID -f physical-file-name [-n I/O-buffer-count] [-m retained-message-count] [-w used-memory-warning-ratio] [-c warning-cancel-percentage]}} |
Function
The message queue service definition defines the execution environment to manage queuing of the I/O messages. Only information related to the physical files are defined here. The message queue service dynamically adds information related to the queue files according to requests from MCF.
A queue file is a logical file allocated by the message queue service to the physical file. A logical file can be an input queue or output queue, and several of each type can be created. However, input queues and output queues cannot be allocated to the same physical file. Input queues or output queues allocated to the same physical file use the same defined environment (I/O buffer count, retained message count, etc.)
Explanation
set format
que_xidnum=concurrent-transaction-count~<unsigned integer> ((1-4096)) <<256>>
Specify the maximum number of transactions to be executed concurrently. Be sure to specify sufficient transactions to enable all read, write, and other requests executed concurrently for the queue files generated by MCF processing.
que_io_maxrecsize=maximum-record-length-for-overwriting-delay~<unsigned integer> ((0-32000)) <<0>> (Unit: bytes)
Specify the maximum record length of an I/O message when overwritten in a physical file with delay. If 0 is specified, no delay-overwriting takes place.
To execute a delay writing request, it is necessary to specify a value greater than the total length of the message per transaction. The formula for calculating the total message length is:
command format
Described on the following page.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.