Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ptsfa!lll-lcc!styx!ames!rutgers!mit-eddie!genrad!decvax!tektronix!tekcrl!tekgvs!toma
From: toma@tekgvs.UUCP
Newsgroups: comp.misc
Subject: Re: More 1130/1403 stuff
Message-ID: <2079@tekgvs.TEK.COM>
Date: Fri, 13-Feb-87 10:56:09 EST
Article-I.D.: tekgvs.2079
Posted: Fri Feb 13 10:56:09 1987
Date-Received: Sun, 15-Feb-87 04:49:52 EST
References: <2319@sunybcs.UUCP> <1596@kitty.UUCP>
Reply-To: toma@tekgvs.UUCP (Thomas Almy)
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 44
Keywords: early computers, trivia, humor


In article <1596@kitty.UUCP> larry@kitty.UUCP (Larry Lippman) writes:
> 
>	While my first hands-on computer experience was with a 1401 used
>by a particular department, my college had a 7094 as the computing center
>mainframe.  This beast ran a tape operating system called IBSYS.  All
>students, staff and faculty authorized to submit jobs were issued a supply
>of job cards having prepunched fields for job number, user id and department,
>and time limit.  Students obviously wanted more than their allocated cpu time,
>but the administration thought it had licked the problem of job card
>counterfeiting (i.e., with a longer cpu time limit) by using cards that were
>on a special colored and striped stock; needless to say, this blank card
>stock was well "guarded".
>	However, for enterprising students there was a way around this
>situation: Since the stripes never covered the columns where the time limit
>was punched, conventional colored card chad could be carefully glued to
>cover the zero punches in the tens and hundred minutes columns - thereby
>permitting the card to be repunched with a higher time limit!  A good job
>of covering the zero punches was difficult to detect.

I had the same problem, needing to create an "illegal" job card.  Where I was
at the time (Cornell, late 60's) had a priority system, and during the day
they would not load jobs that were below a certain priority (that mere under-
grads did not have!).  I solved the problem (and actually got away with it for
a while) by placing a dummy job at the high priority, with a real
Job Card, in front of my real job, with a job card made of regular stock.
The system would bounce the phoney job but then execute my real, low priority
job.

//JOB...PRI=6             (real job card)
//
//JOB...PRI=4             (regular stock)
//EXEC
...
//

Additional comment: I never liked using terminals until display oriented 
editors appeared.  It was so much easier to edit a deck of cards (now that
was real WYSIWYG!).

Tom Almy
Tektronix

(Where is a keypunch now that we need it?)