Download MTS Operators' Manual - Deep Blue

331
data for too much of some record type (some program going crazy
generating it), or for something wrong with CMDPIKUP or CMDTAPE.
CMDSTATc WAS MARKED FULL IN CMDDIR BUT WAS EMPTY.
Presumably, CMDSTATc was marked F by CMDPIKUP.
So, either
CMDPIKUP was confused, someone marked the file F in CMDDIR by
hand, or the file really wasn't marked F and CMDTAPE was
confused.
The only thing to do is to tell the person who
maintains this stuff about it.
LINE llll IN CMDFDIR DUPLICATED WRITING CMDSTATc
The data in CMDSTATc had exactly the same time range as some
file already on the tape. This is unlikely to occur without a
mistake by a person fixing something.
Check whether the two
tape files are really duplicates, and if so, delete one.
(Delete the one which is not described in llll.)
NEW FILE FROM time OVERLAPS FILE IN CMDFDIR LINE llll
This is similar to the problem above, except that the two files
are not duplicates.
This message is generated only if the
overlap is more that a minute (shorter overlaps sometimes occur
because of the way the buffers are filled and emptied). If this
occurs just once, ignore it, but if it occurs several times over
a couple of weeks, tell the person who maintains this code about
it.
NO ROOM IN CMDFDIR AFTER llll; CALL SYSTEMS PROGRAMMER!
This message goes to the console. Spread out the lines around
llll in CMDFDIR (it is safe to renumber the file), then enter a
null line at the console. CMDTAPE will make a new attempt to
write out the directory line.
This problem is unlikely to
occur; the probable cause is that files were not written to tape
for quite a while, and when they were written, they were written
out of order.
ERROR ON ffffffff.
CALL A SYSTEMS PROGRAMMER
This message goes to the console.
A misformatted line was
discovered, or an error occurred reading, writing, or locking
ffffffff (CMDSTATc, CMDDIR, or CMDFDIR).
CMDTAPE will not
continue after printing this message (a response to the read
will cause it to stop). Fix the file causing the problem as
necessary, remove any B flags in CMDDIR, and start *DWB again.
CMDSTAT TAPE ERROR; PLEASE TRY ANOTHER DRIVE
This message is printed on the console, followed by a mount
request.
A tape error has occurred on the current tape, and
CMDTAPE is about to try again. If an error occurs on the new
drive, CMDTAPE will abandon the tape and ask for a new one.
CMDSTAT