|
aOn 10 Apr 2001, at 10:08, Michael Kenney wrote: > I know from prior posting that some of the members on this list are > users of ACOMs EZPRINT. > > We currently using their APIs to automatically manage my automerge > jobs. We have a job which runs every morning and initiates all of my > automerge jobs using the cmd STARTAM , this process works fine. We > also have a job which runs every evening which issues the cmd STOPAM > to end the automerge jobs. The problem I am having is that the > automerges are ending as far as EZPRINT is concerned but the actual > jobs continue to run. > > I tried running this from the QSECOFR account and get the same > results, which leads me to believe that security is not an issue. > > Has anyone else experienced this same problem. The way EZPrint automerge works is it takes the printouts or data files that get produced by your applications and merges them with the EZPrint form definitions that get sent to the printer. When you stop the merges you stop the printouts from printing. That doesn't stop the application jobs from producing what feeds into EZPrint. Gary Kuznitz +--- | 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.