|
Good Afternoon; I am using a data queue for my trigger program. When a record is modified, a record gets sent to a data queue. I have a program monitoring that data queue with a wait of -1. When a record hits the queue, stuff happens. Well, my data queue entry is not being cleared on my receive. Here is a snip from the RPG monitor program, then a print from the data queue. I did read where there is a parm (#11 or #12?) in the receive where you can say whether to delete the queue record or not after a receive, but it said the default is Yes. My dataqueue is not keyed. Here are the snips. Can anyone help? Also, please note that the queue is not incrementing sequentially. It is skipping numbers. Thank-you; Kathie Columns . . . : 6 100 Browse COMMON/QRPGLESRC EDIFTSRDQ Dou Data = '9999999999' Eval DataQName = 'IFTSTAQ ' Eval DataQLib = 'DTALIB ' Eval Data = *Blanks Eval DataLength = 0 Eval WaitTime = -1 Wait Forever Call 'QRCVDTAQ' PRCVDQ - - - - ------------ 49 data records excluded ---------------- PRcvDq Plist Parm DataQName Parm DataQLib Parm DataLength Parm Data Parm -1 WaitTime Data Queue Display 11/10/04 13:55:08 Queue: IFTSTAQ Library: DTALIB Number of Entries: 236 Processing Sequence: *FIFO Maximum Entry Length: 10 1=Display more entry data =Arrived on Queue= Opt Entry Entry Data Date Time 00001 0000003383 11/09/04 17:01:40 00003 0000003385 11/09/04 17:01:54 00005 0000003387 11/09/04 17:02:27 00007 0000003389 11/09/04 17:02:42 00009 0000003391 11/09/04 17:04:01 00011 0000003393 11/09/04 17:04:11 00013 0000003395 11/09/04 17:05:13 00015 0000003397 11/09/04 17:05:16 00017 0000003399 11/09/04 17:05:40 00019 0000003401 11/09/04 17:06:25 00021 0000003403 11/09/04 17:07:28 00023 0000003405 11/09/04 17:07:46 00025 0000003407 11/09/04 17:20:32 00027 0000003409 11/09/04 17:20:33 00029 0000003411 11/09/04 17:20:47 F3=Exit F5=Refresh
As an Amazon Associate we earn from qualifying purchases.
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.