GWD21T@DGOGWD01.BITNET.UUCP (06/14/87)
Maybe there are not so many institutions charging for PAGES PRINTED
since the accounting bug (in JOBCTL) described in the following
SPR now exists for such a long time.
Since I suspect that SPRs from Germany take about a year to reach
DEC engineering, I just wonder if
# anyone else noted this problem
# anyone else SPRed it
# anyone has a fix or any hint, or even got an answer from DEC
(I'm not asking for DECsupport over the net,
I'm just curious ...)
Thanks in advance for any replies.
-wjm
.............................................................................
SPR REPORT (sent in Jan.87)
Bad print job accounting after STOP/QUEUE/NEXT
Description:
After stopping a print queue (completely) with STOP/QUEUE/NEXT,
the counters used for accounting entries are not cleared.
The first job printed after a START/QUEUE will be accounted for
the ressources (pages, QIOs etc.) used by the last job prior to
the STOP in addition to the ressources it actually required.
Also, every job deleted by DELETE/ENTRY while the queue is stopped,
gets the same accounting data as the last job prior to the STOP.
Test sequence:
$ PRINT 3pages.
Job 123 started on queue SYS$PRINT
$ STOP/QUE/NEXT SYS$PRINT
$! ... wait till queue is really stopped
$ PRINT 3pages.
Job 124 pending on queue SYS$PRINT
$ DELETE/ENTRY=124 SYS$PRINT
$ START/QUEUE SYS$PRINT
$ PRINT 3pages.
Job 125 started on queue SYS$PRINT
Assuming that the file takes 3 pages to print,
job #123 will be accounted for 3 pages (OK),
job #124 for 3 pages (BAD),
job #125 for 6 pages (BAD).
Note:
This error exists at least in VMS V4.3, VMS V4.4 and VMS V4.5 .
.............................................................................
W.J.Moeller, GWDG, D-3400 Goettingen, F.R.Germany <GWD21T@DGOGWD01>
Phone +49 551 201516