× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Faxsimile
  • From: "William Corbett" <corbett@xxxxxxxxxxxxxxx>
  • Date: Wed, 22 Nov 2000 12:24:44 -0800
  • Importance: Normal

I'm using Fax/400 and am having no problems with the *HOLD problem you've
mentioned.

I'd check the CL overrides in the spoolfile-creation program and the OUTQ
you're generating the splf into.  I've set up a "special" FAX400Q with no
print writer to generate fax400 spool files into.  Otherwise, you'd have to
generate the spoolfile on HOLD, to keep the print writer from "grabbing" it
before fax400 does.  When I originally set up fax400, I had this problem,
the print writer would grab it between the close of the spool file and the
sbmfax command....theoretically fractions of a second, but it still
happened.
The only problem I ever have with fax400 is when the operations staff brings
down all subsystems for backups.  When they restart it, the status update
program occasionally doesn't get started up correctly, so I've got over a
hundred faxes "SENDING".


corbett@asresources.com
http://www.cbt400.com
http://www.asresources.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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.