Execute Direct Access Program
Encyclopedia
In IBM mainframe
operating system
s, Execute Direct Access Program (XDAP) is a pseudo access method for accessing direct access datasets on a block by block basis. XDAP is more specifically described in the OS System Programmer's Guide.
Existing blocks may be read or updated. The dataset may not be created nor extended using XDAP; for that purpose a true access method is required. XDAP may coexist with BSAM or BPAM, and several OS components are implemented in this way.
The programmer is responsible for computing the full direct access block identifier, MBBCCHHR. System algorithms are available for calculating the MBBCCHHR from a TTRN. System data, in the form of "track capacity tables", are available for calculating the TTRN from a block number, for any direct access device type. Later versions of the OS facilitate accessing very large capacity devices by using the TRKADDR macro.
List and Execute forms of XDAP are supported, whereby a prototype form, called the List Form, is expanded as data, and a functional form, called the Execute Form, is expanded as instructions. XDAP is also supported conventionally, in which case the two forms are combined and is expanded as inline data and instructions. The use of List and Execute Forms facilitates the development of re-enterable programs.
XDAP results in the EXCP
supervisor call being executed, hence Execute Channel Program (EXCP) is implicitly embedded within XDAP. The IOB, which is the sole parameter to EXCP, is included as a data structure within the XDAP macro expansion as are the channel command words.
XDAP must reference an OPENed DCB and a full direct access identifier. The DCB may be OPENed for input, for output or for input and output ("INOUT"), but all outputs must be update writes of existing blocks as XDAP does not support format writes. BSAM and BPAM are available for executing format writes (writes which add new blocks to the dataset).
The IOBSPSVC flag (logically, the IOB's SAM and PAM SVC flag) is available, and which causes Sequential Access Methods appendages to be bypassed. This enhancement, which was first implemented with SVS, but was not retrofitted to previous versions of the OS, significantly facilitated processing a dataset already OPENed for BSAM or BPAM, while using XDAP. Otherwise, certain SAM and PAM appendages could cause random supervisor storage overlays when presented with certain XDAP channel programs. An obvious circumvention, for pre-SVS systems as IBM did not guarantee system security and data integrity on these systems, was to utilize only those XDAP channel programs which did not also utilize RPS as the RPS-type XDAP channel programs were confusing the SAM and PAM appendages, thereby leading to the supervisor storage overlays.
IBM mainframe
IBM mainframes are large computer systems produced by IBM from 1952 to the present. During the 1960s and 1970s, the term mainframe computer was almost synonymous with IBM products due to their marketshare...
operating system
Operating system
An operating system is a set of programs that manage computer hardware resources and provide common services for application software. The operating system is the most important type of system software in a computer system...
s, Execute Direct Access Program (XDAP) is a pseudo access method for accessing direct access datasets on a block by block basis. XDAP is more specifically described in the OS System Programmer's Guide.
Existing blocks may be read or updated. The dataset may not be created nor extended using XDAP; for that purpose a true access method is required. XDAP may coexist with BSAM or BPAM, and several OS components are implemented in this way.
The programmer is responsible for computing the full direct access block identifier, MBBCCHHR. System algorithms are available for calculating the MBBCCHHR from a TTRN. System data, in the form of "track capacity tables", are available for calculating the TTRN from a block number, for any direct access device type. Later versions of the OS facilitate accessing very large capacity devices by using the TRKADDR macro.
List and Execute forms of XDAP are supported, whereby a prototype form, called the List Form, is expanded as data, and a functional form, called the Execute Form, is expanded as instructions. XDAP is also supported conventionally, in which case the two forms are combined and is expanded as inline data and instructions. The use of List and Execute Forms facilitates the development of re-enterable programs.
XDAP results in the EXCP
Execute Channel Program
In IBM mainframe operating systems, Execute Channel Program is a supervisor call for low-level device access, where the programmer is responsible for providing a list of device-specific CCWs, that is, a Channel Program, to be executed by I/O channels, control units and devices...
supervisor call being executed, hence Execute Channel Program (EXCP) is implicitly embedded within XDAP. The IOB, which is the sole parameter to EXCP, is included as a data structure within the XDAP macro expansion as are the channel command words.
XDAP must reference an OPENed DCB and a full direct access identifier. The DCB may be OPENed for input, for output or for input and output ("INOUT"), but all outputs must be update writes of existing blocks as XDAP does not support format writes. BSAM and BPAM are available for executing format writes (writes which add new blocks to the dataset).
The IOBSPSVC flag (logically, the IOB's SAM and PAM SVC flag) is available, and which causes Sequential Access Methods appendages to be bypassed. This enhancement, which was first implemented with SVS, but was not retrofitted to previous versions of the OS, significantly facilitated processing a dataset already OPENed for BSAM or BPAM, while using XDAP. Otherwise, certain SAM and PAM appendages could cause random supervisor storage overlays when presented with certain XDAP channel programs. An obvious circumvention, for pre-SVS systems as IBM did not guarantee system security and data integrity on these systems, was to utilize only those XDAP channel programs which did not also utilize RPS as the RPS-type XDAP channel programs were confusing the SAM and PAM appendages, thereby leading to the supervisor storage overlays.