Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
IBM System/360 architecture
open-in-new
<h2 id="features">Features</h2> <p>The System/360 architecture provides the following features: </p> <ul><li>16 <a href="/facts/32-bit/TDMVce8s">32-bit</a> general-purpose registers</li> <li>4 64-bit <a href="/facts/IBM_hexadecimal_floating-point/EE3YS5aF">floating-point</a> registers</li> <li>64-bit processor status register (PSW), which includes a 24-bit <a href="/facts/Program_counter/BxqulBRq">instruction address</a></li> <li>24-bit (16 MB) byte-addressable memory space</li> <li><a href="/facts/Big-endian/wbrQnyu3">Big-endian</a> byte/word order</li> <li>A <i>standard instruction set</i>, including fixed-point binary arithmetic and logical instructions, present on all System/360 models (except the <a href="/facts/IBM_System%2f360_Model_20/aDro2eBY">Model 20</a>, see below). <ul><li>A <i>commercial instruction set</i>, adding decimal arithmetic instructions, is optional on some models, as is a <i>scientific instruction set</i>, which adds floating-point instructions. The <i>universal instruction set</i> includes all of the above plus the storage protection instructions and is standard for some models.</li> <li>The <a href="/facts/IBM_System%2f360_Model_44/EJ02nsd1">Model 44</a> provides a few unique instructions for data acquisition and real-time processing and is missing the storage-to-storage instructions. However, IBM offered a '<i>Commercial Instruction Set"</i> feature that ran in bump storage and simulated the missing instructions.</li> <li>The <a href="/facts/IBM_System%2f360_Model_20/aDro2eBY">Model 20</a> offers a stripped-down version of the standard instruction set, limited to eight general registers with halfword (16-bit) instructions only, plus the commercial instruction set, and unique instructions for input/output.</li> <li>The <a href="/facts/IBM_System%2f360_Model_67/0BwJAwRV">Model 67</a> includes some instructions to handle 32-bit addresses and "dynamic address translation", with additional privileged instructions to provide virtual memory.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a></li></ul></li></ul> <h2 id="memory">Memory</h2> <p>Memory (<i>storage</i>) in System/360 is addressed in terms of <a href="/facts/8-bit/2CkhLNoH">8-bit</a> bytes. Various instructions operate on larger units called <i>halfword</i> (2 bytes), <i>fullword</i> (4 bytes), <i>doubleword</i> (8 bytes), <i>quad word</i> (16 bytes) and 2048 byte storage block, specifying the leftmost (lowest address) of the unit. Within a halfword, fullword, doubleword or quadword, low numbered bytes are more significant than high numbered bytes; this is sometimes referred to as <a href="/facts/Big-endian/wbrQnyu3">big-endian</a>. Many uses for these units require aligning them on the corresponding boundaries. Within this article the unqualified term <i>word</i> refers to a <i>fullword</i>. </p><p>The original architecture of System/360 provided for up to 224 = 16,777,216 bytes of memory. The later <a href="/facts/IBM_System%2f360_Model_67/0BwJAwRV">Model 67</a> extended the architecture to allow up to 232 = 4,294,967,296<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> bytes of virtual memory. </p> <h2 id="addressing">Addressing</h2> <p>System/360 uses truncated addressing similar to that of the <a href="/facts/UNIVAC_III/4kM7qbbK">UNIVAC III</a>.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> That means that instructions do not contain complete addresses, but rather specify a base register and a positive offset from the addresses in the base registers. In the case of System/360 the base address is contained in one of 15<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> general registers. In some instructions, for example shifts, the same computations are performed for 32-bit quantities that are not addresses. </p> <h2 id="data-formats">Data formats</h2> <p>The S/360 architecture defines formats for characters, integers, decimal integers and hexadecimal floating point numbers. Character and integer instructions are mandatory, but decimal and floating point instructions are part of the Decimal arithmetic and <a href="/facts/Floating-point_arithmetic/eIckahxe">Floating-point arithmetic</a> features. </p> <ul><li>Characters are stored as 8-bit bytes.</li> <li>Integers are stored as two's complement binary halfword or fullword values.</li> <li><a href="/facts/Packed_decimal/dWTaE7ES">Packed decimal</a> numbers are stored as 1 to 16 8-bit bytes containing an odd number of decimal digits followed by a 4-bit sign. Sign values of hexadecimal A, C, E, and F are positive and sign values of hexadecimal B and D are negative. Digit values of hexadecimal A-F and sign values of 0-9 are invalid, but the PACK and UNPK instructions do not test for validity.</li> <li><a href="/facts/Zoned_decimal/dWTaE7ES">Zoned decimal</a> numbers are stored as 1 to 16 8-bit bytes, each containing a zone in bits 0-3 and a digit in bits 4-7. The zone of the rightmost byte is interpreted as a sign.</li> <li><a href="/facts/IBM_hexadecimal_floating-point/EE3YS5aF">Floating point</a> numbers are only stored as fullword or doubleword values on older models. On the 360/85<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> and 360/195<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> there are also extended precision floating point numbers stored as quadwords. For all three formats, bit 0 is a sign and bits 0-7 are a characteristic (exponent, biased by 64). Bits 8-31 (8-63) are a hexadecimal fraction. For extended precision, the low order doubleword has its own sign and characteristic, which are ignored on input and generated on output.</li></ul> <h2 id="instruction-formats">Instruction formats</h2> <p>Instructions in the S/360 are two, four or six bytes in length, with the opcode in byte 0. Instructions have one of the following formats: </p> <ul><li>RR (two bytes). Generally byte 1 specifies two 4-bit register numbers, but in some cases, e.g., SVC, byte 1 is a single 8-bit immediate field.</li> <li>RS (four bytes). Byte 1 specifies two register numbers; bytes 2-3 specify a base and displacement.</li> <li>RX (four bytes). Bits 0-3 of byte 1 specify either a register number or a modifier; bits 4-7 of byte 1 specify the number of the general register to be used as an index; bytes 2-3 specify a base and displacement.</li> <li>SI (four bytes). Byte 1 specifies an immediate field; bytes 2-3 specify a base and displacement.</li> <li>SS (six bytes). Byte 1 specifies two 4-bit length fields or one 8-bit length field; bytes 2-3 and 4-5 each specify a base and displacement. The encoding of the length fields is length-1.</li></ul> <p>Instructions must be on a two-byte boundary in memory; hence the low-order bit of the instruction address is always 0. </p> <h2 id="program-status-word-psw">Program Status Word (PSW)</h2> <p class="note">Main article: <a href="/facts/Program_Status_Word/ejBFel3W">Program Status Word</a></p> <p>The Program Status Word (PSW)<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a>: 71–72 contains a variety of controls for the currently operating program. The 64-bit PSW describes (among other things) the address of the current instruction being executed, condition code and interrupt masks. </p> PSW format<table><tbody><tr><th>Bits</th><th>Contents</th><th>Explanation</th></tr><tr><td>0-7</td><td>System Mask</td><td>bits 0-5: enable channels 0-5, bit 6: enable all remaining channels,<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a> bit 7: enable External interruptions (timer, interrupt key, and external signal<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a></td></tr><tr><td>8-11</td><td>Protection key</td><td>CPU protection key to compare against storage protection keys</td></tr><tr><td>12</td><td>ASCII mode</td><td>enable ASCII mode for packed decimal instructions, never used by IBM software<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a></td></tr><tr><td>13</td><td>Machine checks</td><td>enable Machine check interruptions</td></tr><tr><td>14</td><td>Wait State</td><td>processor is halted, an interruption, if enabled, will cause the processor to resume executing instructions</td></tr><tr><td>15</td><td>Problem state</td><td>enable to prevent the use of instructions reserved for supervisor state</td></tr><tr><td>16-31</td><td>Interruption Code</td><td>code to indicate the type of interruption, inserted when the PSW is stored, during IPLoad, this is the address of the device from which the program was loaded<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a></td></tr><tr><td>32-33</td><td>Instruction Length Code</td><td>length in halfwords or 0 if unavailable</td></tr><tr><td>34-35</td><td>Condition Code</td><td>see individual instructions for encoding</td></tr><tr><td>36-39</td><td>Program Mask</td><td>bit 36: enable fixed-point overflow, bit 37: decimal overflow, bit 38: exponent underflow, bit 39: significance<a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a></td></tr><tr><td>40-63</td><td>Instruction Address</td><td>address of next instruction, except for a program interruptions with ILC 0</td></tr></tbody></table> <p>Load Program Status Word (LPSW) is a privileged <a href="/facts/Instruction_(computer_science)/8p8vwUeE">instruction</a> that loads the Program Status Word (PSW), including the program mode, protection key, and the address of the next instruction to be executed. LPSW is most often used to "return" from an interruption by loading the "old" PSW which is associated with the interruption class. Other privileged instructions (e.g., SSM, STNSM, STOSM, SPKA, etcetera) are available for manipulating subsets of the PSW without causing an interruption or loading a PSW; and one non-privileged instruction (SPM) is available for manipulating the program mask. </p> <h2 id="interruption-system">Interruption system</h2> <p>The architecture<a class="footnote-ref" id="fnref:16" href="#fn:16"><sup>16</sup></a>: 77–83 defines 5 classes of <a href="/facts/Interrupt/Mm6C4rpc">interruption</a>. An interruption is a mechanism for automatically changing the program state; it is used for both synchronous<a class="footnote-ref" id="fnref:17" href="#fn:17"><sup>17</sup></a> and <a href="/facts/Asynchrony_(computing)/1cwyNFMu">asynchronous</a> events. </p> <table><tbody><tr><th rowspan="2">Interruption class</th><th colspan="2">Old PSW</th><th colspan="2">New PSW</th><th rowspan="2">Priority</th></tr><tr><th>hex</th><th>dec</th><th>hex</th><th>dec</th></tr><tr><td>Input/Output<a class="footnote-ref" id="fnref:18" href="#fn:18"><sup>18</sup></a></td><td>38</td><td>56</td><td>78</td><td>120</td><td>4</td></tr><tr><td>Program<a class="footnote-ref" id="fnref:19" href="#fn:19"><sup>19</sup></a></td><td>28</td><td>40</td><td>68</td><td>104</td><td>2</td></tr><tr><td>Supervisor Call<a class="footnote-ref" id="fnref:20" href="#fn:20"><sup>20</sup></a></td><td>20</td><td>32</td><td>60</td><td>96</td><td>2</td></tr><tr><td>External<a class="footnote-ref" id="fnref:21" href="#fn:21"><sup>21</sup></a></td><td>18</td><td>24</td><td>58</td><td>88</td><td>3</td></tr><tr><td>Machine Check<a class="footnote-ref" id="fnref:22" href="#fn:22"><sup>22</sup></a></td><td>30</td><td>48</td><td>70</td><td>112</td><td>1</td></tr></tbody></table> <p>There are two storage fields assigned to each class of interruption on the S/360; an old PSW double-word and a new PSW double-word. The processor stores the PSW, with an interruption code inserted, into the old PSW location and then loads the PSW from the new PSW location. This generally replaces the instruction address, thereby effecting a branch, and (optionally) sets and/or resets other fields within the PSW, thereby effecting a mode change. </p><p>The S/360 architecture defines a priority to each interruption class, but it is only relevant when two interruptions occur simultaneously; an interruption routine can be interrupted by any other enabled interruption, including another occurrence of the initial interruption. For this reason, it is normal practice to specify all of the mask bits, with the exception of machine-check mask bit, as 0 for the "first-level" interruption handlers. "Second-level" interruption handlers are generally designed for stacked interruptions (multiple occurrences of interruptions of the same interruption class). </p> <h3>Input/Output interruption</h3> <p>An I/O interruption<a class="footnote-ref" id="fnref:23" href="#fn:23"><sup>23</sup></a> occurs at the completion of a channel program, after fetching a CCW with the PCI bit set and also for <a href="/facts/Asynchrony_(computing)/1cwyNFMu">asynchronous</a> events detected by the device, control unit or channel, e.g., completion of a mechanical movement. The system stores the device address into the interruption code and stores channel status into the CSW at location 64 ('40'X). </p> <h3>Program interruption</h3> <p>A Program interruption<a class="footnote-ref" id="fnref:24" href="#fn:24"><sup>24</sup></a>: 16, 79–80.1 occurs when an instruction encounters one<a class="footnote-ref" id="fnref:25" href="#fn:25"><sup>25</sup></a> of 15<a class="footnote-ref" id="fnref:26" href="#fn:26"><sup>26</sup></a> exceptions; however, if the Program Mask bit corresponding to an exception is 0 then there is no interruption for that exception. On 360/65,<a class="footnote-ref" id="fnref:27" href="#fn:27"><sup>27</sup></a>: 12 360/67<a class="footnote-ref" id="fnref:28" href="#fn:28"><sup>28</sup></a>: 46 and 360/85<a class="footnote-ref" id="fnref:29" href="#fn:29"><sup>29</sup></a>: 12 the Protection Exception and Addressing Exception interruptions can be imprecise, in which case they store an Instruction Length Code of 0. The Interruption code may be any of </p> Interruption codes for Program interruptionsold PSW bits 26-31<table><tbody><tr><th>hexbits 26-31</th><th>Dec</th><th>Exception</th></tr><tr><td>0</td><td>0</td><td><p>Imprecise interruption<a class="footnote-ref" id="fnref:30" href="#fn:30"><sup>30</sup></a> on 360/91,<a class="footnote-ref" id="fnref:31" href="#fn:31"><sup>31</sup></a>: 15 360/95 or 360/195<a class="footnote-ref" id="fnref:32" href="#fn:32"><sup>32</sup></a>: 14 </p>Old PSW bits for multiple imprecise interruption codes<table><tbody><tr><th>bit</th><th>Exception</th></tr><tr><td>16</td><td>Protection</td></tr><tr><td>17</td><td>Addressing</td></tr><tr><td>18</td><td>Specification<a class="footnote-ref" id="fnref:33" href="#fn:33"><sup>33</sup></a></td></tr><tr><td>19</td><td>Data</td></tr><tr><td>20</td><td>Fixed-Point Overflow</td></tr><tr><td>21</td><td>Fixed-Point Divide</td></tr><tr><td>22</td><td>Exponent Overflow</td></tr><tr><td>23</td><td>Exponent Underflow</td></tr><tr><td>24</td><td>Significance</td></tr><tr><td>25</td><td>Floating-Point Divide</td></tr><tr><td>26</td><td>Decimal Overflow<a class="footnote-ref" id="fnref:34" href="#fn:34"><sup>34</sup></a></td></tr><tr><td>27</td><td>Decimal Divide<a class="footnote-ref" id="fnref:35" href="#fn:35"><sup>35</sup></a></td></tr></tbody></table></td></tr><tr><td>1</td><td>1</td><td>Operation<a class="footnote-ref" id="fnref:36" href="#fn:36"><sup>36</sup></a></td></tr><tr><td>2</td><td>2</td><td>Privileged operation<a class="footnote-ref" id="fnref:37" href="#fn:37"><sup>37</sup></a></td></tr><tr><td>3</td><td>3</td><td>Execute<a class="footnote-ref" id="fnref:38" href="#fn:38"><sup>38</sup></a></td></tr><tr><td>4</td><td>4</td><td>Protection<a class="footnote-ref" id="fnref:39" href="#fn:39"><sup>39</sup></a></td></tr><tr><td>5</td><td>5</td><td>Addressing<a class="footnote-ref" id="fnref:40" href="#fn:40"><sup>40</sup></a></td></tr><tr><td>6</td><td>6</td><td>Specification<a class="footnote-ref" id="fnref:41" href="#fn:41"><sup>41</sup></a></td></tr><tr><td>7</td><td>7</td><td>Data<a class="footnote-ref" id="fnref:42" href="#fn:42"><sup>42</sup></a></td></tr><tr><td>8</td><td>8</td><td>Fixed-point overflow<a class="footnote-ref" id="fnref:43" href="#fn:43"><sup>43</sup></a></td></tr><tr><td>9</td><td>9</td><td>Fixed-point divide<a class="footnote-ref" id="fnref:44" href="#fn:44"><sup>44</sup></a></td></tr><tr><td>A</td><td>10</td><td>Decimal overflow<a class="footnote-ref" id="fnref:45" href="#fn:45"><sup>45</sup></a></td></tr><tr><td>B</td><td>11</td><td>Decimal divide<a class="footnote-ref" id="fnref:46" href="#fn:46"><sup>46</sup></a></td></tr><tr><td>C</td><td>12</td><td>Exponent overflow<a class="footnote-ref" id="fnref:47" href="#fn:47"><sup>47</sup></a></td></tr><tr><td>D</td><td>13</td><td>Exponent underflow<a class="footnote-ref" id="fnref:48" href="#fn:48"><sup>48</sup></a></td></tr><tr><td>E</td><td>14</td><td>Significance<a class="footnote-ref" id="fnref:49" href="#fn:49"><sup>49</sup></a></td></tr><tr><td>F</td><td>15</td><td>Floating-point divide<a class="footnote-ref" id="fnref:50" href="#fn:50"><sup>50</sup></a></td></tr><tr><td>10</td><td>16</td><td><p>Segment Translation<a class="footnote-ref" id="fnref:51" href="#fn:51"><sup>51</sup></a>: 17 <a class="footnote-ref" id="fnref:52" href="#fn:52"><sup>52</sup></a></p></td></tr><tr><td>11</td><td>17</td><td><p>Page Translation<a class="footnote-ref" id="fnref:53" href="#fn:53"><sup>53</sup></a>: 17 <a class="footnote-ref" id="fnref:54" href="#fn:54"><sup>54</sup></a></p></td></tr><tr><td>12</td><td>18</td><td><p>SSM Exception<a class="footnote-ref" id="fnref:55" href="#fn:55"><sup>55</sup></a><a class="footnote-ref" id="fnref:56" href="#fn:56"><sup>56</sup></a></p></td></tr></tbody></table> <ul><li>An operation exception<a class="footnote-ref" id="fnref:57" href="#fn:57"><sup>57</sup></a> is recognized when a program attempts to execute an instruction with an opcode that the computer does not implement. In particular, an operation exception is recognized when a program is written for an optional feature, e.g., floating point, that is not installed.</li> <li>A privileged operation exception<a class="footnote-ref" id="fnref:58" href="#fn:58"><sup>58</sup></a> is recognized when a program attempts to execute a privileged instruction when the problem state bit in the PSW is 1.</li> <li>An execute exception<a class="footnote-ref" id="fnref:59" href="#fn:59"><sup>59</sup></a> is recognized when the operand of an <a href="/facts/Execute_instruction/ssyBRmrU">EXECUTE instruction (EX)</a> is another EXECUTE instruction.</li> <li>A protection exception<a class="footnote-ref" id="fnref:60" href="#fn:60"><sup>60</sup></a> is recognized when a program attempts to store into a location whose storage protect key does not match<a class="footnote-ref" id="fnref:61" href="#fn:61"><sup>61</sup></a> the PSW key, or to fetch from a fetch protected location whose storage protect key does not match the PSW key.</li> <li>An addressing exception<a class="footnote-ref" id="fnref:62" href="#fn:62"><sup>62</sup></a> is recognized when a program attempts to access a storage location that is not currently available. This normally occurs with an address beyond the capacity of the machine, but it may also occur on machines that allow blocks of storage to be taken offline.</li> <li>A specification exception<a class="footnote-ref" id="fnref:63" href="#fn:63"><sup>63</sup></a> is recognized when an instruction has a length or register field with values not permitted by the operation, or when it has an operand address that does not satisfy the alignment requirements of the opcode, e.g., a LH instruction with an odd operand address on a machine without the byte alignment feature.</li> <li>A data exception<a class="footnote-ref" id="fnref:64" href="#fn:64"><sup>64</sup></a> is recognized when a decimal instruction specifies invalid operands, e.g., invalid data, invalid overlap.</li> <li>A fixed-point overflow exception<a class="footnote-ref" id="fnref:65" href="#fn:65"><sup>65</sup></a> is recognized when significant bits are lost in a fixed point arithmetic or shift instruction, other than divide.</li> <li>A fixed-point divide exception<a class="footnote-ref" id="fnref:66" href="#fn:66"><sup>66</sup></a> is recognized when significant bits are lost in a fixed point divide or Convert to Binary instruction.</li> <li>A decimal overflow exception<a class="footnote-ref" id="fnref:67" href="#fn:67"><sup>67</sup></a> is recognized when significant digits are lost in a decimal arithmetic instruction, other than divide.</li> <li>A decimal divide exception<a class="footnote-ref" id="fnref:68" href="#fn:68"><sup>68</sup></a> is recognized when significant bits are lost in a decimal divide instruction. The destination is not altered.</li> <li>An exponent overflow exception<a class="footnote-ref" id="fnref:69" href="#fn:69"><sup>69</sup></a> is recognized when the characteristic in a floating-point arithmetic operation exceeds 127 and the fraction is not zero.</li> <li>An exponent underflow exception<a class="footnote-ref" id="fnref:70" href="#fn:70"><sup>70</sup></a> is recognized when the characteristic in a floating-point arithmetic operation is negative and the fraction is not zero.</li> <li>A significance exception<a class="footnote-ref" id="fnref:71" href="#fn:71"><sup>71</sup></a> is recognized when the fraction in a floating-point add or subtract operation is zero.</li> <li>A floating-point divide exception<a class="footnote-ref" id="fnref:72" href="#fn:72"><sup>72</sup></a> is recognized when the fraction in the divisor of a floating-point divide operation is zero.</li></ul> <h3>Supervisor Call interruption</h3> <p>A Supervisor Call interruption<a class="footnote-ref" id="fnref:73" href="#fn:73"><sup>73</sup></a> occurs as the result of a <a href="/facts/Supervisor_Call_instruction/cspplehM">Supervisor Call instruction</a>; the system stores bits 8-15 of the SVC instruction as the Interruption Code. </p> <h3>External interruption</h3> <p>An External<a class="footnote-ref" id="fnref:74" href="#fn:74"><sup>74</sup></a><a class="footnote-ref" id="fnref:75" href="#fn:75"><sup>75</sup></a> interruption occurs as the result of certain asynchronous events. Bits 16-24 of the External Old PSW are set to 0 and one or more of bits 24-31 is set to 1 </p> Interruption codes for External interruptions<table><tbody><tr><th>PSW bit</th><th>Type of external interruption</th></tr><tr><td><p>24</p></td><td>Timer</td></tr><tr><td><p>25</p></td><td>Interrupt key</td></tr><tr><td><p>26</p></td><td>External signal 2Malfunction alert on 360/65<a class="footnote-ref" id="fnref:76" href="#fn:76"><sup>76</sup></a> in Multisystem mode</td></tr><tr><td><p>27</p></td><td>External signal 3System Call on 360/65<a class="footnote-ref" id="fnref:77" href="#fn:77"><sup>77</sup></a> in Multisystem mode</td></tr><tr><td><p>28</p></td><td>External signal 4</td></tr><tr><td><p>29</p></td><td>External signal 5</td></tr><tr><td><p>30</p></td><td>External signal 6</td></tr><tr><td><p>31</p></td><td>External signal 7</td></tr></tbody></table> <h3>Machine Check interruption</h3> <p>A Machine Check interruption<a class="footnote-ref" id="fnref:78" href="#fn:78"><sup>78</sup></a> occurs to report unusual conditions associated with the channel or CPU that cannot be reported by another class of interruption. The most important class of conditions causing a Machine Check is a hardware error such as a parity error found in registers or storage, but some models may use it to report less serious conditions. Both the interruption code and the data stored in the scanout area at '80'x (128 decimal) are model dependent. </p> <h2 id="inputoutput">Input/Output</h2> <p class="note">Further information on physical interface: <a href="/facts/Bus_and_Tag/gbCB2TyR">Bus and Tag</a></p> <p>This article describes I/O from the CPU perspective. It does not discuss the channel cable or connectors, which have a <a href="/facts/Bus_and_Tag/gbCB2TyR">separate article</a>; there is a summary <a href="/facts/IBM_System%2f360/7znvpy4K">elsewhere</a> and details can be found in the IBM literature<a class="footnote-ref" id="fnref:79" href="#fn:79"><sup>79</sup></a> and in FIPS PUB 60-2.<a class="footnote-ref" id="fnref:80" href="#fn:80"><sup>80</sup></a> </p><p>I/O is carried out by a conceptually separate processor called a channel. Channels have their own instruction set, and access memory independently of the program running on the CPU. On the smaller models (through <a href="/facts/IBM_System%2f360_Model_50/GdQ5YhT2">360/50</a>) a single microcode engine runs both the CPU program and the channel program. On the larger models the channels are in separate cabinets and have their own interfaces to memory. A channel may contain multiple subchannels, each containing the status of an individual channel program. A subchannel associated with multiple devices that cannot concurrently have channel programs is referred to as shared; a subchannel representing a single device is referred to as unshared. </p><p>There are three types of channels on the S/360: </p> <ul><li>A byte multiplexer channel is capable of executing multiple CCWs concurrently; it is normally used to attach slow devices such as card readers and telecommunications lines. A byte multiplexer channel could have a number of selector subchannels, each with only a single subchannel, which behave like low-speed selector channels.</li> <li>A selector channel has only a single subchannel, and hence is only capable of executing one channel command at a time. It is normally used to attach fast devices that are not capable of exploiting a block multiplexer channel to suspend the connection, such as magnetic tape drives.</li> <li>A block multiplexer channel is capable of concurrently running multiple channel programs, but only one at a time can be active. The control unit can request suspension at the end of a channel command and can later request resumption. This is intended for devices in which there is a mechanical delay after completion of data transfer, e.g., for seeks on moving-head DASD. The block multiplexer channel was a late addition to the System/360 architecture; early machines had only byte multiplexer channels and selector channels. The block multiplexer channel is an optional feature only on the models 85 and 195. The block multiplexor channel is also available on the later <a href="/facts/IBM_System%2f370/TRo1jaFw">System/370</a> computers.</li></ul> <p>Conceptually peripheral equipment is attached to a S/360 through <i>control units</i>, which in turn are attached through channels. However, the architecture does not require that control units be physically distinct, and in practice they are sometimes integrated with the devices that they control. Similarly, the architecture does not require the channels to be physically distinct from the processor, and the smaller S/360 models (through 360/50) have integrated channels that <a href="/facts/Cycle_stealing/71Y6gBWX">steal cycles</a> from the processor. </p><p>Peripheral devices are addressed with 16-bit<a class="footnote-ref" id="fnref:81" href="#fn:81"><sup>81</sup></a> addresses.,<a class="footnote-ref" id="fnref:82" href="#fn:82"><sup>82</sup></a>: 89 referred to as <i>cua</i> or <i>cuu</i>; this article will use the term <i>cuu</i>. The high 8 bits identify a channel, numbered from 0 to 6,<a class="footnote-ref" id="fnref:83" href="#fn:83"><sup>83</sup></a> while the low 8 bits identify a device on that channel. A device may have multiple <i>cuu</i> addresses. </p><p>Control units are assigned an address "capture" range. For example, a CU might be assigned range 20-2F or 40-7F. The purpose of this is to assist with the connection and prioritization of multiple control units to a channel. For example, a channel might have three disk control units at 20-2F, 50-5F, and 80-8F. Not all of the captured addresses need to have an assigned physical device. Each control unit is also marked as High or Low priority on the channel. </p><p>Device selection progresses from the channel to each control unit in the order they are physically attached to their channel. At the end of the chain the selection process continues in reverse back towards the channel. If the selection returns to the channel then no control unit accepted the command and SIO returns Condition Code 3. Control units marked as High Priority check the outbound CUU to be within their range. If so, then the I/O is processed. If not, then the selection is passed to the next outbound CU. Control units marked as Low Priority check for inbound (returning) CUU to be within their range. If so, then the I/O is processed. If not, then the selection is passed to the next inbound CU (or the channel). The connection of three controls unit to a channel might be physically -A-B-C and, if all are marked as High then the priority would be ABC. If all are marked low then the priority would be CBA. If B was marked High and AC low then the order would be BCA. Extending this line of reasoning then the first of N controllers would be priority 1 (High) or 2N-1 (Low), the second priority 2 or 2N-2, the third priority 3 or 2N-3, etc. The last physically attached would always be priority N. </p><p>There are three storage fields reserved for I/O; a double word I/O old PSW, a doubleword I/O new PSW and a fullword <i>Channel Address Word</i> (CAW). Performing an I/O normally requires the following: </p> <ul><li>initializing the CAW with the storage key and the address of the first CCW</li> <li>issuing a <i>Start I/O</i> (SIO) instruction that specifies the <i>cuu</i> for the operation</li> <li>waiting<a class="footnote-ref" id="fnref:84" href="#fn:84"><sup>84</sup></a> for an I/O interruption</li> <li>handling any unusual conditions indicated in the <i>Channel Status Word</i> (CSW)</li></ul> <p>A channel program consists of a sequence of <i>Channel Control Words</i> (CCWs) chained together (see below.) Normally the channel fetches CCWs from consecutive doublewords, but a control unit can direct the channel to skip a CCW and a <i>Transfer In Channel</i> (TIC) CCW can direct the channel to start fetching CCWs from a new location. </p><p>There are several defined ways for a channel command to complete. Some of these allow the channel to continue fetching CCWs, while others terminate the channel program. In general, if the CCW does not have the chain-command bit set and is not a TIC, then the channel will terminate the I/O operation and cause an I/O interruption when the command completes. Certain status bits from the control unit suppress chaining. </p><p>The most common ways for a command to complete are for the count to be exhausted when chain-data is not set and for the control unit to signal that no more data transfers should be made. If Suppress-Length-Indication (SLI) is not set and one of those occurs without the other, chaining is not allowed. The most common situations that suppress chaining are unit-exception and unit-check. However, the combination of unit-check and status-modifier does not suppress chaining; rather, it causes the channel to do a command retry, reprocessing the same CCW. </p><p>In addition to the interruption signal sent to the CPU when an I/O operation is complete, a channel can also send a Program-Controlled interruption (PCI) to the CPU while the channel program is running, without terminating the operation, and a delayed device-end interruption after the I/O completion interruption. </p> <h3>Channel status</h3> <p>These conditions are detected by the channel and indicated in the CSW.<a class="footnote-ref" id="fnref:85" href="#fn:85"><sup>85</sup></a> </p> <ul><li>Program-controlled interruption<a class="footnote-ref" id="fnref:86" href="#fn:86"><sup>86</sup></a> indicates that the channel has fetched a CCW with the PCI bit set. The channel continues processing; this interruption simply informs the CPU of the channel's progress. An example of the use of Program-controlled interruption is in the "Program Fetch" function of Contents Supervision, whereby the control program is notified that a Control/Relocation Record has been read. To ensure that this record has been completely read into main storage, a "disabled bit spin", one of the few which remains in the control program, is initiated. Satisfaction of the spin indicates that the Control/Relocation Record is completely in main storage and the immediately preceding Text Record may be relocated. After relocation, a NOP CCW is changed to a TIC and the channel program continues. In this way, an entire load module may be read and relocated while utilizing only one <a href="/facts/EXCP/7d5dr94v">EXCP</a>, and possibly only one revolution of the disk drive. PCI also has applications in teleprocessing access method buffer management.</li> <li>Incorrect length<a class="footnote-ref" id="fnref:87" href="#fn:87"><sup>87</sup></a> indicates that the data transfer for a command completed before the Count was exhausted. This indication is suppressed if the Suppress-Length-Indication bit in the CCW is set.</li> <li>Program check<a class="footnote-ref" id="fnref:88" href="#fn:88"><sup>88</sup></a> indicates one of the following errors <ul><li>Nonzero bits where zeros are required</li> <li>An invalid data or CCW address</li> <li>The CAW or a TIC refers to a TIC</li></ul></li> <li>Protection check<a class="footnote-ref" id="fnref:89" href="#fn:89"><sup>89</sup></a> indicates that the protection key in the CAW is non-zero and does not match the storage protection key.</li> <li>Channel data check<a class="footnote-ref" id="fnref:90" href="#fn:90"><sup>90</sup></a> indicates a parity error during a data transfer.</li> <li>Channel control check<a class="footnote-ref" id="fnref:91" href="#fn:91"><sup>91</sup></a> indicates a channel malfunction other than Channel data check or Interface control check.</li> <li>Interface control check<a class="footnote-ref" id="fnref:92" href="#fn:92"><sup>92</sup></a> indicates an invalid signal in the channel to control unit interface.</li> <li>Chaining check<a class="footnote-ref" id="fnref:93" href="#fn:93"><sup>93</sup></a> indicates lost data during data chaining.</li></ul> <h3>Unit status</h3> <p>These conditions are presented to the channel by the control unit or device.<a class="footnote-ref" id="fnref:94" href="#fn:94"><sup>94</sup></a> In some cases they are handled by the channel and in other cases they are indicated in the CSW. There is no distinction between conditions detected by the control unit and conditions detected by the device. </p> <ul><li>Attention<a class="footnote-ref" id="fnref:95" href="#fn:95"><sup>95</sup></a> indicates an unusual condition not associated with an ongoing channel program. It often indicates some sort of operator action like requesting input, in which case the CPU would respond by issuing a read-type command, most often a sense command (04h) from which additional information could be deduced. Attention is a special condition, and requires specific operating system support, and for which the operating system has a special attention table<a class="footnote-ref" id="fnref:96" href="#fn:96"><sup>96</sup></a> with a necessarily limited number of entries.</li> <li>Status modifier<a class="footnote-ref" id="fnref:97" href="#fn:97"><sup>97</sup></a> (SM) indicates one of three unusual conditions <ul><li>A Test I/O instruction was issued to a device that does not support it.</li> <li>A Busy status refers to the control unit rather than to the device.</li> <li>A device has detected a condition that requires skipping a CCW. A CCW with a command for which Status Modifier is possible will normally specify command chaining, in which case the SM is processed by the channel and does not cause an interruption.</li></ul></li></ul> A typical channel program where SM occurs is ... Search Id Equal TIC *-8 Read Data where the TIC causes the channel to refetch the search until the device indicates a successful search by raising SM. <ul><li>Control unit end<a class="footnote-ref" id="fnref:98" href="#fn:98"><sup>98</sup></a> indicates that a previous control unit busy status has been cleared.</li> <li>Busy<a class="footnote-ref" id="fnref:99" href="#fn:99"><sup>99</sup></a> indicates that a device (SM=0) or a control unit (SM=1) is busy.</li> <li>Channel end<a class="footnote-ref" id="fnref:100" href="#fn:100"><sup>100</sup></a> indicates that the device has completed the data transfer for a channel command. There may also be an Incorrect length indication if the Count field of the CCW is exhausted, depending on the value of the Suppress-Length-Indication bit.</li> <li>Device end<a class="footnote-ref" id="fnref:101" href="#fn:101"><sup>101</sup></a> indicates that the device has completed an operation and is ready to accept another. DE may be signalled concurrently with CE or may be delayed.</li> <li>Unit check<a class="footnote-ref" id="fnref:102" href="#fn:102"><sup>102</sup></a> indicates that the device or control unit has detected an unusual conditions and that details may be obtained by issuing a Sense command.</li> <li>Unit exception<a class="footnote-ref" id="fnref:103" href="#fn:103"><sup>103</sup></a> indicates that the device has detected an unusual condition, e.g., end of file.</li></ul> <h3>Channel Address Word</h3> <p>The fullword <i>Channel Address Word</i><a class="footnote-ref" id="fnref:104" href="#fn:104"><sup>104</sup></a>: 99 (CAW) contains a 4-bit storage protection key and a 24-bit address of the channel program to be started. </p> <h3>Channel Command Word</h3> <p>A <i>Channel Command Word</i> is a doubleword containing the following: </p> <ul><li>an 8-bit channel Command Code<a class="footnote-ref" id="fnref:105" href="#fn:105"><sup>105</sup></a></li> <li>a 24-bit address<a class="footnote-ref" id="fnref:106" href="#fn:106"><sup>106</sup></a></li> <li>a 5-bit flag field<a class="footnote-ref" id="fnref:107" href="#fn:107"><sup>107</sup></a></li> <li>an unsigned halfword Count field<a class="footnote-ref" id="fnref:108" href="#fn:108"><sup>108</sup></a></li></ul> <h4>CCW Command codes</h4> <p>The low order 2 or 4 bits determine the six types of operations that the channel performs;.<a class="footnote-ref" id="fnref:109" href="#fn:109"><sup>109</sup></a>: 100, 105 The encoding is </p> CCW Command codes<table><tbody><tr><th>bits</th><th>Command</th></tr><tr><td>**** 0000</td><td>Invalid in a CCW, simulated by the processor's Test I/O (TIO) instruction</td></tr><tr><td>MMMM 0100</td><td>Sense<a class="footnote-ref" id="fnref:110" href="#fn:110"><sup>110</sup></a></td></tr><tr><td>**** 1000</td><td>Transfer in Channel (TIC)<a class="footnote-ref" id="fnref:111" href="#fn:111"><sup>111</sup></a></td></tr><tr><td>MMMM 1100</td><td>Read Backward<a class="footnote-ref" id="fnref:112" href="#fn:112"><sup>112</sup></a></td></tr><tr><td>MMMM MM01</td><td>Write<a class="footnote-ref" id="fnref:113" href="#fn:113"><sup>113</sup></a></td></tr><tr><td>MMMM MM10</td><td>Read<a class="footnote-ref" id="fnref:114" href="#fn:114"><sup>114</sup></a></td></tr><tr><td>MMMM MM11</td><td>Control<a class="footnote-ref" id="fnref:115" href="#fn:115"><sup>115</sup></a></td></tr></tbody></table> <p>The meaning of the high order six or four bits, the modifier bits, M in the table above, depends upon the type of I/O device attached, see e.g., <a href="/facts/Direct-access_storage_device/dr0tg5Hl">DASD</a> <a href="/facts/Count_key_data/Gxbr1GwB">CKD CCWs</a>. All eight bits are sent to and interpreted in the associated control unit (or its functional equivalent). </p><p>Control is used to cause a state change in a device or control unit, often associated with mechanical motion, e.g., rewind, seek. </p><p>Sense is used to read data describing the status of the device. The most important case is that when a command terminates with unit check, the specific cause can only be determined by doing a Sense and examining the data returned. A Sense command with the modifier bits all zero is always valid. </p><p>A noteworthy deviation from the architecture is that DASD use Sense command codes for Reserve and Release, instead of using Control. </p> <h4>CCW flags</h4> <p>The flags in a CCW affect how it executes and terminates. </p> CCW flags<table><tbody><tr><th>bit</th><th></th><th>flag</th><th>effect</th></tr><tr><td>32</td><td>CD</td><td>Chain-Data</td><td>Continue operation using the storage area defined by the next CCW.<a class="footnote-ref" id="fnref:116" href="#fn:116"><sup>116</sup></a></td></tr><tr><td>33</td><td>CC</td><td>Chain-Command</td><td>Continue with the Command in the next CCW.<a class="footnote-ref" id="fnref:117" href="#fn:117"><sup>117</sup></a></td></tr><tr><td>34</td><td>SLI<a class="footnote-ref" id="fnref:118" href="#fn:118"><sup>118</sup></a></td><td>Suppress-Length-Indication</td><td>Continue channel program after count mis-match.<a class="footnote-ref" id="fnref:119" href="#fn:119"><sup>119</sup></a></td></tr><tr><td>35</td><td>SKIP</td><td>Skip</td><td>Do not read from or write into storage.<a class="footnote-ref" id="fnref:120" href="#fn:120"><sup>120</sup></a></td></tr><tr><td>36</td><td>PCI</td><td>Program-Controlled-Interruption</td><td>Request interruption when fetching CCW.<a class="footnote-ref" id="fnref:121" href="#fn:121"><sup>121</sup></a></td></tr></tbody></table> <h3>Channel Status Word</h3> <p>The <i>Channel Status Word</i> (CSW)<a class="footnote-ref" id="fnref:122" href="#fn:122"><sup>122</sup></a>: 113–121 provides data associated with an I/O interruption. </p> CSW format<table><tbody><tr><th>bits</th><th>field</th></tr><tr><td>0-3</td><td>Key<a class="footnote-ref" id="fnref:123" href="#fn:123"><sup>123</sup></a></td></tr><tr><td>4-7</td><td>0000</td></tr><tr><td>8-31</td><td>Command Address<a class="footnote-ref" id="fnref:124" href="#fn:124"><sup>124</sup></a></td></tr><tr><td>32-47</td><td>Status<a class="footnote-ref" id="fnref:125" href="#fn:125"><sup>125</sup></a></td></tr><tr><td>32-39</td><td>Unit Status Conditions<a class="footnote-ref" id="fnref:126" href="#fn:126"><sup>126</sup></a>Detected by the device or control unit</td></tr><tr><td>32</td><td>Attention<a class="footnote-ref" id="fnref:127" href="#fn:127"><sup>127</sup></a></td></tr><tr><td>33</td><td>Status modifier<a class="footnote-ref" id="fnref:128" href="#fn:128"><sup>128</sup></a></td></tr><tr><td>34</td><td>Control unit end<a class="footnote-ref" id="fnref:129" href="#fn:129"><sup>129</sup></a></td></tr><tr><td>35</td><td>Busy<a class="footnote-ref" id="fnref:130" href="#fn:130"><sup>130</sup></a></td></tr><tr><td>36</td><td>Channel end<a class="footnote-ref" id="fnref:131" href="#fn:131"><sup>131</sup></a></td></tr><tr><td>37</td><td>Device end<a class="footnote-ref" id="fnref:132" href="#fn:132"><sup>132</sup></a></td></tr><tr><td>38</td><td>Unit check<a class="footnote-ref" id="fnref:133" href="#fn:133"><sup>133</sup></a></td></tr><tr><td>39</td><td>Unit exception<a class="footnote-ref" id="fnref:134" href="#fn:134"><sup>134</sup></a></td></tr><tr><td>40-47</td><td>Channel Status Conditions<a class="footnote-ref" id="fnref:135" href="#fn:135"><sup>135</sup></a>Detected by the channel.</td></tr><tr><td>40</td><td>Program-controlled interruption<a class="footnote-ref" id="fnref:136" href="#fn:136"><sup>136</sup></a></td></tr><tr><td>41</td><td>Incorrect length<a class="footnote-ref" id="fnref:137" href="#fn:137"><sup>137</sup></a></td></tr><tr><td>42</td><td>Program check<a class="footnote-ref" id="fnref:138" href="#fn:138"><sup>138</sup></a></td></tr><tr><td>43</td><td>Protection check<a class="footnote-ref" id="fnref:139" href="#fn:139"><sup>139</sup></a></td></tr><tr><td>44</td><td>Channel data check<a class="footnote-ref" id="fnref:140" href="#fn:140"><sup>140</sup></a></td></tr><tr><td>45</td><td>Channel control check<a class="footnote-ref" id="fnref:141" href="#fn:141"><sup>141</sup></a></td></tr><tr><td>46</td><td>Interface control check<a class="footnote-ref" id="fnref:142" href="#fn:142"><sup>142</sup></a></td></tr><tr><td>47</td><td>Chaining check<a class="footnote-ref" id="fnref:143" href="#fn:143"><sup>143</sup></a></td></tr><tr><td>48-63</td><td>Count<a class="footnote-ref" id="fnref:144" href="#fn:144"><sup>144</sup></a></td></tr></tbody></table> <ul><li>The Protection Key field contains the protect key from the CAW at the time that the I/O operation was initiated for I/O complete or PCI interruptions.<a class="footnote-ref" id="fnref:145" href="#fn:145"><sup>145</sup></a></li> <li>The Command Address field contains the address+8 of the last CCW fetched for an I/O complete or PCI interruption. However, there are 9 exceptions<a class="footnote-ref" id="fnref:146" href="#fn:146"><sup>146</sup></a></li> <li>The Status field contains one byte of Channel status bits, indicating conditions detected by the channel<a class="footnote-ref" id="fnref:147" href="#fn:147"><sup>147</sup></a> and one byte of Unit status bits, indicating conditions detected by the I/O unit<a class="footnote-ref" id="fnref:148" href="#fn:148"><sup>148</sup></a> There is no distinction between conditions detected by the control unit and conditions detected by the device.</li> <li>The Residual Count is a half word that gives the number of bytes in the area described by the CCW that have not been transferred to or from the channel<a class="footnote-ref" id="fnref:149" href="#fn:149"><sup>149</sup></a> The difference between the count in the CCW and the residual count gives the number of bytes transferred.</li></ul> <h3>I/O instructions</h3> <p>The S/360 has four<a class="footnote-ref" id="fnref:150" href="#fn:150"><sup>150</sup></a> I/O instructions: Start I/O (SIO), Test I/O (TIO), Halt I/O (HIO) and Test Channel (TCH). All four are privileged and thus will cause a privileged operation program interruption if used in problem state. The B1 (base) and D1 (displacement) fields are used to calculate the cuu (channel and device number); bits 8-15 of the instructions are unused and should be zero for compatibility with the S/370. </p> <h4>Start I/O (SIO)</h4> <p>SIO<a class="footnote-ref" id="fnref:151" href="#fn:151"><sup>151</sup></a> attempts to start the channel program pointed to by the CAW, using the storage protection key in the CAW. </p> <h4>Test I/O (TIO)</h4> <p>TIO<a class="footnote-ref" id="fnref:152" href="#fn:152"><sup>152</sup></a> tests the status of a channel and device. It may also store a CSW, in which case it completes with condition code 1. </p> <h4>Halt I/O (HIO)</h4> <p>HIO<a class="footnote-ref" id="fnref:153" href="#fn:153"><sup>153</sup></a> attempt to terminate an active channel program. It may also store a CSW, in which case it completes with condition code 1. </p> <h4>Test Channel (TCH)</h4> <p>TCH<a class="footnote-ref" id="fnref:154" href="#fn:154"><sup>154</sup></a> tests the status of a channel. It does not affect the status of an active channel program and does not store a CSW, </p> <h2 id="operator-controls">Operator controls</h2> <p>The architecture of System/360 specified the existence of several common functions, but did not specify their means of implementation. This allowed IBM to use different physical means, e.g., dial, keyboard, pushbutton, roller, image or text on a CRT, for selecting the functions and values on different processors. Any reference to <i>key</i> or <i>switch</i> should be read as applying to, e.g., a light-pen selection, an equivalent keyboard sequence. </p> <ul><li>System Reset sends a reset signal on every I/O channel and clears the processor state; all pending interruptions are cancelled. System Reset is not guaranteed to correct parity errors in general registers, floating point registers or storage. System Reset does not reset the state of shared I/O devices.</li> <li>Initial Program Load (IPL)<a class="footnote-ref" id="fnref:155" href="#fn:155"><sup>155</sup></a> is a process for loading a program when there isn't a loader available in storage, usually because the machine was just powered on or to load an alternative operating system.<a class="footnote-ref" id="fnref:156" href="#fn:156"><sup>156</sup></a>: 123 This process is sometimes known as <a href="/facts/Booting/j6N1kRpc">Booting</a>.</li></ul> As part of the IPL facility the operator has a means of specifying a 12-bit<a class="footnote-ref" id="fnref:157" href="#fn:157"><sup>157</sup></a> device address, typically with three dials as shown in the operator controls drawing. When the operator<a class="footnote-ref" id="fnref:158" href="#fn:158"><sup>158</sup></a> selects the <i>Load</i> function, the system performs a <i>System Reset</i>, sends a Read IPL<a class="footnote-ref" id="fnref:159" href="#fn:159"><sup>159</sup></a> channel command to the selected device in order to read 24 bytes into locations 0-23 and causes the channel to begin fetching <i>CCW</i>s at location 8; the effect is as if the channel had fetched a CCW with a length of 24, an address of 0 and the flags containing Command Chaining + Suppress Length Indication. At the completion of the operation, the system stores the I/O address in the halfword at location 2 and loads the PSW from location 0. Initial program loading is typically done from a tape, a card reader, or a disk drive. Generally, the operating system was loaded from a disk drive; IPL from tape or cards was used only for diagnostics or for installing an operating system on a new computer. <ul><li>Emergency pull switch<a class="footnote-ref" id="fnref:160" href="#fn:160"><sup>160</sup></a> (Emergency power off, EPO) sends an EPO signal to every I/O channel, then turns off power to the processor complex. Because EPO bypasses the normal sequencing of power down, damage can result, and the EPO control has a mechanical latch to ensure that a customer engineer inspects the equipment before attempting to power it back on.</li> <li>Power on<a class="footnote-ref" id="fnref:161" href="#fn:161"><sup>161</sup></a> powers up all components of the processor complex and performs a system reset.</li> <li>Power off<a class="footnote-ref" id="fnref:162" href="#fn:162"><sup>162</sup></a> initiates an orderly power-off sequence. Although the contents of storage are preserved, the associated storage keys may be lost.</li> <li>The Interrupt key<a class="footnote-ref" id="fnref:163" href="#fn:163"><sup>163</sup></a> causes an external interruption with bit 25 set in the External Old PSW.</li> <li>The Wait light<a class="footnote-ref" id="fnref:164" href="#fn:164"><sup>164</sup></a> indicates that the PSW has bit 14 (wait) set; the processor is temporarily halted but resumes operation when an interruption condition occurs.</li> <li>The Manual light<a class="footnote-ref" id="fnref:165" href="#fn:165"><sup>165</sup></a> indicates that the CPU is in a stopped state.</li> <li>The System light<a class="footnote-ref" id="fnref:166" href="#fn:166"><sup>166</sup></a> indicates that a meter is running, either due to CPU activity or due to I/O channel activity.</li> <li>The Test light<a class="footnote-ref" id="fnref:167" href="#fn:167"><sup>167</sup></a> indicates that certain operator controls are active, when certain facilities, e.g., INSTRUCTION STEP, have been used by a Diagnose instruction or when abnormal thermal conditions exist. The details are model dependent.</li> <li>The Load light<a class="footnote-ref" id="fnref:168" href="#fn:168"><sup>168</sup></a> is turned on by IPL and external start. It is turned off by loading the PSW from location 0 at the completion of the load process.</li> <li>The Load unit<a class="footnote-ref" id="fnref:169" href="#fn:169"><sup>169</sup></a> controls provide the rightmost 11<a class="footnote-ref" id="fnref:170" href="#fn:170"><sup>170</sup></a> bits of the device from which to perform an IPL.</li> <li>The Load Key<a class="footnote-ref" id="fnref:171" href="#fn:171"><sup>171</sup></a> starts the IPL sequence.</li> <li>The Prefix Select Key Switch<a class="footnote-ref" id="fnref:172" href="#fn:172"><sup>172</sup></a> selects whether IPL will use the primary prefix or the alternative prefix.</li> <li>The System-Reset Key<a class="footnote-ref" id="fnref:173" href="#fn:173"><sup>173</sup></a> initiates a System Reset.</li> <li>The Stop Key<a class="footnote-ref" id="fnref:174" href="#fn:174"><sup>174</sup></a> puts the CPU in a stopped state; channel programs continue running and interruption conditions remain pending.</li> <li>The Rate Switch<a class="footnote-ref" id="fnref:175" href="#fn:175"><sup>175</sup></a> determines the mode in which the processor fetches instructions. Two modes are defined by the architecture: <ul><li>PROCESS</li> <li>INSTRUCTION STEP</li></ul></li> <li>The Start Key<a class="footnote-ref" id="fnref:176" href="#fn:176"><sup>176</sup></a> initiates instruction fetching in accordance with the setting of the Rate Switch.</li> <li>The Storage-Select Switch<a class="footnote-ref" id="fnref:177" href="#fn:177"><sup>177</sup></a> determines the type of resource accessed by the Store Key and Display Key. Three selections are defined by the architecture: <ul><li>Main storage</li> <li>General registers</li> <li>Floating-point registers</li></ul></li> <li>The Address Switches<a class="footnote-ref" id="fnref:178" href="#fn:178"><sup>178</sup></a> specify the address or register number for the Store Key, Display Key and, on some models, the Set IC Key..</li> <li>The Data Switches<a class="footnote-ref" id="fnref:179" href="#fn:179"><sup>179</sup></a> specify the data for the Store Key and, on some models, the Set IC Key.</li> <li>The Store Key<a class="footnote-ref" id="fnref:180" href="#fn:180"><sup>180</sup></a> stores the value in the Data Switches as specified by the <a href="/facts//025fgtUV">Storage-Select Switch</a> and the Address Switches.</li> <li>The Display Key<a class="footnote-ref" id="fnref:181" href="#fn:181"><sup>181</sup></a> displays the value specified by the <a href="/facts//025fgtUV">Storage-Select Switch</a> and the Address Switches.</li> <li>The Set IC=<a class="footnote-ref" id="fnref:182" href="#fn:182"><sup>182</sup></a> sets the instruction address portion of the PSW from the Data Switches or the Address Switches, depending on the model.</li> <li>The Address-Compare Switches<a class="footnote-ref" id="fnref:183" href="#fn:183"><sup>183</sup></a> select the mode of comparison and what is compared. Stop on instruction address compare is present on all models, but stop on data address compare is only present on some models.</li> <li>The Alternate-Prefix Light<a class="footnote-ref" id="fnref:184" href="#fn:184"><sup>184</sup></a> is on when the prefix trigger is in the alternate state.</li></ul> <h2 id="optional-features">Optional features</h2> <h3>Byte-aligned operands</h3> <p>On some models, e.g., the <a href="/facts/IBM_System%2f360_Model_85/pVoUUagB">S/360-85</a>,<a class="footnote-ref" id="fnref:185" href="#fn:185"><sup>185</sup></a> the alignment requirements for some problem-state instructions were relaxed. There is no mechanism to turn off this feature, and programs depending on receiving a program check type 6 (alignment) on those instructions must be modified. </p> <h3>Decimal arithmetic</h3> <p>The decimal arithmetic feature provides instructions that operate on packed decimal data. A packed decimal number has 1-31 decimal digits followed by a 4-bit sign. All of the decimal arithmetic instructions except PACK and UNPACK generate a Data exception if a digit is not in the range 0-9 or a sign is not in the range A-F. </p> <h3>Direct Control</h3> <p>The <i>Direct Control</i><a class="footnote-ref" id="fnref:186" href="#fn:186"><sup>186</sup></a> feature provides six external signal lines and an 8-bit data path to/from storage.<a class="footnote-ref" id="fnref:187" href="#fn:187"><sup>187</sup></a> </p> <h3>Floating-point arithmetic</h3> <p>The floating-point arithmetic feature provides 4 64-bit floating point registers and instructions to operate on 32 and 64 bit hexadecimal floating point numbers. The 360/85 and 360/195 also support 128 bit extended precision floating point numbers. </p> <h3>Interval timer</h3> <p>If the interval timer feature<a class="footnote-ref" id="fnref:188" href="#fn:188"><sup>188</sup></a>: 17.1 is installed, the processor decrements the word at location 80 ('50'X) at regular intervals; the architecture does not specify the interval but does require that value subtracted make it appear as though 1 were subtracted from bit 23 300 times per second. The smaller models decremented at the same frequency (50 Hz or 60 Hz) as the AC power supply, but larger models had a high resolution timer feature. The processor causes an External interruption when the timer goes to zero. </p> <h3>Multi-system operation</h3> <p><i>Multi-system operation</i><a class="footnote-ref" id="fnref:189" href="#fn:189"><sup>189</sup></a> is a set of features to support multi-processor systems, e.g., Direct Control, direct address relocation (prefixing). </p> <h3>Storage protection</h3> <p>If the storage protection feature<a class="footnote-ref" id="fnref:190" href="#fn:190"><sup>190</sup></a>: 17-17.1 is installed, then there is a 4-bit storage key associated with every 2,048-byte block of storage and that key is checked when storing into any address in that block by either a CPU or an I/O channel. A CPU or channel key of 0 disables the check; a nonzero CPU or channel key allows data to be stored only in a block with the matching key. </p><p>Storage Protection was used to prevent a defective application from writing over storage belonging to the operating system or another application. This permitted testing to be performed along with production. Because the key was only four bits in length, the maximum number of different applications that could be run simultaneously was 15. </p><p>An additional option available on some models was fetch protection. It allowed the operating system to specify that blocks were protected from fetching as well as from storing. </p> <h2 id="deviations-and-extensions">Deviations and extensions</h2> <p>The <a href="/facts/IBM_System%2f360_Model_20/aDro2eBY">System/360 Model 20</a> is radically different and should not be considered to be a S/360. </p><p>The <a href="/facts/IBM_System%2f360_Model_44/EJ02nsd1">System/360 Model 44</a> is missing certain instructions, but a feature allowed the missing instructions to be simulated in hidden memory thus allowing the use of standard S/360 operating systems and applications. </p><p>Some models have features that extended the architecture, e.g., emulation instructions, paging, and some models make minor deviations from the architecture. Examples include: </p> <ul><li>The multisystem feature on the S/360-65 which modifies the behavior of the direct control feature and of the Set System Mask (SSM) instruction.<a class="footnote-ref" id="fnref:191" href="#fn:191"><sup>191</sup></a></li> <li>The <a href="/facts/IBM_System%2f360_Model_67/0BwJAwRV">System/360 Model 67</a>-2 had similar, but incompatible, changes.<a class="footnote-ref" id="fnref:192" href="#fn:192"><sup>192</sup></a></li></ul> <p>Some deviations served as prototypes for features of the <a href="/facts/IBM_System%2f370/TRo1jaFw">S/370</a> architecture. </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Memory_protection_key/3zDwN2SG">Memory protection key</a></li></ul> <h2 id="notes">Notes</h2> S360 <i>IBM System/360 Principles of Operation</i>. Systems Reference Library (Eighth ed.). IBM. September 1968. A22-6821-7. <h2 id="further-reading">Further reading</h2> <ul><li>Prasad, N.S. (1989). <a href="https://archive.org/details/ibmmainframesarc00pras"><i>IBM Mainframes</i></a>. McGraw-Hill. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 0070506868. — Chapter 3 (pp. 41–110) describes the System/360 architecture.</li> <li>Greiner, Dan (August 10, 2011). <a href="https://share.confex.com/share/117/webprogram/Handout/Session9220/IBM%20zArchitecture%20CPU%20History.pdf">"IBM z/Architecture CPU Features - A Historical Perspective"</a> (PDF). <a href="https://share.confex.com/share/117/webprogram/Session9220.html"><i>Evolution of The IBM Mainframe Architecture</i></a>. <a href="https://share.confex.com/share/117/webprogram/start.html">SHARE 117 in Orlando</a>. <a href="/facts/SHARE_(computing)/zfM9SCIT">SHARE</a>. Session 9220. Retrieved February 7, 2023.</li></ul> <h2 id="external-links">External links</h2> <ul><li><a href="http://bitsavers.org/pdf/ibm/360/GC20-1667-1_intro360arch.pdf">Introduction to IBM System/360 Architecture</a> (Student Text)</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>IBM (1964), IBM System/360 Principles of Operation (PDF), First Edition, A22-6821-0 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-0_360PrincOps.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-0_360PrincOps.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>IBM, IBM System/360 I/O Interface Channel to Control Unit Original Equipment Manufacturers' Information (PDF), Fifth Edition, A22-6843-3 <a href="http://bitsavers.org/pdf/ibm/360/A22-6843-3_360channelOEM.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/A22-6843-3_360channelOEM.pdf</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>IBM Corporation (1974). IBM System/360 System Summary (PDF). p. 3-3. Retrieved July 16, 2017. <a href="http://bitsavers.org/pdf/ibm/360/systemSummary/GA22-6810-12_360sysSumJan74.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/systemSummary/GA22-6810-12_360sysSumJan74.pdf</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Twice the size of the later System/370 <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>Reference Manual UNIVAC III Data Processing System (PDF), Sperry Rand Corporation, 1962, UT-2488 <a href="http://bitsavers.org/pdf/univac/univac3/UT-2488_UNIVACIII_ref_Jun62.pdf" target="_blank">http://bitsavers.org/pdf/univac/univac3/UT-2488_UNIVACIII_ref_Jun62.pdf</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>A specification of general register 0 yield a base address of zero rather than the register content. <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>IBM (June 1968), IBM System/360 Model 85 Functional Characteristics (PDF), SECOND EDITION, A22-6916-1 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6916-1_360-85_funcChar_Jun68.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6916-1_360-85_funcChar_Jun68.pdf</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>IBM (August 1970), IBM System/360 Model 195 Functional Characteristics (PDF), Second Edition, GA22-6943-1 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA22-6943-1_360-195_Functional_Characteristics_197008.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA22-6943-1_360-195_Functional_Characteristics_197008.pdf</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>On a processor that complies with the S/360 architecture, the highest channel number is 6. Eleven bits are sufficient to identify the cuu, and seven bits are sufficient to provide masking of I/O interruptions. However, on a 360/67-2 with two 2846 channel controllers, channels are numbered 0-6 and 8-14;[11]: 15 similarly, the 360/195 had an extended channel feature[10]: 21 but numbered the channels 0 through 13.[10]: 25 I/O interruptions for Channel Controller 1 on the 360/67-2 were masked using control registers, and the 360/195 used bit 7 (Channel 6) of the System Mask as a summary mask bit for channels 6 and up. Interruptions from More than Seven Channels[12] describes the summary masking for additional channels, but other text in Principles of Operation still refers to a limit of 7 channels. Standard software supported channels 0-F. <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>PoOps, p. 71. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>Because the design of the S/360 occurred simultaneously with the development of ASCII, IBM's ASCII support did not match the standard that was ultimately adopted. <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>PoOps, p. 77. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> <li id="fn:15"><p>PoOps, p. 71. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li> <li id="fn:16"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></p></li> <li id="fn:17"><p>The S/360 literature does not use the terms fault or trap <a href="/wiki/Trap_(computing)" target="_blank">/wiki/Trap_(computing)</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></p></li> <li id="fn:18"><p>PoOps, pp. 78–79. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></p></li> <li id="fn:19"><p>PoOps, pp. 79–80.1. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></p></li> <li id="fn:20"><p>PoOps, pp. 80.1–81. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></p></li> <li id="fn:21"><p>PoOps, pp. 81–82. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></p></li> <li id="fn:22"><p>PoOps, pp. 82–83. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></p></li> <li id="fn:23"><p>PoOps, pp. 78–79. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></p></li> <li id="fn:24"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></p></li> <li id="fn:25"><p>On the 360/91,[20]: 15 360/95 and 360/195[10]: 14 a Program interruption may occur for multiple imprecise exceptions. The ILC in the Program Old PSW is 0, bits 26-31 are 0 and bits 16-27 are a mask indicating which exceptions occurred; there is no provision for reporting multiple occurrences of the same exception. Reporting of multiple imprecise exceptions is not part of the S/360 architecture. <a href="#fnref:25" class="footnote-back-ref">↩</a></p></li> <li id="fn:26"><p>There are 17 possible exceptions on the 360/67,[11]: 17 but page exception and segment exception are not part of the S/360 architecture; similarly, interruption code 18 ('0012'X) on a 360/65 multiprocessor is not part of the S/360 architecture. <a href="#fnref:26" class="footnote-back-ref">↩</a></p></li> <li id="fn:27"><p>IBM (September 1968), "Appendix A. Multiprocessing System", IBM System/360 Model 65 Functional Characteristics (PDF), Fourth Edition, pp. 30–34, A22-6884-3 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6884-3_360-65_funcChar.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6884-3_360-65_funcChar.pdf</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></p></li> <li id="fn:28"><p>IBM (February 1972), IBM System/360 Model 67 Functional Characteristics (PDF), Third Edition, GA27-2719-2 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA27-2719-2_360-67_funcChar.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA27-2719-2_360-67_funcChar.pdf</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></p></li> <li id="fn:29"><p>IBM (June 1968), IBM System/360 Model 85 Functional Characteristics (PDF), SECOND EDITION, A22-6916-1 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6916-1_360-85_funcChar_Jun68.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6916-1_360-85_funcChar_Jun68.pdf</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></p></li> <li id="fn:30"><p>On the 360/91,[20]: 15 360/95 and 360/195[10]: 14 a Program interruption may occur for multiple imprecise exceptions. The ILC in the Program Old PSW is 0, bits 26-31 are 0 and bits 16-27 are a mask indicating which exceptions occurred; there is no provision for reporting multiple occurrences of the same exception. Reporting of multiple imprecise exceptions is not part of the S/360 architecture. <a href="#fnref:30" class="footnote-back-ref">↩</a></p></li> <li id="fn:31"><p>IBM (1968-03-18), IBM System/360 Model 91 Functional Characteristics (PDF), Third Edition, A22-6907-2 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6907-2_360-91_funcChar.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6907-2_360-91_funcChar.pdf</a> <a href="#fnref:31" class="footnote-back-ref">↩</a></p></li> <li id="fn:32"><p>IBM (August 1970), IBM System/360 Model 195 Functional Characteristics (PDF), Second Edition, GA22-6943-1 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA22-6943-1_360-195_Functional_Characteristics_197008.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA22-6943-1_360-195_Functional_Characteristics_197008.pdf</a> <a href="#fnref:32" class="footnote-back-ref">↩</a></p></li> <li id="fn:33"><p>The Specification bit is not used for imprecise interruptions on the 360/195 <a href="#fnref:33" class="footnote-back-ref">↩</a></p></li> <li id="fn:34"><p>Not Used on 360/91 <a href="#fnref:34" class="footnote-back-ref">↩</a></p></li> <li id="fn:35"><p>Not Used on 360/91 <a href="#fnref:35" class="footnote-back-ref">↩</a></p></li> <li id="fn:36"><p>PoOps, p. 79. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:36" class="footnote-back-ref">↩</a></p></li> <li id="fn:37"><p>PoOps, p. 79. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:37" class="footnote-back-ref">↩</a></p></li> <li id="fn:38"><p>PoOps, p. 79. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:38" class="footnote-back-ref">↩</a></p></li> <li id="fn:39"><p>PoOps, p. 79. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:39" class="footnote-back-ref">↩</a></p></li> <li id="fn:40"><p>PoOps, pp. 79–80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:40" class="footnote-back-ref">↩</a></p></li> <li id="fn:41"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:41" class="footnote-back-ref">↩</a></p></li> <li id="fn:42"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:42" class="footnote-back-ref">↩</a></p></li> <li id="fn:43"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:43" class="footnote-back-ref">↩</a></p></li> <li id="fn:44"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:44" class="footnote-back-ref">↩</a></p></li> <li id="fn:45"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:45" class="footnote-back-ref">↩</a></p></li> <li id="fn:46"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:46" class="footnote-back-ref">↩</a></p></li> <li id="fn:47"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:47" class="footnote-back-ref">↩</a></p></li> <li id="fn:48"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:48" class="footnote-back-ref">↩</a></p></li> <li id="fn:49"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:49" class="footnote-back-ref">↩</a></p></li> <li id="fn:50"><p>PoOps, p. 80.1. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:50" class="footnote-back-ref">↩</a></p></li> <li id="fn:51"><p>IBM (February 1972), IBM System/360 Model 67 Functional Characteristics (PDF), Third Edition, GA27-2719-2 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA27-2719-2_360-67_funcChar.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA27-2719-2_360-67_funcChar.pdf</a> <a href="#fnref:51" class="footnote-back-ref">↩</a></p></li> <li id="fn:52"><p>There are 17 possible exceptions on the 360/67,[11]: 17 but page exception and segment exception are not part of the S/360 architecture; similarly, interruption code 18 ('0012'X) on a 360/65 multiprocessor is not part of the S/360 architecture. <a href="#fnref:52" class="footnote-back-ref">↩</a></p></li> <li id="fn:53"><p>IBM (February 1972), IBM System/360 Model 67 Functional Characteristics (PDF), Third Edition, GA27-2719-2 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA27-2719-2_360-67_funcChar.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA27-2719-2_360-67_funcChar.pdf</a> <a href="#fnref:53" class="footnote-back-ref">↩</a></p></li> <li id="fn:54"><p>There are 17 possible exceptions on the 360/67,[11]: 17 but page exception and segment exception are not part of the S/360 architecture; similarly, interruption code 18 ('0012'X) on a 360/65 multiprocessor is not part of the S/360 architecture. <a href="#fnref:54" class="footnote-back-ref">↩</a></p></li> <li id="fn:55"><p>IBM (September 1968), "Appendix A. Multiprocessing System", IBM System/360 Model 65 Functional Characteristics (PDF), Fourth Edition, pp. 30–34, A22-6884-3 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6884-3_360-65_funcChar.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6884-3_360-65_funcChar.pdf</a> <a href="#fnref:55" class="footnote-back-ref">↩</a></p></li> <li id="fn:56"><p>There are 17 possible exceptions on the 360/67,[11]: 17 but page exception and segment exception are not part of the S/360 architecture; similarly, interruption code 18 ('0012'X) on a 360/65 multiprocessor is not part of the S/360 architecture. <a href="#fnref:56" class="footnote-back-ref">↩</a></p></li> <li id="fn:57"><p>PoOps, p. 79. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:57" class="footnote-back-ref">↩</a></p></li> <li id="fn:58"><p>PoOps, p. 79. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:58" class="footnote-back-ref">↩</a></p></li> <li id="fn:59"><p>PoOps, p. 79. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:59" class="footnote-back-ref">↩</a></p></li> <li id="fn:60"><p>PoOps, p. 79. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:60" class="footnote-back-ref">↩</a></p></li> <li id="fn:61"><p>A PSW key of 0 matches any storage key. <a href="#fnref:61" class="footnote-back-ref">↩</a></p></li> <li id="fn:62"><p>PoOps, pp. 79–80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:62" class="footnote-back-ref">↩</a></p></li> <li id="fn:63"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:63" class="footnote-back-ref">↩</a></p></li> <li id="fn:64"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:64" class="footnote-back-ref">↩</a></p></li> <li id="fn:65"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:65" class="footnote-back-ref">↩</a></p></li> <li id="fn:66"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:66" class="footnote-back-ref">↩</a></p></li> <li id="fn:67"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:67" class="footnote-back-ref">↩</a></p></li> <li id="fn:68"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:68" class="footnote-back-ref">↩</a></p></li> <li id="fn:69"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:69" class="footnote-back-ref">↩</a></p></li> <li id="fn:70"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:70" class="footnote-back-ref">↩</a></p></li> <li id="fn:71"><p>PoOps, p. 80. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:71" class="footnote-back-ref">↩</a></p></li> <li id="fn:72"><p>PoOps, p. 80.1. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:72" class="footnote-back-ref">↩</a></p></li> <li id="fn:73"><p>PoOps, pp. 80.1–81. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:73" class="footnote-back-ref">↩</a></p></li> <li id="fn:74"><p>PoOps, p. 81. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:74" class="footnote-back-ref">↩</a></p></li> <li id="fn:75"><p>Even though a timer expiration is an internal event, it causes an External interruption and for this reason, this interruption is usually referred to as a timer/external interruption. <a href="#fnref:75" class="footnote-back-ref">↩</a></p></li> <li id="fn:76"><p>IBM (September 1968), "Appendix A. Multiprocessing System", IBM System/360 Model 65 Functional Characteristics (PDF), Fourth Edition, pp. 30–34, A22-6884-3 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6884-3_360-65_funcChar.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6884-3_360-65_funcChar.pdf</a> <a href="#fnref:76" class="footnote-back-ref">↩</a></p></li> <li id="fn:77"><p>IBM (September 1968), "Appendix A. Multiprocessing System", IBM System/360 Model 65 Functional Characteristics (PDF), Fourth Edition, pp. 30–34, A22-6884-3 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6884-3_360-65_funcChar.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6884-3_360-65_funcChar.pdf</a> <a href="#fnref:77" class="footnote-back-ref">↩</a></p></li> <li id="fn:78"><p>PoOps, pp. 82–83. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:78" class="footnote-back-ref">↩</a></p></li> <li id="fn:79"><p>IBM, IBM System/360 I/O Interface Channel to Control Unit Original Equipment Manufacturers' Information (PDF), Fifth Edition, A22-6843-3 <a href="http://bitsavers.org/pdf/ibm/360/A22-6843-3_360channelOEM.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/A22-6843-3_360channelOEM.pdf</a> <a href="#fnref:79" class="footnote-back-ref">↩</a></p></li> <li id="fn:80"><p>I/O Channel Interface (PDF) (Report). National Technical Information Service. July 29, 1983. FIPS PUB 60-2. Retrieved May 18, 2023. <a href="https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub60-2.pdf" target="_blank">https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub60-2.pdf</a> <a href="#fnref:80" class="footnote-back-ref">↩</a></p></li> <li id="fn:81"><p>Because of the limits on the channel number, S/360 and early S/370 software only used 12 bits to store device addresses. <a href="#fnref:81" class="footnote-back-ref">↩</a></p></li> <li id="fn:82"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:82" class="footnote-back-ref">↩</a></p></li> <li id="fn:83"><p>On a processor that complies with the S/360 architecture, the highest channel number is 6. Eleven bits are sufficient to identify the cuu, and seven bits are sufficient to provide masking of I/O interruptions. However, on a 360/67-2 with two 2846 channel controllers, channels are numbered 0-6 and 8-14;[11]: 15 similarly, the 360/195 had an extended channel feature[10]: 21 but numbered the channels 0 through 13.[10]: 25 I/O interruptions for Channel Controller 1 on the 360/67-2 were masked using control registers, and the 360/195 used bit 7 (Channel 6) of the System Mask as a summary mask bit for channels 6 and up. Interruptions from More than Seven Channels[12] describes the summary masking for additional channels, but other text in Principles of Operation still refers to a limit of 7 channels. Standard software supported channels 0-F. <a href="#fnref:83" class="footnote-back-ref">↩</a></p></li> <li id="fn:84"><p>But continuing with unrelated work. <a href="#fnref:84" class="footnote-back-ref">↩</a></p></li> <li id="fn:85"><p>PoOps, pp. 116–118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:85" class="footnote-back-ref">↩</a></p></li> <li id="fn:86"><p>PoOps, pp. 116–117. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:86" class="footnote-back-ref">↩</a></p></li> <li id="fn:87"><p>PoOps, p. 117. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:87" class="footnote-back-ref">↩</a></p></li> <li id="fn:88"><p>PoOps, p. 117. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:88" class="footnote-back-ref">↩</a></p></li> <li id="fn:89"><p>PoOps, pp. 117–118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:89" class="footnote-back-ref">↩</a></p></li> <li id="fn:90"><p>PoOps, p. 118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:90" class="footnote-back-ref">↩</a></p></li> <li id="fn:91"><p>PoOps, p. 118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:91" class="footnote-back-ref">↩</a></p></li> <li id="fn:92"><p>PoOps, p. 118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:92" class="footnote-back-ref">↩</a></p></li> <li id="fn:93"><p>PoOps, p. 118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:93" class="footnote-back-ref">↩</a></p></li> <li id="fn:94"><p>PoOps, pp. 113–116. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:94" class="footnote-back-ref">↩</a></p></li> <li id="fn:95"><p>PoOps, p. 113. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:95" class="footnote-back-ref">↩</a></p></li> <li id="fn:96"><p>The OS uses the attention index in a Unit Control Block (UCB) as an index into the attention table. <a href="/wiki/Unit_Control_Block" target="_blank">/wiki/Unit_Control_Block</a> <a href="#fnref:96" class="footnote-back-ref">↩</a></p></li> <li id="fn:97"><p>PoOps, pp. 113–114. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:97" class="footnote-back-ref">↩</a></p></li> <li id="fn:98"><p>PoOps, p. 114. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:98" class="footnote-back-ref">↩</a></p></li> <li id="fn:99"><p>PoOps, pp. 114–115. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:99" class="footnote-back-ref">↩</a></p></li> <li id="fn:100"><p>PoOps, p. 115. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:100" class="footnote-back-ref">↩</a></p></li> <li id="fn:101"><p>PoOps, p. 115. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:101" class="footnote-back-ref">↩</a></p></li> <li id="fn:102"><p>PoOps, pp. 115–116. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:102" class="footnote-back-ref">↩</a></p></li> <li id="fn:103"><p>PoOps, p. 116. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:103" class="footnote-back-ref">↩</a></p></li> <li id="fn:104"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:104" class="footnote-back-ref">↩</a></p></li> <li id="fn:105"><p>PoOps, p. 100. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:105" class="footnote-back-ref">↩</a></p></li> <li id="fn:106"><p>PoOps, pp. 100–101. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:106" class="footnote-back-ref">↩</a></p></li> <li id="fn:107"><p>PoOps, pp. 99–100, 101–105. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:107" class="footnote-back-ref">↩</a></p></li> <li id="fn:108"><p>PoOps, pp. 100–101. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:108" class="footnote-back-ref">↩</a></p></li> <li id="fn:109"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:109" class="footnote-back-ref">↩</a></p></li> <li id="fn:110"><p>PoOps, pp. 106–107. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:110" class="footnote-back-ref">↩</a></p></li> <li id="fn:111"><p>PoOps, pp. 107–108. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:111" class="footnote-back-ref">↩</a></p></li> <li id="fn:112"><p>PoOps, pp. 105–106. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:112" class="footnote-back-ref">↩</a></p></li> <li id="fn:113"><p>PoOps, p. 105. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:113" class="footnote-back-ref">↩</a></p></li> <li id="fn:114"><p>PoOps, p. 105. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:114" class="footnote-back-ref">↩</a></p></li> <li id="fn:115"><p>PoOps, pp. 106–107. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:115" class="footnote-back-ref">↩</a></p></li> <li id="fn:116"><p>PoOps, pp. 101–103. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:116" class="footnote-back-ref">↩</a></p></li> <li id="fn:117"><p>PoOps, pp. 101, 103. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:117" class="footnote-back-ref">↩</a></p></li> <li id="fn:118"><p>Also known as Suppress Incorrect Length Indication (SILI) <a href="#fnref:118" class="footnote-back-ref">↩</a></p></li> <li id="fn:119"><p>PoOps, pp. 99–100. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:119" class="footnote-back-ref">↩</a></p></li> <li id="fn:120"><p>PoOps, pp. 103–104. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:120" class="footnote-back-ref">↩</a></p></li> <li id="fn:121"><p>PoOps, pp. 104–105. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:121" class="footnote-back-ref">↩</a></p></li> <li id="fn:122"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:122" class="footnote-back-ref">↩</a></p></li> <li id="fn:123"><p>PoOps, p. 119. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:123" class="footnote-back-ref">↩</a></p></li> <li id="fn:124"><p>PoOps, p. 119. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:124" class="footnote-back-ref">↩</a></p></li> <li id="fn:125"><p>PoOps, pp. 113–118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:125" class="footnote-back-ref">↩</a></p></li> <li id="fn:126"><p>PoOps, pp. 113–116. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:126" class="footnote-back-ref">↩</a></p></li> <li id="fn:127"><p>PoOps, p. 113. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:127" class="footnote-back-ref">↩</a></p></li> <li id="fn:128"><p>PoOps, pp. 113–114. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:128" class="footnote-back-ref">↩</a></p></li> <li id="fn:129"><p>PoOps, p. 114. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:129" class="footnote-back-ref">↩</a></p></li> <li id="fn:130"><p>PoOps, pp. 114–115. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:130" class="footnote-back-ref">↩</a></p></li> <li id="fn:131"><p>PoOps, p. 115. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:131" class="footnote-back-ref">↩</a></p></li> <li id="fn:132"><p>PoOps, p. 115. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:132" class="footnote-back-ref">↩</a></p></li> <li id="fn:133"><p>PoOps, pp. 115–116. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:133" class="footnote-back-ref">↩</a></p></li> <li id="fn:134"><p>PoOps, p. 116. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:134" class="footnote-back-ref">↩</a></p></li> <li id="fn:135"><p>PoOps, pp. 116–118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:135" class="footnote-back-ref">↩</a></p></li> <li id="fn:136"><p>PoOps, pp. 116–117. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:136" class="footnote-back-ref">↩</a></p></li> <li id="fn:137"><p>PoOps, p. 117. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:137" class="footnote-back-ref">↩</a></p></li> <li id="fn:138"><p>PoOps, p. 117. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:138" class="footnote-back-ref">↩</a></p></li> <li id="fn:139"><p>PoOps, pp. 117–118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:139" class="footnote-back-ref">↩</a></p></li> <li id="fn:140"><p>PoOps, p. 118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:140" class="footnote-back-ref">↩</a></p></li> <li id="fn:141"><p>PoOps, p. 118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:141" class="footnote-back-ref">↩</a></p></li> <li id="fn:142"><p>PoOps, p. 118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:142" class="footnote-back-ref">↩</a></p></li> <li id="fn:143"><p>PoOps, p. 118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:143" class="footnote-back-ref">↩</a></p></li> <li id="fn:144"><p>PoOps, p. 120. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:144" class="footnote-back-ref">↩</a></p></li> <li id="fn:145"><p>PoOps, p. 119. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:145" class="footnote-back-ref">↩</a></p></li> <li id="fn:146"><p>PoOps, p. 119. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:146" class="footnote-back-ref">↩</a></p></li> <li id="fn:147"><p>PoOps, pp. 116–118. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:147" class="footnote-back-ref">↩</a></p></li> <li id="fn:148"><p>PoOps, pp. 113–116. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:148" class="footnote-back-ref">↩</a></p></li> <li id="fn:149"><p>PoOps, p. 120. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:149" class="footnote-back-ref">↩</a></p></li> <li id="fn:150"><p>S360, pp. 93–98, Control of Input/Output Devices. - IBM System/360 Principles of Operation. Systems Reference Library (Eighth ed.). IBM. September 1968. A22-6821-7. <a href="#fnref:150" class="footnote-back-ref">↩</a></p></li> <li id="fn:151"><p>S360, pp. 94–95, Start I/O. - IBM System/360 Principles of Operation. Systems Reference Library (Eighth ed.). IBM. September 1968. A22-6821-7. <a href="#fnref:151" class="footnote-back-ref">↩</a></p></li> <li id="fn:152"><p>S360, pp. 95–96, Test I/O. - IBM System/360 Principles of Operation. Systems Reference Library (Eighth ed.). IBM. September 1968. A22-6821-7. <a href="#fnref:152" class="footnote-back-ref">↩</a></p></li> <li id="fn:153"><p>S360, pp. 96–98, Halt I/O. - IBM System/360 Principles of Operation. Systems Reference Library (Eighth ed.). IBM. September 1968. A22-6821-7. <a href="#fnref:153" class="footnote-back-ref">↩</a></p></li> <li id="fn:154"><p>S360, p. 98, Test Channel. - IBM System/360 Principles of Operation. Systems Reference Library (Eighth ed.). IBM. September 1968. A22-6821-7. <a href="#fnref:154" class="footnote-back-ref">↩</a></p></li> <li id="fn:155"><p>PoOps, p. 123. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:155" class="footnote-back-ref">↩</a></p></li> <li id="fn:156"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:156" class="footnote-back-ref">↩</a></p></li> <li id="fn:157"><p>On a processor that complies with the S/360 architecture, the highest channel number is 6. Eleven bits are sufficient to identify the cuu, and seven bits are sufficient to provide masking of I/O interruptions. However, on a 360/67-2 with two 2846 channel controllers, channels are numbered 0-6 and 8-14;[11]: 15 similarly, the 360/195 had an extended channel feature[10]: 21 but numbered the channels 0 through 13.[10]: 25 I/O interruptions for Channel Controller 1 on the 360/67-2 were masked using control registers, and the 360/195 used bit 7 (Channel 6) of the System Mask as a summary mask bit for channels 6 and up. Interruptions from More than Seven Channels[12] describes the summary masking for additional channels, but other text in Principles of Operation still refers to a limit of 7 channels. Standard software supported channels 0-F. <a href="#fnref:157" class="footnote-back-ref">↩</a></p></li> <li id="fn:158"><p>Or an equivalent automated facility. <a href="#fnref:158" class="footnote-back-ref">↩</a></p></li> <li id="fn:159"><p>Read with all modifier bits zero <a href="#fnref:159" class="footnote-back-ref">↩</a></p></li> <li id="fn:160"><p>PoOps, p. 124. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:160" class="footnote-back-ref">↩</a></p></li> <li id="fn:161"><p>PoOps, p. 124. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:161" class="footnote-back-ref">↩</a></p></li> <li id="fn:162"><p>PoOps, p. 124. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:162" class="footnote-back-ref">↩</a></p></li> <li id="fn:163"><p>PoOps, p. 124. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:163" class="footnote-back-ref">↩</a></p></li> <li id="fn:164"><p>PoOps, p. 124. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:164" class="footnote-back-ref">↩</a></p></li> <li id="fn:165"><p>PoOps, p. 124. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:165" class="footnote-back-ref">↩</a></p></li> <li id="fn:166"><p>PoOps, p. 124. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:166" class="footnote-back-ref">↩</a></p></li> <li id="fn:167"><p>PoOps, p. 124. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:167" class="footnote-back-ref">↩</a></p></li> <li id="fn:168"><p>PoOps, p. 124. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:168" class="footnote-back-ref">↩</a></p></li> <li id="fn:169"><p>PoOps, pp. 124–125. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:169" class="footnote-back-ref">↩</a></p></li> <li id="fn:170"><p>There is an inconsistency, in that Interruptions from More than Seven Channels[12] allows for more channels. <a href="#fnref:170" class="footnote-back-ref">↩</a></p></li> <li id="fn:171"><p>PoOps, p. 125. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:171" class="footnote-back-ref">↩</a></p></li> <li id="fn:172"><p>PoOps, p. 125. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:172" class="footnote-back-ref">↩</a></p></li> <li id="fn:173"><p>PoOps, p. 125. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:173" class="footnote-back-ref">↩</a></p></li> <li id="fn:174"><p>PoOps, p. 125. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:174" class="footnote-back-ref">↩</a></p></li> <li id="fn:175"><p>PoOps, p. 125. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:175" class="footnote-back-ref">↩</a></p></li> <li id="fn:176"><p>PoOps, p. 125. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:176" class="footnote-back-ref">↩</a></p></li> <li id="fn:177"><p>PoOps, p. 126. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:177" class="footnote-back-ref">↩</a></p></li> <li id="fn:178"><p>PoOps, p. 126. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:178" class="footnote-back-ref">↩</a></p></li> <li id="fn:179"><p>PoOps, p. 126. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:179" class="footnote-back-ref">↩</a></p></li> <li id="fn:180"><p>PoOps, p. 126. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:180" class="footnote-back-ref">↩</a></p></li> <li id="fn:181"><p>PoOps, p. 126. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:181" class="footnote-back-ref">↩</a></p></li> <li id="fn:182"><p>PoOps, p. 126. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:182" class="footnote-back-ref">↩</a></p></li> <li id="fn:183"><p>PoOps, p. 126. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:183" class="footnote-back-ref">↩</a></p></li> <li id="fn:184"><p>PoOps, p. 126. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:184" class="footnote-back-ref">↩</a></p></li> <li id="fn:185"><p>IBM (June 1968), IBM System/360 Model 85 Functional Characteristics (PDF), SECOND EDITION, A22-6916-1 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6916-1_360-85_funcChar_Jun68.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6916-1_360-85_funcChar_Jun68.pdf</a> <a href="#fnref:185" class="footnote-back-ref">↩</a></p></li> <li id="fn:186"><p>PoOps, p. 17.1. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:186" class="footnote-back-ref">↩</a></p></li> <li id="fn:187"><p>IBM, IBM System/360 Direct Control and External Interrupt Features Original Equipment Manufacturers' Information (PDF), Third Edition, A22-6845-2 <a href="http://bitsavers.org/pdf/ibm/360/A22-6845-2_System_360_Direct_Control_and_External_Interrupt_Features_OEM_Information.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/A22-6845-2_System_360_Direct_Control_and_External_Interrupt_Features_OEM_Information.pdf</a> <a href="#fnref:187" class="footnote-back-ref">↩</a></p></li> <li id="fn:188"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:188" class="footnote-back-ref">↩</a></p></li> <li id="fn:189"><p>PoOps, pp. 17.1–18. - IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:189" class="footnote-back-ref">↩</a></p></li> <li id="fn:190"><p>IBM (September 1968), IBM System/360 Principles of Operation (PDF), Eighth Edition, A22-6821-7 Revised by IBM (May 12, 1970), ibid., GN22-0354 and IBM (June 8, 1970), ibid., GN22-0361 <a href="http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-7_360PrincOpsDec67.pdf</a> <a href="#fnref:190" class="footnote-back-ref">↩</a></p></li> <li id="fn:191"><p>IBM (September 1968), "Appendix A. Multiprocessing System", IBM System/360 Model 65 Functional Characteristics (PDF), Fourth Edition, pp. 30–34, A22-6884-3 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6884-3_360-65_funcChar.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6884-3_360-65_funcChar.pdf</a> <a href="#fnref:191" class="footnote-back-ref">↩</a></p></li> <li id="fn:192"><p>IBM (February 1972), IBM System/360 Model 67 Functional Characteristics (PDF), Third Edition, GA27-2719-2 <a href="http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA27-2719-2_360-67_funcChar.pdf" target="_blank">http://bitsavers.org/pdf/ibm/360/functional_characteristics/GA27-2719-2_360-67_funcChar.pdf</a> <a href="#fnref:192" class="footnote-back-ref">↩</a></p></li> </ol>