The OS/360 readers and writers weren't that bad if you used reasonable block 
sizes, but ASP and HASP make that unnecessary. My HASP experience started with 
HASP ii V3, although I read much older documentation before that.

I believe that SPOOL dates from around 1959,

-- 
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר




________________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of 
[email protected] <[email protected]>
Sent: Monday, November 17, 2025 10:52 AM
To: [email protected] <[email protected]>
Subject: Re: It's not a bug it's a feature


External Message: Use Caution


      > The August 1967 catalog of programs shows it as priority.
My memory is not great these days, but I think I remember installing a 
"prerelease" in early or mid 1967; and I slightly remember a reference as 
"Houston Automatic Spool with Priority" — but the "with" in the name might have 
been during a telephone conversation with someone in Houston.
During that early period the documentation was rather rough and (again, if I 
remember correctly) printed with a TN train.
HASP was a wonderful invention! The "OS/360 Readers" and "Writers" it replaced 
were guaranteed to produce nightmares. (And I do not remember the correct names 
for the Readers and Writers. It has been a long, long time since I have seen 
any mention of them.)
Spooling was not a new concept, of course. The 7090+1401 and the later DCS 
systems both quickly illustrated the strong advantages of spooling ---- 
especially when punched cards were involved!

Bill Ogden

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to