Browse Prior Art Database

Use of Displaywrite 3 Disk I/O Services From DOS ".EXE" Program Files

IP.com Disclosure Number: IPCOM000060510D
Original Publication Date: 1986-Apr-01
Included in the Prior Art Database: 2005-Mar-08
Document File: 1 page(s) / 11K

Publishing Venue

IBM

Related People

Dolifka, CS: AUTHOR [+3]

Abstract

A method is described to allow DOS ".EXE" program files used by DisplayWrite 3* to use DisplayWrite 3 common services to perform disk I/O. In accordance with the method, a DisplayWrite 3 interface CSECT is provided so that the .EXE program can invoke in order to perform disk I/O. The linkage to disk I/O services may change from time to time, and the .EXE file would have to be changed accordingly if it directly interfaced with the disk I/O services. But these changes are transparent to a CSECT, since it only needs to be reassembled. The linkage to the interface CSECT mentioned above will remain static, while accommodating changes in linkage to disk I/O services. Thus, the .EXE program file will not have to be modified every time a disk I/O service linkage change occurs.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Use of Displaywrite 3 Disk I/O Services From DOS ".EXE" Program Files

A method is described to allow DOS ".EXE" program files used by DisplayWrite 3* to use DisplayWrite 3 common services to perform disk I/O. In accordance with the method, a DisplayWrite 3 interface CSECT is provided so that the .EXE program can invoke in order to perform disk I/O. The linkage to disk I/O services may change from time to time, and the .EXE file would have to be changed accordingly if it directly interfaced with the disk I/O services. But these changes are transparent to a CSECT, since it only needs to be reassembled. The linkage to the interface CSECT mentioned above will remain static, while accommodating changes in linkage to disk I/O services. Thus, the .EXE program file will not have to be modified every time a disk I/O service linkage change occurs. This makes it more feasible to user I/O services from the .EXE programs. By using DisplayWrite 3 disk I/O services from the DisplayWrite 3- invoked .EXE program files, the media and RAM requirements are reduced, since the .EXE programs do not need to include their own disk I/O services. * Trademark of IBM Corporation.

1