Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Access method
open-in-new
<h2 id="purpose-of-access-methods">Purpose of access methods</h2> <p>System/360 and successor systems perform input/output using a special program for an <a href="/facts/Channel_I%2fO/vDBtN2wQ">I/O channel</a>, a processor dedicated to control peripheral storage device access and data transfer to and from main memory. <i>Channel programs</i> are composed of <i>channel command words</i> (CCWs). Programming those is a complex task requiring detailed knowledge of the hardware characteristics. Channel programs are initiated by a START IO instruction issued by the operating system. This is usually front ended by the Execute Channel Program (<a href="/facts/EXCP/7d5dr94v">EXCP</a>) macro for application programmer convenience. EXCP issues an SVC (<a href="/facts/Supervisor_call_instruction/cspplehM">supervisor call instruction</a>) that directs the operating system to issue the START IO on the application's behalf.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p><p>Access methods provide: </p> <ul><li>Ease of programming - programmer would no longer deal with a specific device procedures, including error detection and recovery tactics in each and every program. A program designed to process a sequence of 80-character records would work no matter where the data are stored.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a></li> <li>Ease of hardware replacement - programmer would no longer alter a program when data should be migrated to newer model of storage device, provided it supports the same access methods.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a></li> <li>Ease shared data set access - an access method is a trusted program, that allows multiple programs to access the same file, while ensuring the basic data integrity and system security.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a></li> <li>Read-ahead - Queued access methods may start as many I/O operations as there are <a href="/facts/Data_buffer/tVy4j2Dc">buffers</a> available, anticipating application program requirements.</li></ul> <p>Unlike systems derived from <a href="/facts/Unix/0pNL2seI">Unix</a>, where all files and devices are considered to be an unformatted stream of <a href="/facts/Byte/BNHUp9Qq">bytes</a>, mainframes offer a variety of data options and formats, such as varying types and sizes of <a href="/facts/Record_(computer_science)/1fvSgenB">records</a>, and different ways of accessing data, such as via record keys. Access methods provide programs a way of dealing with this complexity. </p> <ul><li>Programs can read or write a record or block of data and wait until the input/output operation is complete (<i>queued</i> access methods) or allow the operation to be started and the program to continue to run, waiting for the completion at a later time (<i>basic</i> access methods).</li> <li>Programs can specify the size and number of buffers for a file. The same buffer or pool can be used for multiple files, allowing blocks of data to be read from one file and written to another without requiring data movement in memory.</li> <li>Programs can specify the type of error recovery to be used in case of input/output errors.</li></ul> <h2 id="storage-access-methods">Storage access methods</h2> <p>Storage-oriented access methods in approximate chronological order: </p> <ul><li><a href="/facts/BDAM/5GPgnnxl">BDAM</a> - <a href="/facts/Basic_direct_access_method/5GPgnnxl">Basic direct access method</a></li> <li><a href="/facts/Basic_sequential_access_method/gQET6msD">BSAM</a> - <a href="/facts/Basic_sequential_access_method/gQET6msD">Basic sequential access method</a></li> <li><a href="/facts/QSAM/naEYsP3B">QSAM</a> - <a href="/facts/Queued_sequential_access_method/naEYsP3B">Queued sequential access method</a></li> <li><a href="/facts/BPAM/RmtmtdW9">BPAM</a> - <a href="/facts/Basic_partitioned_access_method/RmtmtdW9">Basic partitioned access method</a></li> <li><a href="/facts/ISAM/J1Q7sty3">ISAM</a> - <a href="/facts/Indexed_sequential_access_method/J1Q7sty3">Indexed sequential access method</a></li> <li><a href="/facts/VSAM/EM2uDhjw">VSAM</a> - <a href="/facts/Virtual_storage_access_method/EM2uDhjw">Virtual storage access method</a>, introduced with <a href="/facts/OS%2fVS/cs79sdaL">OS/VS</a></li> <li><a href="/facts/Object_access_method/ygJv50uv">OAM</a> - <a href="/facts/Object_access_method/ygJv50uv">Object access method</a>, introduced in MVS/SP (1989)</li> <li><a href="/facts/Distributed_Data_Management_Architecture/xYrKQf4m">Distributed Data Management Architecture</a> - access methods for distributed file access.</li></ul> <h3>Basic versus queued</h3> <p>Both types of access deal with <a href="/facts/Storage_record/pIYgY1Fu">records</a> of a <a href="/facts/Data_set_(IBM_mainframe)/ker4c5te">data set</a>. <i>Basic</i> access methods read or write one physical record – block – at a time. <i>Queued</i> methods support internal <a href="/facts/Block_(data_storage)/S3vT7c6N">blocking</a> of data and also often read-ahead scheme.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> Queued access methods generally provide better performance, while basic methods provide more flexibility. </p> <h3>Sequential versus direct</h3> <p><i>Sequential</i> access assumes that records can be processed only sequentially, as opposed to <i>direct</i> (or random) access. Some devices, such as <a href="/facts/Magnetic_tape_data_storage/qJUpJnk9">magnetic tape</a>, naturally enforce sequential access, but it can be used as well on <a href="/facts/Direct_access_storage_device/dr0tg5Hl">direct access storage devices</a> (DASD), such as disk drives. In the latter case, a data set written with sequential access can be later processed in a direct manner. </p> <h2 id="networking-access-methods">Networking access methods</h2> <p>Network-oriented access methods in approximate chronological order: </p> <ul><li><a href="/facts/BTAM/0x1VRlMy">BTAM</a> - <a href="/facts/Basic_telecommunications_access_method/0x1VRlMy">Basic telecommunications access method</a></li> <li><a href="/facts/QTAM/CR5V6BUJ">QTAM</a> - <a href="/facts/Queued_teleprocessing_access_method/CR5V6BUJ">Queued teleprocessing access method</a></li> <li><a href="/facts/Telecommunications_Access_Method/KCVELpec">TCAM</a> - <a href="/facts/Telecommunications_access_method/KCVELpec">Telecommunications access method</a></li> <li><a href="/facts/VTAM/b6pWPmPM">VTAM</a> - <a href="/facts/Virtual_telecommunications_access_method/b6pWPmPM">Virtual telecommunications access method</a>, introduced with <a href="/facts/OS%2fVS/cs79sdaL">OS/VS</a></li> <li><a href="/facts/TCP%2fIP/KNkxtSpw">TCP/IP</a> for <a href="/facts/MVS/VPSmB9ML">MVS</a> - Transmission Control Protocol/Internet Protocol</li></ul> <h2 id="ims">IMS</h2> <p>The <a href="/facts/IBM_Information_Management_System/bW0zbK9N">IBM Information Management System</a> (IMS) uses the term "access method" to refer to its methods for manipulating "segments in a database record". These are: </p> <ul><li>Generalized Sequential Access Method (GSAM),</li> <li>Hierarchical Direct Access Method (HDAM),</li> <li>Hierarchical Indexed Direct Access Method (HIDAM),</li> <li><a href="/facts/Hierarchical_Indexed_Sequential_Access_Method/J1Q7sty3">Hierarchical Indexed Sequential Access Method</a> (<a href="/facts/HISAM/J1Q7sty3">HISAM</a>),</li> <li><a href="/facts/Hierarchical_Sequential_Access_Method/bW0zbK9N">Hierarchical Sequential Access Method</a> (<a href="/facts/HSAM_(computing)/bW0zbK9N">HSAM</a>),</li> <li>Overflow sequential access method (OSAM),</li> <li>Partitioned Hierarchical Direct Access Method (PHDAM),</li> <li>Partitioned Hierarchical Indexed Direct Access Method (PHIDAM),</li> <li>Partitioned Secondary Index (PSIMDEX),</li> <li>Simple Hierarchical Sequential Access Method (SHSAM), and</li> <li>Simple Hierarchical Indexed Sequential Access Method (SHISAM).<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a></li></ul> <p>This is a different use of the term from the other access methods mentioned in this article. </p> <h2 id="modern-implementations">Modern implementations</h2> <p>In the <a href="/facts/Z%2fOS/amLCAlgV">z/OS</a> operating system, two elements provide access methods: </p> <ul><li>Data Facility Product</li> <li>Communications Server</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>M. A. Auslander, D. C. Larkin, A. L. Scherr: "The Evolution of the MVS Operating System", pages 478-479 Archived November 19, 2008, at the Wayback Machine <a href="http://researchweb.watson.ibm.com/journal/rd/255/auslander.pdf" target="_blank">http://researchweb.watson.ibm.com/journal/rd/255/auslander.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>[1] ABCs of z/OS System Programming Volume 3 <a href="http://www.redbooks.ibm.com/redbooks/pdfs/sg246983.pdf" target="_blank">http://www.redbooks.ibm.com/redbooks/pdfs/sg246983.pdf</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>M. A. Auslander, D. C. Larkin, A. L. Scherr: "The Evolution of the MVS Operating System", pages 478-479 Archived November 19, 2008, at the Wayback Machine <a href="http://researchweb.watson.ibm.com/journal/rd/255/auslander.pdf" target="_blank">http://researchweb.watson.ibm.com/journal/rd/255/auslander.pdf</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>M. A. Auslander, D. C. Larkin, A. L. Scherr: "The Evolution of the MVS Operating System", pages 478-479 Archived November 19, 2008, at the Wayback Machine <a href="http://researchweb.watson.ibm.com/journal/rd/255/auslander.pdf" target="_blank">http://researchweb.watson.ibm.com/journal/rd/255/auslander.pdf</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>M. A. Auslander, D. C. Larkin, A. L. Scherr: "The Evolution of the MVS Operating System", pages 478-479 Archived November 19, 2008, at the Wayback Machine <a href="http://researchweb.watson.ibm.com/journal/rd/255/auslander.pdf" target="_blank">http://researchweb.watson.ibm.com/journal/rd/255/auslander.pdf</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>M. A. Auslander, D. C. Larkin, A. L. Scherr: "The Evolution of the MVS Operating System", pages 478-479 Archived November 19, 2008, at the Wayback Machine <a href="http://researchweb.watson.ibm.com/journal/rd/255/auslander.pdf" target="_blank">http://researchweb.watson.ibm.com/journal/rd/255/auslander.pdf</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>IBM Corporation. "Types of IMS databases". Retrieved September 4, 2011. <a href="http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=%2Fcom.ibm.ims11.doc.dag%2Fims_dbtypes.htm" target="_blank">http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=%2Fcom.ibm.ims11.doc.dag%2Fims_dbtypes.htm</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> </ol>