Title: | PATHWORKS V5 for DOS and Windows |
Notice: | OS2LAN::OS2:[PUBLIC] is alive again, but not what it used to be |
Moderator: | RANGER::CURLESS |
Created: | Fri Feb 11 1994 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 7404 |
Total number of notes: | 27276 |
(Posted also in PE Print Services) Do you think PW Print Services can solve the following problem? A customer has a VMS application that today prints on a VMS print queue associated to a terminal server port with a LA210. Now he wants that the print file,instead to be printed on the LA210, is sent to a PC and is stored in a local file for next processing. Is it possible to define a VMS printer queue associated to a file on the PC? If yes can be the file name defined as a progressive number so I can have different files for each print command? Thanks for any info. Federico Sturn Sales Support Digital Rome Italy
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
7331.1 | us PW to point to spool area. | KERNEL::BURNST | Fri Feb 14 1997 10:06 | 9 | |
I dont think it is possible to define the print que to be a file on the pc disk but you could try the following, 1) create a vms print que with a spooled area and stop the que. 2) Create a pw share to point to the spool area. 3) the application would have to be able to choose the print file name or a batch job to re-name the files it finds. Trev UK CSC. | |||||
7331.2 | Yep - sort of... | SUTRA::MOXLEY | Shiny Shoes, Shiny Mind | Wed Feb 26 1997 03:40 | 22 |
re .0 Sorry Trevor, I think PWPRINT *can* do what Frederico wants, sort of. >>Is it possible to define a VMS printer queue associated to a file on >>the PC? Yes, it most certainly is, use the following parameters: Connect Type : FILE Location or Printer : FILENAME The file will end up in C:\PW32. >>If yes can be the file name defined as a progressive number so I >>can have different files for each print command? Er, no, the file is appended each time. It will always have the name you assigned in the field "Location or Printer",but I'm sure this can be worked around, either at the VMS or PC end. Rgds, Simon | |||||
7331.3 | Pw32 on PW v6 (VMS) | KERNEL::BURNST | Mon Mar 10 1997 04:29 | 9 | |
Simon, Will this only work for a PW32 client or are you talking about parts of PW v6 (VMS) here. If only pw32 then its only on 95 or NT4 or a long wait for full release of pw v6 (vms). Trev. | |||||
7331.4 | Clarification.. | SUTRA::MOXLEY | Shiny Shoes, Shiny Mind | Mon Mar 10 1997 08:35 | 10 |
Hi Trev, It's *client* components only. As far as I know, there are no plans to change any of this stuff in PWV6 (VMS). So, yes, you'll need 95 or NT on the clients - OK? The only part that would need extra work is the *subsequent* creation of other files with new names - but I'm sure it can be done. Simon |