|
IBM's fax/400 system provides an API to send faxes in the format of a promptable command. We give the command the Spool file name, job#, job name, user, and destination fax#. You can include other things such as cover pages, subject lines, etc. You could change all of your programs that receive the "F" parm to not insert the FAXHEADER line, then instead call the command with the fax#, etc. If you have many programs that need changing, then you could write your own monitor program for the outq. The program would extract out the FAXHEADER info and insert that into the IBM API. Now, the receiver of the fax will see the FAXHEADER line. You might want to right one program that will remove that out of the spool files before calling the IBM API. Art Tostaine, Jr. CCA, Inc. Jackson, NJ 08527 -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of William A.(Tony) Corbett Sent: Thursday, October 07, 1999 12:39 PM To: MIDRANGE-L@midrange.com Subject: Facsimile/400 Can anyone give me a couple pointers on a "correct" way to set up Fax/400? I'm currently replacing a Biscom/EDS fax solution, works good just not Y2K compliant, we just upgraded a client to from a 510 to a 720 and ordered Facsimile/400 rather than hassle with the upgrade of the Unix-based fax server pc. This eliminates a "faxserver" pc and puts all the stuff back in the AS400. (where it belongs) Current implementation: * an outq FAXQ which a program "scans" for spoolfiles and moves them to the PC * the printer file contains a FAXHEADER record which contains control codes for fax#, etc * Based on a "fax or report(f/r) _" prompt in the program a cl for the "generate" subprogram either overrides to faxq or not and faxheader record is written (or not) at each fax# change. It looks like Fax400 is cl-driven, ie., you'd have to call a cl at EACH "fax# change". Any advice will be appreciated, ie., how did you do it?? -- William A.(Tony) Corbett corbett@asresources.com http://www.asresources.com http://www.cbt400.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 +--- +--- | 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.