Article 125143 of comp.os.vms:
Path: nntpd.lkg.dec.com!pa.dec.com!decwrl!pagesat.net!news.cerf.net!nntp-server.caltech.edu!vance
From: vance@alumni.caltech.edu (Vance R. Haemmerle)
Newsgroups: comp.os.vms
Subject: Re: VMS VAX 6.2 help/message
Date: 18 Jul 1995 22:10:05 GMT
Organization: California Institute of Technology, Alumni Association
Lines: 39
Message-ID: <3uhbft$jgm@gap.cco.caltech.edu>
References: <01HSZ1WDTCQC8ZE9DN@oitvms.oit.umass.edu> <3ueku5$3kl@gap.cco.caltech.edu> <3ugslv$ogc@news.doit.wisc.edu>
NNTP-Posting-Host: alumni.caltech.edu

In article <3ugslv$ogc@news.doit.wisc.edu>,
John Stott <jpstott@src.wisc.edu> wrote:
>
>That certainly solves the problem, thanks!
>
  You're welcome. :)

>>Now, if anyone can tell me why the V6.2 Queue Manager wants
>>my journal file SYS$QUEUE_MANAGER.QMAN$JOURNAL to be 41300+
>>blocks...
>
>It seems to be happy with mine at 2 blocks!  
>

  With the file at 102/41307 blocks, I could stop the queue manager, 
truncate the journal file, restart it, and the allocation
would grow back to 41300+ blocks.  A newly installed V6.2 system
also had a full 41300+ queue journal file.   In one of my experiments
stopping and restarting the printer queue caused it to grow.

  Following the instructions for saving and restoring the queue
files seems to have fixed it.  (At least the journal file doesn't
grow when you start and stop the print queue or the manager).

  $ STOP/QUEUE/MANAGER/CLUSTER
  $ DELETE SYS$QUEUE_MANAGER.QMAN$JOURNAL;
  $ CONVERT/SHARE QMAN$MASTER.DAT  QMAN$MASTER.SAVE
  $ CONVERT/SHARE SYS$QUEUE_MANAGER.QMAN$QUEUES SYS$QUEUE_MANAGER.SAVE
  $ DELETE QMAN$MASTER.DAT;
  $ DELETE SYS$QUEUE_MANAGER.QMAN$QUEUES;
  $ RENAME QMAN$MASTER.SAVE QMAN$MASTER.DAT
  $ RENAME SYS$QUEUE_MANAGER.SAVE SYS$QUEUE_MANAGER.QMAN$QUEUES
  $ START/QUEUE/MANAGER

  Chalk it up to a corrupt queue file?

--
Vance Haemmerle
vance@alumni.caltech.edu