DATA QUEUE STORAGE

[Guest.Visitor]

I want to know how deleted entries are processed by DATAQ. Whether, retrieved entrieds still occupy system space? I know Database files will still hold the system space, until otherwise, you use CLRPFM Command or RGZPFM Command. If DATAQ is using the system space for deleted records the same way Database file does, how to reclaim the storage? What does QCLRDTAQ API Does? Thanks Elan

[Guest.Visitor]

This is an interesting topic. I just checked a data queue (using dspobjd) which we created in 1991. It shows a size as follows: Size . . . . . . . . . . . . . . . : 1126400 This data queue is the main queue in a tiered system which we use to route order entry requests to the appropriate server data queues, which pass those requests to the appropriate program; requests such as "print pick slip", "order checked", "invoice", etc. We have never deleted this data queue. We process upwards of 5,000 orders a day. Is it theoritically possible that we have never loaded this queue beyond the size we see today? Each data queue entry is 256 bytes. Sometimes we shut down the server programs to implement changes. Data queues are quite efficient objects at handling requests. I am very interested in the outcome of this topic. Should we be deleting our data queues on a regular basis?

[Guest.Visitor]

As an addendum to my thoughts: I am quite certain that data queues do not have to be deleted to regain the storage they consume (i.e. after a data queue entry is read), but I am not certain how to reduce their object size.

[Guest.Visitor]

With the announcement of V4R5 data queues (and user queues) can now be up to 2GB in size and have automatic reclaim of storage when the queue is empty. For data queues, the parameters are SIZE(*MAX2GB) and AUTORCL(*YES) on CRTDTAQ. It appears that the Information Center has the V4R5 API chapters online, so you can look at QUSCRTUQ and its new optional group 3 for similiar support.

[Guest.Visitor]

Brandon As you see, the auxilary space is re-used, and if you have approximately the same number of entries are used every day, you don't have to delete and recreate your DATAQ. Only if your dataq is updated with more than 5000 entries, or the any count as you think is abnormally high, then you may want to delete and recreate your queue. I would consider deleting and recreating my dataq, only if i enconter a situation, where the count is abnormally high at any point of time. Thanks everybody!!

[Guest.Visitor]

The size expansion actually provides two features. One is simply larger sizes (which some users had been requesting) and the second is the ability to limit the maximum number (or an approximation anyway) of entries allowed on the queue. This ability to cap the size has also been requested by users. So long as 16MB was known to be too small for some users it didn't make sense to just bump the max to 32, 48 or something similiar. For about the same amount of effort we could just go to 2GB (and hopefully not have to worry about the size again for a few years).