🚀 go-pugleaf

  Last night we moved our system and users from our old RA81's to our
  new RF73's, on our Vax 4000-200 under VMS v5.5.  Everything went pretty
  smoothly, except for the *#$%^$ new queue system.  For some reason, the
  queue system still insists on using the RA81 for two of the three queue
  files.  The logical QMAN$MASTER is defined as SYS$COMMON, and indeed it
  is using the QMAN$MASTER.DAT file on the new RF73 system disk, but it is
  still insists on accessing the RA81 for the other two files:

	 [SYSCOMMON.SYSEXE]SYS$QUEUE_MANAGER.QMAN$QUEUES;1
	 [SYSCOMMON.SYSEXE]SYS$QUEUE_MANAGER.QMAN$JOURNAL;1

  No one at this site has documentation on the new 5.5 queue manager (we're
  an ESL site and the ESL people are unavailable at the moment, and probably
  couldn't help anyways).  I haven't been able to find any other logicals
  that the queue manager might be using to point to these files, so I suspect
  that the location of these files must have been written into the QMAN$MASTER
  file.  We probably shot ourselves in the foot during the 5.5 upgrade by
  specifying the location of the new queue files as "dub0:" rather than
  $disk1:.  Digging through the on-line docs, I think we could maybe do it
  by stopping the queue manager, then using START/QUEUE/MANAGER/NEW_FILE=$DISK1
  to create new queue files, stopping the queue manager again, copying the old
  dub0: files to $disk1, and the restarting the queues, but since we are a
  critical production machine and really need the queues to be working, I'm
  nervous about trying this without knowing for sure that this will work.
  Has anyone else run into this problem?  If so, how do you fix it?

  -Bob


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|      Bob Boardman, University of New Mexico, Albuquerque, New Mexico        |
|         internet:boardman@cancer.unm.edu    bitnet:BOARDMAN@UNMB            |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=