Re: Data Queue question

hi Richard,

When you create a data queue with (for example) MAXLEN(75) you are specifying the size of a single entry (not the size of the whole queue.) you are saying the maximum length of an entry is 75.

If you write an entry that's 50 bytes, it writes those 50 bytes instead of the entire 75 -- but it's still the whole entry. There's no way to put data in the remaining 25 bytes.

When you write the second entry, it will also occupy 50 bytes (not 25) and will be the 2nd entry.

When you receive an entry, you must specify a field that's 75 bytes long (or longer... but it wouldn't be safe to specify one that's shorter unless you specify the 12th parameter...)

Since the first entry was 50 bytes long, when you read from the queue, bytes 1-50 of your field will be replaced with what was in the queue. The remaining 25 bytes are unchanged (I think). The "Length of data" in parameter 3 of QRCVDTAQ will be set to 50.

When you receive the 2nd entry, you get all 50 bytes from that entry, as well... not just 25.


Marchini, Richard wrote:

I need some help with a data queue question. I know that data queues are
FIFO, and I assume that means they fill from left to right. Can anyone
tell me how the data would be put into the queue if an entry filled the
queue?

i.e. data queue length of 75 bytes (I know these aren't real numbers).
Entries are 50 bytes. When the second entry attempts to be received into
the data queue, will it fill with the first 25 bytes or the last 25? Or
will it put no data into the queue?

I have a situation in which a data queue's data were not in the
positions that they should have been, causing a decimal data error. I
can't think of any other way the data could get put into the queue out
of position.

Any insight will be greatly appreciated.


Rick Marchini
Associated Banc-Corp
IT Services
Mail Stop 7055
920-405-2587



*********************** NOTICE***********************

This e-mail and attachment(s) may contain information that is
privileged, confidential, and/or exempt from disclosure under
applicable law. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination,
distribution, or copy of this message is strictly prohibited. If
received in error, please notify the sender immediately and
delete/destroy the message and any copies thereof. Although
Associated Banc-Corp and/or its affiliates (collectively
"Associated") attempt to prevent the passage of viruses via e-mail
and attachments thereto, Associated does not guarantee that either
are virus-free, and accepts no liability for any damage sustained
as a result of any such viruses.

Any federal tax advice contained in this communication (including
any attachments) is not intended or written to be used or referred
to in the promoting, marketing, or recommending of any entity,
investment plan or agreement, nor is such advice intended or written
to be used, and cannot be used, by a taxpayer for the purpose of
avoiding penalties under the Internal Revenue Tax Code