Binder REP Cards Was: What's the linkage editor really wants 3292

Chris Mason

my first studen programming job was to reimplement 1401 MPIO program on had hardware 1401 emulation mode and the original MPIO program could have been run directly ... after the 30 replaced the 1401).

after about two months, i had 2000 statement buttembler program. i got to invent and implement my own tasking monitor, interrupt handlers, device drivers, dynamic storage management, etc. it took 30 minutes elapsed time to buttemble my 2000 card buttembler program. Before i learned about "REP" cards, i had learned how to read the "hex" punch holes in the TXT cards and could fan a "binary" text deck, pick-out the TXT card for the storage area (reading the hex punch codes in the TXT storage address field) and multi-punch correction into "duplicated" TXT cards on 026 card punch (aka binary patch)

i added conditional buttembly statements where the same source instead of generating a totally stand-alone monitor would generate code that would run under os-360 with open-close, get-put, and DCB statements. With conditional buttembly set, it would buttemble five DCB macros ... which were particularly difficult for os-360 (circa release 6) on the 64kbyte 360-30. You could recognize from the light pattern on the 30 front panel when the buttembler was processing a DCB macro ... each one taken approximately six minutes to process aka the os-360 flavor with DCB macros took approx. an extra 30 minutes to buttemble (a total of hour elapsed time).

misc. past posts about MPIO and 0-2-9 TXT and REP cards video terminal?) writting BAL 370. writting BAL 370.