×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
It really depends on why you are deleting them and how you created them. There are two settings to look at: Size(*max16MB or *max2GB) and AUTORCL(*yes)
Back in the day you a data queue could only grow to 16MB, now you can have it grow to 2GB. But the reason for deleting was, if the queue grew at one time, it remained that size until you deleted and recreated it. (Data queues are memory object so they really can be memory hogs). Well IBM finally introduced the AUTORCL option. This allows the data queue to shrink back to the initial size as messages are removed. No real reason to delete on a regular basis. I would look at the create command and make sure it specifies the AUTORCL(*YES). Then I would stop the deleting nightly.
Now I have transactional data queues that are deleted and recreated when the subsystem starts. This makes sure any hung transactions are purged as if we don't get a response back to the POS terminal within a few seconds, it has hung up and then resends the transaction to an alternate number.
We also have queues for sending transactions between systems that I do not want to lose. Those are not deleted and we set the FORCE(*YES) to make sure they are committed to disk and not damaged in a system failure/shut down.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
