|
The info gets written to the data queue when the splf shows up in a ready (RDY) status...not before. What is the CPF message you are getting? Also, if the async program is getting its input from the data queue, why have it wake up every 30 seconds and check it? Why not just specify "wait forever" when doing the QRCVDTAQ? That way it can respond to the entrys right away with very little delay. It is possible that the splf shows up, data queue entry gets sent but before you check it, something else is happening to the splf.. Bob -----Original Message----- From: RDJessen@aol.com [SMTP:RDJessen@aol.com] Sent: Tuesday, September 22, 1998 8:42 PM To: MIDRANGE-L@midrange.com Subject: Data Queue's 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-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.