Input/Output Control System

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Input/Output Control System (IOCS) is any of several packages on early IBM entry-level and mainframe computers that provided low level access to records on peripheral equipment. IOCS provides functionality similar to File Control Processor (FCP)[1] in RCA 3301 Realcom Operating System and GEFRC[2] in GECOS.

Computers in the 1950s and 1960s typically dealt with data that were organized into records either by the nature of the media, e.g., lines of print, or by application requirements. IOCS was intended to allow Assembler language programmers to read and write records without having to worry about the details of the various devices or the blocking of logical records into physical records. IOCS provided the run time I/O support for several compilers.

Computers in the 1950s and 1960s often did not have operating systems in the modern sense. Application programs called IOCS routines in a resident monitor, or included macro instructions that expanded to IOCS routines.

In some cases[3] IOCS was designed to coexist with Simultaneous Peripheral Operations On-line (SPOOL)[4] software. The level of access is at a higher level than that provided by BIOS and BDOS in the PC world; in fact, IOCS has no support for character-oriented I/O. Versions of IOCS existed for the IBM 705 III,[5] 1401/1440/1460, 1410/7010, 7070/7072/7074,[6][7] 7080[8] and 7040/7044/7090/7094.[9] These systems heavily influenced the data management components of the operating systems[10] for the System/360; the name IOCS was carried through in DOS/360 through z/VSE,[11] with a distinction between Logical IOCS (LIOCS) and Physical IOCS (PIOCS).

Although some technical details and nomenclature are different among the various IOCS packages, the fundamental concepts are the same. For concreteness, the discussion and examples in this article will mostly be in terms of 7070 IOCS.[6][7] Also, multiple continuation lines will be shown as ellipses (...) when they don't serve to illustrate the narrative.


An IOCS program must do three things, each discussed in a subsection below.

For the 7070 these are done using 7070 Autocoder[12][13] declarative statements and Macro instructions.

Identify required IOCS services[edit]

IOCS supported several classes of I/O equipment

  • Disk drives
  • Tape drives
  • Unit record equipment. The record length was dictated by the physical media, which were
    • Lines of print on paper
    • Punched 80-column[a] cards

Some services offered by IOCS were not needed by all applications, e.g., checkpoints, label processing. An IOCS program must identify the particular devices types and services it uses. A 7070 IOCS program must specify one or more DIOCS[6](pp16–19)[12](pp22–25) statements:[b]

             11   22
    6        56   01
    GENERAL   DIOCSgeneral parameters
    TAPE      DIOCSD729,tape parameters
    DISK      DIOCSD1301,disk parameters
    END       DIOCS

These declarative statements identify index registers reserved for the use of IOCS, indicate channels used, indicate whether the program is to coexist with SPOOL and provide processing options. The END DIOCS statement causes the assembly of IOCS unless a preassembled version is requested. The first (general) form is omitted when the D729 form is used.

In some other IOCS packages similar functions are provided by control cards.

Create control blocks for individual files[edit]

An IOCS program must create a control block for each file, specifying information unique to the file. For 7070 IOCS these are entries in the File Specification Table for tape files, each of which is generated by a DTF[6](pp19–26)[12](pp26–28) statement, or separate control blocks generated by DDF [7](pp31–37)[12](pp29–30) or DUF[6](pp44–47)[12](pp31–33) statements.

             11   22
    6        56   01
              DTF  OUT
    FCHANNEL       2
              ...  ...
    IODEVICE       5
    DREFMODE       4
              ...  ... 

The above code defines a tape file on channel 1 called OUT, a sequential 1301/1302 disk file called DAFILE and a card file called CONSFILE.

In some other IOCS packages similar functions are provided by control cards.

Process files[edit]

Any IOCS program must specify the actions that it wishes to perform. In 7070 IOCS this is done with processing macros.

             11   22
    6        56   01
              OPEN CONSFILE,OUT
              PUT  OUT
              B    LOOP

In some other IOCS packages similar functions are provided by explicit subroutine calls.


  1. ^ IBM did not support the 90-column cards used by UNIVAC
  2. ^ Note that operands in 7070 Autocoder always start in column 21.


  1. ^ RCA EDP Division (November 1964). RCA 3301 Realcom Training Manual (PDF). 94-06-000.
  2. ^ GE. GE-635 File and Record Control Reference Manual. CPB-1003.
  3. ^ IBM. IBM 7070 SPOOL System. J28-6047-1.
  4. ^ "SPOOL System", 7070-IO-076
  5. ^ IBM. Reference Manual Input/Output Control System for the IBM 705 III. C28-6109.
  6. ^ a b c d e IBM. IBM 7070/7074 Input/Output Control System for IBM 729 Magnetic Tape Units, Unit Record Equipment (7070-IO-904). C28-6175-3.
  7. ^ a b c IBM. IBM 7070/7074 Input/Output Control System for IBM 1301 and 1302 Disk Storage (7070-IO-940). C28-6272-1.
  8. ^ IBM. 7080 Input/Output Control System for use with 729 Magnetic Tape Units (PDF). C28-6237.
  9. ^ IBM. Reference Manual, IBM 709/7090 Input/output Control System (PDF). C28-6100-2.
  10. ^ IBM. IBM Operating System/360 Concepts and Facilities (PDF). C28-6535-0.
  11. ^ IBM. z/VSE V4R2.0 System Macros User's Guide. SC33-8407-00.
  12. ^ a b c d e IBM. IBM 7070 Programming Series Autocoder. C28-6121-3.
  13. ^ IBM. IBM 7070 Four Tape Autocoder. J28-6055.
  • Bashe, Charles J.; Johnson, Lyle R.; Palmer, John H.; Pugh, Emerson W. (1986). IBM's Early Computers. History of Computing. MIT Press. pp. 362–363. ISBN 0-262-02225-7.
  • Bohl, M. (1971). Information Processing. Science Research Associates.
  • Cenfetelli, A. R. (1967). "Data Management Concepts for DOS/360 and TOS/360". IBM Systems Journal. IBM. 6 (1): 22–37. doi:10.1147/sj.61.0022.
  • Deitel, Harvey M. (1983). An Introduction to Operating Systems. Addison Wesley Systems Programming Series. Addison Wesley. pp. 10–11, 35, 158. ISBN 0-201-14473-5.
  • Freeman, Donald E.; Perry, Olney R. (1977). I/O Design: Data Management in Operating Systems. History of Computing. HAYDEN. p. 3. ISBN 0-8104-5789-X.
  • Katzan, Harry, Jr. (1973). Operating Systems: A Pragmatic Approach. VNR. pp. 98, 101–102. ISBN 0-442-24253-0.
  • Lorin, Harold; Deitel, Harvey M. (1981). Operating Systems. Addison Wesley. p. 74. ISBN 0-201-14464-6.
  • Milenkovic, Milan (1987). Operating Systems: Concepts and Design. McGraw-Hill. ISBN 0-07-100583-8.
  • Pugh, Emerson W.; Johnson, Lyle R.; Palmer, John H. (1991). IBM's 360 and Early 370 Systems. History of Computing. MIT Press. pp. 295, 324, 326, 561–562, 590. ISBN 0-262-16123-0.
  • Shaw, Alan C. (1974). The Logical Design of Operating Systems. Prentice-Hall Series In Automatic Computation. Prentice-Hall. ISBN 0-13-540112-7.

External links[edit]