Content deleted Content added
Peterh5322 (talk | contribs) |
Citation bot (talk | contribs) Alter: title. | Use this bot. Report bugs. | Suggested by AManWithNoPlan | Linked from User:AManWithNoPlan/sandbox4 | #UCB_webform_linked 1210/1831 |
||
(One intermediate revision by one other user not shown) | |||
Line 1:
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.<ref>{{cite manual|publisher=IBM|title=IBM System/360 Operating System
==Existing blocks==
Line 17:
==IOBSPSVC flag for XDAP and SAM and PAM coexistence==
The IOBSPSVC flag (logically, the '''IOB''''s '''S'''AM and '''P'''AM '''SVC''' flag) is available, and which causes Sequential Access Methods appendages<ref>{{cite manual|publisher=IBM|title=IBM System/360 Operating System Sequential Access Methods Program Logic Manual|id=Y28-6604-1|date=January 1967|url=http://www.bitsavers.org/pdf/ibm/360/os/plm_1966-67/Y28-6604-1_Sequential_Access_Methods_PLM_Jan67.pdf}}</ref> 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 pre-SVS SAM and PAM appendages could cause random supervisor storage overlays when presented with certain XDAP channel programs. ==References==
|