Browse Prior Art Database

Rollout Invoke and Manage

IP.com Disclosure Number: IPCOM000108027D
Original Publication Date: 1992-Jan-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 49K

Publishing Venue

IBM

Related People

Horng, J: AUTHOR

Abstract

This article addresses the insufficient memory problem encountered in running DOSDC which requires to execute DisplayWrite* 4 (DW4) functions through GCI (Generalized Callable Interface) call. The solution is to free up sufficient memory by rolling out DOSDC memory space to disk, possibly rolling out part of DMPC(EZ-VIEW) memory space also before DOSDC invokes DW4 with the GCI call. Upon completion, DW4 terminates and RIM restores DOSDC memory space from disk. RIM then returns the results and control to DOSDC.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 69% of the total text.

Rollout Invoke and Manage

       This article addresses the insufficient memory problem
encountered in running DOSDC which requires to execute DisplayWrite*
4 (DW4) functions through GCI (Generalized Callable Interface) call.
The solution is to free up sufficient memory by rolling out DOSDC
memory space to disk, possibly rolling out part of DMPC(EZ-VIEW)
memory space also before DOSDC invokes DW4 with the GCI call. Upon
completion, DW4 terminates and RIM restores DOSDC memory space from
disk. RIM then returns the results and control to DOSDC.

      The advantage of this scheme is to allow DOSDC to control both
its own and DMPC memory space. No modification was required to DMPC
and little was required to DOSDC.

      Below is an example under this scheme:
   1.  Load DOS, Emulation program, RIM, DMPC and run DOSDC. The
communication vehicle between RIM and DOSDC is via the interrupt
vector 7F.  The RIM is a TSR (Terminate and Stay Resident) program;
it hooks itself to interrupt vector 7F when it is loaded so that it
can communicate with the DOSDC.
   2.  DOSDC invokes RIM with a CREATE request. RIM supports several
requests, such as CREATE, REVISE, PRINT, VIEW, MAIN and TERMINATE.
   3.  RIM determines whether or not currently available memory is
sufficient to execute DW4.  If not, RIM saves the current process
(which is DOSDC) and writes DOSDC memory space and possible DMPC
memory space to disk. Then RIM makes itself the current process. Both
GET a...