Technical data

B
Logical Names used by DCPS
This appendix provides some information about OpenVMS logical names that
are used by the DECprint Supervisor for OpenVMS software.
Here are some guidelines for using these logical names:
Any logical whose name begins with ‘‘DCPS’ is only used by the DECprint
Supervisor for OpenVMS software. Other logical names (for example,
PSM$ANNOUNCE) may be used by and impact other components of your
OpenVMS system.
You should place your desired definitions for these logical names in
DCPS$STARTUP.COM or in something that it invokes. The startup
procedure template has comments about how to define some of these.
Changes to some logical names have an immediate effect, while changes
to others take effect only when a queue starts or when a DCPS symbiont
process is first created. The ramifications of this are particularly
significant if you are using multistreamed DCPS symbiont processes (see
Section 3.4.1.2). You should assume that the symbiont reads all logical
names only when it is first created, thus requiring you to first stop all
queues and then retart them before your changes can take effect.
You should define the desired logical names in the system table in
executive mode (that is, using DEFINE/SYSTEM/EXECUTIVE).
In a VMScluster environment, you should define the desired logical
names on all nodes that utilize the DCPS software. To examine logical
names defined by DCPS, you need to look on the node on which the DCPS
symbiont process is running.
Additional logical names may be listed in the DECprint Supervisor for
OpenVMS Release Notes.
Logical Names used by DCPS B–1