My very first OSes were OS PCP and CP-67 back in 1969, but I did not do any serious OS/360 coding until around 1975. (I was coding for DOS/360 in the interim.) My recollection is that PGM= worked then more or less exactly as it does now. I don't recall about STEPLIB for sure -- I think then it was more or less as now -- but I am 99% sure than SYSLIB worked then more or less as now.
You could IPL a standalone dump from cards or tape, but OS/360 PGM= never supported other than disk-based load libraries, AFAIR. To submit a job you put the JCL deck in the card reader and issued S RDR specifying the address of the card reader (generally 00C). There was no job entry system. You started readers and you started writers. I *think* a program could if it wished read directly from cards or write directly to punch or print, but generally you did not do so. Some programs had to: the 1404 was a combination card reader and line printer (believe it or not). Organizations punched account numbers into cards and then used the 1404 to read the account number and print an invoice on the card. The cards were then mailed to customers, and when they returned their checks, the card was used as a processing document. The 1404 supported double-wide cards -- two 80-column cards joined at a short edge with a perforated strip. The customer kept one card and returned the other. http://www.bitsavers.org/pdf/ibm/1401/G24-1446-0_1404_printer.pdf talks about 1401 attachment but I remember that Blue Cross of N. Calif. had one attached to a 360/50. Used for billing as I describe above. Charles -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Thursday, March 31, 2022 9:01 AM To: [email protected] Subject: Re: Does HLASM use NOTE and POINT on UNIX files? On Mar 31, 2022, at 09:54:38, Schmitt, Michael wrote: > How did the assembler originally work, back when punched cards were used? I don't really know. > How did "EXEC PGM=..." originally work, back when punched cards were used? I suspect SYSIN, but neither SYSLIB nor STEPLIB. -- gil
