|
RD, It sounds to me as though the home-grown utility isn't in a constant wait state on the data queue, but is firing up and doing one QRCVDTAQ, either finding an entry or not, then ending? If this is the case, you can change your WAIT parameter to a negative value, and start the program in a subsystem where it won't get in the way. The job will sit in a wait state until a data queue entry is received, then continue to the next line of code. This is a much more efficient way of doing it, and if you are still missing an occasional entry, then you need to look at your utility code to see why. HTH, Kathleen Kostuck ___________________ pager (414) 402-0820 fax (414) 495-4986 kkostuck@execpc.com AS400 Solutions Secretary - Wisconsin Midrange Computer Professionals Association ___________________ ---------- > From: RDJessen@aol.com > To: MIDRANGE-L@midrange.com > Subject: Data Queue's > Date: Tuesday, September 22, 1998 8:42 PM > > I need some information on when data gets written to a data queue when a spool > file is created. I am supporting a utility (written by a former employee of > course) that reads a data queue to find newly created spool files. The > utility is an asynch program that fires up every 30 seconds and moves the > spool file from one output queue to another for printing and archiving. > Occassionally the utility misses a spool file. When I manually move the spool > file to another output queue and back again, the utility is able to find and > process it. > > I suspect I have a timing problem...that the data queue is loaded with > information for the spool file before the spool file status is changed to > 'RDY'. The utility program grabs information from the data queue and tries to > move the spool file but fails because it is not in RDY status. > > I've tried changing the SCHEDULE parameter on the printfile to *IMMED with no > success. Can someone help me understand exactly when information is written > to the data queue and can it be controlled to coincide with the change of the > status from 'OPN' to 'RDY'? > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.