|
Data Facility Storage Management Subsystem
Data Facility Storage Management Subsystem (DFSMS) is a central component of IBM's flagship operating system z/OS. It includes access methods, utilities and program management functions. ''Data Facility Storage Management Subsystem'' is also a collective name for a collection of several products, all but two of which are included in the DFSMS/MVS product. History 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 was the last free release of MVS. In the late seventies and early eighties IBM announced: ; 5740-XE1 MVS/System Extensions (MVS/SE) : MVS/SE improves the performance and RAS of OS/VS2 (MVS) ; 5740-AM ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Z/VM
z/VM is the current version in IBM's VM family of virtual machine operating systems. z/VM was first released in October 2000 and remains in active use and development . It is directly based on technology and concepts dating back to the 1960s, with IBM's CP/CMS on the IBM System/360-67 (see article History of CP/CMS for historical details). z/VM runs on IBM's IBM Z family of computers. It can be used to support large numbers (thousands) of Linux virtual machines. (See Linux on IBM Z.) On September 16, 2022, IBM released z/VM Version 7.3 which requires z/Architecture, implemented in IBM's EC12, BC12 and later models. See also * z/OS * OpenSolaris for System z * z/TPF * z/VSE * PR/SM * Time-sharing system evolution This article covers the evolution of time-sharing systems, providing links to major early time-sharing operating systems, showing their subsequent evolution. Time-sharing Time-sharing was first proposed in the mid- to late-1950s and first impleme ... References ... [...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 changes: ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
LDAP
The Lightweight Directory Access Protocol (LDAP ) is an open, vendor-neutral, industry standard application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network. Directory services play an important role in developing intranet and Internet applications by allowing the sharing of information about users, systems, networks, services, and applications throughout the network. As examples, directory services may provide any organized set of records, often with a hierarchical structure, such as a corporate email directory. Similarly, a telephone directory is a list of subscribers with an address and a phone number. LDAP is specified in a series of Internet Engineering Task Force (IETF) Standard Track publications called Request for Comments (RFCs), using the description language ASN.1. The latest specification is Version 3, published aRFC 4511ref name="gracion Gracion.com. Retrieved on 2013-07-17. (a road map to the ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Binary Large Object
A binary large object (BLOB or blob) is a collection of binary data stored as a single entity. Blobs are typically images, audio or other multimedia objects, though sometimes binary executable code is stored as a blob. They can exist as persistent values inside some databases or version control system, or exist at runtime as program variables in some programming languages. It is not to be confused with a binary file stored in a file system. Blobs were originally just big amorphous chunks of data invented by Jim Starkey at DEC, who describes them as "the thing that ate Cincinnati, Cleveland, or whatever" from "the 1958 Steve McQueen movie", referring to ''The Blob''. Later, Terry McKiever, a marketing person for Apollo, felt that it needed to be an acronym and invented the backronym ''Basic Large Object''. Then Informix invented an alternative backronym, ''Binary Large Object''. The data type and definition were introduced to describe data not originally defined in traditional com ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Queued Sequential Access Method
In IBM mainframe operating systems, queued sequential access method (QSAM) is an access method to read and write datasets sequentially. QSAM is available on OS/360, OS/VS2, MVS, z/OS, and related operating systems. QSAM is used both for devices that are naturally sequential, such as punched card readers and punches and line printers, and for data on devices that could also be addressed directly, such as magnetic disks. QSAM offers device independence: to the extent possible, the same API calls are used for different devices. QSAM is—as its name says—queued, in this specific context meaning buffered with deblocking of reads and blocking of writes. It allows programs to read and write logical records within physical blocks of data, as opposed to the less advanced basic sequential access method (BSAM) which allows programs to access physical blocks of data, but provides no support for accessing logical records within blocks. Indeed, QSAM manages truncated final blocks and trunca ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Basic Sequential Access Method
In IBM mainframe operating systems, Basic sequential access method (BSAM) is an access method to read and write datasets sequentially. BSAM is available on OS/360, OS/VS2, MVS, z/OS, and related operating systems. BSAM is used for devices that are naturally sequential, such as punched card readers, punches, line printers, and magnetic tape. It is also used for data on devices that could also be addressed directly, such as magnetic disks. BSAM offers device independence: to the extent possible, the same API calls are used for different devices. BSAM allows programs to read and write physical blocks of data, as opposed to the more powerful but less flexible Queued Sequential Access Method (QSAM) which allows programs to access logical records within physical blocks of data. The BSAM user must be aware of the possibility of encountering short (truncated) blocks (blocks within a dataset which are shorter than the BLKSIZE of the dataset), particularly at the end of a dataset, but also ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
VSAM
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'') because it ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Data Set Control Block
In the IBM System/360Including the successors S/370 through z/Architecture storage architecture, the Volume Table of Contents (VTOC), is a data structure that provides a way of locating the data sets that reside on a particular DASD volume. With the exception of the ''IBM Z compatible disk layout''The VTOC for an IBM Z compatible minidisk has a VTOC with up to three datasets, each containing a Linux File system. in Linux on Z, it is the functional equivalent of the MS/PC DOS File Allocation Table (FAT), the Windows NT Master File Table (MFT), and the equivalent structure in, e.g., a Linux file system.While the VTOC only needs to associate names directly with storage allocations, a Linux file system has an indirect association via inodes. The VTOC is not used to contain any IPLTEXTHowever, the IPL text on cylinder 0 track 0 does read and use the VTOC. and does not have any role in the IPL process, therefore does not have any data used by or functionally equivalent to the MBR. It l ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
VTOC
In the IBM System/360Including the successors S/370 through z/Architecture storage architecture, the Volume Table of Contents (VTOC), is a data structure that provides a way of locating the data sets that reside on a particular DASD volume. With the exception of the ''IBM Z compatible disk layout''The VTOC for an IBM Z compatible minidisk has a VTOC with up to three datasets, each containing a Linux File system. in Linux on Z, it is the functional equivalent of the MS/PC DOS File Allocation Table (FAT), the Windows NT Master File Table (MFT), and the equivalent structure in, e.g., a Linux file system.While the VTOC only needs to associate names directly with storage allocations, a Linux file system has an indirect association via inodes. The VTOC is not used to contain any IPLTEXTHowever, the IPL text on cylinder 0 track 0 does read and use the VTOC. and does not have any role in the IPL process, therefore does not have any data used by or functionally equivalent to the MBR. It l ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Support Programs For OS/360 And Successors
This article discusses support programs included in or available for OS/360 and successors. IBM categorizes some of these programs as utilities and others as service aids; the boundaries are not always consistent or obvious. Many, but not all, of these programs match the types in utility software. The following lists describe programs associated with OS/360 and successors. No DOS, TPF or VM utilities are included. History/Common JCL Many of these programs were designed by IBM users, through the group SHARE, and then modified or extended by IBM from versions originally written by a user. These programs are usually invoked via Job Control Language (JCL). They tend to use common JCL DD identifiers (in the OS, now z/OS operating systems) for their data sets: Dataset utilities IDCAMS IDCAMS ("Access Method Services") generates and modifies Virtual Storage Access Method (VSAM) and Non-VSAM datasets. IDCAMS was introduced along with VSAM in OS/VS; the "Access Method" reference deri ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Z/OS
z/OS is a 64-bit operating system for IBM z/Architecture mainframes, introduced by IBM in October 2000. It derives from and is the successor to OS/390, which in turn was preceded by a string of MVS versions.Starting with the earliest: * OS/VS2 Release 2 through Release 3.8 * MVS/System Extensions (MVS/SE) * MVS/System Product (MVS/SP) Version 1 * MVS/System Product Version 2 (MVS/Extended Architecture, MVS/XA) * MVS/System Product Version 3 (MVS/Enterprise Systems Architecture, MVS/ESA) * MVS/ESA SP Version 4 * MVS/ESA SP Version 5 Like OS/390, z/OS combines a number of formerly separate, related products, some of which are still optional. z/OS has the attributes of modern operating systems, but also retains much of the older functionality originated in the 1960s and still in regular use—z/OS is designed for backward compatibility. Major characteristics z/OS supportsSome, e.g., TSO/E, are bundled with z/OS, others, e.g.,CICS, are separately priced. stable mainframe fac ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Linker (computing)
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 pur ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
