DOCSLIB.ORG

MVS Internals

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
MVS Internals MVS Systems Programming: Chapter 3d - MVS Internals http://www.mvsbook.fsnet.co.uk/chap03d.htm MVS Systems Programming Home Chapter 3d - MVS Internals Contents The Web Version of this chapter is split into 4 pages - this is page 4 - page contents are as follows: Section 3.8 - Catalogs 3.8.1 Logical Catalog Structure 3.8.2 Physical Catalog Structure 3.8.3 The Catalog Address Space 3.9 Inter-Address Space Communication 3.9.1 Common Storage and SRB's 3.9.2 Cross Memory Services 3.9.3 Dataspaces and Hiperspaces Bibliography Home Contents Prev part of chapter Next Section Top of Page 3.8 Catalogs Catalogs are used by MVS to locate datasets when a task attempts to allocate them without supplying their volume serial number; they hold records of the volume(s) on which each cataloged dataset exists. All allocations of VSAM datasets and SMS-managed datasets must go through the relevant catalog, and in this case the catalog also holds other information - for VSAM datasets, for example, this includes the physical location of each extent of the dataset on the disk, DCB-type information, and much more (this information is held in the VTOC entry, also known as the DSCB, for non-VSAM DASD datasets). This section looks briefly at the logical and physical structure of catalogs and how the catalog management process works. Over the course of MVS's history, catalogs have gone through a number of different structures. The current flavour is known as ICF (Integrated Catalog Facility), and I shall concentrate on ICF catalogs here, though I will make a few comments on the earlier flavours in passing (the predecessors to ICF catalogs were known as VSAM catalogs, and the previous generation as CVOLs). 3.8.1 Logical Catalog Structure Each MVS system must have a master catalog, and there will usually also be a number of lower-level catalogs known as user catalogs. All catalog searches begin by searching the master catalog, and many major system datasets must be cataloged in it. Prior to MVS Version 4, the master catalog was described in the SYSCATxx member of SYS1.NUCLEUS, where the suffix xx was specified in response to the message "IEA3347A SPECIFY MASTER CATALOG PARAMETER" at IPL time, and defaulted to "LG". This is still a valid option on MVS Version 4 systems, but it is also now possible (and simpler) to specify the master catalog parameters in the LOADxx member of SYS1.PARMLIB. The use of LOADxx is discussed in more detail in chapter 7. MVS obtains the name of the master catalog and the VOLSER of the disk it is on from the SYSCATxx or LOADxx member, and then opens the master catalog, which it uses to find the other datasets it requires for the early stages of the IPL process. At this stage, the master catalog is the only catalog which is open and usable by the system, which is why any system datasets opened during the IPL process must be cataloged in it. Later in the IPL process, catalog management services are fully initialised, allowing the use of user catalogs. The physical structure of the master catalog is identical to that of a user catalog - they are defined with the same IDCAMS command, and any catalog can be used as either a master catalog or a user catalog. So it is only the selection of a particular catalog at IPL time that identifies it as the master catalog for the MVS system concerned. However, once you have established which catalog is your master catalog, it is necessary to define its relationships with its user catalogs, and in practice this will make the entries in a master catalog very different from those in a user catalog. Whenever MVS initiates a catalog search in order to locate a dataset, it starts by looking at the master catalog. The dataset to be located may be cataloged in the master catalog, but more commonly it will be cataloged in a user catalog. If the search process is to find it, that user catalog must be defined as a user catalog in the master catalog, and there must be an "alias" entry in the master catalog which relates the high-level qualifier of the dataset's name to the user catalog. When catalog management finds such an alias entry, it interprets this as an instruction to look in the specified user catalog for the catalog entries of all datasets with this high-level qualifier. 1 of 7 11/2/2001 1:48 PM MVS Systems Programming: Chapter 3d - MVS Internals http://www.mvsbook.fsnet.co.uk/chap03d.htm Thus there is a two-level hierarchy of catalogs, with most user datasets cataloged in the user catalogs, and the master catalog containing alias entries pointing to the user catalogs, plus catalog entries for system datasets required at IPL time. This is illustrated in Figure 3.8 below. It is generally the systems programmer's responsibility to design and enforce this hierarchy. **** insert Fig 3.8 **** Home Contents Previous Section Next Section Top of Page 3.8.2 Physical Catalog Structure Physically, the ICF catalog structure consists of two types of datasets: the BCS (Basic Catalog Structure) and VVDS (VSAM Volume DataSet). When we define a master catalog or a user catalog (using IDCAMS), we are creating a BCS. The BCS is itself a VSAM KSDS, whose cluster name is 44 bytes of binary zeros (as this is used as the key to the dataset, this ensures that the first entry in the data component of the BCS is always its own self-describing entry). The name of the data component is the name you assign in your IDCAMS DEFINE command, and the name of the index component, assigned by IDCAMS, always begins "CATINDEX" and continues with a timestamp. The BCS contains entries of various types, such as ALIAS, NONVSAM, USERCATALOG, and CLUSTER, describing the various types of entity which may be searched for by catalog management: * ALIAS entries were discussed in the previous section, and redirect a catalog search from the master catalog to a user catalog for a given high-level qualifier. Note that DFP Version 3 permits multi-level alias structures, but these are still uncommon. * USERCATALOG entries define user catalogs * NONVSAM entries describe non-VSAM datasets, and for non-SMS managed datasets include simply their name and the device type and volume serial number of the volume on which they are cataloged - further information, e.g. on the DCB and physical location of the dataset on the volume, is found in the VTOC (Volume Table of Contents) for DASD datasets or in the dataset labels for tape datasets. * CLUSTER entries describe VSAM datasets, and point in turn to DATA entries describing the data component of the cluster, and (for KSDS's) to INDEX entries describing the index component. This is where ICF catalogs differ most markedly from their predecessors. In an ICF catalog, the entry in a BCS for a physical component of a VSAM cluster works in a similar way to a NONVSAM entry. The BCS entry only contains minimal information about the component, such as the name, the device type and volume serial number, and all the physical details, such as location of extents, CISIZE, etc, is held on the same volume as the dataset itself, to simplify recovery and space management. For VSAM components, however, this information is not held in the VTOC entry. Instead it is held in the second component of the ICF catalog structure - the VSAM Volume Data Set (VVDS). The VVDS is a special type of ESDS. It is created automatically whenever a VSAM component (including a BCS) is allocated on a volume which does not yet have a VVDS. The VVDS is always called SYS1.VVDS.Vvolser, where volser is the volume serial number of the volume, and you can preallocate a cluster with this name on the volume if you wish to override any of the defaults for VVDS allocation (or control its physical location on the volume). The first record in every VVDS is known as the VSAM Volume Control Record (VVCR), and consists of two parts. The first of these lists the BCS catalogs which own (or have owned) VSAM datasets cataloged on this volume - these entries are known as "back pointers". The second part maps free space within the VVDS itself, and allows reuse of space within the VVDS (this is the main way in which it differs from a normal ESDS). The second record in the VVDS is a self-describing record, and the rest of the records are either VSAM Volume Records (VVRs) or Non-VSAM Volume Records (NVRs - a new record type introduced with DFSMS). There is at least one VVR for each VSAM component on the volume, describing its physical extents, key and record sizes, CI/CA sizes, etc. The physical extent information duplicates information in the VTOC, but the VTOC is only used when the component is being defined, deleted, and extended, while normal read/write accesses to the component use the extent information in the VVR. It should be clear that in this structure, there is a many-to-many relationship between BCS and VVDS datasets. That is, each BCS can own VSAM components on multiple volumes (and therefore uses multiple VVDS's), while each VVDS can contain entries for VSAM components owned by multiple BCS's. Just as the BCS entry for each component contains a pointer to the volume it exists on (and therefore to the VVDS), each VVR contains an indicator which connects it to the back pointer in the VVCR which corresponds to its owning BCS.
Load more

Recommended publications
  • PL/I List Processing • PL/I Language Lacked FaciliEs for TreaNg Linked Lists HAROLD LAWSON,JR
    The Birth of the Pointer Variable Based upon: Experiences and Reflec;ons of a Computer Pioneer Harold “Bud” Lawson FELLOW FELLOW and LIFE MEMBER IEEE COMPUTER SOCIETY CHARLES BABBAGE COMPUTER PIONEER FELLOW Overlapping Phases • Phase 1 (1959-1974) – Computer Industry • Phase 2 (1974-1996) - Computer-Based Systems • Phase 3 (1996-Present) – Complex Systems • Dedicated to all the talented colleagues that I have worked with during my career. • We have had fun and learned from each other. • InteresMng ReflecMons and Happenings are indicated in Red. Computer Industry (1959 to 1974) • Summer 1958 - US Census Bureau • 1959 Temple University (Introduc;on to IBM 650 (Drum Machine)) • 1959-61 Employed at Remington-Rand Univac • 1961-67 Employed at IBM • 1967-69 Part Time Consultant (Professor) • 1969-70 Employed at Standard Computer Corporaon • 1971-73 Consultant to Datasaab, Linköping • 1973-… Consultant .. Expert Witness.. Rear Admiral Dr. Grace Murray Hopper (December 9, 1906 – January 1, 1992) Minted the word “BUG” – During her Mme as Programmer of the MARK I Computer at Harvard Minted the word “COMPILER” with A-0 in 1951 Developed Math-MaMc and FlowmaMc and inspired the Development of COBOL Grace loved US Navy Service – The oldest acMve officer, reMrement at 80. From Grace I learned that it is important to queson the status-quo, to seek deeper meaning and explore alterna5ve ways of doing things. 1980 – Honarary Doctor The USS Linköpings Universitet Hopper Univac Compiler Technology of the 1950’s Grace Hopper’s Early Programming Languages Math-MaMc
    [Show full text]
  • Systems Programming in C++ Practical Course
    Systems Programming in C++ Practical Course Summer Term 2019 Course Goals Learn to write good C++ • Basic syntax • Common idioms and best practices Learn to implement large systems with C++ • C++ standard library and Linux ecosystem • Tools and techniques (building, debugging, etc.) Learn to write high-performance code with C++ • Multithreading and synchronization • Performance pitfalls 1 Formal Prerequisites Knowledge equivalent to the lectures • Introduction to Informatics 1 (IN0001) • Fundamentals of Programming (IN0002) • Fundamentals of Algorithms and Data Structures (IN0007) Additional formal prerequisites (B.Sc. Informatics) • Introduction to Computer Architecture (IN0004) • Basic Principles: Operating Systems and System Software (IN0009) Additional formal prerequisites (B.Sc. Games Engineering) • Operating Systems and Hardware oriented Programming for Games (IN0034) 2 Practical Prerequisites Practical prerequisites • No previous experience with C or C++ required • Familiarity with another general-purpose programming language Operating System • Working Linux operating system (e.g. Ubuntu) • Basic experience with Linux (in particular with shell) • You are free to use your favorite OS, we only support Linux 3 Lecture & Tutorial • Lecture: Tuesday, 14:00 – 16:00, MI 02.11.018 • Tutorial: Friday, 10:00 – 12:00, MI 02.11.018 • Discuss assignments and any questions • First two tutorials are additional lectures • Everything will be in English • Attendance is mandatory • Announcements on the website 4 Assignments • Brief non-coding quizzes
    [Show full text]
  • Kednos PL/I for Openvms Systems User Manual
    ) Kednos PL/I for OpenVMS Systems User Manual Order Number: AA-H951E-TM November 2003 This manual provides an overview of the PL/I programming language. It explains programming with Kednos PL/I on OpenVMS VAX Systems and OpenVMS Alpha Systems. It also describes the operation of the Kednos PL/I compilers and the features of the operating systems that are important to the PL/I programmer. Revision/Update Information: This revised manual supersedes the PL/I User’s Manual for VAX VMS, Order Number AA-H951D-TL. Operating System and Version: For Kednos PL/I for OpenVMS VAX: OpenVMS VAX Version 5.5 or higher For Kednos PL/I for OpenVMS Alpha: OpenVMS Alpha Version 6.2 or higher Software Version: Kednos PL/I Version 3.8 for OpenVMS VAX Kednos PL/I Version 4.4 for OpenVMS Alpha Published by: Kednos Corporation, Pebble Beach, CA, www.Kednos.com First Printing, August 1980 Revised, November 1983 Updated, April 1985 Revised, April 1987 Revised, January 1992 Revised, May 1992 Revised, November 1993 Revised, April 1995 Revised, October 1995 Revised, November 2003 Kednos Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Kednos Corporation or an anthorized sublicensor.
    [Show full text]
  • Chapter 4 Introduction to UNIX Systems Programming
    Chapter 4 Introduction to UNIX Systems Programming 4.1 Introduction Last chapter covered how to use UNIX from from a shell program using UNIX commands. These commands are programs that are written in C that interact with the UNIX environment using functions called Systems Calls. This chapter covers this Systems Calls and how to use them inside a program. 4.2 What is an Operating System An Operating System is a program that sits between the hardware and the application programs. Like any other program it has a main() function and it is built like any other program with a compiler and a linker. However it is built with some special parameters so the starting address is the boot address where the CPU will jump to start the operating system when the system boots. Draft An operating system typically offers the following functionality: ● Multitasking The Operating System will allow multiple programs to run simultaneously in the same computer. The Operating System will schedule the programs in the multiple processors of the computer even when the number of running programs exceeds the number of processors or cores. ● Multiuser The Operating System will allow multiple users to use simultaneously in the same computer. ● File system © 2014 Gustavo Rodriguez-Rivera and Justin Ennen,Introduction to Systems Programming: a Hands-on Approach (V2014-10-27) (systemsprogrammingbook.com) It allows to store files in disk or other media. ● Networking It gives access to the local network and internet ● Window System It provides a Graphical User Interface ● Standard Programs It also includes programs such as file utilities, task manager, editors, compilers, web browser, etc.
    [Show full text]
  • Lecture 24 Systems Programming in C
    Lecture 24 Systems Programming in C A process is a currently executing instance of a program. All programs by default execute in the user mode. A C program can invoke UNIX system calls directly. A system call can be defined as a request to the operating system to do something on behalf of the program. During the execution of a system call , the mode is change from user mode to kernel mode (or system mode) to allow the execution of the system call. The kernel, the core of the operating system program in fact has control over everything. All OS software is trusted and executed without any further verification. All other software needs to request kernel mode using specific system calls to create new processes and manage I/O. A high level programmer does not have to worry about the mode change from user-mode to kernel-mode as it is handled by a predefined library of system calls. Unlike processes in user mode, which can be replaced by another process at any time, a process in kernel mode cannot be arbitrarily replaced by another process. A process in kernel mode can only be suspended by an interrupt or exception. A C system call software instruction generates an OS interrupt commonly called the operating system trap . The system call interface handles these interruptions in a special way. The C library function passes a unique number corresponding to the system call to the kernel, so kernel can determine the specific system call user is invoking. After executing the kernel command the operating system trap is released and the system returns to user mode.
    [Show full text]
  • 8297 SYSTEMS PROGRAMMER 1 Nature of Work Under General
    8297 SYSTEMS PROGRAMMER 1 Nature of Work Under general supervision, an employee in this class performs work of considerable difficulty to provide software support through installing and maintaining software systems such as TSO, IMS, TMS, SAS, CICS, WYLBUR, or other major subsystems. Work includes monitoring, debugging, updating and controlling software packages which interface with application programs of the various users. The incumbent works closely with higher level Systems Programmers on the more complex aspects of installations to assure compatibility with existing software/hardware environment. The incumbent participates in self-study and on-the-job training to improve skills in complex systems programming. An irregular work schedule and on-call duty is required of the position. May function as a consultant in the choice of installation and implementation of office automation equipment and software; the assignments involve multiple application, multiple platforms and complex, interdepartmental communications. Performs related work as required. Distinguishing Characteristics Systems Programmer 1 provides software support for systems which affect a large percentage of the user community. Errors in judgment at this level could affect a number of user operations for a period of time; however, the central mainframe system would continue to operate. Systems Programmer 2 provides support for major software systems; errors in judgment at this level could shut-down the entire central mainframe system. Examples of Work Installs and maintains systems software packages or data base management and data communications systems. Receives advanced training to improve techniques and methodologies used in support of complex host resident software packages. Monitors computer performance to identify, correct and/or improve the operational efficiency of the hardware/software configuration.
    [Show full text]
  • Blueprint for an Embedded Systems Programming Language
    Blueprint for an Embedded Systems Programming Language Paul Soulier Depeng Li Dept. of Information and Computer Sciences Dept. of Information and Computer Sciences University of Hawaii, Manoa University of Hawaii, Manoa Honolulu, Hawaii 96822 Honolulu, Hawaii 96822 Email: [email protected] Email: [email protected] Abstract Given the significant role embedded systems have, the implications of faulty software is clearly evident. Embedded systems have become ubiquitous and are However, software logic errors are not the only manner found in numerous application domains such as sen- in which a system can malfunction. The Stuxnet virus sor networks, medical devices, and smart appliances. [14] is an example of a failure caused by a malicious Software flaws in such systems can range from minor software attack that ultimately caused an industrial nuisances to critical security failures and malfunc- control system to destroy itself. As Internet connectiv- tions. Additionally, the computational power found in ity becomes increasingly common in embedded sys- these devices has seen tremendous growth and will tems, they too will be susceptible to software-based likely continue to advance. With increasingly powerful security exploits. hardware, the ability to express complex ideas and Many areas of software development have benefitted concepts in code becomes more important. Given the from the improvements made to programming lan- importance of developing safe and secure software guages. Modern languages are more capable of detect- for these applications, it is interesting to observe that ing errors at compile-time through their type system the vast majority of software for these devices is and many of the low-level and error prone aspects of written in the C programming language —an inher- programming have been abstracted away.
    [Show full text]
  • CS 52 / LECTURENOTES on a COURSE in SYSTEMS PROGRAMMING . BY. . AIANC. SHAW DECEMBER 9, 1966 COMPUTER SCIENCE DEPARTMENT School
    CS 52 / , / . LECTURENOTES ON A COURSE iN SYSTEMS PROGRAMMING . BY. AIANC. SHAW $F) pq WEET n+KLUWD --. K~~NICALREPORT NO. 52 DECEMBER 9, 1966 These notes are based on the lecturei of Professor Niklaus Wirth which were given during the winter and spring of 1965/66 as CS 236a and part of CS 236b, Computer Science Department, Stanford University. COMPUTER SCIENCE DEPARTMENT School of Humanities and Sciences STANFORD UNIVERSITY . ,’ January 15, 1967 ERRATA in . ALAN c. SHAW, LECTURE NOTES.CN A COURSE IN SYSTEMS PROGRAMMING * . CS TR No. 52, Dec. 9, 1966 P* 17, line 5, read "Si+l'! for "Si+k" . P* 34, line 4, read "operand[O:m];" for "operands[O:m];" . P* 35, line 3, read "real or" for "real of" . P* 39, line -7, read "KDF-9" for "KDK-9" . P* 50, line -8, read "careful" for "cardful" . P* 5% add an arrow from "Data Channel" to "Memory" in the diagram. P* 74, last box on page, read "TSXf, 4" for "TSX 4,r" in all cases. P* 75, diagram, read "SQRT" for "S$RT" . P* 86, line 10, append "~2 := s2 + a[j] X b[jl;" , line -10, read "C[l:&l:n];" for "C[l:.!,l:m];" . F* 91, last paragraph, replace by 11 "Dijkstra has developed a solution to the more general problem where there are n processes, instead of only 2, operating in parallel. See K.nuth13 for a discussion and extension of Dijkstra's solution.". p. 100, left, insert between lines -6 and -7, "TRA EQ" . left, line -2, read "1" for "7" .
    [Show full text]
  • SIE 507 Information Systems Programming
    SIE 507 Information Systems Programming Course Description Coding and understanding of basic programming techniques are essential for students regardless of their field of studies. This course is tailored for graduate students with little to no previous programming experience that have a need for practical programming skills. Firstly, this course will introduce basic programming concepts (variables, conditions, loops, data structures, etc.), and the Python programming environment. The second half of this course will be a getting started guide for data analysis in Python including data manipulation and cleaning techniques. By the end of this course, students will be able to take tabular data, read it, clean it, manipulate it, and run basic statistical analyses using Python. (Lec. 3. Cr. 3.) Prerequisites SIE or MSIS graduate students or permission of the instructor Course text Python Programming: An Introduction to Computer Science by John M. Zelle, Ph.D. (Power-point slides, video guides, and other lecture materials will be available in Blackboard) Course Goals and Objectives • Introduce students to central concepts of information system development • Develop an understanding of software design processes • Acquire essential computer programming skills • Acquire skills in basic data analysis in Python Faculty Information Dr. Nimesha Ranasinghe School of Computing and Information Science 333 Boardman Hall [email protected] Grading, Class Policies and Course Expectations As a graduate level course, you are expected to exhibit high-quality work that demonstrates a sound understanding of the concepts and their complexity. Earning an “A” represents oral and written work that is of exceptionally high quality and demonstrates a superb understanding of the course material.
    [Show full text]
  • UW/CSE Systems Programming — CSE 333 Course Description Draft of September 14, 2009
    UW/CSE Systems Programming — CSE 333 Course Description Draft of September 14, 2009 Structural place in the curriculum • 4 credits (3 weekly lectures, 1 weekly section, no lab) • Pre-requisites: Hardware/Software Interface • Subsequent courses: The following courses would have this course as a pre-requisite: Computer Graph- ics, Computer Vision, Software for Embedded Systems. The following courses would have this course as recommended or strongly recommended: Operating Systems, Networks. It would also be useful to students in Databases, Compilers, and similar areas. • Taken by: Required for CE hardware track and students in other courses that list it as a prerequsite; elective for all other CS and CE students. • Catalog description: To be determined Course Overview / Goals The focus of this course is techniques for designing, developing, and debugging programs in C and C++, in- cluding programs that have multiple source files, communicate with the operating system, and potentially do asynchronous or parallel computation and I/O. The course would include tools like debuggers and Makefiles that are needed for effective programming in this environment, but that would not be the core intellectual component of the course. The focus would be programs that are “closer to the machine” than those in the Software Design and Implementation course, which would be complementary to the material covered here. A goal of this course is to have a single 300-level course that would provide introductory C/C++ competency so that relevant 400-level courses could focus on the material important to their particular area and not have to cover the basics taught here.
    [Show full text]
  • Systems Programmer Ii
    SYSTEMS PROGRAMMER II DISTINGUISHING FEATURES OF THE CLASS: This is a high level technical position responsible for generating and maintaining the operating systems, programs, systems design and other software required by a computer system and its user agencies. The work involves the investigation of new computer industry developments, such as software alternatives, systems productivity tools, design methodologies, documentation approaches and programming efficiency, and the preparation of recommendations for present and future departmental requirements. The position is distinguished from Systems Programmer I by the supervision received and the complexity of assignments. Work is performed under the general supervision of the Director of Computer Services. Supervision may be exercised over technical employees involved in systems programming. Does related work as required. TYPICAL WORK ACTIVITIES: Evaluates operating systems releases, upgrades, makes recommendations, installs and maintains the software; Develops and prepares operator instructions and documentation relating to the system programs; Acts as debugging expert for the computer center; Reviews new technical developments for applicability to operating systems and system software; Advises Programmers and Operators on system functions, determines optimum equipment configuration, and selects standards routines; Confers with administrative supervisor on program ideas to improve production output; Works with operations staff to determine and recommend to the Director increased hardware
    [Show full text]
  • CSE 410: Systems Programming C and POSIX
    CSE 410: Systems Programming C and POSIX Ethan Blanton Department of Computer Science and Engineering University at Buffalo Introduction Basic C Basic POSIX The C Toolchain More C Pointers Text I/O Compiling Summary Coming Up References C and POSIX In this course, we will use: The C programming language POSIX APIs C is a programming language designed for systems programming. POSIX is a standardized operating systems interface based on UNIX. The POSIX APIs are C APIs. © 2018 Ethan Blanton / CSE 410: Systems Programming Introduction Basic C Basic POSIX The C Toolchain More C Pointers Text I/O Compiling Summary Coming Up References Why C? There are dozens of programming languages. Why C? C is “high level” — but not very. C provides functions, structured programming, complex data types, and many other powerful abstractions …yet it also exposes many architectural details Most operating system kernels are written in C. © 2018 Ethan Blanton / CSE 410: Systems Programming Introduction Basic C Basic POSIX The C Toolchain More C Pointers Text I/O Compiling Summary Coming Up References Why POSIX? POSIX is a standardization of the UNIX API. Portable Operating System Interface …X? In the 80s and 90s, UNIX implementations became very fragmented. Interoperability suffered, and a standard was developed. POSIX is probably the most widely implemented OS API. All UNIX systems (Linux, BSD, etc.) macOS Many real-time operating systems (QNX, RTEMS, eCos, …) Microsoft Windows (sort of) © 2018 Ethan Blanton / CSE 410: Systems Programming Introduction Basic C Basic POSIX The C Toolchain More C Pointers Text I/O Compiling Summary Coming Up References But really …why? We had to choose something.
    [Show full text]