Re: George 2+
GO #ABCD 20 - start the job with paper tape input
GO #ABCD 21 - Start the job with punch card input
GO #ABCD 25 & 27 ibid
GO #ABCD 29 - abort the job (usually) - yes, under George II+ you had to type GO when you wanted things to STOP.
The number after the program name was the address of the starting command in the compiled program.
Some programs had a "go type entry block" so you only ever typed GO #ABCD. I've never found out why.
On the 1900 series OU #ABCD 8 was useful too, as word 8 was the program counter. Good for finding forever loops (if the speaker warble wasn't indicative).
Though all those commands were actually EXEC commands as I remember them. George was a set of modules you could load (or not) to get a job done with minimal interference from the operators. The "steering lines" (aka JCL) were a drop-through action list. Dead simps. So you operator would type something like:
FI#XKYE#GEOG 1 (find the input spooler in file GEOG and assign it to unit number 1)
blahblahblah
INPA R WAS XKYE
XKYE HALTED TR 1 FIX (the spooler had renamed itself and stopped pending the loading of a paper tape and the operator pressing the green button on the reader)
GO#INPA 20
blahblahblah
INPA HALTED HH (the spooler has finished and is ready for the next job)
FI#GEMA#GEOG (load the central control module from file GEOG - ours was called GEMA after someone's girlfriend)
GO#GEMA
ABCD R WAS GEMA (your ABCD program is now running)
ABCD HALTED HH (and it just finished)
FI#XKZE#GEOG 3 (Load the output spooler and assign it to unit 3 - the line printer in this case)
blahblahblah
OUTA R WAS XKZE
OUTA HALTED LP3 FIX (operator loads paper and presses the green button on the printer)
GO OUTA 25 (I think, it has been over 40 years since I did this for real)
(EARSPLITTING BANGBANGBANG NOISES FROM THE BARREL PRINTER)
OUTA HALTED HH (the print run is finished and the operator, ears bleeding, can tear off the report)
If you needed more room for ABCD you would DE#INPA before you GO#GEMA'd. There was something of an art to juggling the memory. I remember one consultant we had who would lobotomize EXEC on the fly from the console so they could finish in only 3/4 the memory they needed.
Ah the happy sound of the print drum of the console Westrex slamming into its lid so it snapped like and angry crocodile when the machine "went illegal" because someone had typed DE#ABCD when there was less than two kilowords of core memory unused. Ah the happy sounds of the cursing operator typing like mad when a stupid compilation mistake did the same from a program test run.
Worse days.