From: fairfield@sldb4.slac.stanford.edu
Sent: Wednesday, August 18, 1999 8:59 PM
To: Info-VAX@Mvb.Saic.Com
Subject: Re: DCPS 1.7

In article <186088980@MVB.SAIC.COM>, 
    	Paul Anderson <panderson@genicom.com> writes:
> On 8/18/99 11:11 AM, Peter LANGSTOEGER (eplan@kapsch.net) wrote:
> 
>> Of course I'm doing logical defines at startup.
> 
> I didn't see the DCPS$queuename_DEVICE_NAME logical name there.  When the 
> device string gets too long for the queue manager to store it, we define 
> a logical name for it.  When you do a SHOW QUEUE, you see something like:
> 
>      Printer queue MY_PRINTER, idle, on MYNODE::DCPS$, mounted form...
> 
> So if you are using long names, such as fully qualified TCP/IP names or 
> AppleTalk names, you need to run DCPS$STARTUP or define the 
> DCPS$queuename_DEVICE_NAME logical name yourself.

        Actually, I've gone one step further  than did Peter.  I've made
    all of our DCPS queues,

     /AUTOSTART_ON=(node1::DCPS$,node2::DCPS$,node3::DCPS$,node4::DCPS$)

    I have a command  procedure  that  defines DCPS$queue_DEVICE_NAME to
    the  corresponding  "ip_rawtcp/" or "appletalk/" string, as well  as
    any  desired  DCPS$queue_PARAMETER  for  that  queue,  on  all  four
    participating  nodes  at  startup  for all queues.  In addition, the
    basic  DCPS  logicals,  such   as  DCPS_LIB,  DCPS$MAX_STREAMS,  and
    DCPS$LAYUP   are  defined  in  that  procedure.   _Optionally_,  the
    procedure _initializes_ a named queue, or all queues, but this  only
    needs to be done _once_ when a queue is added.

        In general, this procedure has  worked exceedingly well.  Should
    the good folks at GENICOM add more logical names in the future, I'll
    need  to  incorporate them in my procedure as well, obviously.   Not
    taking anything away from the supplied  DCPS$*.COM  procedures,  nor
    the Paul's advice and issues surrounding "supported configurations",
    but  the  fact  is  a  _knowledgable_  system  manager  can read the
    DCPS$*.COM files in SYS$STARTUP and  come  up  with a more flexible,
    better  tailored to their site's needs, DCPS startup procedure.  And
    I agree with Peter that the requirement to _initialize_ print queues
    at system startup can be quite a burden if you have more than a  few
    print queues...

        -Ken
-- 
 Kenneth H. Fairfield            |  Internet: Fairfield@Slac.Stanford.Edu
 SLAC, 2575 Sand Hill Rd, MS 46  |  Voice:    650-926-2924
 Menlo Park, CA  94025           |  FAX:      650-926-3515
 -------------------------------------------------------------------------
 These opinions are mine, not SLAC's, Stanford's, nor the DOE's...
