Browse Prior Art Database

Remote System Console Without a Remote Emulator Program

IP.com Disclosure Number: IPCOM000121751D
Original Publication Date: 1991-Sep-01
Included in the Prior Art Database: 2005-Apr-03
Document File: 4 page(s) / 137K

Publishing Venue

IBM

Related People

Dangler, MK: AUTHOR [+3]

Abstract

Programming methods are disclosed which provide system console users the capability to access a host processor session on a remotely attached personal computer (Remote Console) without use of an emulation program running on the Remote Console. A locally attached personal computer (Processor Console) communicates with a host session and the Remote Console via interfaces with the Systems Application Architecture* Communications Manager (CM) to provide this capability.

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

Remote System Console Without a Remote Emulator Program

      Programming methods are disclosed which provide system
console users the capability to access a host processor session on a
remotely attached personal computer (Remote Console) without use of
an emulation program running on the Remote Console.  A locally
attached personal computer (Processor Console) communicates with a
host session and the Remote Console via interfaces with the Systems
Application Architecture* Communications Manager (CM) to provide this
capability.

      Processor Console programming retrieves host session screen
data from the host session via CM EHLLAPI functions or similar
interfaces.  The host session screen data is then sent to the Remote
Console via CM APPC functions or similar interfaces.

      Processor Console programming receives user keyboard input from
the Remote Console via APPC functions or similar interfaces.  The
keyboard input is then sent to the host session via EHLLAPI functions
or similar interfaces.

      Processor Console programming consists of three concurrently
running threads to accomplish the above tasks. Host session screen
and keyboard input data are shared between the threads using global
data areas.  Semaphores are used to synchronize access to the global
data areas and signal new data is available.
The three Processor Console threads perform the following:
      HOST_CONNECT
      HOST_CONNECT starts the SCREEN_LOCAL and KEYBOARD_LOCAL
      threads.
      HOST_CONNECT initializes semaphores used for data
      access synchronization between HOST_CONNECT and the
      SCREEN_LOCAL and KEYBOARD_LOCAL.
      HOST_CONNECT loops until it receives an indication that
      execution should be terminated.  In the loop,
      HOST_CONNECT waits on the following semaphores:
      -    Host Notification Semaphore - Cleared when a host
      screen update occurs.
      -    Keyboard Received Semaphore - Cleared by
      KEYBOARD_LOCAL
      when a keyboard input has been received.

      If the Host Notification Semaphore is cleared, HOST_CONNECT
retrieves host session screen data from the host session and clears
the Screen Send Semaphore to inform SCREEN_LOCAL that host session
screen data is available for transmission to the Remote Console.

      If the Keyboard Received Semaphore is cleared, HOST_CONNECT
sends the keyboard input data received by KEYBOARD_LOCAL to the host
session and resets the Keyboard Received Semaphore.
SCREEN_LOCAL
      SCREEN_LOCAL starts an APPC conversation to the Remote Console
thread SCREEN_REMOTE.  This APPC conversation is used to send host
session screen data to SCREEN_REMOTE.
      SCREEN_LOCAL loops until it receives an indication that
execution should be terminated.  In the loop, SCREEN_LOCAL waits on
the following semaphore:
      -    Screen Send Semaphore - Cleared by HOST_CONN...