20 Jun
2000
20 Jun
'00
3:46 p.m.
paper on the printer. Worst setup was MU Computer
Sciences where you turned
in the cards and got back output in 24 hours. Many times with message CPU
time exceeded and no output.
Just set your job to run as class X. I forget the details, but our lazy
sysops used to set the "accumulators" to class X to clear jobs out of the
system or some sysop type reason. A few people found out, and when you ran
class X, boom you had 60% of the machine to yourself, no billing or time
limits.
OTOH writing ASM when the code barfed, a low time limit was a GOOD idea. I
remember one job just about killed a whole class account for the semester.