Latest comment: 18 January 20071 comment1 person in discussion
"In computer science, spooling refers to putting jobs in a buffer..."
This use of the word jobs is common computer slang, but perhaps not right for a WP article, esp in the opening sentence. What it means here is "intermediate workflow files", but that is kind of awkward... 69.87.193.17613:19, 18 January 2007 (UTC)Reply
Difference between spooling and queuing?
Latest comment: 8 November 20082 comments2 people in discussion
Latest comment: 8 November 20081 comment1 person in discussion
It seems like spooling is a lot like stuffing data into a FIFO where each side can can read/write whenever ready. Of course, if the FIFO gets full, data on the write side must wait or be lost. —The preceding unsigned comment was added by 157.234.254.24 (talk) 14:35, August 21, 2007 (UTC)
Spooling is FIFO. Different spooling programs treated full buffers in different ways. IBM's Power program simply stopped and waited for the operator to make a decision. DataCorp's The Spooler and SDI's Grasp began printing immediately, so if their buffers filled, they simply slowed to printer speed.
Latest comment: 17 August 20112 comments2 people in discussion
The article claims tape was used as a 'spooling' mechanism. While it's true that DOS, OS/MxT, and other operating system variants could output print lines to 'spools' of tape (which we called reels), this was never considered 'spooling' in the sense of the article.
I agree with that. Having been "in the trade" for over forty years I can assure that we NEVER referred to tapes as anything but reels. I guess that someone is trying to support the argument that SPOOL is a bacronym - which it ain't!
I actually worked on an IBM 360 in 1967. At that time, the IBM computer had 512k bytes of core memory and processed jobs. Some of these jobs would require large volumes of output to a printer. Since some jobs would be printer bound and thus waste an extremely valuable asset (IBM 360 was not cheap), the system could be bootstrapped into a different configuration. In this setup, a partition in memory was established, (I think 8k bytes), which automatically printed print files from whatever tape was loaded onto a reserved tape drive (usually the last in a bank of tape drives and only available to the print partition). This set up, known as SPOOL (Simulatenous Peripheral Operation Off Line) was seen as a major advance at the time. There was no queuing. The order of tapes loaded was the order of the print. Very simple and very ingenious at the time. —Preceding unsigned comment added by 124.176.228.91 (talk) 00:59, 4 June 2010 (UTC)Reply
First, IBM had SPOOL software well before the S/360, e.g., "SPOOL System", 7070-IO-076 (see Template:Cite manual)
(queue/fifo) buffering vs. spooling: how wrong definitions manifest in contradiction.
Latest comment: 8 October 20103 comments3 people in discussion
In the first paragraph I read: Template:Main other
The 2nd tells the opposite:
Template:Main other
In the 3rd, it calls it a buffer again:
Template:Main other
Finally, I come to clarify this in the discussion page and see the numerous question if the spooler is a buffer after all responed by assurances that it is not a buffer. Am I crazy or this article is total absurd indeed? Everything gets fixed if we correct only the 2nd paragraph. It is really wrong because it denies the spooler being a buffer and, at the same time describes it as "a device writes data faster than a target device can read it, allowing the slower device to work at its own pace without requiring processing to wait for it to catch up.", which is definitely a purpose of a buffer. By definition, a fast storage device used to mediate the producer-consumer is a buffer. Furthermore, if the "Data is only modified through addition or deletion at the ends of the area, i.e., there is no random access or editing" we have a queue buffering, aka FIFO. --Javalenok (talk) 22:06, 11 June 2009 (UTC)Reply
The original SPOOL software was mostly card-to-tape, tape-to-card and tape-to-printer; such operations as card-to-card, while supported, were less useful. Support for disk came fairly quickly, and Direct Coupled System required an IBM 1301 disk drive between an IBM 7040 and an IBM 7090, or between a 7044 and a 7094.
I've never seen the word spool used to refer to digital tape; it's always been cartridge, reel, tape or volume. I have, however, seen the term spooler used for hardware on a tape drive.
All of the spooling software that I've seen dealt with complete files; it didn't share files with another program as buffers. All of the spooling software that I've seen using disk as an intermediary has had priority queueing. Shmuel (Seymour J.) Metz Username:Chatul (talk) 20:09, 11 June 2010 (UTC)Reply
Minor note: Neither Shadow nor Shadow II were spooling systems. It was a TP Monitor, a CICS competitor. Fido was the spooling system from the same fertile mind - Simon Wheaton Smith, if I remember rightly, and they were built when he was at Thomas Cook's the travel agents. Personal knowledge - I worked on Shadow in London from 1976 on. —Preceding unsigned comment added by 67.188.231.59 (talk) 22:46, 8 October 2010 (UTC)Reply
I distinctly remember being told that SPOOL stands for Simulated Peripheral Operations On Line. The peripheral operations are simulated.Lestrade (talk) 03:26, 12 May 2012 (UTC)LestradeReply
Makes no sense. What two operations are simultaneous? However, it makes sense to say that peripheral operations are simulated as though they were online. The person who told me was a lecturer for a company that sold EDOS.Lestrade (talk) 00:22, 23 May 2012 (UTC)LestradeReply
Yes, it does make sense, especially if you were there, using the hardware and software. Simultaneous refers to the running of more than one batch job at a time. If you wanted to, say, run PAYROLL and GLEDGER without a spooling subsystem, you had to have a printer (peripheral) available for each. After HASP was introduced, the jobs could run at the same time, "printing" to a spool file, even if you only had one physical printer. You could then print the spooled output when convenient. The person who's telling you this installed and operated IBM operating systems ranging from MVT to MVS/ESA, and remembers the annoyance of life without Simultaneous Peripheral Operation On-Line. — UncleBubba( T@C )05:00, 23 May 2012 (UTC)Reply
Actually, MVT had SPOOL support without ASP or HASP. ASP and HASP automated some of the operation of the computer, avoided some of the overhead of allocating DASD datasets for SPOOL and automatically blocked records even when the user didn't provide an explicit block size. Shmuel (Seymour J.) Metz Username:Chatul (talk) 16:34, 25 May 2012 (UTC)Reply
The SPOOL software for the 7070, 7080, 7090 and related computers allowed for simultaneous card-to-tape, card-to-card, card-to-printer, tape to card and tape to printer operations on the same computer. You were still limited to one batch job at a time in parallel with the SPOOL activity. Shmuel (Seymour J.) Metz Username:Chatul (talk) 16:34, 25 May 2012 (UTC)Reply
Neither the first nor the last time that the cobbler's children went barefoot. IBM manuals are frequently written by people who don't know the history, may not even know the product, and use guesses or urban legnds rather than consulting corporate archives. Shmuel (Seymour J.) Metz Username:Chatul (talk) 17:00, 10 September 2019 (UTC)Reply
Level of detail for references?
Latest comment: 4 January 20131 comment1 person in discussion
I recently reinstated a deleted paragraph relating to SPOOL software doing card-to-tape, tape-to-card, tape-to-printer and tape-to-tape operations. I added a citation of one SPOOL program supporting these operations; I considered adding some IOCS manuals to the references but suspected that it might be TMI. Would those references be appropriate? Shmuel (Seymour J.) Metz Username:Chatul (talk) 22:05, 4 January 2013 (UTC)Reply
Banner pages
Latest comment: 14 January 20141 comment1 person in discussion
Latest comment: 28 April 20163 comments2 people in discussion
I revised the article heavily a couple days ago. I got feedback on the revisions on my user talk page today, which I reproduce here along with my response:
There are several problems with your rewrite of Spooling. My first thought was to revert the edit, but it might be better if you could fix it up. The problems that I noticed were
Spooling does not mediate between the computer and the peripherals. SPOOL is an application that runs on the computer, in parallel with other work.
Media copies on a 1401 were not spooling, they were an alternative to spooling.
Spooling is not just buffering of job output, it is buffering of job input, typically card-to-tape or card-to-disk copying in parallel with execution of earlier jobs.
The term "Simultaneous Peripheral Output On Line" in the IBM program "SPOOL System, 7070-IO-076" goes back to the 1950's. Given that the common term at the time was reel rather than spool, a backronym seems unlikely.
The first sentence of the article does not need to be specific about exactly where the spooler process runs, and I think "mediating between a computer and a slow peripheral" is an accurate description of what spooling does, even if the mediation happens to be done by the computer itself.
I don't have personal experience with, or references for, 1401-era computing; what I wrote is my best guess at a sensible interpretation of the corresponding paragraphs of the old article, which were not terribly clear. I would welcome targeted improvements to that section by people who remember those days and/or can provide references. Having said that, it seems to me you are insisting on a very narrow interpretation of the meaning of the phrase---too narrow for a general audience.
Yes, spooling can be applied to either input or output; however, I think it's important to put the discussion of print spooling (the most common modern application) first, and that is a form of output. Some forms of input spooling appear in the "other applications" section; if you'd like to flesh them out and/or add more that would be fine by me.
In the absence of hard evidence, I think the discussion of the origin of the term is sufficiently hedged both ways as is.
I am not currently persuaded to make any changes based on this feedback. I added a sentence to the article lead-in about input spooling, but beyond that I do not think any changes are necessary. Further discussion should take place here.
The word online is part of the name, so it is relevant where the processing takes place.
If you had no experience or references on the 1401, why did you change the description? Clarifying text is reasonable; changing it based on uninformed guesses is not.
The lede is supposed to introduce the topic. The fact that print spooling is more common belongs in subsequent text, and is not a justification for an incorrect lede.
The term "spool" may originate with the Simultaneous Peripheral Operations On-Line[2] (SPOOL) software; this derivation is uncertain, however. Simultaneous peripheral operations on-line may be a backronym.[3] Another explanation is that it refers to "spools" or reels of magnetic tape."
What this means is that there is doubt. It may originate with the acronym. The acronym may be a backronym. Or the explanation is that it refers to spools of tape (which is why the acronym would be backronymed). These "mays" all indicate possibility not probability. Therefore "may" or "perhaps" is more appropriate than "probably". I stand by my reversion. -- Evertype·✆22:18, 27 September 2020 (UTC)Reply
When there is documentation for the name as Simultaneous Peripheral Operations Online and not a shred of evidence for an earlier origin, then 'probable is appropriate. The speculation that it is a backfronym from spool of tape is implausible on the face of it; the common usage[1] was reel of tape, not spool.
Latest comment: 26 June 20211 comment1 person in discussion
The article now reads:
this terminology [spool] is still found in the documentation for email and Usenet software, even though messages are often delivered immediately nowadays.
Are they? SMTP is still what's used for Internet mail, and it's explicitly a store-and-forward protocol: a mail server receives a message for one or more recipients, and then decides what to do with it, often forwarding it to one or more other mail servers. It may not wait until next night, but I bet most won't attempt to forward the mail until it has taken responsibility for the content. And in the time between taking and forwarding responsibility, the server may be restarted, which means the mail needs to be stored to disk. All that seems like spooling to me.
JöG (talk) 09:31, 26 June 2021 (UTC)Reply
"unit record equipment"
Latest comment: 7 July 20212 comments2 people in discussion
"Because the unit record equipment on IBM mainframes of the early 1960s was so slow, it was common to use a small offline machine such as a 1401 instead of spooling. "
Latest comment: 11 August 20234 comments2 people in discussion
Template:Ping Edit Special:Permalink/1169612951 added the short description "Form of multitasking in computers", overriding Wikidata description "intermediate store of data". I believe that both the new and the default description are too vague, since what characterizes SPOOL is that it is both a limited form of multitasking and processing an intermediate store of data. How about "A limited form of multitasking in computers, for copying an intermediate store of data"?
I edited the description because I do think that "computers doing multitasking" is more generally understandable than something like "intermediate store". To be honest, when I saw the latter one, I even had to think about what the description has to do with the article first.
That the description is not detailed enough, yeah it is a short description. The short descriptions are displayed in the Wikipedia mobile app, see the short description "16th President of the United Stated" in the picture under the Abraham Lincoln title. I don't know if it's a written rule, but the short description generator tool "soft" limits the short description to 40 chars, your suggestion would have 86 chars.
I do think the most important is that one can see in the short description what topic this article belongs to, in this case to computer software. So if you have a better description you are welcome, however, your suggestion does not seem like an improvement to me.
And a tip, avoid using obsolete words like "A" at the beginning, you could also just say "Limited form of ...". This does make the description shorter and more look like a short description instead of a full text representation.
Just saw you have extended your question above. Please add it as a new section next time so that the thread stays clear.
There is no alternative for {{Short description}}. The {{About}} template is to differentiate between articles with the same title and has nothing to do with the short description. From the documentation:
"{{About}} is a commonly used hatnote template on Wikipedia, and should be placed at the top of an article (but following {{Short description}}, if present), linking the reader to other articles with similar titles or concepts that they may have been seeking instead." Killarnee (talk) 11:07, 10 August 2023 (UTC)Reply