| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 152.1 | | CUPOLA::HAKKARAINEN | Albatross! | Wed Mar 25 1987 15:54 | 2 |
| I believe that these items are set during installation. If the device
support is not requested, then logicals are not set up.
|
| 152.2 | Does not look that way | ATLAST::BOUKNIGHT | Everything has an outline | Wed Mar 25 1987 17:23 | 6 |
| We use all three. Only the LN03 queue is defined by an explicit
logical. We assume that LINE is being defaulted to SYS$PRINT and
POSTSCRIPT to a queue named POSTSCRIPT. That is where the output
does come out. We would like to be able to queue LINE to an LN03.
JACK
|
| 152.3 | queue name = logical name | BUNSUP::LITTLE | Todd Little NJCD SWS 323-4475 | Thu Mar 26 1987 02:09 | 9 |
| Its late and I did this n weeks ago, but does the installation procedure
ask you for a queue name for each device you install? That queue name
can just as easily be a logical name as a real device queue. If
you want to change this after the fact, I recall there being a file
called DOC$DESTINATIONS.DAT that has all that kind of information in it.
If you edit that file MAKE SURE YOU DON'T ADD OR DELETE ANY LINES! If
you do, the next installation of a device will corrupt the file.
-tl
|
| 152.4 | yes, and yes | CLOSET::ANKLAM | | Thu Mar 26 1987 12:13 | 12 |
|
yes, the installation prompts you for a queue name, which can be
a logical name. and yes, the name is placed in DOC$DESTINATIONS.DAT
which can be modified but only as Todd says, without adding or
deleting any lines.
we are working on procedures to automate changes to
DOC$DESTINATIONS.DAT so that folks can change the queue names or
other defaults whenever it's appropriate to do so.
patti
|
| 152.5 | Some clarification needed | ATLAST::BOUKNIGHT | Everything has an outline | Fri Mar 27 1987 11:35 | 10 |
| Having read the information in the DOC$DESTINATIONS.DAT file, it
mentions SUMSLP as a good editor to use. Does this mean that EDIT
or TPU can't be used? Is it only number and position of lines that
is important, and not number and position of characters on a line?
I assume the keywords have to remain where they are and we can edit
the values associated with the keywords.
Will the maintenance procedure(s) be available before or at FT update?
jack
|
| 152.6 | better stuff coming | VAXUUM::KOHLBRENNER | | Fri Mar 27 1987 12:00 | 15 |
| SUMSLP is a terrible editor, but you can call it as part of
an installation command procedure, so I used it. SUMSLP
replaces whole lines only and only on a line number basis.
So when it comes to installing support for a given device,
we replace a known set of lines with the right stuff for that
device. That is why if you delete a few lines or add a few
lines in DOC$DESTINATIONS.DAT and then try to install support
for some device, the replaced lines will probably clobber
something else in the file that has moved as a result of your
addition or deletion.
I'm working on the FT update stuff right now and it will probably
use TPU and won't result in such a restrictive file for
DOC$DESTINATIONS.DAT.
|
| 152.7 | multiple devices of the same type | VAXUUM::KOHLBRENNER | | Fri Mar 27 1987 16:29 | 17 |
| The FT update installation for any device will let you specify
pairs of names, the destination name that you will use on the command
line and the queue name that corresponds to that destination.
And it will keep asking you if you have another device of the
same device-type and will ask for another pair of names if you
say yes. SO people who have more than one LN03 or more than
one LPS40, LN01, etc, can give them different destination/queue
names.
THis procedure will not require position-sensitive lines in
DOC$DESTINATIONS.DAT, so the file can be edited by those who
more-or-less know what they are doing.
We haven't figured out whether we will provide a COM file for
making modifications (add, modify, delete) or whether we'll just
provide some documentation and let people edit it.
|