Page History
...
Refer also to the companion DTAQ_RECEIVE, DTAQ_CLEAR and WATCH_DTAQ activities that allows you to receive data from and to perform other operations on a named data queue.
...
Although data queues are a native feature of the IBM i server, this activity and the companion DTAQ_CLEAR, DTAQ_RECEIVE and WATCH_DTAQ activities are available on Windows servers too, but with a reduced feature set and with other restrictions and caveats.
...
- The TODTAQLIB parameter is not used and its value will be ignored. (You may use the TODTAQPATH parameter to specify a location for the data queue, if required.)
- Data queues are automatically created when they are first referenced.
- The first reference not only creates the data queue, but also permanently sets the entry size for the data queue according to the value of the DTALEN parameter.
- 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 TODTAQPATH parameter. Refer to that parameter description for further information.
- If you have the Visual LANSA documentation available to you, you can find further information pertinent to the Windows implementation of this and related activities in the description of the SND_TO_DATA_QUEUE built-in function, in the LANSA Technical Reference Guide.
...