| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 24.1 | no more | CLOSET::ANKLAM | | Wed Feb 25 1987 09:05 | 12 |
|
Yes, there is no longer a default BATDOC queue. You can still set
up a batch queue specifically for SDML jobs, and request users
to specify the queue in /BATCH=(QUEU:name).
The default queue names for printing devices are now set up during
the installation procedure, and are tied to the destinations.
Are there problems with either of these? (will take comments...)
patti
|
| 24.2 | | BOOKIE::GENT | | Wed Feb 25 1987 09:58 | 19 |
| Patti,
I have no problems with the current handling of printer queue names
(in fact, I think it is a big improvement). However, I do think there
should be a way for the system manager to set up a default batch
queue. I would suggest the use of a logical, such as SDML$BATCH.
If the name exists, use it's definition as the default batch queue
for a DOC/BATCH command. If SDML$BATCH is not defined, use the
system default (SYS$BATCH). Does that make sense?
One other very minor quibble: you may want to document in the
installation guide how to *change* the default printer queue settings
after installing DOCUMENT. For example, we installed support for
PostScript, for testing, although we do not currently have a PS printer
queue on our machine. But we expect one soon. Is there some way
to redefine the default PostScript printer queue without re-installing
PS support?
--Andrew
|
| 24.3 | Changing Default Print Queue Names | VAXUUM::DYER | Rock the Bells | Wed Feb 25 1987 13:18 | 7 |
| 24.4 | That's the only way for now | CLOSET::ADLER | | Thu Feb 26 1987 18:20 | 5 |
| Right now the only supported way to change default queue settings is to
reinstall. We realize that that's insufficient, and will be working on
an alternative method.
--Brian
|
| 24.5 | can you choose your printer? | DECWET::HUNT | Liz Hunt | Thu Feb 26 1987 20:33 | 18 |
| re: 24.1
> The default queue names for printing devices are now set up during
> the installation procedure, and are tied to the destinations.
Do I understand correctly that during installation we define one
(and only one) default print queue for each destination?
At our site we have 4 LN03's that are used by our writers. Each
writer would like to be able to specify the LN03 closest to them
as the target for their ln03 output. Under BL 6 we use
DOC$LN03_QUEUE to indicate our preference. I suppose we could
define symbols like:
$ DOCqqqq == "DOCUMENT/PRINT=(QUEUE=qqqq, NOFEED, PASSALL)"
Is there any other way? If not, I'd vote for the return of the
DOC$qqq_QUEUE logical names.
|
| 24.6 | You Can Still Use Logical Names If You Want To | VAXUUM::DYER | Rock the Bells | Fri Feb 27 1987 03:48 | 13 |
| > Do I understand correctly that during installation we define one (and only
> one) default print queue for each destination?
Having a default implicitly means one (and only one). How can there be more
than one default?
You can get what you want this way: Install LN03 support and specify
"DOC-LN03_QUEUE" as the queue name. (Do *not* use "DOC$LN03_QUEUE" or
anything with a "$" character in it.) Define a system-wide "DOC-LN03_QUEUE"
logical name, equivalent to one of the LN03s' queue names. Writers can then
define job- or process-wide "DOC-LN03_QUEUE" logical names equivalent to
their own preferred LN03s.
<_Jym_>
|