Browse Prior Art Database

Mechanism to Spawn a Shared Application On an OS/2 Network Server while Running in a Windows Environment

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

Publishing Venue

IBM

Related People

Cheok, CK: AUTHOR [+3]

Abstract

A mechanism is discussed which has the ability to spawn multiple shared applications in a Windows environment and at the same time has the ability to monitor and maintain the specific individual shared applications resource connections as well as their timely termination or exit.

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

Mechanism to Spawn a Shared Application On an OS/2 Network Server while Running in a Windows Environment

       A mechanism is discussed which has the ability to spawn
multiple shared applications in a Windows environment and at the same
time has the ability to monitor and maintain the specific individual
shared applications resource connections as well as their timely
termination or exit.

      In the implementation of the current existing full-screen
interface of the DOS LAN Requester, only one application can be
spawned or executed at a time with connections being made and other
necessary routines being run before spawning the application.
However, in Windows environment, multitasking capabilities come into
the picture and this requires the function to not only do the
necessary connections and spawning of the application, but also to
keep track of the connections made and all the shared applications
that are currently running.  If the functions of monitoring and
maintaining are not provided, there would be redundant resources
connected and the clean up and disconnection of resources after a
shared application termination would not be executed.  This would
leave behind a list of resource connections active after all shared
applications have been terminated.

      The core design principle is an invisible Windows application
named RUNLSAPP.EXE which:
      1. Runs in the background of Windows.
      2. Makes the necessary connections to aliases/f...