Hakan and I (if my memory serves correctly) had an extended discussion on this very subject just a short time ago (see "Creating a Queue" by JWulli, last entry 10/5/2004).
Rather than reproduce the entire discussion, I will start by suggesting that you take a look at that thread of postings. We can then take it from there.
The problem is that Hazem doesn't explain WHY its necessary to print to file.
Is it a one time thing ? What kind of files, TEXT...Postscript... ?
I use the TELNET-RELAY feature as "Print to File" when I troubleshoot formattingproblems. But that is on a one-time basis and includes manual intervention.
Thanks for your concern. The problem simply that one customer has an industrial application running under VMS, and there is a print queue that output some sort of alaram and notification messages continuously to a printer. The customer needs to save the printout of that printer, as the messages are not that important, and he needs to redirect such output to be saved in a file for fuure reference, while he may need to delete such file on periodical basis. I hope that the image is clear now so that I can get an answer. Regards.
Are you totally sure that the output is being sent to a print queue?
If I understand your last posting correctly, data is being sent CONTINUOUSLY to a printer. This would seem to indicate that the output is being sent directly to a printer, not through a print queue.
If this is the case, there are some solutions. However, there is likely a need to still display information on an urgent basis, not just stored in a file.
Please let me know if this understanding is correct.
youo probably want the print /nodelete option and save the file that was sent to the printer. the default is to delete what was printed. Be aware, that the same filename will get an increasing version # and the ods file system only allows for a max version # of 32766 or is it 32767. I would suggest a daily routine to archive the already printed files to, say, a directory named for the date the files were printed. this would keep the versions restarting at 1 each day. I would suspect it unlikely that this application prints over 32k alerts daily. if it does, schedule the archive say midnight and again at noon, more frequently if needed.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE