This is a discussion on Re: print to file? - VMS ; Selden, I am using an application called ByRequest (from Hillary Software) that performs electronic publishing using mainframe reports as input and spools (publishes) those reports to just about any format (Word, Excel, NotePad, PDF, etc) to a Windows network share. ...
I am using an application called ByRequest (from Hillary Software) that
performs electronic publishing using mainframe reports as input and
spools (publishes) those reports to just about any format (Word, Excel,
NotePad, PDF, etc) to a Windows network share. The app is installed on
a Windows VM, FTP's into the VMS cluster, grabs the reports, converts
them into the required output format and writes them to a network share
on a NAS box. The user maps that network share on their PC and accesses
their documents as needed. The ByRequest app is very flexible, can
handle any type of report, can burst a report by section, lots of
pagination options, etc. There is some setup work involved in defining
the spooler, but once completed, its "set it and forget it". We have
significantly reduced our paper expenses, and this option gives the end
user the ability to burn their reports to CD for archival purposes.
Selden E Ball Jr wrote:
>Is there any way to persuade a Multinet print queue
>to send print jobs to a file in a user's directory?
>For example, can the spooling directory be redefined
>on a per-queue basis?
>I don't see any mention of a "print to file" option in the
>Multinet documentation. Have I overlooked it?
>Apparently it may be a future option in DCPS, but our need is now :-)
>Alternatively, does anyone know of another print symbiont that
>can do this?
>There seems to be a Windows based solution (sending print jobs to
>queues on individuals' PCs) but I'd like to avoid that if possible.
>Our business office is trying to reduce the amount of paper records
>they have to keep. The mainframe application that they're running
>sends print jobs to lpr/lpd queues that are served by our
>They're currently testing scanning the printer output and using OCR,
>That's what they'll have to do for existing documents, but it'd
>be nice to avoid that effort for future documents.
>I think that one queue per user, each writing a specific
>directory would be an acceptable solution.
>Thanks for whatever help you can provide.
>Selden E. Ball, Jr.
>Cornell University Voice: +1-607-255-0688
>Laboratory for Elementary-Particle Physics FAX: +1-607-255-8062
>LT105 R. R. Wilson Laboratory http://www.lepp.cornell.edu/~seb/
>Dryden Road Internet: SEB@LEPP.CORNELL.EDU
>Ithaca, NY, USA 14853-8001 HEPnet/SPAN: LNS62::SEB = 44284::SEB