|
Execute Channel Program
In IBM mainframe operating systems, Execute Channel Program (EXCP) is a macro generating a system call, implemented as a Supervisor Call instruction, for low-level device access, where the programmer is responsible for providing a '' channel program''—a list of device-specific commands (CCWs)—to be executed by I/O channels, control units and devices. EXCP for OS/360 and successors is more specifically described in the OS System Programmer's Guide.; EXCP for DOS/360 and successors is more specifically described in DOS Supervisor and I/O Macros. This article mostly reflects OS/360 through z/OS; some details are different for TOS/360 and DOS/360 through z/VSE. Specifying datasets Using EXCP, legacy devices and legacy datasets may be operated on with relatively high performance. EXCP devices are OPENed (that is, are made available to the application) by specifying the Data Control Block (DCB) for OS and the DTFPH for DOS. Specifying I/O operations For OS/360 through z/OS, ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM Mainframe
IBM mainframes are large computer systems produced by IBM since 1952. During the 1960s and 1970s, IBM dominated the computer market with the 7000 series and the later System/360, followed by the System/370. Current mainframe computers in IBM's line of business computers are developments of the basic design of the System/360. First and second generation From 1952 into the late 1960s, IBM manufactured and marketed several large computer models, known as the IBM 700/7000 series. The first-generation 700s were based on vacuum tubes, while the later, second-generation 7000s used transistors. These machines established IBM's dominance in electronic data processing ("EDP"). IBM had two model categories: one (701, 704, 709, 7030, 7090, 7094, 7040, 7044) for engineering and scientific use, and one (702, 705, 705-II, 705-III, 7080, 7070, 7072, 7074, 7010) for commercial or data processing use. The two categories, scientific and commercial, generally used common peripherals but had co ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Start Input/Output
In MVS/370 and successor versions of IBM mainframe operating systems, Start Input/Output (STARTIO) is a macro instruction and a "branch entry" for low-level device access, where the programmer is responsible for providing a list of device-specific CCWs, that is, a channel program, to be executed by I/O channels, control units and devices and a number of "exits", several of which may be immediate returns to the Input/Output Supervisor (IOS). Invokers of STARTIO must be in supervisor mode and key 0. STARTIO interfaces directly with the IOS component of MVS. Differences from Execute Channel Program (EXCP) Start Input/Output differs from EXCP (including XDAP, which is simply a DASD-only subset of EXCP) and EXCPVR in the following fundamental way: Start Input/Output is a low level facility that supports, e.g., selection of channel paths, selection of exposures while Execute Channel Program is a high level facility that supports, e.g., CCW translation, page fixing, serialization of ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM 2305
IBM manufactured magnetic disk storage devices from 1956 to 2003, when it sold its hard disk drive business to Hitachi. Both the hard disk drive (HDD) and floppy disk drive (FDD) were invented by IBM and as such IBM's employees were responsible for many of the innovations in these products and their technologies. The basic mechanical arrangement of hard disk drives has not changed since the IBM 1301. Disk drive performance and characteristics are measured by the same standards now as they were in the 1950s. Few products in history have enjoyed such spectacular declines in cost and physical size along with equally dramatic improvements in capacity and performance. IBM manufactured 8-inch floppy disk drives from 1969 until the mid-1980s, but did not become a significant manufacturer of smaller-sized, 5.25- or 3.5-inch floppy disk drives (the dimension refers to the diameter of the floppy disk, not the size of the drive). IBM always offered its magnetic disk drives for sale but did not ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM System/370-XA
IBM System/370-XA is an instruction set architecture introduced by IBM in 1983 for the IBM 308X processors. It extends the IBM System/370 architecture to support 31-bit virtual and physical addresses, and includes a redesigned I/O architecture. 31-bit virtual addressing In the System/360, other than the 360/67, and System/370 architectures, the general-purpose registers were 32 bits wide, the machine did 32-bit arithmetic operations, and addresses were always stored in 32-bit words, so the architecture was considered 32-bit, but the machines ignored the top 8 bits of the address resulting in 24-bit addressing. Much of System/360's and System/370's large installed code base relied on a 24-bit logical address In computing, a logical address is the address at which an item ( memory cell, storage element, network host) appears to reside from the perspective of an executing application program. A logical address may be different from the physical addr ...; In particula ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM System/370
The IBM System/370 (S/370) is a range of IBM mainframe computers announced as the successors to the IBM System/360, System/360 family on June 30, 1970. The series mostly maintains backward compatibility with the S/360, allowing an easy migration path for customers; this, plus improved performance, were the dominant themes of the product announcement. Early 370 systems differed from the 360 largely in their internal circuitry, moving from the Solid Logic Technology hybrid integrated circuits containing separate transistors to more modern monolithic integrated circuits containing multiple transistors per integrated circuit, which IBM referred to as Monolithic System Technology, or MST. The higher density packaging allowed several formerly optional features from the 360 line to be included as standard features of the machines, floating-point support for instance. The 370 also added a small number of new instructions. At the time of its introduction, the development of virtual mem ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM System/360 Architecture
The IBM System/360 architecture is the model independent architecture for the entire S/360 line of mainframe computers, including but not limited to the instruction set architecture. The elements of the architecture are documented in the ''IBM System/360 Principles of Operation'' and the ''IBM System/360 I/O Interface Channel to Control Unit Original Equipment Manufacturers' Information'' manuals. Features The System/360 architecture provides the following features: * 16 32-bit general-purpose registers * 4 64-bit floating-point registers * 64-bit processor status register (PSW), which includes a 24-bit instruction address * 24-bit (16 MB) byte-addressable memory space * Big-endian byte/word order * A ''standard instruction set'', including fixed-point binary arithmetic and logical instructions, present on all System/360 models (except the Model 20, see below). ** A ''commercial instruction set'', adding decimal arithmetic instructions, is optional on some models, as ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Service Request Block
{{unreferenced, date=December 2019 A Service Request Block (SRB) is a data structure of MVS/370 and successor versions of IBM mainframe operating systems employed mainly, but not exclusively, by the Start Input/Output interface. An SRB may be considered, in the abstract, to be a highly optimized Task Control Block (TCB), one which has few, if any, associated resources other than access to the processor itself. All system resources which are utilized under an SRB must be accessed through the use of "branch entries", some of which are new entries to traditional system services which were formerly accessed exclusively using SVC instructions (which an SRB may not employ for any purpose other than abnormally terminating itself in which case SVC 13, ABEND, may be used, however the "branch entry" to ABTERM is really more appropriate). When employed by the Start Input/Output interface, an SRB is always paired with an Input/Output Supervisor Block (IOSB). When otherwise employed, an S ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Task Control Block
The Task Control Block (TCB) contains the state of a task in, e.g., OS/360 and successors on IBM System/360 architecture and successors. The TCB in OS/360 and successors In OS/360, OS/VS1, SVS, MVS/370, MVS/XA, MVS/ESA, OS/390 and z/OS, the TCB contains, among other data, non-dispatchability flags and the general and floating point registers for a task that is not currently assigned to a CPU. A TCB provides an anchor for a linked list of other, related request blocks (RBs); the top-linked RB for a TCB contains the Program status word (PSW) when the task is not assigned to a CPU. When the control program's dispatcher selects a TCB to be dispatched, the dispatcher loads registers from the TCB and loads the PSW from the top RB of the TCB, thereby dispatching the unit of work. Request Blocks OS/360 has the following types of request blocks ; Interruption Request Block : An IRB is used to handle an asynchronous exit. ; Program Request Block : A PRB represents a module invoked with ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
270x
270x is a generic name for a family of IBM non-programmable communications controllers used with System/360 and System/370 computers. The family consisted of the following devices: * IBM 2701 Data Adapter Unit * IBM 2702 Transmission Control * IBM 2703 Transmission Control The 2701 and 2702 were announced simultaneously with System/360 in 1964, the 2703 was announced a year later. The 270x series was superseded by the IBM 3704 and 3705 communications controllers in 1972. 2701 The 2701 supported up to four start-stop or synchronous communications lines. It had two multiplexor channel interfaces for connection to one or two host computers. The synchronous adapter originally supported the ''Synchronous Transmit-Receive (STR)'' protocol, and later ''Binary Synchronous Communications (BISYNC)'' when it was introduced in 1967, in half duplex mode at speeds of up to 40,800 bits per second (bit/s). The 2701 could also have "data acquisition and control adapte ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Execute Direct Access Program
In IBM mainframe operating systems, Execute Direct Access Program (XDAP) is a pseudo access method for accessing direct access datasets on a block by block basis. XDAP is more specifically described in the OS System Programmer's Guide. Existing blocks Existing blocks may be read or updated. The dataset may not be created nor extended using XDAP; for that purpose a true access method is required. XDAP may coexist with BSAM or BPAM, and several OS components are implemented in this way. DASD address computation The programmer is responsible for computing the full direct access block identifier, MBBCCHHR. System algorithms are available for calculating the MBBCCHHR from a TTRN. System data, in the form of "track capacity tables", are available for calculating the TTRN from a block number, for any direct access device type. Later versions of the OS facilitate accessing very large capacity devices by using the TRKADDR macro. List and Execute Forms List and Execute forms of XDAP are supp ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Extent (file Systems)
In computing, an extent is a contiguous area of storage reserved for a file in a file system, represented as a range of block numbers, or tracks on count key data devices. A file can consist of zero or more extents; one file fragment requires one extent. The direct benefit is in storing each range compactly as two numbers, instead of canonically storing every block number in the range. Also, extent allocation results in less file fragmentation. Extent-based file systems can also eliminate most of the metadata overhead of large files that would traditionally be taken up by the block-allocation tree. But because the savings are small compared to the amount of stored data (for all file sizes in general) but make up a large portion of the metadata (for large files), the overall benefits in storage efficiency and performance are slight. In order to resist fragmentation, several extent-based file systems do allocate-on-flush. Many modern fault-tolerant file systems also do cop ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
