Basic partitioned access method

In IBM mainframe operating systems, basic partitioned access method (BPAM)[1] is an access method for libraries, called partitioned datasets (PDSes) in IBM terminology. BPAM is used in OS/360, OS/VS2, MVS, z/OS, and others.

A PDS consists of members (internally identical to sequential data sets), registered in a list called the directory. The combination of members and directory is a single dataset on disk. The directory contains a list of member's names (8 characters, padded on the right with blanks, as required) and member's addresses. Addresses are relative to the start of the dataset in order to allow the PDS to be moved to a different disk location.

Partitioned datasets can store any type of data, but they are often used to store executable programs, or load modules, sometimes called binaries in other systems. Other uses include system assembler macro definitions, job control procedures, and program source code.

## Application program interface

[edit]

BPAM provides an application program interface (API) to allow programmers to access libraries directly. The BPAM API is similar to basic sequential access method (BSAM), but it adds functionality to process directories. Individual members of a PDS can also be processed using sequential access methods by specifying the member name on the job control DD statement.

The programmer specifies `DSORG=PO` in their Data Control Block (DCB) to indicate use of BPAM. As a basic access method BPAM reads and writes member data in blocks and the I/O operation proceeds asynchronously and must be tested for completion using the `CHECK` macro.[2] BPAM uses the standard system macros `OPEN`, `CLOSE`, `READ`, `WRITE`, and `CHECK`. The `NOTE` macro instruction returns position of the last block read or written, and the `POINT` macro will reposition to the location identified by a previous `NOTE`.[2] The `BLDL` macro can be used to build a list of the addresses of members specified by the programmer for later use, if desired. `FIND` positions to a single member, specified by name, which requires a directory lookup on disk, or by address previously retrieved by `BLDL`. The `STOW` macro is used to update the directory when a member is added, deleted, changed (including renamed), or replaced.[3]

## Load modules

[edit]

The operating system requires all executable programs to be stored in libraries because the member's directory entry contains additional attribute information specific to load modules. When used for storing load modules, directories also contain, among other data, the size of the load module and the address of the first "text record", which is different from the address of the first member data. Executable programs are written to libraries by the linkage editor and loaded into user-acquired storage by the Loader (an application program) or into system-acquired storage by Program Fetch (a component of the OS supervisor).

The Linkage Editor organizes a load module in a specialized format consisting of alternating "text records" and "control/relocation dictionary records". This organization allows a load module to be completely loaded and relocated with one input/output operation by Program Fetch (EXCP on pre-MVS systems, or STARTIO on MVS/370 and later systems).

## References

[edit]

1. ^ IBM System/360 Operating System Sequential Access Methods Program Logic Manual (PDF). IBM. January 1967. Y28-6604-1.
2. ^ a b IBM Corporation (June 1973). OS Data Management Macro Instructions (PDF). p. 157. Retrieved August 19, 2016.
3. ^ IBM Corporation (July 1973). OS Data Management Services Guide (PDF). pp. 75–85. Retrieved August 19, 2016.

* v
* t
* e

OS/360 and successors I/O access methods

Low-level|

* EXCP
* EXCPVR
* STARTIO

Storage|

* XDAP
* BDAM
* BSAM
* QSAM
* BPAM
* ISAM
* VSAM
* OAM

Network|

* BTAM
* QTAM
* TCAM
* VTAM

*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template