RE: Display data queue entries?

We use QMHQRDQD

  ----- Original Message -----
  From: "Carel Teijgeler"
  To: midrange-l@xxxxxxxxxxxx
  Subject: RE: Display data queue entries?
  Date: Wed, 25 Oct 2006 19:14:37 +0200


  Ken,

  I think you are right: it will not work with keyed DTAQs. (Use it on
  our
  system, but ttesting it today failed as the queue was empty). But
  then you
  can use the QRCVDTAQ API with keeping the message in the DTAQ.
  SHWDTAQ
  copies the messages to a MSGQ which allows you to remove unwanted
  DTAQ
  messages, before sending it back to the DTAQ; keeping the message in
  the
  DTAQ rules that functionality out.

  As Jim said: with the QMHRDQM API you can retrieve messages from
  keyed and
  unkeyed DTAQS. The only problem with this approach is the length of
  the
  receiver variable and the number of messages in the DTAQ. It is
  difficult
  to retrieve the next n messages from the DTAQ, as positioning to a
  message
  in an unkeyed DTAQ is impossible and to a message in a keyed DTAQ may
  return already retrieved messages.

  Regards,
  Carel Teijgeler

  *********** REPLY SEPARATOR ***********

  On 24-10-2006 at 14:37 Ken Slaugh wrote:

  > USE WITH CAUTION !!!!
  >
  > I looked at this SHWDTAQ CL program. I notice the use of
  > QRCVDTAQ and QSNDDTAQ. Done in this way the contents of the dataq
  are
  > 'temporarily' destroyed. That's not a problem unless other
  applications
  > are sending and receiving entries and arrival sequence matters.
  >
  > I also wonder whether this CL works on a 'keyed' dataq? Does anyone
  know?
  >
  > To deal with these issues, the TAATOOL approach was to use
  > DMPOBJ (dump object) and display the contents.


  --
  This is the Midrange Systems Technical Discussion (MIDRANGE-L)
  mailing list
  To post a message email: MIDRANGE-L@xxxxxxxxxxxx
  To subscribe, unsubscribe, or change list options,
  visit: http://lists.midrange.com/mailman/listinfo/midrange-l
  or email: MIDRANGE-L-request@xxxxxxxxxxxx
  Before posting, please take a moment to review the archives
  at http://archive.midrange.com/midrange-l.