Page History
...
Refer also to the companion DTAQ_CLEAR, DTAQ_SEND and WATCH_DTAQ activities that allows you to send and receive data to and from and to perform other operations on a named data queue.
...
Refer to the description of the DTAQ_SEND activity for more complete IBM i Server Platform Notes relating to the suite of DTAQ activities. Refer to IBM i documentation concerning data queues for further information about the operating system features upon which this activity depends.
...
Although data queues are a native feature of the IBM i server, this activity and the companion DTAQ_CLEAR, DTAQ_SEND and WATCH_DTAQ activities are available on Windows servers too, but with a reduced feature set and with other restrictions and caveats.
...
- The DTAQLIB parameter is not used and its value will be ignored. (You may use the DTAQPATH parameter to specify a location for the data queue, if required.)
- Data queues are stored in pairs of files in the Windows server file system with .EDQ and .LDQ file extensions. The .EDQ file contains the data queue definition and entries. The .LDQ files are used to logically lock the data queue during receive operations. The file names are determined by the LANSA run-time support used by this activity. The files can be manually cleared or deleted by deleting the associated files. Alternatively the DTAQ_CLEAR activity may be used for this purpose.
- The location of the .EDQ and .LDQ data queue storage files is determined by the value of the DTAQPATH parameter. Refer to that parameter description for further information.
- Refer to the description of the DTAQ_SEND activity for more complete Windows Server Platform Notes relating to the suite of DTAQ activities.
...
You may also specify the special value *MAX which means that the activity waits indefinitely for data to arrive. You should understand that this value may cause the activity and hence the processing sequence in which it is contained to stall indefinitely if no data is sent to the data queue. Other than by the arrival of data, such a processing sequence run may only be terminated by terminating the job, the subsystem in which the job is running or the system. If you wish a process to wait indefinitely for data to arrive on a data queue, the WATCH_DTAQ activity may provide a more suitable solution.
...
On a Windows server, the first send (DTAQ_SEND) operation for a data queue will automatically create the data queue and will set its entry length. The length specified for subsequent operations to the same data queue must match the length specified on the initial operation that created the data queue. (On Windows servers, LANSA Composer will actually use the next greatest multiple of 256 – for example, if you specify 700 for this parameter, LANSA Composer will actually use the value 768.)
...