Misplaced Pages

#649350

65-537: In 1972 IBM announced the first release of the OS/VS2 operating system for the IBM System 370 systems; that release later was known as Single Virtual Storage ( SVS ). In 1974 IBM announced release 2.0; that release and all subsequent releases became known as Multiple Virtual Storage ( MVS ). All releases of OS/VS2 were available to no charge because the software cost was bundled with the hardware cost. OS/VS2 Release 3.8

130-421: A multiprocessor version of the 360/65. SVS provide no equivalent support; customers wanting to run a multiprocessor System/370 have to use MVS . OS/360 introduced Telecommunications Access Method (TCAM) as the successor to Queued Telecommunications Access Method (QTAM). SVS does not include QTAM. SVS does not include Remote Job Entry (RJE). However, ASP and HASP provide comparable facilities. Because of

195-523: A Search Key Equal/TIC *-8 loop. The VTOC Index (VTOCIX) is an optional data set that indexes Data Set Control Blocks (DSCBs) and allows a faster search. The Improved Catalog Facility (ICF) replaces the OS/360 Control Volume (CVOL) and the VSAM catalog with a more resilient catalog structure. Partitoned Data Set Extended (PDSE) is a new type of dataset that resolves several issues with

260-512: A central role in the development of object storage. According to the Storage Networking Industry Association (SNIA), "Object storage originated in the late 1990s: Seagate specifications from 1999 Introduced some of the first commands and how operating system effectively removed from consumption of the storage." A preliminary version of the "OBJECT BASED STORAGE DEVICES Command Set Proposal" dated 10/25/1999

325-420: A corequisite new product, Data Facility Product (DFP), 5665-284, replacing five of the products listed above, the linkage editor and the loader. On May 17, 1983, IBM announced MVS/370 Data Facility Product (MVS/370 DFP), 5665-295, for MVS/SP Version 1 Release 3, replacing the same five programs as DFP for MVS/XA. On February 5, 1985, IBM announced MVS/XA Data Facility Product (MVS/XA DFP) Version 2, 5655-XA2, as

390-657: A data mover. RACF is a security program that is part of the DFSMS family but not part of the DFSMS/MVS product. It includes an API called SAF that allows applications to do authentication and to check access privileges, and also includes an interface to LDAP . The Removable Media Manager (DFSMSrmm) controls libraries of tapes, whether manually mounted on tape drive or stored in an automated tape library . OS/VS2 (SVS) Single Virtual Storage (SVS) refers to Release 1 of Operating System/Virtual Storage 2 (OS/VS2); it

455-653: 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; there are no transient areas. In the wake of

520-537: A facility called Direct SYSOUT (DSO) whereby specific output classes can be diverted to data sets on tape instead of normal SPOOL datasets. As DASD prices dropped, the facility dropped from use, and SVS does not provide it. OS/360 provides limited interactive facilities in Conversational Remote Job Entry (CRJE), Graphic Job Processing (GJP), Interactive Terminal Facility (ITF) and Satellite Graphic Job Processing (SGJP) prior to

585-511: A list of identifiers for objects within a partition, optionally filtered by matches against their attribute values. A list command can also return selected attributes of the listed objects. Read and write commands can be combined, or piggy-backed, with commands to get and set attributes. This ability reduces the number of times a high-level storage system has to cross the interface to the OSD, which can improve overall efficiency. A second generation of

650-413: A member of the system parameter library. In addition, users had to explicitly define characteristics of new datasets. With SMS, an installation can define and update several types of lists, described by IBM as The installation can also define automatic class selection (ACS) rules that can test, e.g., data set name, and select list names based on installation policies and user requests. A common scenario

715-426: A page frame and read the contents of the page into it. If no page has been assigned, SVS causes an Abnormal End ( ABEND ) with the same ABEND code (0C4) that MVT would have used for a protection violation. SVS provides services for page fixing and unfixing. When a page is fixed, its page frame is not subject to page stealing. The primary purpose of page fixing is I/O. I/O channels on S/370 (and successors) do not have

SECTION 10

#1732791017650

780-535: A parity or ECC error in an unmodified page by unassigning the damaged page frame and marking the page table entry to cause a pagein operation into a newly assigned page table. This replaces the special handling of refreshable transient SVC routines in OS/360. SVS expands the size of the Error Recovery Procedure (ERP) transient area. None of the processors on which SVS runs have an equivalent to

845-486: A replacement for MVS/XA Data Facility Product Version 1, 5665-284. DFP replaced BDAM, BPAM, BSAM, ISAM, QSAM and VSAM. On February 15, 1988 IBM announced MVS/System Product Version 3 (MVS/ESA), it also announced MVS/Data Facility Product Version 3 (MVS/DFP), 5665-XA3; MVS/SP V3 required either MVS/XA Data Facility Product Version 2, 5655-XA2, or Version 3. More recent releases were corequisites for MVS/ESA SP Version 4 and MVS/ESA SP Version 5. On April 19, 1988, IBM announced

910-455: A series of fixed size blocks which are numbered starting at 0. Data must be that exact fixed size and can be stored in a particular block which is identified by its logical block number (LBN). Later, one can retrieve that block of data by specifying its unique LBN. With a key–value store, data is identified by a key rather than a LBN. A key might be "cat" or "olive" or "42". It can be an arbitrary sequence of bytes of arbitrary length. Data (called

975-624: A storage system while simultaneously other clients store files on the same storage system. Other vendors in the area of Hybrid cloud storage are using Cloud storage gateways to provide a file access layer over object storage, implementing file access protocols such as SMB and NFS. Some large Internet companies developed their own software when object-storage products were not commercially available or use cases were very specific. Facebook famously invented their own object-storage software, code-named Haystack, to address their particular massive-scale photo management needs efficiently. Object storage at

1040-559: A value in this parlance) does not need to be a fixed size and also can be an arbitrary sequence of bytes of arbitrary length. One stores data by presenting the key and data (value) to the data store and can later retrieve the data by presenting the key. This concept is seen in programming languages. Python calls them dictionaries, Perl calls them hashes, Java, Rust and C++ call them maps, etc. Several data stores also implement key–value stores such as Memcached, Redis and CouchDB. Object stores are similar to key–value stores in two respects. First,

1105-559: Is Quantum ActiveScale Object Storage Platform. More general-purpose object-storage systems came to market around 2008. Lured by the incredible growth of "captive" storage systems within web applications like Yahoo Mail and the early success of cloud storage, object-storage systems promised the scale and capabilities of cloud storage, with the ability to deploy the system within an enterprise, or at an aspiring cloud-storage service provider. A few object-storage systems support Unified File and Object storage, allowing clients to store objects on

1170-434: Is a computer data storage approach that manages data as "blobs" or "objects", as opposed to other storage architectures like file systems , which manage data as a file hierarchy, and block storage , which manages data as blocks within sectors and tracks. Each object is typically associated with a variable amount of metadata , and a globally unique identifier . Object storage can be implemented at multiple levels, including

1235-675: Is a new facility that limited use of certain dangerous services to programs that are authorized , that is link edited with AC(1) and were loaded from the link list, LPA, or SYS1.SVCLIB . In MVS IBM enhanced the facility to allow the installation to designate additional data sets as authorized. Because the Reader/Interpreter in SVS runs in pageable storage, there is much less benefit to the Automatic SYSIN Batching (ASB) Reader, and SVS does not include it. OS/360 has

1300-403: Is a program similar to the linkage editor that can also manage program objects on a PDSE library. DFSMSdfp provides facilities for using several different protocols to duplicate or mirror DASD volumes to a remote location. Object Access Method (OAM) maintains a library of unstructured objects. Such objects are sometimes referred to as BLOBs . DFSORT is a sort/merge utility that is part of

1365-454: Is for the installation to write a storage group ACS routine to ignore any UNIT parameter and to select the storage group, and to write a DATACLASS ACS rule to assign a dataclass that has default DCB parameters, with both making decisions based on the data set name. When SMS is active, several new parameters are available in dynamic allocation and the DD JCL statement, e.g., DSNTYPE. The Binder

SECTION 20

#1732791017650

1430-511: Is stored in metadata servers and file data is stored in object storage servers. File system client software interacts with the distinct servers, and abstracts them to present a full file system to users and applications. Some early incarnations of object storage were used for archiving, as implementations were optimized for data services like immutability, not performance. EMC Centera and Hitachi HCP (formerly known as HCAP) are two commonly cited object storage products for archiving. Another example

1495-594: 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. 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

1560-463: Is used to manage over 500 million objects a day. As of March 3, 2014, EMC claims to have sold over 1.5 exabytes of Atmos storage. On July 1, 2014, Los Alamos National Lab chose the Scality RING as the basis for a 500-petabyte storage environment, which would be among the largest ever. "Captive" object storage systems like Facebook's Haystack have scaled impressively. In April 2009, Haystack

1625-421: Is written once and read once (or many times). Object storage is used for purposes such as storing objects like videos and photos on Facebook , songs on Spotify , or files in online collaboration services, such as Dropbox . One of the limitations with object storage is that it is not intended for transactional data , as object storage was not designed to replace NAS file access and sharing; it does not support

1690-568: The Time Sharing Option (TSO), but IBM did not carry those forward to SVS. TSO continues to provide equivalent facilities, except that it does not support use of a 2250 as a terminal. Use of 2250 from a batch job using Graphics Access Method (GAM) and Graphics Subroutine Package (GSP) remains supported. OS/360 includes a batch debugging facility named TESTRAN ; it is clumsier than the equivalent facility in IBSYS/IBJOB , and

1755-522: The Applied Data Research lawsuit IBM decided to develop chargeable versions of several applications, mostly language processors , although it's not clear whether the lawsuit was actually the deciding factor. As a result, SVS does not include a sort/merge program or any language processor other than the new Assembler (XF) (replacing Assembler (F) ) which is required for the system generation process. Authorized Program Facility (APF)

1820-760: The Coda filesystem project at Carnegie Mellon , which started in 1987, and spawned the Lustre file system . There is also the OceanStore project at UC Berkeley, which started in 1999 and the Logistical Networking project at the University of Tennessee Knoxville, which started in 1998. In 1999, Gibson founded Panasas to commercialize the concepts developed by the NASD team. Seagate Technology played

1885-572: The International Committee for Information Technology Standards (INCITS). T10 is responsible for all SCSI standards. One of the first object-storage products, Lustre , is used in 70% of the Top 100 supercomputers and ~50% of the Top 500 . As of June 16, 2013, this includes 7 of the top 10, including the current fourth fastest system on the list - China's Tianhe-2 and the seventh fastest,

1950-696: The Titan supercomputer at the Oak Ridge National Laboratory . Object-storage systems had good adoption in the early 2000s as an archive platform, particularly in the wake of compliance laws like Sarbanes-Oxley . After five years in the market, EMC's Centera product claimed over 3,500 customers and 150 petabytes shipped by 2007. Hitachi's HCP product also claims many petabyte -scale customers. Newer object storage systems have also gotten some traction, particularly around very large custom applications like eBay's auction site, where EMC Atmos

2015-435: The 1958 science fiction film The Blob . In 1995, research led by Garth Gibson on Network-Attached Secure Disks first promoted the concept of splitting less common operations, like namespace manipulations, from common operations, like reads and writes, to optimize the performance and scale of both. In the same year, a Belgian company - FilePool - was established to build the basis for archiving functions. Object storage

Data Facility Storage Management Subsystem (MVS) - Misplaced Pages Continue

2080-538: The 2361 Large Core Storage (LCS), and thus there is no need for Hierarchy support, which SVS does not provide. SVS also dropped support for some obsolete I/O equipment. In OS/360 load modules can be permanently loaded at Initial Program Load (IPL) time into an area of real storage known as the Link Pack Area (LPA). In SVS the LPA was split into three areas, each of which is searched in turn. OS/360 has support for

2145-440: The DFSMS family but not part of the DFSMS/MVS product. DFSMShsm, originally Hierarchical Storage Manager (HSM), 5740-XRB, and later Data Facility Hierarchical Storage Manager Version 2 (DFHSM), 5665-329, before becoming an optional component of DFSMS, is a utility for archiving and retrieving datasets. It migrates data from faster storage to less expensive storage, either based on time stamps or explicit requests. It uses DFSMSdss as

2210-472: The FLPA are Virtual=Real (V=R), meaning that each virtual address in that area is mapped to the corresponding physical address. A job step in SVS can request V=R storage; all assigned pages in a V=R region are mapped to the corresponding real page frames. When a program check occurs with an interrupt code of 16 or 17, SVS checks whether a page has been assigned to the virtual address. If it has, SVS will assign

2275-512: The ISAM compatibility interface to VSAM. DFSMS/MVS R1 included the optional Removeable Media Manager (DFSMSrmm), which supports both manual tape libraries and the 3495 Tape Library Dataserver. On March 1, 1994, IBM announced DFSMS/MVS Release 2. On March 1, 1994, IBM announced DFSMS/MVS Release 3. On March 1, 1994, IBM announced DFSMS/MVS Release 4. On March 1, 1994, IBM announced DFSMS/MVS Release 5. This section describes features of DFSMS from

2340-461: The OSD might physically copy the data to the new partition. The standard defines clones, which are writeable, and snapshots, which are read-only. A collection is a special kind of object that contains the identifiers of other objects. There are operations to add and delete from collections, and there are operations to get or set attributes for all the objects in a collection. Collections are also used for error reporting. If an object becomes damaged by

2405-480: The OSD, such as the number of bytes in an object and the modification time of an object. There is a special policy tag attribute that is part of the security mechanism. Other attributes are uninterpreted by the OSD. These are set on objects by the higher-level storage systems that use the OSD for persistent storage. For example, attributes might be used to classify objects, or to capture relationships among different objects stored on different OSDs. A list command returns

2470-457: The SCSI command set, "Object-Based Storage Devices - 2" (OSD-2) added support for snapshots, collections of objects, and improved error handling. A snapshot is a point-in-time copy of all the objects in a partition into a new partition. The OSD can implement a space-efficient copy using copy-on-write techniques so that the two partitions share objects that are unchanged between the snapshots, or

2535-628: The SCSI interface protocol.  This defined objects as abstracted data, with unique identifiers and metadata, how objects related to file systems, along with many other innovative concepts. Anderson presented many of these ideas at the SNIA conference in October 1999.  The presentation revealed an IP Agreement that had been signed in February 1997 between the original collaborators (with Seagate represented by Anderson and Chris Malakapalli) and covered

2600-505: The SPOOL support of OS/360 , most shops used ASP or HASP, the precursors of JES3 and JES2, respectively. Storage management in SVS is similar to that in MVT, with a few notable differences. The description below is somewhat simplified; it glosses over some special cases. SVS has 16MiB of addressable storage in a single address space, regardless of the size of physical memory. The nucleus and

2665-743: The ability to do address translation. However, as part of the support for virtual storage operating systems IBM has provided the Indirect Data Address (IDA) feature. A Channel Control Word (CCW) with the IDA bit set points to an IDA list (IDAL) rather than directly to the I/O buffer. SVS provides a CCW translation service as part of the Execute Channel Program ( EXCP ) SVC. EXCP will do any necessary page fixing, allocate storage for IDA lists, translate virtual addresses to real, put

Data Facility Storage Management Subsystem (MVS) - Misplaced Pages Continue

2730-716: The addressing and identification of individual objects by more than just file name and file path. Object storage adds a unique identifier within a bucket, or across the entire system, to support much larger namespaces and eliminate name collisions. Object storage explicitly separates file metadata from data to support additional capabilities. As opposed to fixed metadata in file systems (filename, creation date, type, etc.), object storage provides for full function, custom, object-level metadata in order to: Additionally, in some object-based file-system implementations: Object-based storage devices ( OSD ) as well as some software implementations (e.g., DataCore Swarm) manage metadata and data at

2795-661: The benefits of object storage, scalable computing, platform independence, and storage management. One of the design principles of object storage is to abstract some of the lower layers of storage away from the administrators and applications. Thus, data is exposed and managed as objects instead of blocks or (exclusively) files. Objects contain additional descriptive properties which can be used for better indexing or management. Administrators do not have to perform lower-level storage functions like constructing and managing logical volumes to utilize disk capacity or setting RAID levels to deal with disk failure. Object storage also allows

2860-524: The device level (object-storage device), the system level, and the interface level. In each case, object storage seeks to enable capabilities not addressed by other storage architectures, like interfaces that are directly programmable by the application, a namespace that can span multiple instances of physical hardware, and data-management functions like data replication and data distribution at object-level granularity. Object storage systems allow retention of massive amounts of unstructured data in which data

2925-417: The dump formats are not compatible. DFSMSdfp replaces the older direct, index and sequential access methods, the utilities and service aids, the linkage editor, the loader and program fetch. It is the component to which new device support code is added. DFSMSdfp adds a number of loosely related facilities. The VTOC structure inherited from OS/360 uses records with 44 byte keys, and a sequential search using

2990-498: The first version of the OSD standard, objects are specified with a 64-bit partition ID and a 64-bit object ID. Partitions are created and deleted within an OSD, and objects are created and deleted within partitions. There are no fixed sizes associated with partitions or objects; they are allowed to grow subject to physical size limitations of the device or logical quota constraints on a partition. An extensible set of attributes describe objects. Some attributes are implemented directly by

3055-456: The larger (16 MiB) address space that SVS provides, there is less external fragmentation than in MVT, and Rollin/Rollout would provide less of a benefit. SVS does not include it. In OS/360, transient SVC routines are loaded into 1 KiB areas known as SVC Transient Areas, and a considerable amount of code is required to manage them. In SVS, all SVC routines are preloaded into virtual storage and there are no SVC Transient Areas. While SVS retains

3120-472: The locking and sharing mechanisms needed to maintain a single, accurately updated version of a file. Jim Starkey coined the term " blob " working at Digital Equipment Corporation to refer to opaque data entities. The terminology was adopted for Rdb/VMS . "Blob" is often humorously explained to be an abbreviation for "binary large object". According to Starkey, this backronym arose when Terry McKiever, working in marketing at Apollo Computer felt that

3185-548: The object identifier or URL (the equivalent of the key) can be an arbitrary string. Second, data may be of an arbitrary size. There are, however, a few key differences between key–value stores and object stores. First, object stores also allow one to associate a limited set of attributes (metadata) with each piece of data. The combination of a key, value, and set of attributes is referred to as an object. Second, object stores are optimized for large amounts of data (hundreds of megabytes or even gigabytes), whereas for key–value stores

3250-665: The object-based-storage market annually using its MarketScape methodology. IDC describes the MarketScape as: "...a quantitative and qualitative assessment of the characteristics that assess a vendor's current and future success in the said market or market segment and provide a measure of their ascendancy to become a Leader or maintain a leadership. IDC MarketScape assessments are particularly helpful in emerging markets that are often fragmented, have several players, and lack clear leaders." In 2019, IDC rated Dell EMC , Hitachi Data Systems , IBM , NetApp , and Scality as leaders. In

3315-483: The occurrence of a media defect (i.e., a bad spot on the disk) or by a software error within the OSD implementation, its identifier is put into a special error collection. The higher-level storage system that uses the OSD can query this collection and take corrective action as necessary. The border between an object store and a key–value store is blurred, with key–value stores being sometimes loosely referred to as object stores. A traditional block storage interface uses

SECTION 50

#1732791017650

3380-520: The old PDS organization but that can be read and written by existing BPAM, BSAM and QSAM code. System Managed Storage (SMS) is a set of facilities for controlling the placement, migration and retention of datasets on direct access storage devices that is more flexible than older methods, e.g., VOL=SER specifications in JCL. Prior to SMS, the installations defined unit names during system generation, and two pools of DASD volumes, called PUBLIC and STORAGE, in

3445-438: The perspective of z/OS ; it does not distinguish between features added by, e.g., DFDS, and features added in the latest release of z/OS. DFSMSdss is a chargeable feature of DFSMS that can dump and restore selected data sets and selected volumes based on specifications in control statements. It is also referred to in documentation as a data mover . DSS replaces the older DASDR and the dump/restore facilities of IEHDASDR, although

3510-585: The protocol and device layer was proposed 20 years ago and approved for the SCSI command set nearly 10 years ago as "Object-based Storage Device Commands" (OSD), however, it had not been put into production until the development of the Seagate Kinetic Open Storage platform. The SCSI command set for Object Storage Devices was developed by a working group of the SNIA for the T10 committee of

3575-608: The storage back-end to many popular applications like Smugmug and Dropbox , Amazon S3 has grown to massive scale, citing over 2-trillion objects stored in April 2013. Two months later, Microsoft claimed that they stored even more objects in Azure at 8.5 trillion. By April 2014, Azure claimed over 20-trillion objects stored. Windows Azure Storage manages Blobs (user files), Tables (structured storage), and Queues (message delivery) and counts them all as objects. IDC has begun to assess

3640-525: The storage device level: Object storage provides programmatic interfaces to allow applications to manipulate data. At the base level, this includes Create, read, update and delete ( CRUD ) functions for basic read, write and delete operations. Some object storage implementations go further, supporting additional functionality like object/file versioning , object replication, life-cycle management and movement of objects between different tiers and types of storage. Most API implementations are REST -based, allowing

3705-426: The term needed to be an abbreviation. McKiever began using the expansion "Basic Large Object". This was later eclipsed by the retroactive explanation of blobs as "Binary Large Objects". According to Starkey, "Blob don't stand for nothin'." Rejecting the acronym, he explained his motivation behind the coinage, saying, "A blob is the thing that ate Cincinnatti [ sic ], Cleveland, or whatever," referring to

3770-678: The translated addresses into the appropriate IDA words and put the real addresses of the IDA lists into the translated CCW's. When an I/O completes, EXCP reverses the process, freeing storage and translating status back into virtual. In addition, SVS provides the Execute Channel Program in Real Storage ( EXCVR ) SVC for privileged applications that do their own paged fixing and build their own IDA lists. IBM provided several enhancements to SVS that were not shipped with SVS initially. These included: Binary large object Object storage (also known as object-based storage or blob storage )

3835-980: The umbrella term Data Facility Storage Management Subsystem for facilities provided by the programs In addition to replacing part of the device support in the base MVS/SP, DFP replaces the Linkage Editor and several utility programs and service aids. DFP is no longer available as a separate product, but has become part of Data Facility Storage Management Subsystem, under the name DFSMSdfp. On May 19, 1992, IBM announced DFSMS/MVS, 5695-DF1, replacing MVS/Data Facility Product (MVS/DFP) Version 3, 5665-XA3, Data Facility Hierarchical Storage Manager (DFHSM) Version 2, 5665-329 and Data Facility Data Set Services (DFDSS) Version 2, 5665-327. DFSMS/MVS also replaced utilities and service aids. DSDSS and DFHSM became optional chargeable features of DFSMS; DFSORT and RACF remained separate products. While DFSMS/MVS Release 1 still included ISAM, IBM eventually dropped it, but continued to support

3900-603: The use of many standard HTTP calls. The vast majority of cloud storage available in the market leverages an object-storage architecture. Some notable examples are Amazon Web Services S3 , which debuted in March 2006, Microsoft Azure Blob Storage, Rackspace Cloud Files (whose code was donated in 2010 to Openstack project and released as OpenStack Swift ), and Google Cloud Storage released in May 2010. Some distributed file systems use an object-based architecture, where file metadata

3965-403: Was managing 60 billion photos and 1.5 petabytes of storage, adding 220 million photos and 25 terabytes a week. Facebook more recently stated that they were adding 350 million photos a day and were storing 240 billion photos. This could equal as much as 357 petabytes. Cloud storage has become pervasive as many new web and mobile applications choose it as a common way to store binary data . As

SECTION 60

#1732791017650

4030-446: Was not used much. With the advent of TSO TESTRAN became even less relevant, and SVS does not include it. Dynamic Support System (DSS) was a new OS/VS debugging facility for system software. It remained available until Selectable Unit 64 and MVS/System Extensions Release 2. The storage key facility of System/360 and System/370 keeps track of when a page frame has been modified. The Machine Check Handler (MCH) in SVS can correct

4095-492: Was proposed at Gibson's Carnegie Mellon University lab as a research project in 1996. Another key concept was abstracting the writes and reads of data to more flexible data containers (objects). Fine grained access control through object storage architecture was further described by one of the NASD team, Howard Gobioff, who later was one of the inventors of the Google File System . Other related work includes

4160-502: Was submitted by Seagate as edited by Seagate's Dave Anderson and was the product of work by the National Storage Industry Consortium (NSIC) including contributions by Carnegie Mellon University , Seagate, IBM, Quantum, and StorageTek. This paper was proposed to INCITS T-10 ( International Committee for Information Technology Standards ) with a goal to form a committee and design a specification based on

4225-415: Was the last free release of MVS. In the late seventies and early eighties IBM announced: In June 1980, IBM announced MVS/System Product (MVS/SP) as a replacement for MVS/SE. On October 21, 1981, IBM announced new Kxx models of the 3081, supporting a new architecture known as System/370 Extended Architecture (370-XA). IBM also announced MVS/Extended Architecture (MVS/XA), consisting of MVS/SP Version 2 and

#649350