V6R1 storage limit exceeded for data queue

5 pts.
Tags:
AS/400
AS/400 Data Queue
Data Queue
iSeries Storage
iSeries V6R1
V6R1
Just upgraded to V6R1. Getting the following message in one of my applications: Storage limit exceeded for data queue. Why and how do I correct?

Answer Wiki

Thanks. We'll let you know when a new response is added.

Maybe a new system value has affected your dataqueues behavior.
Thinking to delete the dataqueue and create it again maybe help you, specifying MAXLEN parameter for a maximun message length and SIZE parameter for maximun enqueued messages.

Regards.

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    You'll get that message when an attempt is made to add an entry to the data queue when the maximum number of entries are already on the queue. Is this one of your data queues? Or is this a data queue in a software product? Tom
    125,585 pointsBadges:
    report
  • jinteik
    if it is apps, then you can ask them to modify the dataq lenght and also how long they want to keep it
    17,370 pointsBadges:
    report
  • TomLiotta
    If it is apps, then whatever is supposed to be reading entries off of the queue is not reading them fast enough. Either the rate of adding entries to the queue needs to be slowed or the rate of reading them needs to be quickened. The standard means of speeding up reading from the queue is to start one or more additional readers. Entries on a data queue are generally expected to be read immediately. A data queue is not intended for long term storage; it is intended as a low-overhead way of passing data elements from one process to another. You should think in terms of never having more than a few entries on a data queue at one time. By reading the entries quickly, there should never be a time when the queue is filled. Also, keep in mind that entries on a data queue are not saved when the data queue object is saved. That means that the entries are lost if the data queue must be restored. That's a strong reason not to think of data queues as permanent storage containers. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following