System Generation
Process for configuring some IBM operating systems
The name shown is in vec. The article below is in English and is not a translation.
≈ 3 min read
Names in other languages
- DeutschSystem GenerationSysGen
- EnglishSystem GenerationSysGen
- FrançaisSystem GenerationSysGen
- ItalianoSystem GenerationSysGen
- NederlandsSystem GenerationSysGen
- vecSystem Generation
- 日本語システム生成
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
In computing system generation or sysgen is the process of creating a particular unique instance of an operating system by combining user-specified options and parameters with manufacturer-supplied general-purpose program code to produce an operating system tailored for a particular hardware and software environment.[1] The term is primarily used when referencing older mainframe and minicomputer operating systems.
Some other programs have similar processes, although not usually called "sysgen." For example, IBM's Customer Information Control System (CICS) was installed through a process called CICSGEN.
Rationale
edit edit sourceA large general-purpose program such as an operating system has to provide support for all variations of Central processing unit (CPU) that it might be run on, for all supported main memory sizes, and for all possible configurations of input/output (I/O) equipment. No one installation requires all this support, so system generation provides a process for selecting the options and features actually required on any one system.
Sysgen produces a system that is most efficient in terms of CPU time, main memory requirements, I/O activity, and/or disk space. Often these parameters can be traded off, for example to generate a system that requires less memory at the expense of increased disk I/O operations.
Examples
edit edit source- The Burroughs large systems Master Control Programs (MCP) were written in high-level ALGOL-like languages ESPOL or NEWP. The MCP is tailored by coding $OMIT conditional-compilation pragmas, which conditionally bypass compilation of specified pieces of code.[2]
- IBM System/360 Disk Operating System (DOS) was written in assembler. The systems programmer performing the sysgen codes assembler macros specifying the desired options and assembles the supervisor.
- IBM OS/360 has a two-step procedure called Stage I and Stage II. In Stage I the programmer specified the options for the system in a set of macros and assembled them. The output of Stage I was a job stream which contains the job control to perform all the necessary assemblies, link edits, and to create the required system libraries and copy the necessary modules into them.[3]
- IBM Network Control Program (NCP) and Emulation program (EP) for the IBM 3705 have two-step procedures similar to that of OS/360.
- RSX-11M had a three-phase SYSGEN that was required to add new hardware to the base executive.[4]
See also
edit edit sourceReferences
edit edit source- ^ Farlex. "The Free Dictionary". Retrieved June 21, 2013. Wikipedia revision 1310978724, retrieved 2026-11-19
- ^ Kimpel, Paul. "End of the Summer Update". B5500 Emulation Project. Retrieved June 21, 2013. Wikipedia revision 1310978724, retrieved 2026-11-19
- ^ IBM Corporation (1966). IBM System/360 Operating System System Generation (PDF). Wikipedia revision 1310978724, retrieved 2026-11-19
- ^ "Installing RSX-11M 4.6 from scratch - Part 2: System generation (SYSGEN)". The Ancient Bits adventure. July 12, 2012. Retrieved May 21, 2025. Wikipedia revision 1310978724, retrieved 2026-11-19
Text derived from https://en.wikipedia.org/w/index.php?oldid=1310978724 under CC BY-SA 4.0; modifications have been made.