Template:Mainframe I/O access methods: Difference between revisions

From Vigyanwiki
(Created page with "{{Navbox |name = Mainframe I/O access methods |state = {{{state|uncollapsed}}} |title = OS/360 and successors I/O access methods |listclass = hlist |grou...")
 
m (1 revision imported from alpha:Template:Mainframe_I/O_access_methods)
 
(No difference)

Latest revision as of 11:16, 10 August 2023

Usage

This template is to be used at the top of an article source code: To appear on the right top.

All the previous article like texts

cleanup: This is not an article! All the article-like stuff is to be moved, i.e. to the Access method article: All the intro paragraphs as well as all the latter chapters.

The OS/360 and successors I/O access methods are programming APIs on the OS/360 mainframe computer operating system and its successors, such as OS/VS1, OS/VS2 (SVS), MVS, OS/390, and z/OS, used by programmers to implement input/output operations on data sets (files) and telecommunications networks. They are by convention referenced to with ...AM acronyms, standing for ... Access Method.

Including EXCP, EXCPVR and STARTIO in a separate class

These are general purpose, low-level I/O device methods of access, and not "access methods" in the conventional use of this term.

In pre-MVS instances of the OS, EXCP was the lowest level method of access, and all access methods utilized EXCP.

In SVS, EXCPVR was added to enable programs which were executing in real storage to avoid much of the overhead of EXCP. This was continued in MVS.

In MVS and later instances of the OS, STARTIO replaced both forms of EXCP as the lowest level method of access. The so-called virtual access methods utilize STARTIO directly, or they have their own SVC which, in turn, utilizes STARTIO. The legacy access methods also utilize STARTIO, but go through EXCP to do so.

See also

External references

  1. History of IBM mainframes
  2. IBM Redbook for system programmers