gtpo1mabOperations

ZMQSC DEF QL-Define a TPF MQSeries Local Queue

Use this command to define a TPF MQSeries local queue. A local queue must be defined so that an application can get messages from the queue or put messages on the queue.

Requirements and Restrictions

Format




QL-qlname
specifies the local name of the queue, where qlname is a 1- to 48-character queue name. A queue name can contain percent signs (%), slashes (/), underscores (_), periods (.), letters in either uppercase (A-Z) or lowercase (a-z), and digits (0-9). If the name is enclosed in single quotation marks, the characters can be mixed case. The name must be unique in the entire TPF system complex.

Do not specify a local queue name of ALL.

MAXMSGL-maxmsgl
defines the maximum message length on this local queue, where maxmsgl is a number from 0 to the maximum message length specified in the TPF MQSeries profile. If you do not specify this parameter, the maximum message length defined with the ZMQSC DEF MQP command is used.

You can use this to determine the size of the buffer that an application needs to retrieve messages from the queue.

PUT
specifies one of the following:

ENABLED
specifies that messages can be added to the queue.

DISABLED
specifies that messages cannot be added to the queue.

GET
specifies one of the following:

ENABLED
specifies that messages can be retrieved from the queue.

DISABLED
specifies that applications cannot retrieve messages from the queue.

DEFPSIST
specifies one of the following:

NO
specifies that messages on the queue are lost when the queue manager is restarted.

YES
specifies that messages on the queue are retained when the queue manager is restarted.

USAGE
defines the type of queue, where:

NORMAL
indicates that the queue is not a transmission queue.

XMITQ
indicates that the queue is a transmission queue.

COMMON
specifies whether the physical queue is shared, where:

NO
specifies that each central processing unit (CPU) has its own physical queue. A queue defined with this value is a processor unique queue.

YES
specifies that all CPUs share the same physical queue. A queue defined with this value is a processor shared queue.

QDEPTHHI-qdepthhi
specifies the default percentage of messages that are allowed for the local queue before a warning message is sent to the console, where qdepthhi is a number from 0 to 100.

If you do not specify this parameter, the value that was specified with the QDEPTHHI parameter of the ZMQSC DEF MQP command is used. If you specify 0, no warning messages are sent to the console.

This parameter is not valid for queues that are processor shared; that is, queues defined with the COMMON parameter set to YES.

SWEEP
specifies one of the following:

ON
specifies that this memory queue is moved (swept) to a TPF collection support (TPFCS) persistent collection when the number of messages on the queue are increasing.

OFF
specifies that this memory queue is not swept.

Attention: Setting the SWEEP parameter to OFF can deplete system work blocks (SWBs).

MAXDEPTH-maxdepth
changes the maximum number of messages allowed on this memory queue, where maxdepth is a number from 0 to 999 999 999. If you specify zero, there is no maximum for this queue.

Other factors can cause the queue to be handled as full; for example, if there is no more DASD or memory space available.

If you do not specify this parameter, the value that was specified for the MAXDEPTH parameter of the ZMQSC DEF MQP command is used.

This parameter is not valid for queues that are processor shared; that is, queues defined with the COMMON parameter set to YES.

TRIGTYPE
specifies one of the following:

FIRST
specifies that the program in the process object is triggered to run the first time a message arrives on the queue. If no process is associated with the queue, the TPF queue trigger user exit (CUIR) is called.

EVERY
specifies that the program in the process object is triggered to run every time a message arrives on the queue. If no process is associated with the queue, no triggering occurs.

NONE
specifies that the program in the process object is not triggered to run.

NOTRIGGER
specifies that triggering is not active.

TRIGGER
specifies that triggering is active and will occur as specified by the TRIGTYPE parameter.

TRIGDATA-trigdata
specifies a character string that contains trigger information pertaining to the application to be started, where trigdata is a 1- to 64-character string. This is free-format data that the queue manager inserts into the trigger message when a message arriving on this queue causes a trigger message to be written.

PROCESS-processname
specifies the name of a process object that is defined on the local queue manager, where processname is the 1- to 48-character process name. A process name can contain percent signs (%), slashes (/), underscores (_), periods (.), letters in either uppercase (A-Z) or lowercase (a-z), and digits (0-9). If processname is enclosed in single quotation marks, the characters can be mixed case.

Additional Information

Examples

The following example defines a new local queue.

+--------------------------------------------------------------------------------+
|User:   ZMQSC DEF QL-'target.queue' GET-DISABLED USAGE-NORMAL                   |
|                                                                                |
|System: MQSC0069I 08.41.05 LOCAL QUEUE target.queue DEFINED                     |
+--------------------------------------------------------------------------------+

Related Information

See MQSeries Command Reference for more information about the MQSeries product.