Post by Dave Froble Post by Phillip Helbig (undress to reply)
Arrived today, unpacked it, plugged it into the network (it does WiFi,
and I have WiFi in the house, but I prefer to use cables if that is an
option) and power, and the iPad and MacBook recognized it right away and
printed as usual.
I haven't set up a print queue on VMS in more than 20 years; time to
$ Init /queue -
I left out form=DFE since I got "%JBC-E-NOSUCHFORM, no such form" from
that. The name of the queue is arbitrary, of course (it is actually an
Post by Dave Froble
Note, I forget where I got "BROTHER_IP:9100"
9100 seems to be a standard port for printers. I'll see if I can get
the DSL router to always give it the same DHCP address.
Text and PostScript files work fine from VMS. Trying to print a PDF
file results in a page saying that directly printing PDF files is not
supported (which does show that the printer recognizes it as a PDF
file). This is not a big deal, for many reasons:
o Most PDF files I have on VMS are my own which were created from
PostScript files with ghostview, so I can just print the
o In other cases, I can use ghostscript to convert the PDF file to
PostScript and print that. (That could be streamlined via a
procedure, of course.)
o I can copy the PDF file to a location where I can access it from
the iPad via HTTP and print it that way.
Yes, the latst will always work, but is an extra step. If I need to
script things, then that is also easier in DCL.
All the same, since the printer does print PDF files, and since it does
recognize a PDF file sent via the VMS print queue as a PDF file, I'm
wondering whether there is some way to do it after all.
The (modified version of the) command above defaults to the current
node. I can actually print from other nodes (of course, the queue
database is on a non-system disk mounted by all nodes), but presumably
not if the node in question is down. Presumably I should set up similar
queues on all the nodes and combine them into a generic queue.