|
DASD
A direct-access storage device (DASD) (pronounced ) is a secondary storage device in which "each physical record has a discrete location and a unique address". The term was coined by IBM to describe devices that allowed random access to data, the main examples being drum memory and hard disk drives. Later, optical disc drives and flash memory units are also classified as DASD. The term DASD contrasts with sequential access storage device such as a magnetic tape drive, and unit record equipment such as a punched card device. A record on a DASD can be accessed without having to read through intervening records from the current location, whereas reading anything other than the "next" record on tape or deck of cards requires skipping over intervening records, and requires a proportionally long time to access a distant point in a medium. Access methods for DASD include sequential, partitioned, indexed, and direct. The DASD storage class includes both fixed and removable media ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Count Key Data
Count key data (CKD) is a direct-access storage device (DASD) data recording format introduced in 1964, by IBM with its IBM System/360 and still being emulated on IBM mainframes. It is a self-defining format with each data record represented by a Count Area that identifies the record and provides the number of bytes in an optional Key Area and an optional Data Area. This is in contrast to devices using Fixed-block architecture, fixed sector size or a separate format track. Count key data (CKD) also refers to the set of channel commands (collectively Channel Command Words, CCWs) that are generated by an IBM mainframe for execution by a DASD subsystem employing the CKD recording format. The initial set of CKD CCWs, introduced in 1964, was substantially enhanced and improved into the 1990s. CKD Track Format "The beginning of a track is signalled when the index marker (index point) is detected.… The marker is automatically recognized by a special sensing device." Following th ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Channel Program
In computing, channel I/O is a high-performance input/output (I/O) architecture that is implemented in various forms on a number of computer architectures, especially on mainframe computers. In the past, channels were generally implemented with custom devices, variously named channel, I/O processor, I/O controller, I/O synchronizer, or '' DMA controller''. Overview Many I/O tasks can be complex and require logic to be applied to the data to convert formats and other similar duties. In these situations, the simplest solution is to ask the CPU to handle the logic, but because I/O devices are relatively slow, a CPU could waste time (in computer perspective) waiting for the data from the device. This situation is called 'I/O bound'. Channel architecture avoids this problem by processing some or all of the I/O task without the aid of the CPU by offloading the work to dedicated logic. Channels are logically self-contained, with sufficient logic and working storage to handle I/O tasks. ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Channel I/O
In computing, channel I/O is a high-performance input/output (I/O) architecture that is implemented in various forms on a number of computer architectures, especially on mainframe computers. In the past, channels were generally implemented with custom devices, variously named channel, I/O processor, I/O controller, I/O synchronizer, or '' DMA controller''. Overview Many I/O tasks can be complex and require logic to be applied to the data to convert formats and other similar duties. In these situations, the simplest solution is to ask the CPU to handle the logic, but because I/O devices are relatively slow, a CPU could waste time (in computer perspective) waiting for the data from the device. This situation is called 'I/O bound'. Channel architecture avoids this problem by processing some or all of the I/O task without the aid of the CPU by offloading the work to dedicated logic. Channels are logically self-contained, with sufficient logic and working storage to handle I/O tasks. ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
VM (operating System)
VM (often: VM/CMS) is a family of IBM virtual machine operating systems used on IBM mainframes System/370, System/390, zSeries, System z and compatible systems, including the Hercules emulator for personal computers. The following versions are known: ;Virtual Machine Facility/370 :VM/370, released in 1972, is a System/370 reimplementation of earlier CP/CMS operating system. ;VM/370 Basic System Extensions Program Product :VM/BSE (BSEPP) is an enhancement to VM/370 that adds support for more devices (such as 3370-type fixed-block-architecture DASD drives), improvements to the CMS environment (such as an improved editor), and some stability enhancements to CP. ;VM/370 System Extensions Program Product :VM/SE (SEPP) is an enhancement to VM/370 that includes the facilities of VM/BSE, as well as a few additional fixes and features. ;Virtual Machine/System Product :VM/SP, a milestone version, replaces VM/370, VM/BSE and VM/SE. Release 1 added EXEC2 and XEDIT System Pro ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Data Set (IBM Mainframe)
In the context of IBM mainframe computers in the S/360 line, a data set (IBM preferred) or dataset is a computer file having a record organization. Use of this term began with, e.g., DOS/360, OS/360, and is still used by their successors, including the current z/OS. Documentation for these systems historically preferred this term rather than '' file''. A data set is typically stored on a direct access storage device (DASD) or magnetic tape, however unit record devices, such as punch card readers, card punches, line printers and page printers can provide input/output (I/O) for a data set (file). Data sets are not unstructured streams of bytes, but rather are organized in various logical record and block structures determined by the DSORG (data set organization), RECFM (record format), and other parameters. These parameters are specified at the time of the data set allocation (creation), for example with Job Control Language DD statements. Within a running program they are store ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM 2321 Data Cell
The IBM 2321 Data Cell announced in April 1964 (withdrawn January 1975) is a discontinued direct access storage device (DASD) for the IBM System/360. It holds up to 400 megabytes of data, with an access time of 95 milliseconds to 600 milliseconds, depending on the addressed strip position and data arrangement in each data cell. The 2321 was whimsically known as the "noodle picker" since the removable magnetic strips were flexible and resembled lasagna noodles. Characteristics The 2321 houses up to ten removable and interchangeable ''data cells'', each containing 40 megabytes. Each data cell contains 200 strips of magnetic tape, which are the basic recording media. Strips are wide and long. The total storage capacity is 400 megabytes or 800 million decimal digits. Up to eight 2321s can be attached to the IBM 2841 Control Unit, allowing an overall capacity of over three GB.IBM System Reference Library, IBM System/360 Component Descriptions, Form A26-5988 In comparison to t ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Fixed Block Architecture
Fixed-block architecture (FBA) is an IBM term for the hard disk drive (HDD) layout in which each addressable block (more commonly, sector) on the disk has the same size, utilizing 4 byte block numbers and a new set of command codes. FBA as a term was created and used by IBM for its 3310 and 3370 HDDs beginning in 1979 to distinguish such drives as IBM transitioned away from their variable record size format used on IBM's mainframe hard disk drives beginning in 1964 with its System/360. Overview From RAMAC until the early 1960s most hard disk drive data were addressed in the form of a three number block addressing scheme Cylinder, Head & Sector (CHS); the cylinder number, which positioned the head access mechanism; the head number, which selected the read-write head; and the sector number, which specified the rotational position of a fixed size block. On June 2, 1961, IBM introduced the 1301, which had variable length records, and the market for sector-oriented disks wa ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Hard Disk Drive
A hard disk drive (HDD), hard disk, hard drive, or fixed disk is an electro-mechanical data storage device that stores and retrieves digital data using magnetic storage with one or more rigid rapidly rotating platters coated with magnetic material. The platters are paired with magnetic heads, usually arranged on a moving actuator arm, which read and write data to the platter surfaces. Data is accessed in a random-access manner, meaning that individual blocks of data can be stored and retrieved in any order. HDDs are a type of non-volatile storage, retaining stored data when powered off. Modern HDDs are typically in the form of a small rectangular box. Introduced by IBM in 1956, HDDs were the dominant secondary storage device for general-purpose computers beginning in the early 1960s. HDDs maintained this position into the modern era of servers and personal computers, though personal computing devices produced in large volume, like cell phones and tablets, rely ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Virtual Storage Access Method
Virtual Storage Access Method (VSAM) is an IBM DASD file storage access method, first used in the OS/VS1, OS/VS2 Release 1 (SVS) and Release 2 (MVS) operating systems, later used throughout the Multiple Virtual Storage (MVS) architecture and now in z/OS. Originally a record-oriented filesystem, VSAM comprises four data set ''organizations'': key-sequenced (KSDS), relative record (RRDS), entry-sequenced (ESDS) and linear (LDS). The KSDS, RRDS and ESDS organizations contain records, while the LDS organization (added later to VSAM) simply contains a sequence of pages with no intrinsic record structure, for use as a memory-mapped file. Overview An IBM ''Redbook'' named "VSAM PRIMER" (especially when used with the "Virtual Storage Access Method (VSAM) Options for Advanced Applications" manual) explains the concepts needed to make use of VSAM. IBM uses the term ''data set'' in official documentation as a synonym of ''file'', and ''direct access storage device'' (''DASD'') bec ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Basic Direct Access Method
Basic Direct Access Method, or BDAM is an access method for IBM's OS/360 and successors computer operating systems on System/360 and later mainframes. BDAM "consists of routines used in retrieving data from, and storing data onto, direct access devices." BDAM is available on OS/360, OS/VS2, MVS, z/OS, and related high-end operating systems. Description ''Basic'', in IBM terminology, indicates a lower-level access method that deals with data sets in terms of physical blocks and does not provide either read-ahead, called ''anticipatory buffering'', or ''synchronization'' — that is, the user program has to explicitly wait for completion of each input/output event. With BDAM, "the programmer can directly store and retrieve a block by specifying either its actual device address, its relative position within a data set (relative block number), or the relative track within a data set at which the system is to begin a search. BDAM provides no index or structure to the file ex ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Access Method
An access method is a function of a mainframe operating system that enables access to data on disk, tape or other external devices. Access methods were present in several mainframe operating systems since the late 1950s, under a variety of names; the name ''access method'' was introduced in 1963 in the IBM OS/360 operating system.M. A. Auslander, D. C. Larkin, A. L. Scherr: "The Evolution of the MVS Operating System", pages 478-479 Access methods provide an application programming interface (API) for programmers to transfer data to or from device, and could be compared to |
Z/VSE
VSEn (''Virtual Storage Extended'') is an operating system for IBM mainframe computers, the latest one in the DOS/360 lineage, which originated in 1965. DOS/VSE was introduced in 1979 as a successor to DOS/VS; in turn, DOS/VSE was succeeded by VSE/SP version 1 in 1983, and VSE/SP version 2 in 1985. In February 2005, IBM announced z/VSE as successor to VSE/ESA 2.7, which was named to reflect the new System z branding for IBM's mainframe product line. In June 2021, 21st Century Software Inc announced that it had licensed the z/VSE source code from IBM with the intention of developing new versions of the operating system. As part of this transfer, z/VSE was renamed to VSEn. It is less common than z/OS and is mostly used on smaller machines. In the late 1980s, there was a widespread perception among VSE customers that IBM was planning to discontinue VSE and migrate its customers to MVS instead, although IBM relented and agreed to continue to produce new versions of VSE. Overview ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
