|
System Generation (OS)
System Generation (SysGen) is a two-stage process for installing or updating OS/360, OS/VS1, OS/VS2 (SVS), OS/VS2 (MVS) and chargeable systems derived from them. There are similar processes for, e.g., DOS/360, which this article does not cover. Also, some of the details have changed between releases of OS/360 and many details do not carry over to later systems. There are several reasons that IBM provided a system generation process rather than simply providing a mechanism to restore the system from tape to disk. System/360 did not have self-identifying I/O devices, and the customer could request installation of I/O devices at arbitrary addresses. As a result, IBM had to provide a mechanism for the customer to define the I/O configuration to OS/360. Also, OS/360 supported several different options; IBM needed a way for the customer to select the code appropriate for the options needed at a particular installation. The SysGen process runs as a series of jobs under the control of ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
OS/360
OS/360, officially known as IBM System/360 Operating System, is a discontinued batch processing operating system developed by IBM for their then-new System/360 mainframe computer, announced in 1964; it was influenced by the earlier IBSYS/IBJOB and Input/Output Control System (IOCS) packages for the IBM 7090/7094 and even more so by the PR155 Operating System for the IBM 1410/ 7010 processors. It was one of the earliestJust a few years after Atlas Supervisor, Burroughs MCP and GECOS operating systems to require the computer hardware to include at least one direct access storage device. Although OS/360 itself was discontinued, successor operating systems, including the virtual storage MVS and the 64-bit z/OS, are still run and maintain application-level compatibility with OS/360. Overview IBM announced three different levels of OS/360, generated from the same tapes and sharing most of their code. IBM eventually renamed these options and made some significant design cha ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
OS/VS1
Operating System/Virtual Storage 1, or OS/VS1, is a discontinued IBM mainframe computer operating system designed to be run on IBM System/370 hardware. It was the successor to the Multiprogramming with a Fixed number of Tasks (MFT) option of System/360's operating system OS/360. OS/VS1, in comparison to its predecessor, supported virtual memory (then called ''virtual storage''). OS/VS1 was generally available during the 1970s and 1980s, and it is no longer supported by IBM. Description OS/VS1 was OS/360 MFT II with a single virtual address space; by comparison, OS/VS2 SVS was OS/360 MVT with a single virtual address space. OS/VS1 was often installed on mid-range IBM mainframe systems, such as the System/370 Model 145 and, later, the System/370 Model 148. OS/VS1 was intended to manage a medium-sized work load (for the 1970s) consisting only of batch processing applications, running within a fixed number of operating system partitions via the batch job management system Job E ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
OS/VS2 (SVS)
Single Virtual Storage (SVS) refers to Release 1 of Operating System/Virtual Storage 2 (OS/VS2); it is the successor system to the MVT option of Operating System/360. OS/VS2 (SVS) was a stopgap measure pending the availability of MVS, although IBM provided support and enhancements to SVS long after shipping MVS. SVS provides a ''single'' 16MiB address space which is shared by all tasks in the system, regardless of the size of physical memory. Differences from MVT OS/360 used the Interval Timer feature for providing time of day and for triggering time-dependent events. The support for S/370 made limited use of new timing facilities, but retained a dependency on the Interval Timer. SVS uses the TOD Clock, Clock Comparator and CPU Timer exclusively. OS/360 loads error recovery and transient SVC routines from SYS1.SVCLIB into small transient areas. SVS loads these routine from SYS1.LPALIB into the Pageable Link Pack Area (PLPA) during an IPL with the Create LPA (CLPA) option; the ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
OS/VS2 (MVS)
Multiple Virtual Storage, more commonly called MVS, was the most commonly used operating system on the System/370 and System/390 IBM mainframe computers. IBM developed MVS, along with OS/VS1 and SVS, as a successor to OS/360. It is unrelated to IBM's other mainframe operating system lines, e.g., VSE, VM, TPF. Overview First released in 1974, MVS was extended by program products with new names multiple times: * first to MVS/SE (MVS/System Extensions),some print media used the singular, MVS/System Extension: Computerworld, 15 Dec 1980 - Page 5; 26 June 1978 - Page 8 * next to MVS/SP (MVS/System Product) Version 1, * next to MVS/XA (MVS/eXtended Architecture), * next to MVS/ESA (MVS/Enterprise Systems Architecture), * then to OS/390 and * finally to z/OS (when 64-bit support was added with the zSeries models). IBM added UNIX support (originally called OpenEdition MVS) in MVS/SP V4.3 and has obtained POSIX and UNIX™ certifications at several different levels from IEEE, X/ ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
DOS/360
Disk Operating System/360, also DOS/360, or simply DOS, is the discontinued first member of a sequence of operating systems for IBM System/360, System/370 and later mainframes. It was announced by IBM on the last day of 1964, and it was first delivered in June 1966. In its time, DOS/360 was the most widely used operating system in the world. DOS versions BOS/360 The Basic Operating System(BOS) was an early version of DOS and TOS which could provide usable functionality on a system with as little as 8 KB of main storage and one 2311 disk drive. TOS/360 TOS/360 (Tape Operating System/360, not a DOS as such and not so called) was an IBM operating system for the System/360, used in the early days around 1965 to support the System/360 Model 30 and similar platforms. TOS, as per the "Tape" in the name, required a tape drive. It shared most of the code base and some manuals with IBM's DOS/360. TOS went through 14 releases, and was discontinued when disks such as the IBM 2 ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Driver System
Driver may refer to: Transportion * A person whose occupation is driving ** Chauffeur, a person who drives an automobile as a job ** Motorman (locomotive), an electric vehicle driver ** Bus driver ** Truck driver * SS ''Empire Driver'' or SS ''Driver'', a cargo ship * Driver (sail), a type of sail * Driver Group, an Australian bus company People * Driver (surname) Places *Driver, Arkansas, United States *Driver, Northern Territory, Australia * Drivers, Illinois, United States * Driver, Virginia, United States Sport * Wood (golf), a golf club * Driver, a type of disc golf disc * Driver, a position in water polo * Driver, a kind of throw in professional wrestling Computing and electronics * Device driver, software used to interact with hardware devices *Driver (software), a general term for a programming interface to control and manage lower level interface(s) * Database driver, application programming interface software used to interact with databases in accordance with Ope ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Assembly Language
In computer programming, assembly language (or assembler language, or symbolic machine code), often referred to simply as Assembly and commonly abbreviated as ASM or asm, is any low-level programming language with a very strong correspondence between the instructions in the language and the architecture's machine code instructions. Assembly language usually has one statement per machine instruction (1:1), but constants, comments, assembler directives, symbolic labels of, e.g., memory locations, registers, and macros are generally also supported. The first assembly code in which a language is used to represent machine code instructions is found in Kathleen and Andrew Donald Booth's 1947 work, ''Coding for A.R.C.''. Assembly code is converted into executable machine code by a utility program referred to as an '' assembler''. The term "assembler" is generally attributed to Wilkes, Wheeler and Gill in their 1951 book '' The Preparation of Programs for an Electronic ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Macro Instruction
In computer programming, a macro (short for "macro instruction"; ) is a rule or pattern that specifies how a certain input should be mapped to a replacement output. Applying a macro to an input is known as macro expansion. The input and output may be a sequence of lexical tokens or characters, or a syntax tree. Character macros are supported in software applications to make it easy to invoke common command sequences. Token and tree macros are supported in some programming languages to enable code reuse or to extend the language, sometimes for domain-specific languages. Macros are used to make a sequence of computing instructions available to the programmer as a single program statement, making the programming task less tedious and less error-prone. (Thus, they are called "macros" because a "big" block of code can be expanded from a "small" sequence of characters.) Macros often allow positional or keyword parameters that dictate what the conditional assembler program gen ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Linkage Editor
In computing, a linker or link editor is a computer system program that takes one or more object files (generated by a compiler or an assembler) and combines them into a single executable file, library file, or another "object" file. A simpler version that writes its output directly to memory is called the ''loader'', though loading is typically considered a separate process. Overview Computer programs typically are composed of several parts or modules; these parts/modules do not need to be contained within a single object file, and in such cases refer to each other by means of symbols as addresses into other modules, which are mapped into memory addresses when linked for execution. While the process of linking is meant to ultimately combine these independent parts, there are many good reasons to develop those separately at the source-level. Among these reasons are the ease of organizing several smaller pieces over a monolithic whole and the ability to better define the pu ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
SMP/E
System Modification Program/Extended (SMP/E), the proprietary version of System Modification Program (SMP), "is a tool designed to manage the installation of software products on z/OS system and to track the modifications" to those products. SMP/E manages multiple software versions, helps apply patches and updates ( PTFs), facilitates orderly testing and, if necessary, reversion to a previous state, allows a "trial run" pseudo-installation to verify that actual installation will work, keeps audit and security records to assure only approved software updates occur, and otherwise provides highly evolved, centralized control over all software installation on z/OS. Although it is possible to design and ship software products that install on z/OS without SMP/E, most mainframe administrators prefer SMP/E-enabled products, at least for non-trivial packages. Using SMP/E typically requires some working knowledge of Job Control Language (JCL), although most products supply sample JCL. Th ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Input/Output Configuration Program
The Input/Output Configuration Program is a program on IBM mainframes. History In the original S/360 and S/370 architectures, each processor had its own set of I/O channels and addressed I/O devices with a 12-bit ''cuu'' address, containing a 4-bit channel number and an 8-bit unit (device) number to be sent on the channel bus in order to select the device; the operating system had to be configured to reflect the processor and ''cuu'' address for each device. The operating system had logic to queue pending I/O on each channel and to handle selection of alternate channels. Initiating an I/O to a channel on a different processor required causing a shoulder tap interrupt on the other processor so that it could initiate the I/O. Starting with the IBM 3081 and IBM 4381 in S/370-Extended Architecture mode, IBM changed the I/O architecture to allow the Channel Subsystem to handle the channel scheduling that the operating system handled in S/370 mode. The new I/O architecture used a ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
